Does your llms.txt help an AI agent?

168 of 204 products we drive publish an llms.txt, and 30 of them meet the bar: a title, a summary, sections of working links, under 50,000 characters. If you publish one, check those four things first.

15%, 30 of 204: 30 of 204 products we drive publish an llms.txt that meets the bar for agents.

Share this card: Wide PNG · Tall PNG

Checked 25 Oct 2026204 productsThe bar: FIND-02Markdown

From having one to meeting the bar.

Most products that publish an llms.txt get the format right. Fewer keep it short and every link working.

From an llms.txt to meeting the bar. Of 204 products, 30 passed every checkpoint. Still going after each checkpoint: Have an llms.txt 168, Opened at /llms.txt 111, Start with a # title 108, Title, summary and sections 86, Meet the full bar 30.

Share this card: Wide PNG · Tall PNG

Products at each step, of all the products we drive
StepProductsOf 204
Have an llms.txt16882%
Opened at /llms.txt11154%
Start with a # title10853%
Title, summary and sections8642%
Meet the full bar3015%
  • 91 of the 103 products whose links we opened answered on every one. Of 513 links, 498 answered.
  • 58 also publish an llms-full.txt, the docs in full for an agent that reads everything in one fetch.

Where the rest fall short.

138 products publish an llms.txt that misses the bar. A file can miss it more than one way.

Why an llms.txt misses the bar
What's missingProducts
Not checked yet38
Over 50,000 characters20
We couldn't open it at /llms.txt19
No > summary under the title19
A link we opened didn't answer12
No ## sections of links5
Doesn't start with a # title3

How long they are.

The middle llms.txt is 12,516 characters. 20 are over 50,000, too long to read in one go.

How long each llms.txt is. Under 5,000 characters: 23 of 111, 5,000 to 20,000: 50 of 111, 20,000 to 50,000: 18 of 111, Over 50,000: 20 of 111.

Share this card: Wide PNG · Tall PNG

llms.txt by length
LengthProducts
Under 5,000 characters23
5,000 to 20,00050
20,000 to 50,00018
Over 50,00020

Good examples.

These 30 meet the bar on 25 Oct 2026. 20 of them publish an llms-full.txt too.

What a good llms.txt has.

  • A # title on the first line, then a > one-line summary.
  • ## sections of Markdown links, each with a line on what it covers.
  • Under 50,000 characters. Put the docs in full in /llms-full.txt instead.
  • Links that answer. Check them when your docs move.
  • The full bar: FIND-02 in the standard. The format itself: llms.txt.

Method and limits.

  • Every product we list, on 25 Oct 2026: one GET of /llms.txt and /llms-full.txt on its site, or on its docs site when the main site has none.
  • A product publishes an llms.txt when its drive found one, wherever its docs keep it, or this check opened one. 57 of those files didn't open at /llms.txt on the site or its docs site, so we couldn't read their shape or links.
  • We read a file when it answers 200 as text, not as a web page. It parses when its first line is a # title.
  • We opened five of each llms.txt's links, the product's own first. A link answers with a 200.
  • The bar is FIND-02 of our standard: a title, a summary, sections of links, under 50,000 characters and every link we opened answering. Whether doc pages link to the file isn't checked.
  • A site can publish or change its files any day.

Cite this

AgentDrives, “Does your llms.txt help an AI agent?”, 25 October 2026, https://agentdrives.com/research/llms-txt.
@misc{agentdrives_llms_txt_2026,
  author = {{AgentDrives}},
  title = {Does your llms.txt help an AI agent?},
  year = {2026},
  month = oct,
  url = {https://agentdrives.com/research/llms-txt},
  note = {Agent test drive, CC BY 4.0},
}
CC BY 4.0, with credit

See what an agent finds on your site.

Free: what an agent finds on your site, any wall in its way and how many things to fix.