Public · versioned · auditable

The AgentSpeed rubric

version 2026.05.1grade bands v1

Every score is computed from this rubric. Weights are public; we publish a changelog when they change; historical scans retain their original rubric version.

Sub-score weights

discoverability

22%

readability

22%

structured_data

13%

actionability

28%

performance

15%

Grade bands

≥ 90

≥ 80

≥ 70

≥ 60

≥ 0

discoverability

robots_txt.presentA reachable robots.txt exists at the site root.1

robots_txt.allows_known_agentsrobots.txt does not disallow well-known agent user-agents (GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended).2

robots_txt.content_signalsrobots.txt advertises Content-Signal directives (e.g. `Content-Signal: ai-train=no, ai-summarize=yes`) that let agents respect granular usage preferences.2

llms_txt.presentAn llms.txt file at the site root helps agents locate your most-important content.1

sitemap.presentA sitemap.xml is reachable and referenced from robots.txt.1

discoverability.link_headersHTTP `Link:` response headers carry useful relations (canonical, alternate, describedby) that agents consume without parsing HTML.1

markup.canonicalA canonical URL is declared and resolves to the same page.1

discoverability.mcp_server_cardAn MCP Server Card is reachable at `/.well-known/mcp/server-card.json` (or referenced from a Link header) and validates against the Model Context Protocol spec.2

discoverability.oauth_authorization_server`/.well-known/oauth-authorization-server` is reachable and conforms to RFC 8414, letting agents discover authorization endpoints without out-of-band setup.1

discoverability.oauth_protected_resource`/.well-known/oauth-protected-resource` is published per RFC 9728 so agents can discover required scopes and authorization servers programmatically.1

discoverability.api_catalogAn API catalog is published at `/.well-known/api-catalog` (RFC 9727) or an OpenAPI document is reachable at `/openapi.json` or `/openapi.yaml`.1

discoverability.web_bot_authThe site signals support for the Web Bot Auth IETF draft (HTTP Message Signatures over a known JWKS) so well-behaved agents can prove identity.1

readability

readability.markdown_negotiationRequests with `Accept: text/markdown` return a markdown representation of the page (Markdown content negotiation).2

content.text_ratioVisible text makes up at least 15% of the rendered DOM weight.2

content.js_required_for_primary_contentPrimary content is visible without JavaScript.3

content.headings_hierarchyHeading hierarchy is well-formed (one H1, no skipped levels).1

auth.cookie_consent_blocks_contentA cookie-consent modal does not cover or block the primary content on first load.2

markup.titleA non-empty <title> is present and under 70 characters.1

markup.meta_descriptionA meta description is present and between 50 and 200 characters.1

structured data

structured_data.jsonld_presentAt least one valid JSON-LD block is present.2

structured_data.validatesJSON-LD validates against the declared schema.org type.2

structured_data.type_coverageDeclared JSON-LD types cover the apparent page purpose (e.g. a product page has Product, a blog post has Article).1

actionability

auth.paywall_or_login_wall_on_landingLanding URL is not gated by a login or paywall.3

journey.primary_probeA read-only LLM-driven probe can identify the primary offering and either its price or its primary call-to-action.4

reachability.statusLanding URL returns a 2xx after at most one redirect.2

actionability.agent_skillsAn Agent Skills manifest is reachable (e.g. `/.well-known/agent-skills.json`) describing discrete tasks an agent can perform on the site.2

actionability.web_mcpThe page exposes WebMCP (in-browser Model Context Protocol) so on-page agents can invoke tools without leaving the tab.2

performance

performance.ttfb_msTime-to-first-byte is under 800ms from a US-East origin.2

performance.full_render_msFull render (network idle) completes under 4 seconds.2

performance.payload_kbTotal page weight is under 3 MB.1

Changelog

2026.05.1 — Adds 10 checks for the emerging 2026 agent-protocol stack: Content Signals, Link Headers, MCP Server Card, OAuth authorization-server metadata, OAuth Protected Resource metadata, API Catalog, Web Bot Auth, Markdown content negotiation, Agent Skills, WebMCP. Sub-score weights rebalanced lightly to absorb the larger Discoverability + Actionability surfaces. 30 checks total.

2026.04.1 — Initial rubric. 20 checks across 5 sub-scores. Bands v1.