=== AI Crawler Guard ===
Contributors: serverlessgeeks.com, myselfamar
Requires at least: 6.0
Tested up to: 6.9
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Tags: ai, crawler, bot, security

Detect and control AI crawler access with local logging and history.

== Description ==
AI Crawler Guard detects popular AI-focused crawlers and lets you block or allow them from scraping your WordPress site. Everything runs locally—rules, decisions, logs, and history stay on your server.

* Built-in signatures for common AI bots, plus optional custom patterns
* Global and per-crawler allow/block controls
* Local crawler registry with first/last seen timestamps and hit counters
* Lightweight logs with optional retention cap
* No external calls or remote storage

== Requirements ==
* WordPress 5.8 or newer
* PHP 7.4+
* Works with Classic Editor, Gutenberg, WooCommerce, and major managed hosts
* Respects wp-admin, wp-login, REST API, cron, and CLI contexts automatically

== Installation ==
1. Upload `ai-crawler-guard` to `/wp-content/plugins/`.
2. Activate the plugin through the “Plugins” screen in WordPress.
3. Visit “AI Crawler Guard → Settings” to choose your preferred block mode and logging options.

== Performance ==
* Detection runs once per front-end request (small O(n) UA scan)
* No blocking of social preview bots (Facebook, Meta, Twitter, LinkedIn) by default
* Assets load only on plugin admin pages and stay under 10 KB
* Logs stay capped by your configured limit with auto-pruning

== Privacy ==
All detection logic and data storage live entirely inside WordPress. No data is sent to third-party services in v1.

== Frequently Asked Questions ==
= Does it block paywall bypassing via HTTP 402? =
Not yet. Payment/402 responses are planned for a future release.

= Can it fetch remote rule updates? =
Remote updates are scheduled for v1.1+. v1 ships with local rules only.

== Changelog ==
= 1.0.0 =
* Initial release.