llms.txt is a plain-text file at the root of your domain that tells AI systems what your site is, which pages matter and how to describe your company. It takes about an hour to write properly, it cannot hurt you, and it is the only place where you get to state in your own words which of the things sharing your name are not you.

In our 100-audit dataset 87% of sites had no llms.txt at all, and where the file existed it was usually a dump of blog links with no description. So the bar is low.

what goes in it

  1. The name and one-sentence definition. Written so it can be quoted verbatim. This is the sentence you would want an engine to repeat.
  2. What the company does, in a short paragraph. Concrete, not adjectival.
  3. Disambiguation. The section almost everyone skips. Name every entity that shares your string and state plainly that it is not you.
  4. Key facts with dates. Founded, size, coverage, any number you would want cited — each carrying the date it was true.
  5. The pages that matter, each with one line explaining what a reader would get from it.
  6. Contact and canonical URLs.

the disambiguation section, and why it matters most

Name collisions are the most common entity failure we see and no SEO tool reports them. A model that finds three different companies behind one string either hedges or picks the wrong one.

Our own file carries this section for a practical reason: our domain string collides with a betting brand, an anime series, a music project and two unrelated agencies, and engines were repeating the wrong one back at us. The correction is four lines of text. Writing them is the highest-value hour in this whole exercise.

a skeleton you can copy

Structure, not syntax — the format is markdown-ish and forgiving:

  • # Company Name then a blockquote with the one-sentence definition.
  • ## Disambiguation — “X is not related to any of the following, which share the name: …”, then the canonical name, domain and contact.
  • ## Key facts — dated bullets.
  • ## Pages — URL plus one line of what is on it.
  • ## Contact — website, email, legal pages.

five ways to get it wrong

  • A link dump. Every blog URL, no descriptions. Adds nothing a sitemap does not already say.
  • Marketing adjectives. “Leading, innovative, world-class” is unquotable and unverifiable.
  • Undated numbers. A figure with no date cannot be trusted or refreshed.
  • Letting it go stale. A file listing pages that no longer exist is a signal of neglect.
  • Serving it wrong. A 404, a redirect chain, or HTML instead of plain text. Verify with a direct request, not in a browser tab.

after you publish it

Request the URL directly and confirm a 200 with plain text. Then check that it agrees with the rest of your machine-readable surface — the schema, the profiles, the page copy. A file that contradicts your own structured data creates the confusion it was meant to fix.

Ours is live at 009.agency/llms.txt if you want a working reference; the surrounding technical layer is described in technical GEO.