File availability
Fetches /llms.txt and /llms-full.txt with status, content type, byte count, and fallback-page detection.
AI-readable discovery
llms.txt Checker
Check whether a public site exposes usable llms.txt and llms-full.txt files, then see line-level structure checks alongside robots.txt, sitemap, metadata, and AI crawler access signals.
Real checks
What this tool actually tests
These pages use the same live scanner as the homepage. The difference is the focused report shown after the scan, not a separate static keyword page.
Markdown structure
Checks for a clear H1, short blockquote summary, H2 sections, Markdown links, and unfinished draft text.
Discovery alignment
Compares llms.txt with sitemap.xml, robots.txt, canonical URL, indexability, and AI crawler access.
Methodology
How the report stays evidence-based
The scanner is intentionally conservative: public URLs only, no login bypassing, bounded fetches, no saved reports by default, and no promise of AI ranking or citation.
Same-origin public fetch
The checker only requests public files on the submitted URL's origin and follows a bounded redirect chain.
Structure before promises
llms.txt is experimental, so the report grades whether the file is readable and useful, not whether AI systems will use it.
No saved scans by default
Submitted URLs are processed for the report response and are not stored as public reports by default.
Tool matrix
Related checks in the same suite
Use the matrix to move from a focused issue to the broader AI crawler and readiness report.
AI Crawler CheckerRun the full crawler access scan for robots.txt, AI bots, headers, page signals, sitemap, and llms.txt.llms.txt CheckerValidate AI-readable discovery files and see how they align with sitemap and crawler policy.AEO CheckerCheck technical Answer Engine Optimization readiness from public page and discovery signals.AI Search Visibility CheckerReview whether a URL has the technical foundations AI search systems need before any ranking or prompt testing.MethodologyUnderstand the scoring model, limitations, bot list, and privacy-first scanning boundary.
Limitations
What this checker does not claim
Clear boundaries make the report more useful: it diagnoses technical readiness, not guaranteed visibility.
Boundary
llms.txt adoption is still uneven across AI products.
Boundary
This checker does not guarantee AI visibility, citation, ranking, or inclusion in any answer engine.
Boundary
The free scan validates structure and related discovery signals; it does not recursively crawl every linked URL.
FAQ
Common questions
Short answers for searchers, site owners, and technical SEO teams comparing AI readiness tools.
What does this llms.txt checker validate?
It checks public /llms.txt and /llms-full.txt availability, content type, basic Markdown structure, summary and section presence, Markdown links, sitemap, robots.txt, and page-level AI-readiness signals.
Is llms.txt required for AI search visibility?
No. llms.txt is an experimental discovery file. A clean file can help expose important public pages, but it does not replace robots.txt, sitemap.xml, structured data, or useful content.
Can I check a direct llms.txt URL?
Yes. You can enter a domain, homepage, page URL, or direct file URL. The scanner normalizes the origin and checks the standard same-origin discovery files.
Do you store my llms.txt scan?
No. The current scanner is privacy-first and does not create public saved reports by default.