How to Build a Website That Search Engines & Users Love
Combine technical SEO with great UX to rank higher and convert better.
Paste your llms.txt, upload the file, or enter its URL. Get a score out of 100, 10 detailed spec checks, duplicate detection, token count, and specific fix suggestions in under a second.
Paste your llms.txt, upload the file, or enter its URL. Get a score out of 100, 10 detailed spec checks, duplicate detection, token count, and specific fix suggestions in under a second.
Every AI model that visits your website - ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews - looks for an llms.txt file at the root of your domain. A well-formed file tells these models exactly what your site does, which pages matter, and how to cite you accurately. A poorly formatted one gets ignored entirely, costing you traffic from the fastest-growing source on the web: AI-powered search.
This free llms.txt validator checks your file against the official llmstxt.org specification and scores it out of 100. It runs 10 checks covering every structural requirement: the required H1 site name heading, the blockquote description that explains what your site does, at least one H2 section to organize content, correct Markdown link syntax on every link, valid and accessible URLs, duplicate URL detection across sections, proper Optional section usage for large files, link description length compliance, file size and token count relative to AI context windows, and whether the site name carries meaningful identity rather than a default placeholder.
Each check is weighted by its importance. An H1 heading is worth 10 points. Valid link format is worth 15 points. Invalid links make AI models parse your file incorrectly - that is why it carries the highest weight. The score reflects real AI readability, not cosmetic preferences.
You get three ways to validate. Fetch URL is the fastest: enter the public address of your live llms.txt and the tool fetches and checks it server-side, bypassing any browser CORS restrictions. Upload .txt lets you drag or browse to your local file before you deploy. Paste File lets you test drafts or audit competitor files you have copied. All three produce the same full results.
After validation you get a letter grade, a summary of what passed and failed, and a detailed What to Fix section listing every failed or warned check with the exact change needed. Fix the highest-point items first, use the Re-validate button to confirm your changes, and then deploy. If you do not have an llms.txt yet, use the llms.txt Generator on this site to create a fully spec-compliant file in seconds, then come back here to validate it before publishing.
Everything you need in one amazing tool
Get a clear numeric score and letter grade (A to F) showing how well your llms.txt follows the official spec - shareable and easy to track over time.
Every check maps directly to the official llmstxt.org spec: H1, blockquote, sections, link format, URL validity, duplicates, Optional section, description length, file size, and site name quality.
Every failed check comes with the exact change needed - not vague advice. Fix the highest-point items first and use Re-validate to confirm without re-entering your content.
Fetch any live llms.txt by URL, upload a local .txt file before deploying, or paste content directly. All three methods produce the same full validation results.
Identifies repeated URLs across all sections automatically. Duplicates waste AI context window space and confuse models about which link to prioritize.
Shows estimated token count with color-coded context window status - green (safe), yellow (approaching limit), red (too large) - so you know before AI models silently truncate your file.
Get started in 4 easy steps
Enter the URL of your live llms.txt to fetch it server-side, upload a local .txt file before deploying, or paste content directly into the editor.
Click Validate and the tool runs 10 spec-accuracy checks against the official llmstxt.org standard in under a second - no waiting, no server processing for paste or upload.
Get a score out of 100, a letter grade (A-F), token count with context window status, and a full breakdown of every check showing pass, warn, or fail status.
Follow the exact fix instructions for each failed check, update your file, and click Re-validate to confirm every improvement before publishing your llms.txt.
Stand out from the competition
Every rule maps to the official llmstxt.org spec - no invented requirements, no guesswork. Your score reflects real AI readability.
A numeric score out of 100 and a letter grade give you an instant, trackable measure of file quality you can improve over time.
Every failed check tells you precisely what is wrong and what to change - not vague suggestions. Highest-impact fixes are listed first.
Validate live files by URL, local drafts by upload, or copied content by paste. Audit your file or any competitor's - no sign-in, no limits.
Token count and color-coded size rating show whether your file fits inside AI context windows before it causes silent parsing failures.
Paste and upload modes run entirely in your browser. No content is stored or logged anywhere. Results appear in under a second.
See how others are using this tool
Validate your newly created llms.txt before uploading to ensure it is fully spec-compliant from day one.
Check a file that has been live for months to find issues that may have been missed during initial creation.
Enter any public llms.txt URL to benchmark against competitors and learn from industry leaders like Anthropic or Supabase.
Re-validate any time you manually edit your llms.txt to catch formatting errors introduced during updates.
Run a monthly validation as you add new content to your site and update your llms.txt to keep it spec-compliant.
Quickly audit llms.txt quality for multiple client sites as part of a technical SEO review or GEO audit.
Everything you need to know about llms.txt Validator
llms.txt is a plain Markdown file placed at the root of your website (e.g. https://yoursite.com/llms.txt) that gives AI language models a clean, structured guide to your site. AI tools like ChatGPT, Perplexity, Claude, and Google AI Overviews look for this file when deciding how to represent your content. A well-formed llms.txt helps AI models cite you accurately, understand what your site offers, and surface your pages in AI-generated answers - making it a key part of generative engine optimization (GEO).
The validator runs 10 checks against the official llmstxt.org specification: (1) H1 heading present, (2) blockquote description included, (3) at least one H2 section exists, (4) all links use correct Markdown format, (5) all link URLs are valid, (6) no duplicate URLs across sections, (7) Optional section usage when file is large, (8) link descriptions are under 200 characters, (9) file size and token count relative to AI context windows, and (10) site name is meaningful rather than a generic placeholder.
A score of 90 or above (grade A) means your file is excellent and fully spec-compliant. 75-89 (grade B) is good with minor improvements possible. 55-74 (grade C) means there are real issues affecting how AI models read your file. 35-54 (grade D) indicates significant structural problems. Below 35 (grade F) means the file has critical issues that need immediate fixing before AI models can use it. Aim for A or B before deploying.
Start with the highest-point failures first. Missing an H1 heading costs 10 points, a missing blockquote costs 10 points, and invalid link format costs 15 points - fixing these three alone can recover 35 points. The 'What to Fix' section below your score lists every failed or warned check with the exact change needed. Fix, then click Re-validate to confirm without re-entering your content. If you are starting from scratch, use the llms.txt Generator to build a fully valid file automatically.
Yes. Switch to the Fetch URL tab, enter any public URL ending in llms.txt, and the tool fetches and validates it. This is useful for benchmarking against industry leaders like Anthropic, Supabase, Cloudflare, Vercel, or Cursor - all of whom publish llms.txt files. Comparing your score to theirs shows exactly where you need to improve.
A 'fail' means a required element is completely missing or broken - for example, no H1 heading or invalid Markdown link syntax. These cost the full points for that check. A 'warn' means the element exists but does not fully meet best practices - for example, a link description that is slightly too long or a file size that is approaching AI context window limits. Warns cost partial points. Both appear in the 'What to Fix' section.
No. When you paste content or upload a file, validation runs entirely in your browser - no data is sent to any server. When you enter a URL, our server fetches only the text content of that URL to bypass browser CORS restrictions, but the content is never stored, logged, or processed beyond returning the raw text to your browser for client-side validation.
The llmstxt.org specification defines '## Optional' as a section for lower-priority pages that AI models can skip when they need a shorter context window. This validator only requires an Optional section when your file has more than 10 links AND is large enough to approach AI context window limits (roughly 125,000 tokens or more). If your file is small, Optional is recommended but not penalized. Large files without an Optional section force AI models to either read everything or nothing - the section gives them a smart middle ground.
The token count estimates how many tokens your llms.txt uses inside an AI model's context window, calculated as characters divided by 4. Green (under 125K tokens) means your file fits comfortably in all modern LLMs. Yellow (125K-180K) means you are approaching limits and smaller or older models may truncate your file. Red (above 180K) means your file is too large for many models. Keep your file green by using the Optional section for lower-priority pages and keeping link descriptions concise.
Validate every time you add new pages or sections to your site, update your site description, or change your URL structure. At minimum, run a validation once a month to catch any links that have gone dead or URLs that have changed. Treat your llms.txt like a sitemap - it should always reflect the current state of your site.
Use our free tools to perfect your content and design, then build your full website yourself. No code needed, no developers to hire, no waiting.