# The agent-ready page should announce itself > Why well-known llms paths, discovery headers, full-context exports, and skill manifests make AI discovery easier to trust and easier to use. - Canonical HTML: https://growth.iangoh.com/blog/the-agent-ready-page-should-announce-itself/ - Published: 2026-05-27 - Updated: 2026-05-27T23:20:00Z - Categories: seo, AI discovery, documentation - Niches: SaaS, AI products, developer tools, creator tools, B2B software ## On this page - Compatibility beats elegance on the first fetch - Normal pages should point to the map - Some agents do better with one big file - Discovery and capability are different jobs - Complex products should not hide every workflow in one blob - Where this cluster is most useful ## Start with these related tactics - [Well-known llms aliases for agent compatibility](/growth-ideas/well-known-llms-aliases-for-agent-compatibility/): Serve `/.well-known/llms.txt` and `/.well-known/llms-full.txt` alongside the root files so agents that follow the well-known convention can discover your corpus without guessing. - [llms discovery headers on every page](/growth-ideas/llms-discovery-headers-on-every-page/): Add `Link` and `X-Llms-Txt` headers to normal page responses so an agent can find your machine-readable corpus before it starts crawling blindly. - [llms-full single-file context export](/growth-ideas/llms-full-single-file-context-export/): Publish an `llms-full.txt` file that bundles the important documentation corpus into one fetch for agents that work better with a single large context payload. A lot of teams ship one machine-readable file and then quietly hope the agent will figure out the rest. Sometimes it does. A lot of the time it does not. The agent lands on one page, sees a pile of HTML, and has to guess where the clean map lives, whether a bigger context file exists, and what the product can actually do. That is usually a packaging failure, not a content failure. ## Compatibility beats elegance on the first fetch The first move I would steal is [well-known llms aliases for agent compatibility](/growth-ideas/well-known-llms-aliases-for-agent-compatibility/). A lot of teams are happy once [publish llms.txt for agent retrieval](/growth-ideas/publish-llms-txt-for-agent-retrieval/) is done, but discovery is still fragile if the file only lives in one place. If one client checks the root and another checks a well-known path, the practical answer is to stop making them choose. ## Normal pages should point to the map I like [llms discovery headers on every page](/growth-ideas/llms-discovery-headers-on-every-page/) because it fixes a boring but expensive gap. If an agent opens a normal page first, the response itself should advertise where the clean corpus lives. That fits naturally beside [sitemap.md semantic discovery map](/growth-ideas/sitemap-md-semantic-discovery-map/) and [content-negotiated markdown on canonical URLs](/growth-ideas/content-negotiated-markdown-on-canonical-urls/). One tactic gives the crawler a route. The other makes the route easier to notice. ## Some agents do better with one big file The simplest upgrade in this batch is [llms-full single-file context export](/growth-ideas/llms-full-single-file-context-export/). Not every tool wants to walk a tree of links. Some do better when the useful context is already gathered. That does not replace page-level structure. It gives the retrieval layer a second, lower-friction door. ## Discovery and capability are different jobs That is why [root skill.md for product capability discovery](/growth-ideas/root-skill-md-for-product-capability-discovery/) matters. `llms.txt` tells the agent where to read. `skill.md` tells it what the product can actually help with. I think this is the missing bridge between [llms.txt plus MCP content corpus for AI discovery](/growth-ideas/llms-txt-plus-mcp-content-corpus-for-ai-discovery/) and the actual workflows a buyer wants to run. Reading the docs is one problem. Using the product correctly is another. ## Complex products should not hide every workflow in one blob The most operator-friendly move here is [agent-skills index for multi-workflow products](/growth-ideas/agent-skills-index-for-multi-workflow-products/). If a product has billing, analytics, docs, and admin paths, a single giant capability file becomes its own small maze. Separate skills plus a discovery index keep the machine-readable layer organized the same way a good product keeps its UI organized. Each job gets a clean doorway. ## Where this cluster is most useful This cluster is strongest for SaaS, AI products, developer tools, and creator platforms that want assistants to quote the product accurately or guide a user through a real workflow. It matters most when the site already has useful content but still makes the retrieval layer work too hard to find it. If your machine-readable layer still expects the agent to guess the next file, I would assume the site is leaving easy trust on the table. ## Related GrowthDex tactics - [Well-known llms aliases for agent compatibility](/growth-ideas/well-known-llms-aliases-for-agent-compatibility/) - SEO, AI Search, Website - [llms discovery headers on every page](/growth-ideas/llms-discovery-headers-on-every-page/) - SEO, AI Search, Website - [llms-full single-file context export](/growth-ideas/llms-full-single-file-context-export/) - AI Search, SEO, Documentation - [Root skill.md for product capability discovery](/growth-ideas/root-skill-md-for-product-capability-discovery/) - AI Search, Documentation, Website - [Agent-skills index for multi-workflow products](/growth-ideas/agent-skills-index-for-multi-workflow-products/) - AI Search, Documentation, Integrations ## Essay chronology - [Newer essay: The launch page cannot carry the whole launch](/blog/the-launch-page-cannot-carry-the-whole-launch/) - product launches, operator-led distribution, brand trust - [Older essay: The support doc starts working when the product can point to it](/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/) - support-led growth, documentation, seo ## Keep reading - [An agent needs a capability page, not just a crawl map](/blog/an-agent-needs-a-capability-page-not-just-a-crawl-map/) - AI Search, brand trust, technical SEO - [The support doc starts working when the product can point to it](/blog/the-support-doc-starts-working-when-the-product-can-point-to-it/) - support-led growth, documentation, seo - [The route should stay yours after the click](/blog/the-route-should-stay-yours-after-the-click/) - brand trust, technical SEO, AI visibility ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Mintlify Docs: llms.txt](https://www.mintlify.com/docs/ai/llmstxt) · [GrowthDex source hub](/sources/mintlify-docs-llms-txt-mintlify-com/) - [Mintlify Docs: skill.md](https://www.mintlify.com/docs/ai/skillmd) · [GrowthDex source hub](/sources/mintlify-docs-skill-md-mintlify-com/) - [Mintlify Blog: skill.md](https://www.mintlify.com/blog/skill-md) · [GrowthDex source hub](/sources/mintlify-blog-skill-md-mintlify-com/) ## Editing notes - Kept the essay on one plain claim about machine-readable packaging instead of drifting into grand statements about the future of agents. - Used blunt objects like paths, headers, files, maps, and doorways so the piece stays tied to things a team can inspect today. - Cut promotional AI language and let the Mintlify mechanics carry the proof. - Ended on a simple trust test about guesswork instead of a generic conclusion about discoverability. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.