hammadtq

<p><strong>OpenBotAuth</strong> 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.</p>
<p>Instead of blocking all bots or allowing unrestricted access, you can:</p>
<ul>
<li><strong>See AI bot traffic</strong> – Local-only analytics showing which bots are crawling your site</li>
<li><strong>Verify bot identity</strong> using cryptographic signatures (RFC 9421)</li>
<li><strong>Show teasers</strong> to unverified bots (first N words)</li>
<li><strong>Rate limit</strong> bot access per agent</li>
<li><strong>Whitelist/blacklist</strong> specific bots</li>
</ul>
<h4>Key Features</h4>
<ul>
<li><strong>Bot Traffic Analytics</strong> – See which AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) are visiting your site</li>
<li><strong>Signature Verification</strong> – Verifies RFC 9421 HTTP Message Signatures using Ed25519 cryptography</li>
<li><strong>Content Teasers</strong> – Show first N words to unverified bots with customizable per-post settings</li>
<li><strong>Rate Limiting</strong> – Per-agent rate limits with configurable time windows</li>
<li><strong>Access Control</strong> – Whitelist/blacklist with wildcard pattern matching</li>
<li><strong>Local Analytics</strong> – Visual dashboard with charts, stats cards, and decision breakdowns (no external tracking)</li>
<li><strong>AI-Ready Endpoints</strong> – Serve llms.txt, JSON feed, and markdown for AI crawlers</li>
<li><strong>Tabbed Admin Interface</strong> – Clean organization with Analytics, AI Endpoints, and Configuration tabs</li>
</ul>
<h4>AI-Ready Endpoints</h4>
<p>OpenBotAuth provides machine-readable endpoints for AI systems:</p>
<ul>
<li><strong>/llms.txt</strong> – Standardized AI feed discovery (also at /.well-known/llms.txt)</li>
<li><strong>/.well-known/openbotauth-feed.json</strong> – JSON list of all published posts</li>
<li><strong>/.well-known/openbotauth/posts/{ID}.md</strong> – Per-post markdown content</li>
</ul>
<p>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.</p>
<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>
<p><strong>This plugin connects to an external verifier service.</strong> When a signed bot request is received, the plugin sends the following data to your configured verifier URL via <code>wp_remote_post</code>:</p>
<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>
<p><strong>Privacy protection:</strong> 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.</p>
<p><strong>No WordPress user accounts or personal data is transmitted.</strong> 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.</p>
<p>You can:<br />
* Use the hosted verifier at <code>https://verifier.openbotauth.org/verify</code><br />
* Self-host the verifier service (see documentation)<br />
* The verifier service may log requests server-side depending on your configuration</p>
<p><strong>Analytics are local-only.</strong> 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.</p>
<p>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>.</p>
<h3>Developer Hooks</h3>
<h4>Filters</h4>
<p><strong>openbotauth_policy</strong><br />
Modify policy before applying:</p>
<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>
<p><strong>openbotauth_verified</strong><br />
Triggered when a bot is verified:</p>
<pre><code>add_action('openbotauth_verified', function($agent, $post) {
    error_log("Bot {$agent['jwks_url']} accessed post {$post->ID}");
}, 10, 2);
</code></pre>
<p><strong>openbotauth_payment_required</strong><br />
Triggered when 402 is returned:</p>
<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>
<p><strong>openbotauth_should_serve_llms_txt</strong><br />
Disable llms.txt endpoint (e.g., when using Yoast):</p>
<pre><code>add_filter('openbotauth_should_serve_llms_txt', '__return_false');
</code></pre>
<p><strong>openbotauth_should_serve_feed</strong><br />
Disable JSON feed endpoint:</p>
<pre><code>add_filter('openbotauth_should_serve_feed', '__return_false');
</code></pre>
<p><strong>openbotauth_should_serve_markdown</strong><br />
Disable markdown endpoints:</p>
<pre><code>add_filter('openbotauth_should_serve_markdown', '__return_false');
</code></pre>
<p><strong>openbotauth_feed_item</strong><br />
Modify feed items:</p>
<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>
<p><strong>openbotauth_markdown_content</strong><br />
Post-process markdown output:</p>
<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.

ProAI

<p>ProAI TXT Manager for LLMS and Robots is a powerful WordPress plugin that automatically generates and maintains essential txt files for your website:</p>
<ul>
<li><strong>llms.txt</strong> – Provides structured information for AI language models about your site’s content, navigation, and structure</li>
<li><strong>robots.txt</strong> – Controls search engine crawler access and includes sitemap references</li>
</ul>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic Generation</strong>: Creates both llms.txt and robots.txt files automatically</li>
<li><strong>AI-Optimized Content</strong>: Structures llms.txt content specifically for AI language models</li>
<li><strong>Auto-Regeneration</strong>: Updates files automatically when your content changes</li>
<li><strong>Custom Content</strong>: Add your own custom information to both files</li>
<li><strong>SEO Integration</strong>: Automatically detects and includes sitemaps from popular SEO plugins</li>
<li><strong>WordPress Standards</strong>: Follows WordPress security and coding standards</li>
<li><strong>Easy Management</strong>: Simple admin interface for all settings</li>
</ul>
<h4>What is llms.txt?</h4>
<p>The llms.txt file is a structured text file that provides AI language models with essential information about your website, including:</p>
<ul>
<li>Site information and description</li>
<li>Navigation structure</li>
<li>Recent content and categories</li>
<li>Contact information</li>
<li>Custom information you want AI models to know</li>
</ul>
<h4>What’s Included in Robots.txt</h4>
<ul>
<li>WordPress security best practices</li>
<li>Automatic sitemap detection (Yoast, RankMath, WordPress core)</li>
<li>Common WordPress disallow rules</li>
<li>Custom rules you specify</li>
<li>Crawl delay settings</li>
</ul>
<h4>Perfect For</h4>
<ul>
<li>Website owners who want to be AI-friendly</li>
<li>SEO professionals managing multiple sites</li>
<li>Developers building modern WordPress sites</li>
<li>Anyone wanting automated TXT file management</li>
</ul>
<h3>Technical Details</h3>
<h4>File Serving</h4>
<p>The plugin serves files virtually, meaning they don’t actually exist as physical files in your root directory unless you specifically choose to generate them. This prevents clutter and ensures the files are always up-to-date.</p>
<h4>Performance</h4>
<p>The plugin is designed to be lightweight and efficient. File generation only occurs when content changes, and the files are cached for optimal performance.</p>
<h4>Security</h4>
<p>The robots.txt generation follows WordPress security best practices, including:<br />
* Disallowing access to wp-admin (except admin-ajax.php)<br />
* Disallowing access to wp-includes<br />
* Disallowing access to plugin and theme directories<br />
* Preventing access to WordPress system files</p>
<h4>Compatibility</h4>
<ul>
<li>Works with all major SEO plugins</li>
<li>Compatible with multisite installations</li>
<li>Supports custom post types and taxonomies</li>
<li>Works with custom menu structures</li>
</ul>


ProAI TXT Manager for LLMS and Robots

Automatically generates and manages llms.txt and robots.txt files for your WordPress site with AI-optimized content.

OpenBotAuth – AI Crawler Access Control vs ProAI TXT Manager for LLMS and Robots