# The machine reader is part of the audience now > Why more growth surfaces need to be readable by agents as well as humans, and why clean markdown can be a trust move rather than a technical flourish. - Canonical HTML: https://growth.iangoh.com/blog/the-machine-reader-is-part-of-the-audience-now/ - Published: 2026-05-24 - Updated: 2026-05-24 - Categories: SEO, AI discovery, content systems - Niches: SaaS, AI products, creator tools, SEO ## On this page - The same URL should not tell two different stories - Give the reader a plain door - Discovery needs a map, not just a pile of links - Do not wait for perfect agent behavior - Ship the discovery layer with the content - Where this applies ## Start with these related tactics - [Publish llms.txt for agent retrieval](/growth-ideas/publish-llms-txt-for-agent-retrieval/): Add a root /llms.txt file that tells AI agents what the site is, which URLs matter, and how to interpret the content. - [Content-negotiated markdown on canonical URLs](/growth-ideas/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. - [Markdown shadow routes for direct agent retrieval](/growth-ideas/markdown-shadow-routes-for-direct-agent-retrieval/): Generate a `.md` version for every important content URL so agents, IDEs, and operators can fetch clean text without special headers. A lot of teams still talk about AI discovery as if it were some future channel. It is already a present one. The quiet shift is that some of the readers arriving at your site are not people opening tabs. They are agents trying to decide what your page means and whether it is worth citing. That changes the job. A site no longer only needs to look convincing. It also needs to explain itself cleanly when the chrome is gone. ## The same URL should not tell two different stories This is why [content-negotiated markdown on canonical URLs](/growth-ideas/content-negotiated-markdown-on-canonical-urls/) is more important than it first sounds. The point is not just technical neatness. The point is that the human page and the machine-readable page stay anchored to the same source, which keeps authority and citation pointing in one direction. If the clean version lives somewhere obscure, only specialists will find it. If it lives on the main page path, the retrieval layer starts feeling like part of the product instead of a sidecar. ## Give the reader a plain door The simpler move is still useful: [markdown shadow routes for direct agent retrieval](/growth-ideas/markdown-shadow-routes-for-direct-agent-retrieval/). A `.md` page is a plain door into the same content. No guessing, no custom browser state, no scraping the navigation out of the way. I like this because it helps humans too. A founder, operator, or advisor can paste the clean page into a prompt or notes file without dragging the full interface with it. ## Discovery needs a map, not just a pile of links That is also the logic behind a [sitemap.md semantic discovery map](/growth-ideas/sitemap-md-semantic-discovery-map/). XML is fine for machines that already know the rules. A Markdown sitemap is better for agents that need orientation: what lives where, what each section is for, and which pages deserve attention first. It pairs naturally with [llms.txt](/growth-ideas/publish-llms-txt-for-agent-retrieval/). One file says what the site is. The other shows how to move through it. ## Do not wait for perfect agent behavior The awkward truth is that not every assistant asks nicely. That makes [AI-agent auto-detected markdown fallback](/growth-ideas/ai-agent-auto-detected-markdown-fallback/) a practical move, not an edge case. If a likely agent arrives without the ideal headers, give it the useful version anyway. This is one of those rare SEO improvements that also feels polite. You are reducing waste for the reader, even when the reader is software. ## Ship the discovery layer with the content The strongest case study in this batch is Waldium. Its [onboarding discovery bundle for AI-native sites](/growth-ideas/onboarding-discovery-bundle-for-ai-native-sites/) gives each new blog a sitemap, llms.txt, robots.txt, an MCP install page, and a live endpoint in under five minutes. That is the right instinct. The discovery layer should not be a cleanup sprint after you already have 200 pages. It should be the packaging the page ships in. ## Where this applies For SaaS, this matters on docs, integration pages, changelogs, and comparison content. For AI products, it matters anywhere you want assistants to quote the product accurately. For creator tools and content-heavy products, it matters because machine-readable pages can become a second distribution surface without buying more attention. The trap is treating this as a pure technical concern. It is really a clarity concern. If the page cannot explain itself cleanly to a machine, there is a decent chance it is not explaining itself clearly enough to a hurried human either. ## Related GrowthDex tactics - [Publish llms.txt for agent retrieval](/growth-ideas/publish-llms-txt-for-agent-retrieval/) - SEO, AI Search, Content - [Content-negotiated markdown on canonical URLs](/growth-ideas/content-negotiated-markdown-on-canonical-urls/) - SEO, AI Search, Website - [Markdown shadow routes for direct agent retrieval](/growth-ideas/markdown-shadow-routes-for-direct-agent-retrieval/) - SEO, AI Search, Content - [sitemap.md semantic discovery map](/growth-ideas/sitemap-md-semantic-discovery-map/) - SEO, AI Search, Website - [AI-agent auto-detected markdown fallback](/growth-ideas/ai-agent-auto-detected-markdown-fallback/) - AI Search, Website, Content - [Onboarding discovery bundle for AI-native sites](/growth-ideas/onboarding-discovery-bundle-for-ai-native-sites/) - AI Search, SEO, Website ## Essay chronology - [Newer essay: The launch often goes wrong the week before](/blog/the-launch-often-goes-wrong-the-week-before/) - launches, SEO, operator systems - [Older essay: The narrow surface usually wins first](/blog/the-narrow-surface-usually-wins-first/) - growth strategy, operator-led distribution ## Keep reading - [Borrowed attention only pays if the handoff is clean](/blog/borrowed-attention-only-pays-if-the-handoff-is-clean/) - launch strategy, SEO, operator-led distribution - [The best growth surface is usually already yours](/blog/the-best-growth-surface-is-usually-already-yours/) - growth systems, SEO, operator-led distribution - [The buyer is usually already on the right page](/blog/the-buyer-is-usually-already-on-the-right-page/) - SEO, conversion, operator-led distribution ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Vercel Knowledge Base](https://vercel.com/kb/guide/make-your-documentation-readable-by-ai-agents) · [GrowthDex source hub](/sources/vercel-knowledge-base-vercel-com/) - [Vercel Knowledge Base](https://vercel.com/kb/guide/how-to-serve-documentation-for-agents) · [GrowthDex source hub](/sources/vercel-knowledge-base-vercel-com/) - [Vercel Blog](https://vercel.com/blog/how-waldium-made-a-blog-platform-work-for-humans-and-ai-alike) · [GrowthDex source hub](/sources/vercel-blog-vercel-com/) - [Vercel Blog](https://vercel.com/blog/making-agent-friendly-pages-with-content-negotiation) · [GrowthDex source hub](/sources/vercel-blog-vercel-com/) ## Editing notes - Kept the piece grounded in concrete page mechanics instead of making big claims about the future of AI. - Cut generic optimization language and stayed close to what the reader can actually implement or inspect. - Used short paragraphs and direct opinions so the essay reads like a view from practice, not a framework memo. - Linked the argument back to specific GrowthDex tactics to keep the piece useful for both readers and crawlers. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.