agentspeed.
Leaderboards

Documentation leaderboard

0 domainsupdated every 5mno scans yet

Reference and API documentation sites. Agents and RAG pipelines fetch these heavily, so readable structure, content negotiation, and a published rubric of sections matter most.

Not enough scan data yet.

We surface only real, completed public scans. Once enough documentation domains have a public score on AgentSpeed, this leaderboard fills in automatically.

Scan your site →
What makes a site agent-ready in this category

Documentation sites are read more aggressively by AI agents than any other category, because RAG pipelines pull them as first-party knowledge sources. The discriminator is structure: clear H1/H2/H3 hierarchy, anchor-linkable sections, no JS-required code samples, and an /llms.txt that lists the actually-canonical pages.

Common failures
failure 01

Code samples are JS-rendered

When the actual code lives in a syntax-highlighted React component, agents see a placeholder. Render the literal code in the SSR HTML.

failure 02

Versioned URLs without canonicals

When /v1/, /v2/, and /latest/ all serve the same docs, agents cite three URLs and split the citation count.

failure 03

Search box only, no nav

Sites that hide the table of contents behind a search modal are unnavigable to agents that read SSR HTML.

failure 04

No deep-anchor links

Headings without id="…" make it impossible for agents to cite a specific paragraph.

Best practices
  1. 01Render code samples literally in the SSR HTML, not inside JS components.
  2. 02Add id="…" anchors to every H2 and H3 so agents can deep-link.
  3. 03Set rel=canonical on versioned pages to /latest/.
  4. 04Publish /llms.txt with the docs index, the API reference, and the changelog.
  5. 05Add Article + BreadcrumbList JSON-LD per page.
How this is computed

Each row is the latest completed public scan for one domain. Composite is a 0–100 weighted average of five sub-scores; grade is bound to a published band table. The rubric (current and prior versions) is at /rubric.

FAQ

How are scores calculated?

Every score is the output of the public AgentSpeed rubric. The full check list, weights, and grade bands are at /rubric. New scans use the current active rubric; historical scans render against their original rubric.

How do I get my domain on the leaderboard?

Visit the scanner and submit a URL to generate a score. Every completed public scan creates a permanent score page and makes the domain eligible for ranking. There’s no application process and no editorial gate.

How do I remove my site?

Add User-agent: AgentSpeedBot / Disallow: / to your robots.txt. On the next scan we honour it automatically and the public score page is replaced with a removal notice. See /bot.

Improve your own site
Run free scan

Scan a docs URL to see how an agent reads its structure + canonicalisation.

Compare your site

Side-by-side composite, sub-scores, and per-category winner. Permanent shareable URL.

Browse fixes

Every check in the rubric has a remediation page with paste-ready snippets.

All free tools

Crawler matrix, llms.txt analyzer, structured-data validator, and seven more.