1. Scoring Principles
Separated ownership
Checks own their internal step weights. The assessment suite owns category, subcategory, and check weights. That keeps versioned check behavior isolated from suite composition.
Active denominators
Informational and not-applicable results are displayed when useful, but they are removed from the scoring denominator so irrelevant checks do not punish a page.
Rounded report scores
Each weighted average is rounded to a whole number and clamped between 0 and 100 before it is shown in the report.
2. Formula Chain
A report score rolls up from the smallest scored unit to the final score. The chain below mirrors the current runtime behavior.
Step value
pass = 100, warning = 50, fail = 0
Informational and not-applicable steps do not enter the active denominator.
Check score
sum(step value x step weight) / sum(active step weights)
The versioned check package owns the step list and step weights.
Subcategory score
sum(check score x check weight) / sum(scored check weights)
The suite owns which checks belong to each subcategory and how much each check counts there.
Category score
sum(subcategory score x subcategory weight) / sum(scored subcategory weights)
Subcategories without scored checks are omitted from the category denominator.
Agent readiness
sum(category score x category weight) / sum(scored category weights)
The published suite manifest owns category weights.
Overall score
agent readiness x 0.75 + Performance x 0.10 + accessibility x 0.15
Performance and Accessibility are blended as independent technical slices when requested.
3. Suite Category And Subcategory Weights
The active suite is can-agent-use-agent-readiness@2026.06.10. Category weights are relative contributions to agent readiness, and the published report-card categories sum to the final overall score. Agent readiness contributes 75% of the overall score when Performance and Accessibility are both requested.
| Category | Category Weight | Subcategories | Checks |
|---|---|---|---|
| Discoverability | 0.09 | Crawl Discovery 1 | 4 |
| Content Readiness | 0.09 | Page Structure 1Structured Entities 1 | 7 |
| GEO, AIO & AEO | 0.1 | AI Answer Readiness 1 | 3 |
| Bot Access Control | 0.08 | Bot Policy 1 | 6 |
| Security & Trust | 0.1 | Browser Trust 1 | 5 |
| API | 0.06 | API Discovery 1 | 2 |
| Auth | 0.06 | Auth Discovery 1 | 3 |
| MCP | 0.06 | MCP Discovery 1 | 2 |
| Skill Discovery | 0.06 | Agent Capability Discovery 1 | 4 |
| Agent Commerce | 0.06 | Commerce Protocols 1 | 4 |
Check weights live one level deeper in the same suite manifest. For example, this suite pins 40 runnable check packages, each with its own suite-level check weight and isolated package-level step weights.
4. Technical Score And Final Overall
Performance
Desktop performance x 0.10
The final overall score gives Performance 10% weight when requested. If skipped, that weight is redistributed to agent readiness.
Final Overall
agent readiness x 0.75 + Performance x 0.10 + accessibility x 0.15
The result is rounded to a whole number and shown as the main report score.
Optional-mode fallback: skipped technical slices are redistributed to agent readiness.
SEO is still shown as its own report row. In suite 2026.06.10, displayed as its own report score row. This version does not blend the SEO score into the final overall score.
5. Readiness Levels
The final rounded score maps to a readiness label. The label is descriptive; it does not change the underlying numeric score.
| Score Range | Readiness Label |
|---|---|
90-100 | Level 5, Agent-Ready |
75-89 | Level 4, Mostly Ready |
50-74 | Level 3, Bot-Aware |
25-49 | Level 2, Agent-Limited |
0-24 | Level 1, Not Agent-Ready |