Fetch a site's /llms.txt and check its structure: title, summary, sections and whether its links work.
How to use the llms.txt checker
- Enter a site.
- Read the structure check and link results.
- Fix the missing parts and broken links.
Common issues
No H1 title, no summary blockquote, links to pages that redirect or 404, and the file served as HTML instead of plain text.
What the checks mean
Up to seven checks follow the llms.txt proposal. The first non-empty line must be an H1 (# Site name). A summary line starting with > should follow. There should be at least one ## section. Links should be list items in the form - [Name](url). At least half the links should have a ": description" after them, since that is what helps a model choose. Every link should be a full URL or a path starting with /. And the file should stay under 100 KB; move long detail to llms-full.txt. The score is the share of checks passed, and the file itself is shown underneath so you can see what was read.
Fixing a failing file
If the tool says there is no llms.txt, it must sit at the root of the domain, not in /docs or /public on a subpath. If the H1 check fails, look for a blank line, BOM or comment before the title. Links written as plain URLs or with * bullets won't count; use - [Name](url). If the file shows HTML, your host is serving a 404 page or a single-page app shell for unknown paths; make sure the static file is deployed.