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.

markdownmirror

<p>🚀 <strong>Markdown Mirror</strong> instantly serves Markdown versions of every WordPress post, page, and the homepage—no pre-generation, zero settings, pure speed.</p>
<h3>What it does</h3>
<ul>
<li>⚡ <strong>On-demand export</strong><br />
Just append <code>.md</code> to any public URL (e.g., <code>/hello-world.md</code>) to download the Markdown file.</li>
<li>📑 <strong><code>llms.txt</code> generator</strong><br />
  /llms.txt always lists the freshest links to every Markdown mirror.</li>
<li>🗂️ <strong>Homepage & index</strong><br />
  /index.md gives you a Markdown snapshot of the front page.</li>
<li>🛠️ <strong>Theme-agnostic</strong><br />
Compatible with all themes.</li>
<li>🧹 <strong>Zero clutter</strong><br />
Writes no options, adds no tables; mirrors are generated on the fly.</li>
</ul>
<h3>Why you’ll love it</h3>
<ul>
<li>🕵️ <strong>AI-ready SEO</strong> – Serve clean, semantic text to LLM crawlers.  </li>
<li>📚 <strong>Docs & backups</strong> – Keep human-readable copies of everything.  </li>
<li>💻 <strong>Dev-friendly</strong> – Ideal for static-site workflows and Git versioning.</li>
</ul>
<h3>Quick start</h3>
<ol>
<li>Install & activate Markdown Mirror.  </li>
<li>Visit any post or page with <code>.md</code> at the end to fetch its Markdown.  </li>
<li>Check <code>/llms.txt</code> for the full index and <code>/index.md</code> for the homepage mirror.</li>
</ol>
<p>Enjoy effortless, always-up-to-date Markdown mirrors. ✨</p>
<h3>Features</h3>
<ul>
<li>Dynamic <code>.md</code> endpoints  </li>
<li><code>llms.txt</code> with sitemap-based index  </li>
<li>Admin toggle in Dashboard <span aria-hidden="true" class="wp-exclude-emoji">→</span> Markdown Mirror  </li>
<li>No extra database tables</li>
</ul>
<h3>Support</h3>
<ul>
<li>No support available</li>
</ul>
<h3>Usage</h3>
<ul>
<li>Browse <code>/index.md</code> for homepage Markdown.  </li>
<li>Browse <code>/{post-slug}.md</code> for any post/page.  </li>
<li>Visit <code>/llms.txt</code> for LLM-friendly site index.</li>
</ul>
<h3>License</h3>
<p>GPLv2 or later</p>


Markdown Mirror – llms.txt and .md always up to date


I couldn't find any llms.txt plugin that would also generate the Markdown (.md) copies of all my pages. Markdown Mirror does it wonderfully and on the fly. When I create or update a page all the content is automatically updated.


The only llms.txt that generates markdown files

Generate an llms.txt map and dynamic Markdown (.md) versions of every page of your site to improve your AI SEO and facilitate LLMs indexing.

OpenBotAuth – AI Crawler Access Control vs Markdown Mirror – llms.txt and .md always up to date