Working now
What already works.
- URL Stability and Redirects is relatively strong at 100/100.
- Authentication and Access is relatively strong at 100/100.
- Content Structure is relatively strong at 100/100.
Benchmark report
Docs benchmark report.
Report for
Provedeveloper.prove.com
This report shows where agents can use these docs cleanly and where the biggest points of friction still are.
Benchmark score
95Grade A
This report passes 15 of 23 checks, with 5 warnings, 1 failed checks, and 2 skipped checks still shaping the next score lift.
- Checks passed
- 15/23
- Warnings
- 5
- 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.
Improve next
What to improve next.
- Content Start Position in Page Size and Truncation Risk.
- LLMS TXT Freshness in Observability and Content Health.
- 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 Risk1 passed2 warnings1 failedCan an agent read the page without losing important context?
Page Size and Truncation Risk
1 passed2 warnings1 failed
Can an agent read the page without losing important context?
1 failed check still shape this area.
Rendering Strategy
All 10 sampled pages contain server-rendered content
Page Size Markdown
4 of 9 pages between 50K–100K chars (max 77K)
Page Size Html
1 of 10 sampled pages convert to 50K–100K chars (max 3230K HTML → 51K markdown (88% boilerplate))
Content Start Position
1 of 10 sampled pages have content starting past 50% (worst 52%)
Observability and Content Health1 passed2 warningsCan an agent tell whether the docs are fresh and trustworthy?
Observability and Content Health
1 passed2 warnings
Can an agent tell whether the docs are fresh and trustworthy?
2 warnings still need cleanup here.
LLMS TXT Freshness
llms.txt covers 73/86 sitemap doc pages (85%); 13 missing; 4 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
Markdown Content Parity
5 of 9 pages have minor content differences between markdown and HTML
Cache Header Hygiene
All 11 endpoints have appropriate cache headers
URL Stability and Redirects2 passedCan an agent trust that URLs will stay predictable?
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 Access1 passed1 skippedCan an agent access the docs without getting blocked?
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 Structure2 passed1 skippedCan an agent understand how the page is organized?
Content Structure
2 passed1 skipped
Can an agent understand how the page is organized?
1 check were skipped in this report.
Tabbed Content Serialization
43 tab group(s) across 8 of 10 sampled pages; all serialize under 50K chars
Section Header Quality
8 page(s) with tabs found, but no section headers inside tab panels to evaluate
Markdown Code Fence Validity
All 31 code fences properly closed across 10 pages
Markdown Availability2 passedCan an agent fetch a clean text version of the docs?
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
9/9 sampled pages support .md URLs (100%)
Content Negotiation
9/9 sampled pages support content negotiation (100%)
Content Discoverability6 passed1 warningsCan an agent find the right starting point?
Content Discoverability
6 passed1 warnings
Can an agent find the right starting point?
1 warning still need cleanup here.
LLMS TXT Exists
llms.txt found at https://developer.prove.com/llms.txt
LLMS TXT Valid
llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
LLMS TXT Size
llms.txt is 17,042 characters (under 50,000 threshold)
LLMS TXT Links Resolve
All 10 same-origin sampled links resolve (77 total links)
LLMS TXT Links Markdown
9/10 same-origin sampled links point to markdown content (90%)
LLMS TXT Directive (HTML)
llms.txt directive found in HTML of 9 of 10 sampled pages, but buried deep in the page (past 50%)
LLMS TXT Directive (Markdown)
llms.txt directive found in markdown of all 9 sampled pages, near the top of content; 1 had no markdown version
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.
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.