AI Readiness
The 11 AI-search readiness signals, how the score is computed, and what it does not claim.
AI readiness measures whether your page is legible to AI crawlers and answer
engines. It is a checklist of 11 signals, each grounded in a specific captured
artefact. Methodology version: 2026-08-14.
The 11 signals
| Signal ID | Evidence source |
|---|---|
ai-llms-txt | llms.txt probe |
ai-bot-gptbot | robots.txt |
ai-bot-oai-searchbot | robots.txt |
ai-bot-claudebot | robots.txt |
ai-bot-perplexitybot | robots.txt |
ai-bot-google-extended | robots.txt |
ai-bot-applebot-extended | robots.txt |
ai-jsonld-types | captured JSON-LD |
ai-semantic-landmarks | captured HTML |
ai-entity-clarity | captured JSON-LD |
ai-extractable-html | captured HTML |
The crawler-permission signals read your live robots.txt. The content
signals read the HTML and JSON-LD that were actually fetched during the
audit, not what you think is deployed.
The score
score = round(100 * passes / measured signals)- Measured signals are
pass,warning, andfail. Awarningis measured but does not count as a pass: no partial credit. unavailablesignals are excluded from the denominator. An unreachable robots.txt does not drag the score to zero.- Bounds:
0..100. No signal measured at all: the score isnull, shown as an unmeasured dash, not asLimited.
The grade
| Grade | Range |
|---|---|
| Strong | 75 and above |
| Mixed | 50 to 74 |
| Limited | below 50 |
| unmeasured | null score |
What this score is and is not
The checklist is experimental. It measures readiness signals: crawler permissions, structured data types, semantic landmarks, entity clarity, extractable HTML. It does not and cannot predict:
- Whether a real provider crawler visited your site.
- Whether your content gets cited in AI answers.
- Rankings, traffic, or revenue.
A spoofed user-agent request does not prove a real provider crawler was blocked or allowed, and robots permission does not prove a crawler came. If you want observed AI-answer behaviour rather than readiness signals, that requires external observation, which is reported separately with its own sample counts.
Improving the score
Each signal's finding links to the exact artefact that failed. Common fixes, in rough order of leverage:
Add llms.txt
A curated Markdown index at your site root for AI tools. The single highest-leverage missing file.
Permit AI crawlers in robots.txt
Explicitly allow GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, and the data-usage tokens.
Ship well-formed JSON-LD
Concrete entity types on key pages, readable from the served HTML.
Use semantic landmarks
main, nav, header, footer: structure that extraction tools can parse.
Keep content extractable
Primary content in served HTML, not only in client scripts.
Fixes are verified the same way everything else is: re-scan, compare signal by signal.
