ChatGPT
Perplexity
Claude
Grok
Markdown for agents is the practice of returning Markdown (not HTML) when a client requests your page with Accept: text/markdown. Same URL, HTTP content negotiation: browsers get HTML, many coding agents and some crawlers get a leaner body.
It pairs with generative engine optimization and answer engine optimization as plumbing. It does not replace good content or authority.
Why it matters
Agents waste tokens on nav, scripts, and wrappers. Markdown keeps structure (headings, lists, code) without most HTML chrome. Cloudflare reported ~80% fewer tokens on one of their own posts (HTML vs Markdown); your mileage will vary.
How to implement
Pick one path (details and copy-paste configs on AcceptMarkdown.com recipes and guides):
- Nginx, Caddy, Apache - map
Acceptto.mdfiles or an upstream that returns Markdown. - App (Next.js, Rails, Laravel, Express, …) - middleware: if
Acceptincludestext/markdown, return Markdown; else normal HTML. - Edge worker - Cloudflare Workers, Fastly, Lambda@Edge: fetch or convert, return
text/markdown. - Cloudflare only - enable Markdown for Agents (HTML→Markdown at the edge for enabled zones; see announcement).
Test and verify
curl -sI -H "Accept: text/markdown" 'https://yoursite.com/page'
- Is Your Site Agent-Ready? - broader agent-readiness scan, including Markdown negotiation.
- AcceptMarkdown.com - URL checks and which agents send the header.
AI SEO
Markdown for agents lowers fetch friction; it does not guarantee citations. Still optimize for AI citations and answer engine optimization. AI SEO Tracker shows where you appear in AI answers so you can tie infra changes to visibility.
