The AI-readiness diagnostic
A read-only check of whether AI crawlers can reach and parse what you want cited — ordered by evidence, not by folklore.
The diagnostic checks a target page against the things that demonstrably affect whether an AI engine can use it. It is strictly read-only: it reports, it does not fix.
Checked, in order of evidence
- Per-bot crawler access. GPTBot, OAI-SearchBot, ClaudeBot, Claude-SearchBot, PerplexityBot and Google-Extended, checked individually — including CDN and WAF blocking, which is the common silent failure. A default bot-fighting configuration can block AI crawlers without anyone deciding to.
- Content present in the initial HTML. No major AI crawler executes JavaScript. Content that only exists after hydration does not exist to them.
- Answer-first chunk structure. Whether a page states its answer near a heading, in a passage that can be lifted, rather than burying it after four paragraphs of preamble.
- Schema markup. A supporting signal — real, but well below the three above.
Reported as informational only
`llms.txt`. We check for it and report it, and we tell you plainly that the evidence for it is close to nil: across half a billion bot events, requests for the file numbered in the hundreds, and Google has said explicitly that it ignores it. We report it because clients ask about it. We do not score it.
Saying that out loud costs a feature bullet and buys the thing the bullet was for.
See it against your own client list
A working demo runs your prompts, in your market, on live engines — not a sandbox with seeded data. Bring one client brand and three competitors.