Check a page for AI search readiness
Inspect a public page, its crawler rules and site files, then review a short list of fixes.
The checker reads the page and its site's robots.txt, sitemap.xml and llms.txt files.
How it works
The checker reads the initial HTML, response status and time, title, description, canonical and hreflang links, heading outline, JSON-LD types, indexing directives, and Open Graph fields.
It checks robots.txt rules for the documented crawler names, fetches llms.txt and a served sitemap, then drafts up to five fixes from the detected issues. Each result is a page signal, not a search visibility score.
Sources and checked dates
Limits
- This checks the public HTML and three site files at one moment. It does not measure rankings, citations, or crawler behavior.
- llms.txt is a proposal. Its presence does not show that any answer engine reads or uses it.
- A reachable page can still be excluded by crawler rules, authentication, or search engine decisions.
Common questions
- What does this checker fetch?
- It reads one public HTML page, then checks robots.txt, llms.txt and a served sitemap at the final page origin.
- Does a passing result mean AI answers will cite my page?
- No. The checks cover fetchable page signals, not indexing, rankings, answer selection, or citations.
- Do I need llms.txt?
- No. It is an optional proposal, and current evidence does not establish that publishing it improves citations.
Related tools
- AI robots.txt generator
Create and inspect robots.txt rules for documented AI crawlers.
- llms.txt generator
Generate an llms.txt draft using the llmstxt.org proposal format.
OperatorNest can take on repeat work, check with you before consequential steps, and leave a receipt for the result. See how an always-on operator works.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.