Markdown Twin Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Markdown Twin gives AI agents a clean Markdown version of every page, built from the page as it is actually rendered, whatever the theme or page builder: the content, without the menus, scripts, sliders and cookie banners an agent would otherwise spend its tokens on.
Each twin starts with a YAML front matter: title, description, canonical URL, language, dates, author, image, the same page in the other languages, the breadcrumb trail, the page’s whole schema.org JSON-LD as printed by your SEO plugin, your theme or WooCommerce (empty values left out, each node of a @graph on its own), and, for a product, the price as your shop displays it, currency, availability, SKU, attributes, variations and rating.
How agents get it
- .md URLs:
https://example.com/shop/has its twin athttps://example.com/shop.md, the home page at/index.md. - Content negotiation: the normal URL answers in Markdown when the client prefers
text/markdownin itsAcceptheader. Browsers never do, so visitors always get the HTML page. - Discovery: every HTML page announces its twin with
<link rel="alternate" type="text/markdown">and an HTTPLinkheader. - /llms.txt lists your pages, product categories, products and articles with their Markdown URLs, unless your site already has one.
The publishers’ crawlers fetch HTML today: the .md URLs and /llms.txt are what they can find and follow, and content negotiation serves the tools and agent frameworks that ask for Markdown. Each answer says what it is: X-Markdown-Twin-Cache (HIT; age=N, MISS or BYPASS: a kept copy, a fresh render, or never kept) and X-Markdown-Tokens (an estimate).
Built for real sites
- The content area is found automatically (block themes, Elementor, the common themes, otherwise the part of the page that holds the text); you can set your own CSS selectors instead. Pages that ask not to be indexed, and the cart, checkout and account pages, get no twin.
- No duplicate content: the twin is sent with
X-Robots-Tag: noindexand a canonical link to the HTML page. The page caches tested never store a Markdown answer as if it were the HTML page (the Diagnostic tab says which caches are written from their code and not tested). - Twins are kept ready (12 hours by default), served before WordPress runs its main query, and made again as soon as their page changes.
- Nothing is written to your server configuration when you activate the plugin. On Apache and LiteSpeed, the Diagnostic tab can write one
.htaccessrule for content negotiation behind a page cache, after your confirmation, with a backup copy that is put back if the site stops answering. - What AI agents receive: each twin is checked against the page it stands for (content area, title, text, structured data, price and availability, images, size, robots.txt, media), in the radiography of a page, in the lists of contents and with
wp markdown-twin check. - Difficult content: embedded documents, maps and audio players become typed links instead of disappearing with their frame, also behind a cookie banner; a form becomes one line that says where to fill it in; an animated counter is read at its final value; an image without alt gets the title of its media library file, when someone wrote one.
- Per content: “No Markdown version” and a note for AI agents, in the block editor and the classic one; under each video, audio or document, its transcript or description, from the subtitles of your media library or from what you write in the editor (“Media on this page”). Nothing is fetched from another site.
- Statistics: daily reads per agent (ChatGPT, Claude, Perplexity, their search and training crawlers, Googlebot, Bingbot, coding agents…), grouped by what the agent reads for: a person, AI search, training. No IP, no cookie, no personal data. A dashboard widget tells the last 30 days in one sentence. Off by default: the visits AI assistants send to your pages, and the check of each read against the IP address lists the publishers publish (see “External services”).
- AI access: choose, agent by agent, which AI agents may read your site; nothing is blocked by default. A blocked agent gets its line in your robots.txt and a 403 on its Markdown versions and llms.txt, never cached; the site shows whether it keeps coming. Each family comes with what its publishers say of robots.txt, in their own words. Search engines are never blocked (Google AI Overviews and Microsoft Copilot answer from their indexes: their controls are the snippet robots tags, said on the tab).
- Diagnostic: the site tests what agents get (.md URLs, content negotiation, page cache, llms.txt, robots.txt, firewall or CDN, content area, structured data), every 12 hours and when you open the tab (results less than an hour old are shown as they are; “Test again” runs them at once), and once a day it checks the twins of your most read pages. Both query the site itself and follow a redirect only on its own host name and port (http to https, a trailing slash); the one exception is robots.txt, read as crawlers read it: when your site redirects it to another site, that address is read too (see “External services”). The same tests appear in Site Health.
- No account, no tracking: nothing about your pages or your visitors is sent anywhere. Another site is asked only for the robots.txt your own site redirects to, and for the publishers’ address lists if you turn on the address check (see “External services”).
For developers
Filters markdown_twin_supported, markdown_twin_front_matter, markdown_twin_body_before, markdown_twin_body_after, markdown_twin_output, markdown_twin_product_facts, markdown_twin_product_rows, markdown_twin_max_variations, markdown_twin_llms_sections, markdown_twin_server_rules, markdown_twin_max_bytes, markdown_twin_max_transcript_bytes, markdown_twin_media_hosts, markdown_twin_agents, markdown_twin_stats_detail_families, markdown_twin_referral_sources, markdown_twin_visit_cap, markdown_twin_visit_cap_site, markdown_twin_link_resolution, markdown_twin_cache_hosts, markdown_twin_cache_max_files, markdown_twin_restricted (a content kept for members, whose text never makes a description), markdown_twin_site_closed (the site is closed to visitors: no Markdown version, no llms.txt): add them at the top level of a plugin file or of a must-use plugin, not in a theme nor inside a hook (a twin kept ready, or a refusal, is sent before the theme and the other hooks run). Commands: wp markdown-twin render <url>, stats, check, cache status|flush. Function: markdown_twin_url( $url ). In your templates, data-md="skip" leaves a block out and data-md="keep" always keeps it.
External services
Markdown Twin sends nothing about your pages, your visitors or the agents that read your site to another site. It asks another site in two cases only: the robots.txt your own site redirects to, and the option below (off by default). Both requests carry nothing about your site but its address, and for the address lists the WordPress version, in their user agent. The reader’s IP address never leaves the site.
robots.txt redirected to another site (the Diagnostic, no option). When your site answers a request for /robots.txt with a redirect to another host (www, a CDN), Markdown Twin reads that address as crawlers do, to test the rules that apply to your site: GET requests, five redirects at most, through WordPress’s wp_safe_remote_get(), with the certificate checked, and only on port 80 or 443, or your site’s own port for its own name. Before each request, the name is looked up and must give a public IPv4 address: a local, private or reserved address, an address written in IPv6 or another port is never asked. For a name other than your site’s, wp_safe_remote_get() checks the address once more. WordPress’s HTTP library then connects, resolving the name on its own (over IPv6 too, when the name has an IPv6 address). Once the chain has left your site, every further redirect is checked the same way, a return to your site’s name included. It happens every 12 hours, and when the Diagnostic, the AI access tab or Site Health need fresh results. Besides the standard headers of any HTTP request (host, compression, connection), it carries two: “User-Agent: Mozilla/5.0 (compatible; MarkdownTwin-Diagnostic; +” followed by the address of your site and “)”, and “Accept: /“. No cookie, no body.
Verify the agents’ addresses (Settings > Markdown Twin > Statistics, off by default). Once a week, one GET request per list (two redirects at most), to the file each publisher publishes on its own site, to tell whether a read comes from the addresses of the agent it names. The lists are downloaded by WordPress’s HTTP API with its standard user agent (the WordPress version and the address of your site) and “Accept: application/json”; the request carries nothing else: nothing about your pages, your visitors, or the agents that read your site.
- OpenAI: https://openai.com/gptbot.json, https://openai.com/searchbot.json, https://openai.com/chatgpt-user.json (documentation: https://developers.openai.com/api/docs/bots; terms: https://openai.com/policies/; privacy: https://openai.com/policies/privacy-policy/)
- Anthropic: https://claude.com/crawling/bots.json (documentation: https://support.claude.com/en/articles/8896518; terms: https://www.anthropic.com/legal/consumer-terms; privacy: https://www.anthropic.com/legal/privacy)
- Perplexity: https://www.perplexity.com/perplexitybot.json, https://www.perplexity.com/perplexity-user.json (documentation: https://docs.perplexity.ai/guides/bots; terms: https://www.perplexity.ai/hub/legal/terms-of-service; privacy: https://www.perplexity.ai/hub/legal/privacy-policy)
- Google: https://developers.google.com/static/crawling/ipranges/common-crawlers.json, https://developers.google.com/static/crawling/ipranges/user-triggered-agents.json (documentation: https://developers.google.com/crawling/docs/crawlers-fetchers/verifying-googlebot; terms: https://policies.google.com/terms; privacy: https://policies.google.com/privacy)
- Apple: https://search.developer.apple.com/applebot.json (documentation: https://support.apple.com/en-us/119829; terms: https://www.apple.com/legal/internet-services/terms/site.html; privacy: https://www.apple.com/legal/privacy/)
- Mistral AI: https://mistral.ai/mistralai-user-ips.json, https://mistral.ai/mistralai-index-ips.json (documentation: https://docs.mistral.ai/robots; terms: https://mistral.ai/terms; privacy: https://legal.mistral.ai/terms/privacy-policy)
- DuckDuckGo: https://duckduckgo.com/duckassistbot.json (documentation: https://duckduckgo.com/duckduckgo-help-pages/results/duckassistbot; terms: https://duckduckgo.com/terms; privacy: https://duckduckgo.com/privacy)
- Common Crawl: https://index.commoncrawl.org/ccbot.json (documentation: https://commoncrawl.org/ccbot; terms: https://commoncrawl.org/terms-of-use; privacy: https://commoncrawl.org/privacy-policy)
- Microsoft (Bingbot): https://www.bing.com/toolbox/bingbot.json (announced by Bing Webmaster Tools; terms: https://www.microsoft.com/servicesagreement; privacy: https://privacy.microsoft.com/privacystatement)
Each download replaces the previous list; when one fails, the last valid list is kept and the Diagnostic tab says so. Turning the option off, deactivating or uninstalling the plugin removes the lists and the weekly task.
Screenshots
A product page and its Markdown twin: the front matter with the page’s JSON-LD and the WooCommerce facts.
The dashboard widget “AI reads”: the last 30 days in one sentence.
Overview: who reads your pages, per AI agent, and the state of the site.
The radiography of a page: what AI agents read, what is left out and why.
Diagnostic: what agents get, test by test.
The editor panel: “No Markdown version”, the note for AI agents, “Media on this page”.
Publisher facts: what every twin says about the publisher.
AI access: which agents may read your site, with what their publishers say of robots.txt.

