Quick answer: llms.txt is a proposed standard — a markdown file at yourdomain.com/llms.txt that gives AI systems a curated, annotated index of your most important pages. No major AI search engine officially consumes it yet, but it costs nothing, takes ten minutes, and is read by a growing set of AI agents and developer tools. Add one; just don't expect it to be a ranking lever.
The llms.txt spec is deliberately simple: an H1 with your site name, a blockquote summary, then sections of links with one-line descriptions:
# Acme Widgets > Acme makes industrial widgets and publishes weekly widget-maintenance guides. ## Products - [Widget catalogue](https://acme.com/products): Full product range with specs. ## Guides - [Widget maintenance 101](https://acme.com/guides/maintenance): The definitive maintenance guide.
The idea: language models have limited context windows, and your website is full of navigation, cookie banners and boilerplate. llms.txt hands an AI the map — what matters, where it is, what it covers — in a format models parse trivially.
Honest answer: fewer systems than the hype suggests.
Yes — with calibrated expectations. The case for: it's free, it's ten minutes of work, it can only help AI systems that do look for it, and it signals technical care. The case against adding it instead of real fixes: none of the engines citing you today depend on it. If your content is JavaScript-rendered or your robots.txt blocks OAI-SearchBot, an llms.txt fixes nothing — do the fundamentals first.
llms.txt at your web root, served as plain text.Free scan shows your AI readiness grade · the €29 audit includes the full Fix-it kit
Scan my site →No. robots.txt is about permission (which crawlers may fetch which paths). llms.txt is about guidance (which pages matter and what they cover). They coexist at your site root.
There's no evidence of that today. Treat it as cheap future-proofing and agent-friendliness, not as GEO's main lever. Crawler access, server-rendered content and quotable structure move the needle far more.
An unofficial variant that inlines your full content into one file so agents can ingest everything in a single fetch. Useful for documentation sites; overkill for most others.