Markdown negotiation by platform
In short
9.1 percent of crawled home pages answered a markdown request with markdown, but the rate depends on the platform: Framer sites did 93.7 percent of the time and Wix sites 0.0 percent. The page sets the crawl rates beside the rubric scores for 23 platforms and the vendor statements.
A client that sends Accept: text/markdown to a page asks for the same content without the page chrome. Whether it gets markdown depends on the platform more than on the site owner: some send it by default, some need a switch, a plan or a plugin, and some cannot. The crawl asked 8,802 home pages that answered 200 and 798 of them (9.1 percent) sent markdown.
What the crawl found, by platform
Platform comes from the generator meta tag, so only sites that declare one are counted. Framer sites answered with markdown 93.7 percent of the time (179 of 191); Wix 0.0 percent (0 of 29). The generator tag says what built the page, not what serves it, so a rate above a platform's default score means the owner or the host added markdown on top: Astro sites answer 24.5 percent although a default Astro build does not.
Text equivalent of this chart
| Platform | Markdown | Of | Markdown share | Not markdown |
|---|---|---|---|---|
| Framer (191 pages) | 179 | 191 | 93.7% | 12 |
| Astro (110 pages) | 27 | 110 | 24.5% | 83 |
| Craft CMS (10 pages) | 2 | 10 | 20.0% | 8 |
| WordPress (411 pages) | 23 | 411 | 5.6% | 388 |
| Gatsby (58 pages) | 3 | 58 | 5.2% | 55 |
| Drupal (146 pages) | 6 | 146 | 4.1% | 140 |
| Hugo (27 pages) | 1 | 27 | 3.7% | 26 |
| Elementor (30 pages) | 1 | 30 | 3.3% | 29 |
| HubSpot (68 pages) | 1 | 68 | 1.5% | 67 |
| Docusaurus (10 pages) | 0 | 10 | 0.0% | 10 |
| TYPO3 (19 pages) | 0 | 19 | 0.0% | 19 |
| Wix (29 pages) | 0 | 29 | 0.0% | 29 |
What each scored platform does
The platform rubric scores markdown on request: 2 is on by default, 1 needs setup, a plan, a plugin or an extra service, 0 is not offered. The first sentence of each cell's evidence is shown.
| Platform | Score | What the evidence says |
|---|---|---|
| Cloudflare Markdown for Agents | 2 | The product itself, one toggle per zone. |
| Fern | 2 | Accept: text/markdown documented. |
| Firecrawl llms.txt generator | n/a | A generator. |
| Framer | 2 | On by default for every page. |
| Mintlify | 2 | Accept: text/markdown and Accept: text/plain both return markdown on the page URL. |
| GitBook | 1 | The .md suffix is documented; Accept-header negotiation is not documented on the page read, although gitbook.com answered it. |
| Next.js (App Router defaults) | 1 | Accept: text/markdown returned text/html. |
| Nuxt | 1 | Accept: text/markdown returned text/html. |
| ReadMe | 1 | Markdown for Agents is a documented setting under AI Discoverability; defaults vary by setting. |
| Redocly | 1 | Markdown copies documented; negotiation observed on redocly.com but not documented on the page read. |
| Scalar | 1 | .md URLs documented; negotiation observed on scalar.com only. |
| Vercel markdown handling | 1 | A recipe the developer implements. |
| Webflow | 1 | Enterprise only, since 2026-04-02. |
| WordPress and Elementor | 1 | Accept: text/markdown returned text/html. |
| Astro | 0 | Accept: text/markdown on / returned text/html and /index.md returned 404. |
| Docusaurus | 0 | Accept: text/markdown on / returned text/html and /index.md returned 404. |
| HubSpot CMS | 0 | Hubspot.com returned 406 to a markdown-only request. |
| Scrunch Agent Pages (AXP) | 0 | Routing is by user agent, not by Accept header. |
| Shopify themes | 0 | Not documented for storefront pages; shopify.com answered with text/html. |
| Squarespace | 0 | Not observed. |
| Stoplight | 0 | Not observed and not documented. |
| Wix | 0 | Not observed on wix.com and not documented. |
| Yoast and other WordPress llms.txt plugins | 0 | Yoast added no markdown negotiation; Accept: text/markdown returned text/html. |
The vendors behind them
The vendors section reads each vendor's own pages for the same behaviour. 7 of 74 state that they answer Accept: text/markdown on the same URL.
| Vendor type | Vendors | Supports | Partial or announced | No statement |
|---|---|---|---|---|
| Site builders | 8 | 1 | 1 | 6 |
| Content management systems | 7 | 0 | 2 | 5 |
| Docs platforms | 18 | 6 | 2 | 10 |
| Frameworks | 22 | 0 | 4 | 18 |
| Hosts, CDNs and edge products | 12 | 0 | 4 | 8 |
| Markdown and llms.txt tooling | 7 | 0 | 0 | 7 |
Does it matter
Ora's lab found (2026-10-19) that agents asked for markdown on about 65 percent of fetches, and that markdown mirrors and content negotiation never changed whether they succeeded. Ora's catalogue still scores it: the Markdown agent docs check is emerging tier, and Markdown content negotiation with Vary: Accept, which needs the scanned homepage itself to answer, is recommended tier at 1 point. Ora's passRate for the second reads 99.3 percent and its stricter rate 26.9 percent of 141,709 results (5 November 2026). The guide to serving markdown on request has the rule for each host, and the viewer tests one page.
Cite this: Agent Ready HTML. Markdown negotiation by platform. Edition 2026-11-04. https://agentreadyhtml.com/markdown-negotiation-by-platform/
Sources
- The crawl dataset (this site) https://agentreadyhtml.com/data/, read 4 November 2026
- Ora: AgentReady launch post (Ora's lab findings, 2026-10-19) https://ora.ai/blog/agentready-launch, read 5 November 2026
- Ora check catalogue, contract 1.38.0 https://ora.ai/api/checks, read 5 November 2026
- Ora statistics (pass rates per check) https://ora.ai/api/stats, read 5 November 2026
- Cloudflare: Introducing Markdown for Agents https://blog.cloudflare.com/markdown-for-agents/, read 4 November 2026
- Vercel: Making agent-friendly pages with content negotiation https://vercel.com/blog/making-agent-friendly-pages-with-content-negotiation, read 4 November 2026
- Webflow update: Markdown for AI agents https://webflow.com/updates/markdown-for-agents, read 4 November 2026
- Joost de Valk: Markdown Alternate https://joost.blog/markdown-alternate/, read 4 November 2026
- Vercel and Ora: Make your site readable by AI agents https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents, read 4 November 2026
- Cloudflare: agent readiness score and Radar numbers https://blog.cloudflare.com/agent-readiness/, read 4 November 2026
Last reviewed 5 November 2026