What it solves
An AI engine piecing together a company from its website, LinkedIn, press and directories will find contradictions — and cite nothing. llms.txt provides one official anchor: our definition, our page index, our case figures with sources, and the rule that the website wins conflicts.
The typical contradiction: the website says the company was founded in 2014, a directory says 2016, and an old press release still describes the previous business. Faced with three versions, the engine cannot tell which to trust — the safest choice is to cite nothing, or to cite the wrong one. llms.txt cannot remove the other sources, but it gives the engine a tie-breaker: when sources conflict, this file and the official website win.
llms.txt is a convention proposed by Jeremy Howard in 2024: a Markdown file at the website root, in a fixed format, stating what the company is. It is not a standard and not a protocol, and no body enforces it — its strength is simplicity. Any agent that reads Markdown can read it in one fetch instead of crawling a dozen pages and stitching them together.
How engines actually treat it
The honest picture: there is no published list of which engines read llms.txt. It is a convention, not a standard, and no major engine promises to cite you for having one. Google's official docs state that appearing in AI Overviews and AI Mode requires no extra technical work and no new machine-readable files or AI text files — for Google, llms.txt is not a requirement.
So the correct framing is: llms.txt is an auxiliary piece of the machine-readable layer, not a pass. It makes existing citations more accurate and helps agents find the right version faster, but it does not create citations. What gets you cited is still third-party mentions, content quality, and entity consistency.
What it does not solve
Treating llms.txt as a switch that gets you cited is the most common misconception right now. The strongest citation signal is third-party mentions; llms.txt at best makes existing citations more accurate. That is why our audit scores its absence as a warning, not a failure.
How to write a useful one
- A one-sentence company definition plus category;
- Offering boundaries — what you do and do not do;
- Key figures with sources, explicitly flagging which are not your own results;
- An index of core pages with language pairings;
- Citation rules and a corrections contact.
The figure above this article is the opening of Negency's own llms.txt, verbatim — definition, canonical anchor, fact sheet, and page index. The extended form is llms-full.txt: the full text of every page in one file, so an agent can read the entire site in one fetch. Negency publishes both — feel free to use them as a reference.
Common mistakes
- Write it and forget it: the company changes, the file stays old. A stale official anchor is worse than none — engines will cite the outdated version. Every time a key fact changes on the site, change llms.txt too.
- Stuffing keywords: treating it as SEO text helps no citation and makes agents doubt the quality of the whole site. llms.txt is a fact sheet, not marketing copy.
- Using it instead of structured data: llms.txt is an aid, not a replacement for JSON-LD. The foundation of machine readability is structured data on the pages themselves; llms.txt only adds one more entry point. In our 30-site measurement, 17 sites had no JSON-LD at all — that is the fix to prioritise.