gregrandall

AI agents, LLMs, and crawlers have to wade through navigation bars, sidebars, ads, and comment forms to reach the content they want, and every element costs tokens. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Botkibble adds a Markdown endpoint to every published post and page.
Cloudflare offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge on Pro, Business, and Enterprise plans. Botkibble does the same thing (for free) at the origin, so it works on any host.
<a href="https://github.com/greg-randall/botkibble" rel="nofollow ugc">GitHub Repository</a>
Three ways to request Markdown:
<ul>
<li><code>.md</code> suffix: append <code>.md</code> to any post or page URL (e.g. <code>example.com/my-post.md</code>)</li>
<li>Query parameter: add <code>?format=markdown</code> to any post or page URL</li>
<li>Content negotiation: send <code>Accept: text/markdown</code> in the request header</li>
</ul>
What’s in every response:
<ul>
<li>Structured metadata header with title, date, categories, tags, word count, character count, and estimated token count (in YAML frontmatter format, readable by any AI agent)</li>
<li>Clean Markdown converted from fully-rendered post HTML (shortcodes run, filters applied)</li>
<li><code>Content-Type: text/markdown</code> and <code>Vary: Accept</code> response headers</li>
<li><code>Content-Signal</code> header for AI signal declaration — defaults to <code>ai-train=no, search=yes, ai-input=yes</code> — see <a href="https://contentsignals.org/" rel="nofollow ugc">contentsignals.org</a></li>
<li><code>X-Markdown-Tokens</code> header with estimated token count</li>
<li>Discovery via <code><link rel="alternate"></code> in the HTML head and <code>Link</code> HTTP header</li>
<li>Automatic cache invalidation when a post is updated or deleted</li>
</ul>
Performance:
Botkibble writes Markdown to disk on the first request, then serves it as a static file. A built-in Fast-Path serves cached files during WordPress’s <code>init</code> hook, before the main database query runs. No extra configuration needed.
Add a web server rewrite rule and Botkibble bypasses PHP entirely, serving <code>.md</code> files the same way a server would serve an image or CSS file:
 Method 
 Avg. response time
 Standard HTML 
 0.97s
 Markdown (cold, first request) 
 0.95s
 Markdown (cached, PHP Fast-Path) 
 0.87s
 Markdown (Nginx/Apache direct) 
 0.11s
Serving directly from disk is 88% faster than a full WordPress page load. See the Performance section below for Nginx and Apache configuration.
Security:
<ul>
<li>Drafts, private posts, and password-protected content return <code>403 Forbidden</code></li>
<li>Rate limits cache-miss regenerations (20/min by default) to mitigate DoS abuse</li>
<li><code>X-Robots-Tag: noindex</code> keeps Markdown versions out of search results</li>
<li><code>Link: rel="canonical"</code> points search engines back to the HTML version</li>
</ul>
Cache variants (optional):
You can persist alternate cached representations by adding <code>?botkibble_variant=slim</code> (or any other variant name). 
Variant caches are stored under:
<pre><code>/wp-content/uploads/botkibble/_v/<variant>/<slug>.md
</code></pre>
What it does NOT do:
<ul>
<li>Expose drafts, private posts, or password-protected content</li>
<li>Serve non-post/page content types by default</li>
<li>Require any configuration. Activate and it works.</li>
</ul>
<h3>Why Markdown?</h3>
HTML is expensive for AI systems to process. <a href="https://blog.cloudflare.com/markdown-for-agents/" rel="nofollow ugc">Cloudflare measured</a> an 80% reduction in token usage when converting a blog post from HTML to Markdown (16,180 tokens down to 3,150).
Cloudflare now offers <a href="https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/" rel="nofollow ugc">Markdown for Agents</a> at the CDN edge via the <code>Accept: text/markdown</code> header, available on Pro, Business, and Enterprise plans.
This plugin does the same thing at the origin, so it works on any host. It also adds <code>.md</code> suffix URLs, <code>?format=markdown</code> query parameters, YAML frontmatter, static file caching, and server-level offloading.
If you use Cloudflare, both share the same <code>Accept: text/markdown</code> header, <code>Content-Signal</code> headers, and <code>X-Markdown-Tokens</code> response headers.
Cloudflare currently defaults to <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code> with no way to change it. Botkibble defaults to <code>ai-train=no</code> and lets you override the full signal per site via the <code>botkibble_content_signal</code> filter.
<h3>Performance & Static Offloading</h3>
This plugin supports static file offloading by writing Markdown content to <code>/wp-content/uploads/botkibble/</code>.
<h3>Nginx Configuration</h3>
To bypass PHP entirely and have Nginx serve the files (including variants) directly:
<pre><code># Variants
location ~* ^/(_v/[^/]+/.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}

# Default
location ~* ^/(.+)\.md$ {
 default_type text/markdown;
 try_files /wp-content/uploads/botkibble/$1.md /index.php?$args;
}
</code></pre>
<h3>Apache (.htaccess)</h3>
Add this to your <code>.htaccess</code> before the WordPress rules:
<pre><code>RewriteEngine On
# Variants
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/_v/$1/$2.md -f
RewriteRule ^_v/([^/]+)/(.+)\.md$ /wp-content/uploads/botkibble/_v/$1/$2.md [L,T=text/markdown]

# Default
RewriteCond %{DOCUMENT_ROOT}/wp-content/uploads/botkibble/$1.md -f
RewriteRule ^(.*)\.md$ /wp-content/uploads/botkibble/$1.md [L,T=text/markdown]
</code></pre>
Even without these rules, the plugin uses a “Fast-Path” that serves cached files from PHP before the main database query is executed.
<h3>Credits</h3>
We thank Cristi Constantin (https://github.com/cristi-constantin) for contributing cache variants, URL and SEO improvements, and fixing important bugs.

Botkibble

Serves every published post and page as Markdown for AI agents and crawlers. No configuration, no API keys. Activate and it works.

Marat Nepomnyashy

Overview:
At the time of this writing, the latest version of WordPress, version 4.7, 
 has functionality to discourage search engines from indexing the whole site, 
 but not functionality to discourage search engines from indexing only certain 
 specific pages and posts of the site.
Robots Meta Whiz is a WordPress plugin that allows site administrators to 
 deploy custom meta robots tags to discourage search engines from indexing, 
 following links from, caching, indexing images from, and / or have 
 additional custom restrictions on only for certain specifically-designated 
 pages and posts.
It is an easy way to discourage search engines from indexing only specific 
 pages / posts.
This only applies to search engine robots, and will not effect the site’s 
 local search functionality.
Technical summary:
Plugin works by hooking-in special logic into the action ‘wp_head’ to inject 
 the tag <code><meta name='robots' content='...'></code> with restriction directives for 
 the specified pages and posts.
Official project URLs:
https://wordpress.org/plugins/robotswhiz 
 https://github.com/maratbn/RobotsWhiz

Robots Meta Whiz

Easy way to discourage search engines from indexing only specific pages / posts with custom meta tags.

Botkibble vs Robots Meta Whiz