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
98Grade A

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

Checks passed
21/23
Warnings
0
Failed checks
1
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.

  • Page Size and Truncation Risk 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.

  • Markdown Content Parity in Observability and Content Health.
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
4 passed

Can an agent read the page without losing important context?

This area is already one of the stronger parts of the report.
Rendering Strategy

All 10 sampled pages contain server-rendered content

Page Size Markdown

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

Page Size Html

All 10 sampled pages under 50K chars (median 3258K HTML → 16K markdown (99% boilerplate))

Content Start Position

Content starts within first 10% on all 10 sampled pages (median 0%)

Observability and Content Health
2 passed1 failed

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

1 failed check still shape this area.
LLMS TXT Freshness

llms.txt covers 100% of 1186 sitemap doc pages; 19 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)

Markdown Content Parity

6 of 10 pages have substantive content differences between markdown and HTML (avg 37% missing)

Cache Header Hygiene

All 12 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 63 code fences properly closed across 12 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
7 passed

Can an agent find the right starting point?

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

llms.txt found at 2 locations; using https://docs.merge.dev/llms.txt as canonical

LLMS TXT Valid

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

LLMS TXT Size

llms.txt is 7,395 characters (under 50,000 threshold)

LLMS TXT Links Resolve

All 10 same-origin sampled links resolve (43 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 HTML of all 10 sampled pages, near the top of content

LLMS TXT Directive (Markdown)

llms.txt directive found in markdown of all 10 sampled pages, near the top of content

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.