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.

mohamed wazery

MW LLMS Index is a WordPress plugin that automatically generates AI-friendly index files for your website. It creates <code>llms.txt</code> (plain text) and <code>llms.json</code> (structured JSON) files inside <code>wp-content/uploads/mw-llm-index/</code>, making it easy for AI systems to discover and understand your content.
Key Features:
<ul>
<li>Automatic Index Generation: Automatically generates <code>llms.txt</code> and <code>llms.json</code> files with all your published posts and pages</li>
<li>SEO Plugin Integration: Seamlessly integrates with popular SEO plugins (Rank Math, Yoast SEO, All in One SEO) to use meta descriptions</li>
<li>Flexible Scheduling: Choose from daily, weekly, or manual regeneration schedules using WP Cron</li>
<li>AI Bot Logging: Optional logging of AI bot visits (GPTBot, ClaudeBot, PerplexityBot) to track when AI systems access your site</li>
<li>REST API Access: Access your index data programmatically via WordPress REST API</li>
<li>Auto-Generation: Automatically creates files on activation if they don’t exist</li>
<li>Clean Uninstall: Removes all generated files and settings when uninstalled</li>
</ul>
Technical Features:
<ul>
<li>✔ WP Cron Integration: Uses WordPress built-in cron system for scheduled updates</li>
<li>✔ Editor Compatibility: Works seamlessly with both Gutenberg and Classic Editor</li>
<li>✔ Zero Frontend Assets: No JavaScript or CSS files loaded on the frontend – lightweight and fast</li>
<li>✔ WordPress Standards: Follows WordPress coding standards and best practices</li>
<li>✔ Multisite Compatible: Works on single-site and multisite installations</li>
</ul>
What is llms.txt?
The <code>llms.txt</code> file is a standardized format for providing AI systems with a structured index of your website’s content. It helps AI models like ChatGPT, Claude, and Perplexity understand what content is available on your site and how to access it.
How It Works:
<ol>
<li>The plugin scans all published posts and pages on your WordPress site</li>
<li>Extracts titles, URLs, and descriptions (from SEO plugins when available)</li>
<li>Generates two files:
<ul>
<li><code>llms.txt</code> – Human-readable plain text format</li>
<li><code>llms.json</code> – Machine-readable JSON format for programmatic access</li>
</ul>
</li>
<li>Files are automatically updated based on your chosen schedule</li>
</ol>
Use Cases:
<ul>
<li>Help AI systems discover and index your content</li>
<li>Improve AI model understanding of your website structure</li>
<li>Provide structured content metadata for AI training</li>
<li>Track when AI bots visit your site</li>
<li>Export your content index for external use</li>
</ul>
Useful Links:
<ul>
<li><a href="https://github.com/mohamedwazery/mw-llms-index/wiki" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://github.com/mohamedwazery/mw-llms-index/issues" rel="nofollow ugc">Report Issues</a></li>
<li><a href="https://github.com/mohamedwazery/mw-llms-index" rel="nofollow ugc">GitHub Repository</a></li>
</ul>
<h3>External Services</h3>
This plugin does NOT connect to any external services or APIs. All data is: 
* Generated locally on your WordPress server 
* Stored in your uploads directory 
* Accessible only through your own domain 
* Not transmitted to third parties
The plugin is completely self-contained and operates entirely within your WordPress installation.
<h3>Support</h3>
For support, feature requests, or bug reports, please visit: 
* <a href="https://github.com/mohamedwazery/mw-llms-index/issues" rel="nofollow ugc">GitHub Issues</a> 
* <a href="https://wordpress.org/support/plugin/mw-llms-index/" rel="ugc">WordPress.org Support Forum</a>
<h3>Credits</h3>
Developed by Mohamed Khalil Wazery 
Website: https://wazery.net
<h3>Privacy</h3>
This plugin: 
* Does not collect any user data 
* Does not send data to external servers 
* Only generates files locally on your WordPress installation 
* Optionally logs AI bot visits locally (can be disabled) 
* Does not use cookies 
* Does not track users
The generated <code>llms.txt</code> and <code>llms.json</code> files are publicly accessible (located in <code>wp-content/uploads/mw-llm-index/</code>) and contain information about your published content, similar to what would be available in your sitemap.
<h3>Security Notes</h3>
Important Security Information:
This plugin does not expose private data and only outputs publicly available content, similar to a sitemap. The generated files contain: 
* Only published posts and pages (same visibility as your public website) 
* Titles, URLs, and meta descriptions (already publicly accessible) 
* No private user information 
* No sensitive data or credentials
The files are placed in <code>wp-content/uploads/mw-llms-index/</code> and are publicly accessible, but they only contain information that is already available on your public website. If you have concerns about specific content being indexed, ensure those posts/pages are set to private or draft status.

MW LLMS Index

Generate AI-friendly llms.txt and llms.json index files to help AI systems discover and understand your WordPress content.

OpenBotAuth – AI Crawler Access Control vs MW LLMS Index