1. Input URL or Markdown
Enter your live production URL (e.g. yourdomain.com/llms.txt) to test live HTTP headers and link status codes, or paste draft Markdown directly from our free generator.
llms.txt Validator
Score Your Website's AI Readiness
Validate your llms.txt file by domain or pasted content. Audit Markdown structure, link accessibility, and description quality with an AI Readiness Score.
Input Route
Choose What to Scan
Live Output
Readiness Report
86
AI Readiness Score
Strong foundation. Fix the listed structure issues next.
Choose an input route to begin.
Automated Linter
Test Compliance Against the Official llmstxt.org Standard
An invalid file can cause AI parsers in Perplexity, Claude, or ChatGPT to fail or skip your content entirely. Our llms.txt validator audits your file for broken links, syntax collisions, missing link descriptions, and header hierarchy violations in seconds.
✓ Instant 0-100 Score✓ Live Link Status Check✓ Prioritized Fix List
Quality Assurance
Why Validating Your LLMs.txt File is Critical for AI Crawlers
Publishing an unverified file is risky. When autonomous AI crawlers (like GPTBot, ClaudeBot, and PerplexityBot) encounter malformed Markdown, they do not debug your formatting: they abandon the index and fall back to brute-force crawling.
Preventing Parser Crashes and Lost Citations
The community specification established at llmstxt.org requires strict structural conformance. If a file contains multiple H1 tags or improperly nested bullet points, automated Markdown tokenizers can split the document incorrectly.
When links lack descriptive summaries, language models cannot determine page relevance. A bare link like /pricing provides no clue whether it includes enterprise volume discounts or free trial policies.
Validating before publishing ensures your site presents a flawless knowledge map that AI systems can read, trust, and cite in user answers.
Catching Dead URLs and Insecure Redirects
Websites evolve rapidly. As pages are renamed, relocated, or deleted, knowledge maps frequently retain broken links that return 404 errors or excessive 301 redirect chains.
Every dead link in your knowledge file wastes AI crawling quotas and degrades the perceived reliability of your domain.
Pairing our free llms.txt generator with this validator ensures that every URL is tested for live HTTP 200 OK status codes and correct protocol handling.
Methodology
The 3 Pillars of the AI Readiness Score
Our automated scoring algorithm evaluates your file on a scale of 0 to 100 based on three technical dimensions:
35%
1. Structure & Syntax
Verifies that exactly one H1 header exists, followed by an optional blockquote description. Ensures all category headers use standard H2 Markdown and list items follow standard bullet syntax without parsing collisions.
35%
2. Content & Descriptions
Checks that every Markdown link includes a descriptive summary after a colon. Penalizes vague or generic descriptions (like "Click here" or "Documentation") that fail to explain page content and target audience.
30%
3. Link Health & URLs
Checks that every link uses an absolute URL starting with https:// rather than a relative path. Verifies that public endpoints resolve properly and are not blocked by authentication gates or robots.txt directives.
Standard Rules
Official llmstxt.org Compliance Checklist
Verify each of these mandatory requirements before deploying your knowledge file to production:
✓
Single H1 Project Title
The file must start with exactly one H1 header stating your organization, project, or domain name.
✓
Blockquote Mission Statement
A blockquote summary directly beneath the H1 providing a factual 1-2 sentence overview of your site.
✓
Logical H2 Categories
Links grouped into intuitive categories such as Docs, Products, Tutorials, Guides, and Company.
✓
Valid Markdown Link Syntax
All entries must follow the pattern - [Page Title](https://example.com/url): Description.
✓
Absolute HTTPS URLs
Avoid relative links (/about). Every URL must include full scheme and domain for external crawler compatibility.
✓
Reserved "Optional" Section
Secondary links (terms, changelogs, system status) placed under ## Optional so models can skip them when context is constrained.
Troubleshooting Guide
7 Common LLMs.txt Errors & How to Fix Them
Review these real-world formatting mistakes flagged by our audit engine and apply the exact fixes:
Error 01
Multiple H1 Headers
The specification permits only one top-level H1 header. Using multiple H1s confuses parsers regarding domain identity.
Incorrect (Multiple H1s):
# Acme Analytics
# Documentation
Correct (H1 then H2s):
# Acme Analytics
## Documentation
Error 02
Missing Colon and Summary Description
A link without a description forces the language model to guess what information the page provides.
Incorrect (Bare Link):
- [Quickstart](https://example.com/docs)
Correct (Colon with Summary):
- [Quickstart](https://example.com/docs): Step-by-step setup guide for developers.
Error 03
Relative URLs Instead of Absolute HTTPS
When an AI agent reads an llms.txt file externally, relative paths fail to resolve without domain context.
Incorrect (Relative Path):
- [Pricing](/pricing): Tiers and billing.
Correct (Full HTTPS URL):
- [Pricing](https://example.com/pricing): Tiers and billing.
Syntax Rules
Valid vs Invalid Syntax Comparison
Quick reference guide for common syntax constructs:
| Element | Valid Syntax Example | Invalid Pattern to Avoid |
|---|---|---|
| Project Header | # Acme Corp | # Acme Corp <br> # Second Header |
| Blockquote Intro | > Factual 1-sentence site summary. | Raw text without > blockquote symbol |
| Category Section | ## Core Documentation | ### Deeply nested H3/H4 without H2 |
| Link List Item | - [Title](https://site.com/p): Summary. | * [Title](site.com/p) (missing dash & colon) |
| Secondary Links | ## Optional | ## Secondary / ## Other (use exact "Optional") |
Workflow Guide
How to Audit Your File in 3 Steps
Follow this verification cycle whenever updating website documentation:
2. Review Score & Findings
Examine your AI Readiness Score out of 100. Inspect prioritized issues categorized by severity: critical syntax errors, warning-level link issues, and quality suggestions.
3. Apply Fixes and Re-Test
Make the required edits to your live server file or in-browser draft. Re-run the validator to confirm a 90+ score and complete structural compliance before saving.
Frequently Asked
Validator FAQ
Common questions regarding validation checks, error troubleshooting, and score optimization.
How is the AI Readiness Score calculated?
The score evaluates three core dimensions: Structural Compliance (35%) checking for a single H1, valid markdown headings, and blockquotes; Content Quality (35%) assessing summary clarity, length, and descriptive detail; and Link Health (30%) testing public accessibility and URL formatting.
Can I validate an llms.txt file before publishing it live?
Yes. Switch the input selector to "Paste File" to test raw Markdown text directly. The validator will analyze syntax and formatting without needing a public URL.
What are the most common llms.txt formatting errors?
The three most frequent errors are: multiple H1 headings (the specification permits only one), omitting descriptions after markdown links, and using relative paths instead of absolute https:// URLs.
How often should I validate my live file?
We recommend testing your llms.txt file after major site redesigns, content restructures, or whenever you add new product documentation to ensure all links remain live and return 200 OK status codes.
Does this tool validate llms-full.txt files as well?
Yes. You can paste the contents of an llms-full.txt document to check for proper heading hierarchies, valid markdown code fences, and clean URL references.
Why did my file receive a lower score for link health?
Lower link scores typically result from relative links (such as /docs instead of https://example.com/docs), destination URLs returning 404 or 500 status codes, or links protected behind password authentications or bot firewalls.
Switch Tools Anytime