The AI Readiness Score
Every scan produces a single AI Readiness Score from 0 to 100. It combines three sub-scores, each targeting a different dimension of how well your site works with AI systems.
AI Readiness Score = (Crawlability × 0.40)
+ (Agent Readiness × 0.30)
+ (Agent Interaction × 0.30)
All three sub-scores are themselves 0–100. The final score is rounded to the nearest integer.
The Three Sub-Scores
| Sub-score | Weight | Question it answers |
|---|---|---|
| Crawlability | 40% | Can AI crawlers see your content? |
| Agent Readiness | 30% | Can AI agents act on your content? |
| Agent Interaction | 30% | Can visual AI agents navigate your site? |
Crawlability (40%)
Measures how much of your page's content reaches an AI crawler that does not execute JavaScript. Checks content visibility ratio, semantic HTML structure, markup noise, and Schema.org JSON-LD presence.
A site that relies entirely on client-side rendering typically scores near zero on this dimension regardless of how well everything else is set up.
Agent Readiness (30%)
Measures how actionable your content is for AI agents that need to understand, summarize, or use your site programmatically. Checks OpenGraph and Schema.org metadata completeness, whether the server supports Markdown content negotiation or exposes an llms.txt file, how discoverable pricing and CTAs are in the HTML, and adoption of AI-specific standards in robots.txt and sitemap.xml.
Agent Interaction (30%)
Measures how well visual AI agents — ones that take screenshots and interact with the DOM — can navigate your site. Checks semantic HTML5 landmark usage, interactive element accessibility (labels, aria-label), navigation structure, and whether visual elements are consistent with their semantic meaning.
Check Importance
Each sub-score is composed of four checks. Some checks carry more weight than others within their sub-score.
| Sub-score | Check | Relative importance |
|---|---|---|
| Crawlability | C1 Content Visibility | High |
| C2 Structural Clarity | Medium | |
| C3 Noise Ratio | Low | |
| C4 Schema.org Presence | Low | |
| Agent Readiness | A1 Structured Data | Medium |
| A2 Content Negotiation | Medium | |
| A3 Machine-Actionable Data | High | |
| A4 Standards Adoption | Medium | |
| Agent Interaction | I1 Semantic HTML | Medium |
| I2 Accessibility | High | |
| I3 Navigation & Structure | Medium | |
| I4 Visual-Semantic Consistency | Low |
High-importance checks have the largest effect on the sub-score. A site that scores well on all High checks but poorly on Low checks will still achieve a strong overall score. Conversely, failing a High check is difficult to offset with the remaining checks.
Score Bands
| Score | Label |
|---|---|
| 0–20 | Critical |
| 21–40 | Poor |
| 41–60 | Fair |
| 61–80 | Good |
| 81–100 | Excellent |
Floor Rule
If any sub-score is below 20, the AI Readiness Score is capped at 60, regardless of what the weighted formula would otherwise produce.
This prevents a site from appearing "fair" or "good" overall while being completely broken on one dimension. For example: a site with 95 Crawlability, 95 Agent Readiness, and 5 Agent Interaction would compute to a weighted score of 60.5, but the floor rule caps it at 60.
noindex Cap
If a page sets noindex in its meta robots tag or X-Robots-Tag response header, the AI Readiness Score is hard-capped at 20. A noindex directive signals that the page is intentionally hidden from all crawlers, so a higher score would be misleading.
Score Freshness
Scans are cached for 24 hours. Requesting a scan for the same URL within that window returns the cached result. The scannedAt field in the API response tells you when the scan ran.