llms.txt: what it is, why it matters, and how to serve one

The problem it solves

AI assistants don't browse your site the way people do — they need a fast, reliable answer to 'what is this site and which pages matter?' HTML navigation is built for humans; sitemaps list URLs without meaning. llms.txt is the emerging middle ground: a plain-text, markdown-shaped file at the root of your domain that describes your site in the format language models parse best.

The format, in thirty seconds

An H1 with your site or product name. A blockquote with a one-paragraph summary — who you serve and what you do. Then sections of markdown links, each with a short note explaining why that page matters. That's the whole convention: name, summary, annotated map.

Serve it at https://yoursite.com/llms.txt with content-type text/plain. Keep it current — a stale llms.txt teaches assistants stale answers about you.

What to include (and skip)

Include the pages you'd want quoted in an answer: your core product explanations, your most authoritative guides, your trust or verification page, your pricing. Skip login walls, thin tag pages, and anything you wouldn't stand behind if an assistant repeated it verbatim.

Every GrowthBerry property serves a generated llms.txt automatically — the guide library, the Trust page with verification dates, and the sitemap, each annotated. You can build your own by hand, or use our free llms.txt Generator: fill three fields, copy the file, done.