llmscentral

LLMS Central Bot Tracker helps you understand which AI systems are visiting your website and gives you control over how AI companies use your content.
<h4>Features</h4>
<ul>
<li>Track 16+ AI Bots – Monitor visits from GPTBot, Claude, Gemini, Perplexity, and more</li>
<li>Real-time Analytics – See which AI bots are crawling your site and when</li>
<li>llms.txt Management – Create and manage your llms.txt file (the “robots.txt for AI”)</li>
<li>Privacy-Focused – Only tracks bot user-agents, no personal data collected</li>
<li>Dashboard Widget – View AI bot activity right in your WordPress dashboard</li>
<li>Easy Setup – One-click installation, no coding required</li>
</ul>
<h4>What is llms.txt?</h4>
llms.txt is like robots.txt, but for AI systems. It tells AI companies how they can use your content for training their models. With this plugin, you can:
<ul>
<li>Allow or restrict AI training on your content</li>
<li>Require attribution when AI uses your content</li>
<li>Set commercial use policies</li>
<li>Provide contact information for AI companies</li>
</ul>
<h4>Tracked AI Bots</h4>
<ul>
<li>GPTBot (OpenAI)</li>
<li>ChatGPT-User (OpenAI)</li>
<li>Claude-Web (Anthropic)</li>
<li>Google-Extended (Google)</li>
<li>Perplexity Bot</li>
<li>Bytespider (ByteDance)</li>
<li>Cohere AI</li>
<li>FacebookBot (Meta)</li>
<li>Amazonbot</li>
<li>And 8+ more AI crawlers</li>
</ul>
<h4>Privacy & Data Collection</h4>
This plugin is designed with privacy in mind:
Data Collection is OPT-IN ONLY: 
No data is sent to external servers unless you explicitly enable tracking and provide consent in the plugin settings.
When Tracking is Enabled (with your consent): 
* Bot user-agent strings 
* Page URLs visited by bots 
* Timestamp of visits 
* Your domain name
Data NOT Collected: 
* Visitor IP addresses 
* Personal information 
* Cookies or tracking identifiers 
* Form submissions 
* Human visitor data
You can disable tracking at any time, and no data will be transmitted without your explicit permission.
<h4>Use Cases</h4>
<ul>
<li>Content Creators – Know which AI systems are using your content</li>
<li>Publishers – Monitor AI bot traffic and set training policies</li>
<li>Developers – Track AI crawler behavior on your site</li>
<li>SEO Professionals – Understand AI bot impact on your site</li>
<li>Business Owners – Control how AI companies use your content</li>
</ul>
<h3>Privacy Policy</h3>
This plugin sends data to LLMS Central servers (https://llmscentral.com) for analytics purposes.
Data Sent: 
* Bot user-agent strings 
* Page URLs visited by bots 
* Timestamp of visits 
* Your domain name
Data NOT Sent: 
* Visitor IP addresses 
* Personal information 
* Cookies or tracking identifiers 
* Form submissions 
* Human visitor data
You must explicitly consent to this data collection by checking the consent box in the plugin settings. You can revoke consent at any time by disabling the plugin.
For full details, see our <a href="https://llmscentral.com/privacy" rel="nofollow ugc">Privacy Policy</a> and <a href="https://llmscentral.com/terms" rel="nofollow ugc">Terms of Service</a>.
<h3>External Services</h3>
This plugin connects to the following external service:
LLMS Central API (https://llmscentral.com) 
* Purpose: Send AI bot tracking data and retrieve analytics (OPT-IN ONLY) 
* Privacy Policy: https://llmscentral.com/privacy 
* Terms of Service: https://llmscentral.com/terms 
* Data Transmission: Only when tracking is explicitly enabled by the user
This plugin does NOT send any data to external servers by default. Connection to LLMS Central servers only occurs when you: 
1. Enable the “Bot Tracking” feature in settings 
2. Accept the privacy policy and provide explicit consent 
3. Check the consent checkbox
Without your explicit consent, the plugin operates entirely locally on your WordPress site.
<h3>Support</h3>
For support, please visit:
<ul>
<li><a href="https://llmscentral.com/wordpress-plugin" rel="nofollow ugc">Plugin Documentation</a></li>
<li><a href="https://wordpress.org/support/plugin/llms-central-ai-bot-tracker/" rel="ugc">Support Forum</a></li>
<li><a href="https://llmscentral.com/dashboard" rel="nofollow ugc">LLMS Central Dashboard</a> (requires free account)</li>
<li><a href="https://llmscentral.com/getting-started" rel="nofollow ugc">Getting Started Guide</a></li>
</ul>
Before requesting support, please: 
1. Check the FAQ section above in this readme 
2. Ensure you’re using the latest version 
3. Review the plugin settings in WordPress admin 
4. Check the WordPress debug log for errors 
5. Visit the WordPress.org support forum for community help
<h3>Credits</h3>
Developed by the LLMS Central team. Visit <a href="https://llmscentral.com" rel="nofollow ugc">llmscentral.com</a> to learn more about AI training policies and llms.txt files.

LLMS Central – AI Bot Tracker

Track AI bots (GPT, Claude, Gemini) visiting your site and manage your llms.txt file. See which AI systems are crawling your content.

hammadtq

OpenBotAuth helps publishers control automated access from AI crawlers and agents. It verifies requests using RFC 9421 HTTP Message Signatures (via a configurable verifier) and applies per-site or per-post policies like allow, deny, teaser previews, and 402 payment-required responses. It also publishes AI-friendly endpoints like llms.txt, a JSON feed, and per-post Markdown.
Instead of blocking all bots or allowing unrestricted access, you can:
<ul>
<li>See AI bot traffic – Local-only analytics showing which bots are crawling your site</li>
<li>Verify bot identity using cryptographic signatures (RFC 9421)</li>
<li>Show teasers to unverified bots (first N words)</li>
<li>Rate limit bot access per agent</li>
<li>Whitelist/blacklist specific bots</li>
</ul>
<h4>Key Features</h4>
<ul>
<li>Bot Traffic Analytics – See which AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) are visiting your site</li>
<li>Signature Verification – Verifies RFC 9421 HTTP Message Signatures using Ed25519 cryptography</li>
<li>Content Teasers – Show first N words to unverified bots with customizable per-post settings</li>
<li>Rate Limiting – Per-agent rate limits with configurable time windows</li>
<li>Access Control – Whitelist/blacklist with wildcard pattern matching</li>
<li>Local Analytics – Visual dashboard with charts, stats cards, and decision breakdowns (no external tracking)</li>
<li>AI-Ready Endpoints – Serve llms.txt, JSON feed, and markdown for AI crawlers</li>
<li>Tabbed Admin Interface – Clean organization with Analytics, AI Endpoints, and Configuration tabs</li>
</ul>
<h4>AI-Ready Endpoints</h4>
OpenBotAuth provides machine-readable endpoints for AI systems:
<ul>
<li>/llms.txt – Standardized AI feed discovery (also at /.well-known/llms.txt)</li>
<li>/.well-known/openbotauth-feed.json – JSON list of all published posts</li>
<li>/.well-known/openbotauth/posts/{ID}.md – Per-post markdown content</li>
</ul>
Configure which post types to include (posts, pages, or custom types) and set the feed limit (up to 500 items). All data is served locally from your WordPress database. No external tracking or telemetry. Only published, non-password-protected posts are exposed.
<h4>How It Works</h4>
<ol>
<li>AI agent signs HTTP request with its private key (RFC 9421 signature)</li>
<li>WordPress plugin extracts signature headers and sends them to a verifier service</li>
<li>Verifier fetches agent’s public key from registry and verifies signature</li>
<li>Plugin applies policy: allow full content, show teaser, require payment, or deny</li>
</ol>
<h4>External Service Disclosure</h4>
This plugin connects to an external verifier service. When a signed bot request is received, the plugin sends the following data to your configured verifier URL via <code>wp_remote_post</code>:
<ul>
<li>HTTP method (GET, POST, etc.)</li>
<li>The accessed URL (including query string, if present)</li>
<li>HTTP signature headers (Signature, Signature-Input, Signature-Agent)</li>
<li>Additional HTTP header values explicitly listed in the Signature-Input header (e.g., content-type, accept, user-agent)</li>
</ul>
Privacy protection: Sensitive headers (cookies, authorization, proxy-authorization, www-authenticate) are NEVER forwarded, even if present in the request. If a bot’s signature covers a sensitive header, verification will fail with a clear error.
No WordPress user accounts or personal data is transmitted. Only the headers explicitly covered by the bot’s signature are forwarded to enable cryptographic verification. Note that the URL may include query parameters depending on your site’s structure.
You can: 
* Use the hosted verifier at <code>https://verifier.openbotauth.org/verify</code> 
* Self-host the verifier service (see documentation) 
* The verifier service may log requests server-side depending on your configuration
Analytics are local-only. Decision counts (allow/teaser/deny/pay/rate_limit) and bot traffic observations (User-Agent based) are stored in your WordPress database. No analytics data is sent to external servers.
For more information, please review our <a href="https://openbotauth.org/terms" rel="nofollow ugc">Terms of Service</a> and <a href="https://openbotauth.org/privacy" rel="nofollow ugc">Privacy Policy</a>.
<h3>Developer Hooks</h3>
<h4>Filters</h4>
openbotauth_policy 
Modify policy before applying:
<pre><code>add_filter('openbotauth_policy', function($policy, $post) {
 if ($post->post_type === 'premium') {
 $policy['price_cents'] = 1000;
 }
 return $policy;
}, 10, 2);
</code></pre>
<h4>Actions</h4>
openbotauth_verified 
Triggered when a bot is verified:
<pre><code>add_action('openbotauth_verified', function($agent, $post) {
 error_log("Bot {$agent['jwks_url']} accessed post {$post->ID}");
}, 10, 2);
</code></pre>
openbotauth_payment_required 
Triggered when 402 is returned:
<pre><code>add_action('openbotauth_payment_required', function($agent, $post, $price) {
 // Track payment requests
}, 10, 3);
</code></pre>
<h4>AI Endpoint Filters (v0.1.2+)</h4>
openbotauth_should_serve_llms_txt 
Disable llms.txt endpoint (e.g., when using Yoast):
<pre><code>add_filter('openbotauth_should_serve_llms_txt', '__return_false');
</code></pre>
openbotauth_should_serve_feed 
Disable JSON feed endpoint:
<pre><code>add_filter('openbotauth_should_serve_feed', '__return_false');
</code></pre>
openbotauth_should_serve_markdown 
Disable markdown endpoints:
<pre><code>add_filter('openbotauth_should_serve_markdown', '__return_false');
</code></pre>
openbotauth_feed_item 
Modify feed items:
<pre><code>add_filter('openbotauth_feed_item', function($item, $post) {
 $item['custom_field'] = get_post_meta($post->ID, 'my_field', true);
 return $item;
}, 10, 2);
</code></pre>
openbotauth_markdown_content 
Post-process markdown output:
<pre><code>add_filter('openbotauth_markdown_content', function($markdown, $post) {
 return $markdown . "\n\n---\nCopyright notice here";
}, 10, 2);
</code></pre>

OpenBotAuth – AI Crawler Access Control

Verify AI crawlers with HTTP Signatures and enforce allow/deny/teaser policies; also serves llms.txt and AI-ready feeds.

LLMS Central – AI Bot Tracker vs OpenBotAuth – AI Crawler Access Control