Back to leaderboard
Benchmark report

Docs benchmark report.

Report for

This report shows where agents can use these docs cleanly and where the biggest points of friction still are.

Last checked: May 4, 2026Category: OtherSource: Fern Agent Score
Score your docs
Benchmark score
97Grade A

This report passes 18 of 22 checks, with 3 warnings, 0 failed checks, and 1 skipped checks still shaping the next score lift.

Checks passed
18/22
Warnings
3
Failed checks
0
Key takeaways

What stands out first.

Start with what already works, then move to the fixes most likely to lift the score.

Working now

What already works.

  • Observability and Content Health is relatively strong at 100/100.
  • URL Stability and Redirects is relatively strong at 100/100.
  • Authentication and Access is relatively strong at 100/100.
Improve next

What to improve next.

  • LLMS TXT Size in Content Discoverability.
  • LLMS TXT Directive (HTML) in Content Discoverability.
  • Content Start Position in Page Size and Truncation Risk.
Check results

Full score breakdown

Open each category to review the checks behind the score and see exactly where agents still hit friction.

Page Size and Truncation Risk
3 passed1 warnings

Can an agent read the page without losing important context?

1 warning still need cleanup here.
Rendering Strategy

All 10 sampled pages contain server-rendered content

Page Size Markdown

All 10 pages under 50K chars (median 4K, max 10K)

Page Size Html

All 10 sampled pages convert under 50K chars (median 4K, 0% boilerplate)

Content Start Position

1 of 10 sampled pages have content starting at 10–50% (worst 12%)

Observability and Content Health
3 passed

Can an agent tell whether the docs are fresh and trustworthy?

This area is already one of the stronger parts of the report.
LLMS TXT Freshness

llms.txt covers 99% of 371 sitemap doc pages

Markdown Content Parity

All 10 pages have equivalent markdown and HTML content (avg 0% missing)

Cache Header Hygiene

All 11 endpoints have appropriate cache headers

URL Stability and Redirects
2 passed

Can an agent trust that URLs will stay predictable?

This area is already one of the stronger parts of the report.
Http Status Codes

All 10 sampled pages return proper error codes for bad URLs

Redirect Behavior

No redirects detected across 10 sampled pages

Authentication and Access
1 passed1 skipped

Can an agent access the docs without getting blocked?

1 check were skipped in this report.
Auth Gate Detection

All 10 sampled pages are publicly accessible

Auth Alternative Access

All docs pages are publicly accessible; no alternative access paths needed

Content Structure
3 passed

Can an agent understand how the page is organized?

This area is already one of the stronger parts of the report.
Tabbed Content Serialization

No tabbed content detected across 10 sampled pages

Section Header Quality

No tabbed content found; header quality check not applicable

Markdown Code Fence Validity

All 38 code fences properly closed across 11 pages

Markdown Availability
2 passed

Can an agent fetch a clean text version of the docs?

This area is already one of the stronger parts of the report.
Markdown Url Support

10/10 sampled pages support .md URLs (100%)

Content Negotiation

10/10 sampled pages support content negotiation (100%)

Content Discoverability
4 passed2 warnings

Can an agent find the right starting point?

2 warnings still need cleanup here.
LLMS TXT Exists

llms.txt found at 1 location(s)

LLMS TXT Valid

llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)

LLMS TXT Size

llms.txt is 65,788 characters (between 50,000 and 100,000; consider splitting)

LLMS TXT Links Resolve

All 10 same-origin sampled links resolve (366 total links)

LLMS TXT Links Markdown

10/10 same-origin sampled links point to markdown content (100%)

LLMS TXT Directive (HTML)

llms.txt directive found in 10 of 10 sampled pages, but buried deep in the page (past 50%)

Next steps

Get this report in your inbox or track the score over time.

Save the report to a work email now, or tell us what kind of ongoing monitoring would be useful for this docs site.

Report delivery

Email me the full report

Save this report to a work email so you can revisit the score and the next fixes later.

Monitoring

Monitor your docs performance

Pick the monitoring path that best matches what you would want next from this benchmark.

Built by DocsAlot

Need help improving the score?

DocsAlot helps teams improve help centers, developer docs, API docs, and CLI docs so they are easier for humans to use and easier for agents to read.