In plain English
A real webpage is full of things a language model doesn't care about — navigation, banners, scripts, ads, cookie prompts. When an AI tries to understand your site, it has to wade through all of that. llms.txt hands it a shortcut: a single, tidy Markdown file that says "here's who we are and here are the pages that actually matter."
It lives at yourdomain.com/llms.txt, the same predictable spot as robots.txt, so any AI system that supports the convention knows exactly where to look.
llms.txt vs. robots.txt vs. sitemap.xml
| robots.txt | Permission. Tells crawlers what they may and may not access. |
|---|---|
| sitemap.xml | Inventory. Lists every URL for search engines to crawl. |
| llms.txt | Guidance. Curates the few pages that matter most, in clean Markdown, for AI models. |
What an llms.txt file looks like
It's just Markdown. A typical file has your name, a one-line summary, and grouped links with short descriptions:
- An H1 with the site or product name.
- A short blockquote summarizing what you do.
- Sections of links (Docs, Products, Policies) — each link with a one-line description.
- An optional "Optional" section for secondary links a model can skip under tight context limits.
Why it matters
As people increasingly discover products through AI answers, being understood correctly by a language model becomes as important as ranking in search. llms.txt is a low-cost way to reduce the chance an AI mis-summarizes you, points to the wrong page, or misses your best content entirely. It pairs naturally with GEO and assumes the basics are handled — namely that bots can read your site in the first place.
First, confirm bots can read you
An llms.txt file guides models to your content — but only if that content is actually reachable. Run a free bot-readability scan to catch JavaScript-only pages, robots.txt blocks, and login walls before you add an llms.txt on top.
Scan my site free →