llms.txt structure quality

What this check looks for

For sites with a valid llms.txt already present, this check evaluates four structural elements: an H1 title (# Name) on the first non-blank line, a > blockquote summary line, at least one ## section heading, and markdown links whose hrefs resolve to real absolute URLs against the site's origin. If at least 3 of these 4 pass and at least one link is present, it passes. Otherwise it warns, naming exactly which elements are missing. Sites with no llms.txt to evaluate report "na" — that's the presence check's job.

Why it matters

The llmstxt.org format is deliberately simple, but its structure exists for a reason: the H1 identifies the site by name, the summary blockquote gives an assistant a one-line description before it reads further, and the ## sections with markdown links are what actually let an assistant navigate to your key pages instead of just knowing they exist. A file that technically exists but skips this structure — a wall of unformatted text with no headings or links, for instance — gives an assistant little more than it could infer from a normal crawl, defeating the purpose of publishing the file at all. Broken or relative links that don't resolve are the most common quality gap, since they silently fail to guide an assistant anywhere useful.

How to fix it

Follow the spec's structure exactly, with absolute, resolvable links:

# Acme Audio

> Acme Audio makes wireless headphones and speakers focused on
> noise cancellation and battery life.

## Products
- [Wireless Noise-Cancelling Headphones](https://www.acme.com/audio/headphones/wireless-nc)

## Support
- [Warranty and returns](https://www.acme.com/support/returns)

Use fully-qualified https:// URLs rather than relative paths, and verify each link actually loads before publishing.