Best llms.txt Validators in 2026: 8 Checkers Compared
Free llms.txt validators check whether /llms.txt follows the llmstxt.org format, and the better ones also test every link. Eight checkers compared by what they actually validate, plus what changed in the v2 proposal.
· 9 min read
The best llms.txt validator for a quick check is one that tests both the format and the links: llms-txt-validator.dev fetches every linked URL and scores the file 0 to 100, while TrustSEO and AI Rank Lab validate /llms.txt and /llms-full.txt against the llmstxt.org format with no sign-up. Hota.Digital is the most explicit about following the August 2026 v2 proposal. Google's Lighthouse now has an llms.txt audit, but it only flags server errors. To check llms.txt alongside AI-bot access and the rest of a site's AEO readiness, a site auditor such as Audra covers it as one of eight checks.
Every tool below was checked on its own page on November 11, 2026. None of them can tell you whether an AI system will use your file: llms.txt is a proposal for agents to find LLM-friendly content, not a ranking or citation signal.
What an llms.txt validator should check
The llmstxt.org proposal, now at v2 (dated 2024-09-03, modified 2026-08-10), defines a small Markdown format. In order, a file contains:
- An optional byte-order mark.
- An H1 with the name of the project or site. This is the only required section.
- A blockquote with a short summary.
- Zero or more Markdown sections without headings, with more detail.
- Zero or more sections under H2 headings containing "file lists": Markdown lists where each item has a required
namelink, optionally followed by a colon and notes.
v2 also allows llms.txt at any path, not only the root (for example /docs/llms.txt covering the docs), recommends clean Markdown versions of pages at the same URL with .md, and suggests rel="alternate" type="text/markdown" and rel="describedby" link relations so agents can find them. An "Optional" H2 section marks links an agent can skip.
So a good validator checks, at minimum: the H1 exists and is first, the summary blockquote, that H2 sections contain properly formed link lists, and that the links resolve. Checking /llms-full.txt and path-level files is a bonus.
llms.txt validators compared
| Tool | Input | Checks structure | Tests every link | llms-full.txt | Notes |
|---|---|---|---|---|---|
| llms-txt-validator.dev | Domain | Yes: H1, blockquote, H2 sections, lists | Yes | Not stated | 0 to 100 score across structure, links and best practices |
| TrustSEO llms.txt Checker | Domain | Yes, against the llmstxt.org format | Not stated | Yes | Free, no signup; shows title, summary, sections and link count |
| AI Rank Lab | URL, domain or pasted file | Yes, follows the spec's required order | Not stated | Yes | Free, no sign-up |
| llmstxtchecker.net | URL or pasted file | Yes: Markdown, H1, quote block, file lists | Not stated | Not stated | Lists its validation rules openly |
| Hota.Digital | Domain | Yes, aligned with the v2 proposal | Not stated | Not stated | Separates required structure from a guidance score |
| Kenso llms.txt checker | Domain | Yes, against the proposal | Not stated | Yes | Confirms the file is served as text |
| Lighthouse (llms.txt audit) | Page audit | No | No | No | Flags a server error on /llms.txt; a 404 is "Not Applicable" |
| Audra | Whole-site audit | Yes: H1 title followed by a blockquote summary | Internal links checked site-wide, not inside llms.txt | Detects it | One of 8 AEO checks, worth 10% of the AEO score |
"Not stated" means the tool's page does not claim the feature; it may still do it.
The 8 llms.txt validators in detail
1. llms-txt-validator.dev: best for broken links in llms.txt
You enter a domain; it fetches /llms.txt, validates the H1 title, blockquote summary, H2 link sections and list formatting against the specification, and, unlike most tools, requests every linked URL and flags broken ones. Each issue comes with a recommendation and a 0 to 100 score.
Use it when your llms.txt has grown long and links may have gone stale.
2. TrustSEO llms.txt Checker: best quick check with llms-full.txt
TrustSEO fetches and validates both /llms.txt and /llms-full.txt against the llmstxt.org format, shows the parsed title, summary, number of sections and links, and gives plain fixes for anything missing. It is free with no signup.
3. AI Rank Lab: best for pasted drafts
AI Rank Lab accepts a URL, a bare domain or the raw file pasted in, and checks it in the spec's order: optional BOM, required H1, blockquote, detail blocks and H2 file lists. It looks for both /llms.txt and /llms-full.txt at the root.
Use it when you want to validate a draft before deploying it.
4. llmstxtchecker.net: best for transparent rules
It accepts a URL or pasted content and publishes its rules: valid Markdown, a required H1 title, a quote block with the summary, optional detail sections, and H2-separated file lists with name links and optional notes.
5. Hota.Digital: best for the v2 proposal
Hota.Digital says its checker is aligned with the llmstxt.org v2 proposal updated in August 2026, including path-specific files such as /docs/llms.txt. It separates the required-structure result (the H1 rule and recognisable Markdown) from a guidance score for optional details, and states plainly that llms.txt is an optional discovery format, not a ranking or citation guarantee.
6. Kenso llms.txt checker: best quick live check
Kenso (formerly Ken AI) fetches the file live, confirms it exists and is served as text, checks its structure against the proposal, and looks for the optional /llms-full.txt.
7. Lighthouse llms.txt audit: useful, but not a validator
Chrome's Lighthouse documentation includes an llms.txt audit under agentic browsing. Lighthouse flags the page if a server error occurs when it tries to fetch /llms.txt; if the file is missing (a 404) the audit is marked Not Applicable, because the file is optional. It does not validate the file's structure.
8. Audra: best for llms.txt in a full AEO audit
Audra's llms.txt check confirms that /llms.txt exists and is structurally valid per llmstxt.org (an H1 title line followed by a blockquote summary) and detects /llms-full.txt. It is one of eight answer-engine checks, worth 10% of Audra's AEO score, alongside the checks that usually matter more: whether robots.txt allows the retrieval bots that produce citations (ChatGPT-User, OAI-SearchBot and PerplexityBot, 30% of the score), structured data, answer-first structure, freshness and internal links. Audra is a desktop app for macOS on Apple Silicon and Windows 10/11, $19 once (launch price; regular price $49, also one-time) after a free 7-day trial.
Note: v2 makes the blockquote optional in principle (only the H1 is required), so treat a missing summary as a recommendation rather than a hard error, whichever tool reports it.
Common llms.txt errors to check for
- No H1, or the H1 is not first. The H1 is the only required element.
- Links without Markdown link syntax in H2 sections, such as bare URLs instead of
name. - Broken or redirected links, often after a site restructure.
- The file served as HTML, or behind a redirect, instead of plain text at /llms.txt.
- Extra heading levels inside the file (H3 and below); the format only uses H1 and H2.
- Private or staging URLs listed in a public file.
Does llms.txt matter for AEO?
It is a low-cost addition, but it is not what decides citations. Blocking a retrieval bot in robots.txt stops that engine from fetching your pages at all, whatever your llms.txt says, and Google says there are no additional technical requirements for appearing in its AI features beyond normal Search eligibility. Fix bot access and page quality first; see AI crawlers, robots.txt and verifying bot traffic and what AI crawlers can see.
FAQ
How do I validate my llms.txt file?
Paste your domain or file into a free validator such as llms-txt-validator.dev, TrustSEO, AI Rank Lab or llmstxtchecker.net. Confirm the file starts with an H1, has a blockquote summary, uses H2 sections with name list items, and that every link returns 200.
What is required in an llms.txt file?
Under the llmstxt.org v2 proposal, only an H1 with the name of the project or site is required. A blockquote summary, detail paragraphs and H2 file lists are recommended. The file can live at the root (/llms.txt) or at a subpath such as /docs/llms.txt.
Does Google use llms.txt?
Google has not said its Search systems use llms.txt, and its AI features guidance lists no additional technical requirements beyond normal Search eligibility. Chrome's Lighthouse does include an llms.txt audit, but it only checks that fetching the file does not cause a server error.
What is llms-full.txt?
A companion convention to llms.txt that contains the expanded content itself rather than an index of links. Several validators, including TrustSEO, AI Rank Lab and Kenso, check for it, and Audra detects it during an audit.
Is llms.txt the same as robots.txt?
No. robots.txt tells crawlers what they may fetch; llms.txt gives agents a curated, readable map of useful content. The llmstxt.org proposal describes llms.txt as complementing robots.txt and sitemaps, not replacing them.
Sources
- https://llmstxt.org/
- https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt
- https://llms-txt-validator.dev/
- https://trustseo.me/tools/llms-txt-checker
- https://airanklab.com/tools/llms-txt-checker
- https://llmstxtchecker.net/
- https://hota.digital/t/llms-txt-checker
- https://ken.so/tools/llms-txt-checker
- https://audra.greta.sh/