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.
Why this can grow a startup
A lot of discovery friction happens before an agent reads a single paragraph. When ordinary page responses advertise where the structured corpus lives, the site becomes easier to interpret with fewer wasted fetches. It is a small technical move that makes the content layer easier to find without changing your visible UX.
Company example
Mintlify adds `Link` headers pointing to `/llms.txt` and `/llms-full.txt`, plus an `X-Llms-Txt` header, on every page response so AI tools can discover the files without prior knowledge.
Source and metric
Source: Mintlify Docs · Browse Mintlify Docs tactics
Every page response can advertise `/llms.txt` and `/llms-full.txt` via HTTP headers
Source discovered: May 27, 2026
When to use it
Use this when SEO, AI Search, Website is relevant to ai discovery, crawlability, headers and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Mintlify Docs and identify what is directly supported.
- Choose one channel context: SEO, AI Search, Website.
- Define the test around Every page response can advertise `/llms.txt` and `/llms-full.txt` via HTTP headers.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.