# sitemap.md semantic discovery map

> Publish a Markdown sitemap with section labels and page descriptions so agents can understand the site structure before they start fetching individual pages.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/sitemap-md-semantic-discovery-map/
- 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: free
- Channels: SEO, AI Search, Website
- Stages: seo, site-architecture, ai-discovery


## Why this can grow

XML tells crawlers what exists, but Markdown tells assistants what matters. A semantic sitemap reduces wandering, makes internal clusters legible, and gives answer engines a fast orientation layer for the whole corpus. It is one of the simplest ways to turn a pile of pages into a discoverable knowledge surface.

## 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 sitemap.md semantic discovery map 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 AI-agent documentation checklist explicitly recommends serving `/sitemap.md` as a semantic Markdown sitemap describing docs sections and pages.

## Adjacent tactics in the same lane

- [Content-negotiated markdown on canonical URLs](/growth-ideas/content-negotiated-markdown-on-canonical-urls/) - 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
- [Explicit AI-bot allowlist in robots.txt](/growth-ideas/explicit-ai-bot-allowlist-in-robots-txt/) - same source, 3 shared channels
- [AI-agent auto-detected markdown fallback](/growth-ideas/ai-agent-auto-detected-markdown-fallback/) - same source, 2 shared channels, 1 shared stage

## 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.