See what AI actually reads on your website
Paste any public URL. This reads the raw HTML, the version a crawler sees before JavaScript runs, and reports what a machine can and cannot understand about the page. No signup, no email, no score out of ten.
Why raw HTML
Google renders JavaScript reliably. Many AI crawlers and answer engines read the raw HTML first, or only. Checking what survives before hydration shows you the version of your site that a large part of your machine audience actually receives.
What each result means
Readable means the signal exists in the document where a machine expects to find it. Worth fixing means it exists but is weak, ambiguous, or likely to be truncated. Missing means the signal is not there at all, and any system reading the page has to infer or skip it.
The findings that matter most are the ones about text and structure. A page with no h1, no structured data, and almost no text before JavaScript runs is not a design problem. It is a page that answer engines have to guess about, and guesswork loses to any competitor who made the same facts explicit. That reasoning is unpacked further in what an AI-readable website is.
A machine does not judge your page. It reads what passes through, and reports only what it could actually resolve.
Common questions
What does this checker actually look at?
It fetches the raw HTML of the URL without running any JavaScript, which is what many AI crawlers see, then reports the title, meta description, heading tree, JSON-LD structured data, alt text coverage, canonical tag, and how much text survives before hydration. It also checks robots.txt for AI crawler rules, plus sitemap.xml and llms.txt at the site root.
Why check the raw HTML instead of the rendered page?
Google renders JavaScript reliably. Many AI crawlers and answer engines read the raw HTML first or only. If your meaning only appears after hydration, part of your machine audience never receives it. Checking the raw HTML shows you that gap directly.
Is a pass on everything enough to rank in AI answers?
No, and it is worth being honest about that. This checks whether machines can read your site accurately. Being cited ahead of competitors they can also read takes more: proof, consistency across the web, and authority. Readable is the floor, not the finish line.
Do you store the URLs people check?
No. The check runs on request and the result is returned to your browser. Nothing is saved, and no email address is required to see the findings.
Can I see how it works, or run it myself?
Yes. The checker is open source under the MIT licence at github.com/reidifydesign/ai-readability-checker. It is a single dependency-free module, so you can read exactly what it measures, run it locally, or use it in your own build.
AI-readable websites
The full standard behind every check this tool runs.
What is answer engine optimization
Readability is the floor. Citation is the goal.
AI visibility audit
The human version: proof, consistency, and what to fix first.
What answer engines actually read
How crawlers parse a page, in detail.