// Technical GEO
llms.txt: a useful file or wishful thinking?
What llms.txt does, what it doesn't, and whether to bother.
llms.txt is a proposed convention: a Markdown file at the site root that summarises your most important pages in a form an LLM can ingest in a single fetch. Think of it as a sitemap for meaning rather than for URLs.
Adoption status
No major LLM provider has formally committed to consuming llms.txt as of writing. Some retrieval pipelines and developer tools do read it. The cost of publishing one is trivial; the upside if it becomes a standard is meaningful.
A minimal example
# Acme Co
> Acme Co builds enterprise widgets for industrial automation.
## Docs
- [Getting started](https://acme.co/docs/getting-started): install and first widget
- [API reference](https://acme.co/docs/api): full REST and webhook docs
## Company
- [About](https://acme.co/about): team, history, contact
- [Pricing](https://acme.co/pricing): plans and limitsShould you ship it?
Yes, if you have a coherent set of canonical pages worth surfacing. No, if your site is so small that the homepage already conveys the same thing. There is also an optional llms-full.txt for the full text of those pages – useful for documentation sites.
Want the full playbook?
This article is the appetiser. The GEO course covers the same ground in depth – annotated examples, copy-paste templates, real audit walkthroughs, and a 90-day roadmap. Lifetime access, no upsells.
Or just get a heads-up at launch: