Working now
What already works.
- Content Discoverability is relatively strong at 100/100.
- Markdown Availability is relatively strong at 100/100.
- Page Size and Truncation Risk is relatively strong at 100/100.
Benchmark report
Docs benchmark report.
Report for
Backboarddocs.backboard.io
This report shows where agents can use these docs cleanly and where the biggest points of friction still are.
Benchmark score
98Grade A+
This report passes 18 of 18 checks, with 0 warnings, 0 failed checks, and 0 skipped checks still shaping the next score lift.
- Checks passed
- 18/18
- Warnings
- 0
- 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.
Improve next
What to improve next.
Check results
Full score breakdown
Open each category to review the checks behind the score and see exactly where agents still hit friction.
Content Discoverability3 passedCan an agent find the right starting point?
Content Discoverability
3 passed
Can an agent find the right starting point?
Agents get a clean public entry point and a discoverable machine-readable index.
LLMS TXT Exists
The docs publish llms.txt directly from the docs domain.
Docs Entry Point Is Clear
The homepage exposes a clear public docs starting point for agents.
LLMS TXT Links Resolve
Key discovery links resolve cleanly from the public docs surface.
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?
Agents can pull clean documentation text instead of scraping brittle UI wrappers.
Markdown Route Exists
The docs expose a markdown-friendly representation for agent retrieval.
Readable Text Delivery
Core content is available without heavy UI chrome swallowing the copy.
Page Size and Truncation Risk3 passedCan an agent read the page without losing important context?
Page Size and Truncation Risk
3 passed
Can an agent read the page without losing important context?
Pages stay compact and chunked in a way that agents can digest reliably.
Core Pages Stay Bounded
Primary task pages stay within a range that agents can ingest reliably.
Content Starts Early
Important instructions begin near the top of the page instead of after long nav blocks.
Chunking Strategy Is Agent-Friendly
Longer reference content is split cleanly enough that agents can keep context while navigating.
Content Structure3 passedCan an agent understand how the page is organized?
Content Structure
3 passed
Can an agent understand how the page is organized?
The docs are structured like a task system instead of a wall of text.
Section Hierarchy Is Clear
Headings and subsections create a predictable task flow for agents.
Examples Are Well Framed
Code and examples are separated clearly from surrounding explanation.
Step Order Is Explicit
Core procedures are written in a way that agents can follow without guessing the next action.
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?
Agents can rely on stable links when they cite or revisit the docs.
Canonical Docs URLs Are Stable
Core documentation routes are predictable and stable.
Redirect Churn Is Minimal
The docs do not force agents through noisy redirect chains on key paths.
Observability and Content Health3 passedCan an agent tell whether the docs are fresh and trustworthy?
Observability and Content Health
3 passed
Can an agent tell whether the docs are fresh and trustworthy?
Trust and maintenance signals are clear enough for agent workflows.
Freshness Signals Exist
The docs expose enough freshness cues for agents to trust current guidance.
Content Parity Holds
Readable content stays consistent across public delivery formats.
Maintenance Signals Are Clear
Freshness and maintenance cues are strong enough for agents to trust the current guidance.
Authentication and Access2 passedCan an agent access the docs without getting blocked?
Authentication and Access
2 passed
Can an agent access the docs without getting blocked?
The public docs stay reachable, which keeps agent workflows from failing early.
Public Access Is Clear
Agents can reach the docs without hitting avoidable authentication walls.
Blocked Paths Are Explained
Where auth matters, the docs make the boundary clear instead of failing silently.
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.