# Content-negotiated markdown on canonical URLs

> Serve markdown from the same canonical URL when an agent requests `Accept: text/markdown`, instead of forcing a separate docs-only experience.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/content-negotiated-markdown-on-canonical-urls/
- Source: [vercel.com](https://vercel.com/kb/guide/make-your-documentation-readable-by-ai-agents)
- GrowthDex source hub: [Vercel Knowledge Base](/sources/vercel-knowledge-base-vercel-com/)
- Last checked: May 24, 2026
- Rarity: rare
- Budget: low
- Channels: SEO, AI Search, Website
- Stages: seo, ai-discovery, trust


## Why this can grow

This keeps humans and agents anchored to the same source URL while giving each the format they can actually use. Browsers still get rich HTML, but assistants get clean markdown with less token waste and cleaner citations. That reduces retrieval friction without splitting authority across parallel pages.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where content-negotiated markdown on canonical urls can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the SEO and AI Search channel.
3. Use the evidence from vercel.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Vercel's agent-readability guidance recommends returning markdown for canonical docs URLs when agents send `Accept: text/markdown`, with separate cache treatment via `Vary: Accept`.

## Adjacent tactics in the same lane

- [sitemap.md semantic discovery map](/growth-ideas/sitemap-md-semantic-discovery-map/) - same source, 3 shared channels, 2 shared stages
- [Markdown shadow routes for direct agent retrieval](/growth-ideas/markdown-shadow-routes-for-direct-agent-retrieval/) - same source, 2 shared channels, 2 shared stages
- [AI-agent auto-detected markdown fallback](/growth-ideas/ai-agent-auto-detected-markdown-fallback/) - same source, 2 shared channels, 2 shared stages
- [Explicit AI-bot allowlist in robots.txt](/growth-ideas/explicit-ai-bot-allowlist-in-robots-txt/) - same source, 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The machine reader is part of the audience now](/blog/the-machine-reader-is-part-of-the-audience-now/) - SEO, AI discovery, content systems

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.