What Is llms.txt? Make Your Site AI-Readable in 2026

Somewhere between a client asking “should we have an llms.txt file?” and a developer shrugging “I mean, it can’t hurt,” most SMB owners never get a straight answer on what is llms.txt — what it does, whether it’s worth the hour it takes to build, and whether AI engines actually read it. Here’s the honest version, not the hype version.

llms.txt is a plain-text file, written in markdown, that sits at your domain root — yoursite.com/llms.txt — and gives AI models a short, curated index of your most useful content. Proposed by developer Jeremy Howard in 2024 and documented at llmstxt.org, the format takes deliberate inspiration from robots.txt: a single, predictable file location that any crawler — human-built or AI-built — knows to check.

The spec itself is narrow by design. A valid llms.txt file has an H1 with your site or project name, a blockquote with a one-line summary, an optional paragraph of context, then one or more H2 sections listing markdown links to your key pages with a short note after each. No styling, no images, no fluff — just the pages you’d want an AI model to read first if it could only read five things.

Whether you need one depends on what you’re trying to solve. It is not a ranking factor, it does not replace clean on-page structure or schema markup, and it will not by itself get you cited by ChatGPT or Perplexity — that work is covered properly in how to get cited by ChatGPT and Perplexity. What llms.txt does is remove friction for any AI system that does try to parse your site, the same way a sitemap removes friction for Googlebot without being a ranking signal on its own.

Here’s the part most llms.txt guides skip: the evidence that it currently influences AI citations is thin. An Ahrefs study of 137,000 domains found that while 28% of sites using Ahrefs’ own analytics had published an llms.txt file, 97% of those files were never fetched by anything at all in the month studied. Of the requests that did come through, only 19.5% came from named AI tools — and AI retrieval bots, the specific systems most likely to power a live citation, accounted for just 1.1% of total requests.

That doesn’t mean llms.txt is worthless — it means it isn’t doing the job most people assume it’s doing. Major AI providers have not confirmed that llms.txt influences retrieval or ranking inside their live answer engines, and separate adoption tracking puts it on only around 8.7% of top 1,000 domains as of mid-2026 — meaning most of the web still hasn’t bothered, and the sites racing to add one are often optimising for a signal nobody’s reading yet.

Where it plausibly matters is upstream, not at query time: as a clean, well-labelled source for any future training runs or ingestion pipelines, rather than something ChatGPT reads live before answering your prospect’s question. Treat it as cheap future-proofing, not a growth lever — the actual lever is still the content quality, structure and schema covered in our cross-engine GEO playbook.

Below is a complete, valid llms.txt file for a small services business — short enough to build in one sitting, structured exactly to spec.

# Acme Design Studio > Boutique UI/UX and brand design studio for B2B SaaS companies, based in Austin, TX. Acme Design Studio helps SaaS teams ship interfaces that convert. Founded 2019, 40+ shipped products, remote-first team of 12. ## Docs - [Services overview](https://acmedesign.com/services/): what we do and who it's for
- [Case studies](https://acmedesign.com/work/): results across 12 SaaS clients
- [Pricing](https://acmedesign.com/pricing/): project and retainer rates ## Optional - [Blog](https://acmedesign.com/blog/): design and SaaS growth articles

Notice what’s missing: no navigation menu, no footer links, no cookie-banner copy, no marketing filler. That restraint is the entire point — an llms.txt file is only useful if it’s a genuine shortlist, not a re-export of your sitemap. Twenty links defeats the purpose as thoroughly as zero links does.

1. Open a plain-text editor and create a new file named exactly llms.txt — no .html, no .md extension.
2. Add an H1 with your business or site name, then a blockquote (>) with a one-sentence summary of what you do.
3. Add one short context paragraph if needed — who you serve, where you operate, what makes you specific.
4. Add H2 section headers (“Docs,” “Products,” “Optional”) each containing a short markdown-linked list of your 3–8 most important pages, with a one-line note after each.
5. Upload the file to your site’s root directory so it resolves at yoursite.com/llms.txt — via FTP, your host’s file manager, or a plugin if you’re on WordPress.
6. Re-check it every quarter as pages change; a stale llms.txt pointing at dead URLs is worse than none at all.

If you’re not comfortable editing server files directly, this is exactly the kind of half-hour technical task worth folding into a broader AI search and SEO engagement rather than handling piecemeal — it’s most valuable done alongside schema, sitemap and crawl-budget cleanup, not in isolation.

It’s also worth deciding upfront who owns the file long-term. On most SMB sites, llms.txt quietly rots within a year — a service gets discontinued, a pricing page moves, and nobody updates the one file that was supposed to be the “clean, curated” version of the site. Assign it to whoever already owns your sitemap or robots.txt, and put a quarterly reminder on the same calendar entry that triggers your other technical SEO checks, covered in more depth alongside measurement in how to track AI search traffic once the file is live and you want to know whether any of this is actually working.

Where llms.txt is an index, llms-full.txt is the whole book: a single flat markdown file containing the entire text of your key pages concatenated together, so an AI tool can ingest your full content in one fetch instead of following individual links. It’s most common on documentation-heavy sites — developer tools, SaaS platforms, technical products — where an AI coding assistant benefits from reading the whole reference at once.

For most SMB marketing sites, llms-full.txt is optional and often unnecessary — a services business rarely has the kind of dense reference content that benefits from a full-text dump, and maintaining a duplicate flat-file version of your whole site adds upkeep for a use case you probably don’t have yet. Start with llms.txt; add llms-full.txt only if you’re running documentation, a knowledge base, or a product with genuine technical depth.

If you do build one, treat it as a generated artifact rather than something hand-maintained page by page — export your core content to markdown, concatenate it, and regenerate the file whenever pricing, services or key pages change materially. A stale llms-full.txt that still describes a discontinued product or an old price is arguably worse than not having one, since it hands an AI system confidently wrong information dressed up as an authoritative source.