llms.txt follows the format: what the check tests and how to fix it

Scores your llms.txt on four features: an H1 title, a blockquote summary, a link and ## sections. 70 points passes. It checks more than the proposal requires.

Agent Discovery · Weight 0.5 in the w2agent Score

How common is it?

92% of 868 measured sites where this check applied pass.

Latest audit of each site under rubric v3.1. Sites where the check did not apply or could not be measured (for example, no llms.txt for the llms.txt checks) are left out. A partial result does not count as a pass.

What this check tests

If no llms.txt was found, this check is skipped. Otherwise it adds up points for four features of the file:

FeaturePoints
A line starting with # followed by text (an H1 title)30
A line starting with > followed by text (a blockquote summary)20
At least one http:// or https:// URL anywhere in the file30
A line starting with ## followed by text (a section heading)20

70 points or more is a pass. 1 to 69 is a partial. 0 is a fail. The check does not verify order, link syntax, or that links sit under section headings.

This is stricter than the proposal. The llmstxt.org format lists the H1 as the only required part and treats the blockquote and sections as expected but optional. A file with only a title would be valid under the proposal and would still score a partial here. The check is a heuristic for a useful file, not a conformance test.

Why it matters to agents

An agent reading the file needs to know whose site it is (the title), what it covers (the summary) and where to go next (links grouped under headings). A file that lacks these is harder to use, whichever tool reads it. As with the other llms.txt checks, the readers are mostly coding agents and documentation tools, not chat crawlers.

How to fix it

Start from the structure the proposal describes, in this order: title, blockquote summary, optional prose, then sections of link lists. Each list item is a markdown link, optionally followed by a colon and a note.

# Example Co

> Project-planning software with a REST API. Start with the guides; the API reference lists every endpoint.

## Guides

- [Quickstart](https://example.com/docs/quickstart): Create a project in five minutes

## Optional

- [Changelog](https://example.com/changelog): Release notes
  • Keep the H1 to one line naming the site or product.
  • Write the blockquote as two sentences a stranger could act on.
  • Use absolute URLs so a fetched copy still works out of context.

Related: llms.txt exists and llms.txt links resolve. You can also run the format check on a pasted file with the llms.txt validator.

Test your own file with the llms.txt validator.

Platform guides

Step-by-step instructions for specific platforms:

Examples from measured sites

Up to 10 of the highest-scoring sites in each group, from recent audits. Failing includes partial results.

Passing

Failing or partial

Sources

Verified against these sources on

Does your site pass this check?

Check your own site →