Mescio

Mescio for Agents makes your WordPress site AI-ready by silently serving posts, pages and WooCommerce products as clean, structured Markdown to any AI agent or LLM pipeline that requests it — using the standard HTTP <code>Accept: text/markdown</code> content negotiation header.
Human visitors using a browser are completely unaffected. Mescio for Agents only activates when an AI agent or crawler explicitly asks for Markdown.
<h4>Why Markdown?</h4>
Feeding raw HTML to an AI is expensive and noisy. A heading like <code>## About Us</code> costs ~3 tokens in Markdown vs 12–15 tokens as HTML — before accounting for <code><div></code> wrappers, navigation bars and script tags that carry zero semantic value. This blog post you are reading takes 16,180 tokens in HTML and 3,150 tokens in Markdown. That is an 80% reduction.
Markdown has become the lingua franca for AI systems. Mescio for Agents lets your site speak it natively, at zero cost to your human visitors.
<h4>How it works</h4>
When an HTTP client sends a request with <code>Accept: text/markdown</code>, Mescio for Agents intercepts the WordPress request lifecycle before any template is rendered, converts the post content to clean Markdown, and returns it with the correct <code>Content-Type: text/markdown</code> header.
<pre><code>curl https://yoursite.com/your-post/ \
 -H "Accept: text/markdown"
</code></pre>
<h4>Features</h4>
<ul>
<li>Zero configuration — works out of the box on any singular post, page or custom post type</li>
<li><code>/llms.txt</code> endpoint — auto-generated index of all your content in the <a href="https://llmstxt.org" rel="nofollow ugc">llmstxt.org</a> standard format, so AI agents can discover what’s on your site</li>
<li><code>/llms-full.txt</code> endpoint — full site content in a single Markdown file, ready for RAG pipelines</li>
<li>WooCommerce support — product pages include price, SKU, stock status, rating, attributes and gallery; products are grouped by category in <code>llms.txt</code></li>
<li>YAML front matter — every document includes structured metadata (title, description, URL, date, categories, tags, featured image)</li>
<li>Multilingual — detects language via WPML, Polylang, TranslatePress or WordPress locale; emits <code>Content-Language</code> and <code>Link: rel=alternate</code> headers</li>
<li>REST API endpoint — <code>/wp-json/mescio-for-agents/v1/markdown?id=<post_id></code> or <code>?url=<permalink></code></li>
<li>Page builder cleanup — aggressively strips Elementor, Divi, WPBakery and Beaver Builder layout noise</li>
<li>Token count header — <code>X-Markdown-Tokens</code> tells AI pipelines how large the document is before processing</li>
<li>Content Signals — emits <code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code></li>
<li>Correct HTTP caching — <code>Vary: Accept</code> ensures CDNs cache HTML and Markdown versions separately</li>
</ul>
<h4>Response headers</h4>
<ul>
<li><code>Content-Type: text/markdown; charset=utf-8</code></li>
<li><code>Content-Language: it</code> (or detected language)</li>
<li><code>Vary: Accept</code></li>
<li><code>X-Markdown-Tokens: 725</code></li>
<li><code>Content-Signal: ai-train=yes, search=yes, ai-input=yes</code></li>
<li><code>Link: <url>; rel="alternate"; hreflang="en"</code> (when translations available)</li>
</ul>
<h4>Multilingual plugin support</h4>
<ul>
<li>WPML — reads language and available translations automatically</li>
<li>Polylang — reads language and links to translated post IDs</li>
<li>TranslatePress — reads <code>trp_language</code> post meta</li>
<li>Manual — configure primary language and additional languages in Settings → Mescio for Agents</li>
</ul>
<h4>REST API</h4>
<pre><code>GET /wp-json/mescio-for-agents/v1/markdown?id=42
GET /wp-json/mescio-for-agents/v1/markdown?url=https://yoursite.com/my-page/
</code></pre>
<h4>Developer hooks</h4>
Filter: <code>mescio_enabled_post_types</code> — add or remove post types dynamically.
Filter: <code>mescio_pre_convert_content</code> — modify the HTML before conversion to Markdown.
Filter: <code>mescio_post_convert_content</code> — modify the Markdown after conversion.
<h4>Privacy</h4>
This plugin does not collect, store or transmit any personal data. It does not set cookies. It does not make external HTTP requests.

Mescio for Agents


simple, plug and play, for any website; implemented on tens of sites and validated the setup with cloudflare's free isitagentready.com check for content, everything is in the green.


plug and play AI discoverability

Mescio for Agents serves your WordPress content as clean Markdown to AI agents and GPT crawlers. Human visitors never notice a thing.

chancerylaneproject

Markdown for Agents and Statistics converts your WordPress content to Markdown and serves it 
to AI agents and language model tools that request it via HTTP content negotiation 
(<code>Accept: text/markdown</code>).
The Chancery Lane Project is a charity that helps organisations reduce emissions using the power of legal documents and processes. We’ve published this plugin as we believe that making content more legible for AI Agents makes a meaningful difference to their energy usage – not only by reducing the amount of tokens required (by up to 90% over HTML) to consume the content, but also minimising the server resources required to render, process and display pages at source.
How it works:
<ol>
<li>Posts and taxonomy archive pages are converted to Markdown and saved as static 
files on disk inside <code>wp-content/uploads/</code>.</li>
<li>When a visitor (or AI agent) requests a page with <code>Accept: text/markdown</code> in 
the HTTP headers, WordPress serves the pre-generated <code>.md</code> file directly — 
no page render required.</li>
<li>A <code><link rel="alternate" type="text/markdown"></code> tag is added to each page’s 
 so agents can discover Markdown versions automatically.</li>
</ol>
Features:
<ul>
<li>Content negotiation (<code>Accept: text/markdown</code>, <code>?output_format=md</code>, or known AI User-Agents)</li>
<li>Taxonomy archive support — category, tag, and custom taxonomy term pages served as Markdown post listings</li>
<li>Automatic Markdown generation on post save; taxonomy archives auto-update when any post in the term changes</li>
<li>AJAX bulk generation with live progress counter — no page timeouts on large sites</li>
<li>Per-post-type field configuration — choose which meta/ACF fields go in frontmatter or body</li>
<li>ACF support with dot notation for nested group fields (e.g. <code>group.subfield</code>)</li>
<li>Content fields option — use ACF fields as the body content instead of post_content</li>
<li>Manifest generation with content hashes and change tracking per post type</li>
<li>Incremental export — only re-export changed documents (<code>--incremental</code>)</li>
<li>Delta file (<code>changes.json</code>) for RAG system sync</li>
<li>Access statistics — logs AI agent requests with a dedicated stats admin page</li>
<li>Optional frontmatter fields — hierarchy (parent/ancestors/children IDs), author display name, root-relative featured image paths</li>
<li>Topics section — appends a <code>## Topics</code> section with linked taxonomy terms to the Markdown body</li>
<li>Export preview — preview generated Markdown inline in the post editor without writing to disk</li>
<li>WP-CLI commands: <code>generate</code>, <code>generate-taxonomies</code>, <code>prune-stats</code>, <code>status</code>, <code>delete</code></li>
<li>Fully unit-tested</li>
</ul>

Markdown for Agents and Statistics

Serve pre-generated Markdown files to AI agents via HTTP content negotiation.

Mescio for Agents vs Markdown for Agents and Statistics