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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/well-known-llms-aliases-for-agent-compatibility/
- Source: [mintlify.com](https://www.mintlify.com/docs/ai/llmstxt)
- GrowthDex source hub: [Mintlify Docs](/sources/mintlify-docs-mintlify-com/)
- Last checked: 2026-05-27
- Rarity: rare
- Budget: free
- Channels: SEO, AI Search, Website
- Stages: ai discovery, crawlability, technical seo, documentation


## Why this can grow

Agent clients do not all start from the same place. Some check the site root. Others look for a well-known path first. Shipping both removes an avoidable discovery failure and makes the machine-readable layer more durable if your docs stack or proxy setup changes later.

## 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 well-known llms aliases for agent compatibility 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 mintlify.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

Mintlify hosts `llms.txt` and `llms-full.txt` at both the site root and the `/.well-known/` paths for compatibility with tools that follow the well-known convention.

## Adjacent tactics in the same lane

- [llms discovery headers on every page](/growth-ideas/llms-discovery-headers-on-every-page/) - same source, 3 shared channels, 3 shared stages
- [llms-full single-file context export](/growth-ideas/llms-full-single-file-context-export/) - same source, 2 shared channels, 3 shared stages
- [Reverse-proxy forwarding for agent skill paths](/growth-ideas/reverse-proxy-forwarding-for-agent-skill-paths/) - same source, 2 shared channels, 2 shared stages
- [Root skill.md for product capability discovery](/growth-ideas/root-skill-md-for-product-capability-discovery/) - 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 agent-ready page should announce itself](/blog/the-agent-ready-page-should-announce-itself/) - seo, AI discovery, documentation
- [The route should stay yours after the click](/blog/the-route-should-stay-yours-after-the-click/) - brand trust, technical SEO, AI visibility

## Reading path: AI products

- [The route should stay yours after the click](/blog/the-route-should-stay-yours-after-the-click/) (2026-06-09T12:07:33.000Z)
- [The agent-ready page should announce itself](/blog/the-agent-ready-page-should-announce-itself/) (2026-05-27T23:20:00Z)

## Reading path: developer tools

- [The route should stay yours after the click](/blog/the-route-should-stay-yours-after-the-click/) (2026-06-09T12:07:33.000Z)
- [The agent-ready page should announce itself](/blog/the-agent-ready-page-should-announce-itself/) (2026-05-27T23:20:00Z)

## Advisory

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