What is generative engine optimization (GEO)?
How AI assistants choose which sources to cite, and what you can change.
Guide
What the file holds, who actually reads it and when it is worth adding.
llms.txt is a small Markdown file at the root of a website that gives AI tools a short map of the site: whose site it is, what it covers and which pages to read first. It is a proposal that anyone may follow, not a rule that search engines enforce. For a company that sells services, it is a quick task with an unproven payoff, so it belongs after the work on your real pages.
Jeremy Howard of Answer.AI published the idea on llmstxt.org in September 2024. His reasoning is simple. A model that reads a site while doing a task has limited room, and an ordinary web page buries its useful text under menus and scripts. A short file written for machines saves that room and points the tool at the right pages.
The proposal goes one step further: it suggests offering a clean Markdown copy of each useful page at the same address with “.md” added. Few business sites do this, and you can skip it.
The spec makes only one line mandatory: a top heading with the name of the site or project. Everything else is optional, but it has a fixed order.
| Part | What it holds | Example for a dental clinic |
|---|---|---|
| H1 heading | the name | # Example Dental Clinic |
| Quote block | a one or two sentence summary | > Family dentistry and implants, two locations |
| Plain text | extra notes, no headings | languages spoken, insurance accepted |
| H2 sections with links | groups of pages, one link per line, a note after a colon | [Implants](https://example.com/implants/): prices and steps |
| Section named “Optional” | links a tool may skip when short on room | blog archive, careers |
The file can also sit in a folder, such as /docs/llms.txt, and then describes only that part of the site. When several files apply, the spec says the most specific one wins.
Here is what we could confirm in first-hand sources as of October 2026.
Our reading: the file has real use on software documentation. For a clinic, a law firm or an agency, we know of no public evidence that it brings more mentions or citations in AI answers.
The proposal goes one step further: it suggests offering a clean Markdown copy of each useful page at the same address with “.
When a buyer asks ChatGPT with search, Perplexity or Google about your field, these systems run a search and read your normal pages. So the pages decide the outcome.
Our own site is a small example. On September 22, 2026, Google AI Overviews linked to aoe.kz in 0 of the 17 queries we track. By October 6 the count was 2 of 20 (three queries were added to the set). The changes behind it were on the pages: a direct answer in the first paragraph, comparison tables, a block of questions. The first two links were seen at the September 29 check. The llms.txt file entered the aoe.kz site code on October 5, according to the repository history, six days later, so it could not have caused them. The queries were Russian-language searches in Almaty, measured on desktop. How we measure this is described on our AI search optimization page.
When a buyer asks ChatGPT with search, Perplexity or Google about your field, these systems run a search and read your normal pages.
Not for Search. Google’s AI features documentation says no special AI text files are needed, and John Mueller said in a 2025 post that, in his view, no AI system uses the file. The only Google product we found that looks at it is Lighthouse, which checks whether the file loads without errors.
OpenAI and Anthropic publish their own files for developers but have not said their assistants use other sites’ files to choose sources. A tool may fetch it when a user points it at your site. That is a narrow case, not a route into answers.
robots.txt tells bots what they may crawl. The sitemap lists every page you want indexed. llms.txt is a short, human-written summary for AI tools. None of the three replaces the others.
If your site platform can create it in a few clicks, yes, and keep it accurate. If it means a developer ticket, put it behind the page work in our AI citations guide. Short definitions of related terms are in the AI search glossary.
Keep reading
How AI assistants choose which sources to cite, and what you can change.
How answer engines pick a source and what to check on your pages.
How language models learn about your business, and how to check and fix what they say.
Who does the work, who owns the client and how reports and pricing work.