What already works.
- Markdown Availability is relatively strong at 100/100.
- Content Structure is relatively strong at 100/100.
- URL Stability and Redirects is relatively strong at 100/100.
Notion scored 92/100 on Mintlify's public score report across 29 published checks. This developer docs benchmark shows where agents can use these docs cleanly and where the biggest points of friction still are.
This report passes 23 of 29 checks, with 2 warnings, 2 failed checks, and 2 skipped checks still shaping the next score lift.
Start with what already works, then move to the fixes most likely to lift the score.
Open each category to review the checks behind the score and see exactly where agents still hit friction.
Can an agent find the right starting point?
llms.txt found at 1 location(s)
llms.txt contains parseable links but doesn't fully follow the proposed structure: https://developers.notion.com/llms.txt: No blockquote summary found Your llms.txt contains parseable links but doesn't follow the standard structure. Add an H1 title as the first line and a blockquote summary (lines starting with >) to improve agent parsing.
llms.txt is 24,913 characters (under 50,000 threshold)
All 15 same-origin sampled links resolve (162 total links)
15/15 same-origin sampled links point to markdown content (100%) (1 external link excluded)
llms.txt directive found in all 15 sampled pages, near the top of content
Can an agent fetch a clean text version of the docs?
15/15 sampled pages support .md URLs (100%)
15/15 sampled pages support content negotiation (100%)
Can an agent read the page without losing important context?
All 15 sampled pages contain server-rendered content
2 of 15 pages between 50K–100K chars (max 97K) 2 of 15 markdown pages are between 50K and 100K characters. These may be truncated on some agent platforms or routed through summarization. Consider splitting large pages.
15 of 15 sampled pages convert to over 100K chars (max 584K, 28% boilerplate) 15 of 15 pages convert to over 100K characters of markdown. Reduce inline CSS/JS, break large pages, or provide markdown versions as a smaller alternative.
Content starts within first 10% on all 15 sampled pages (median 9%)
Can an agent understand how the page is organized?
50 tab group(s) across 13 of 15 sampled pages; all serialize under 50K chars
13 page(s) with tabs found, but no section headers inside tab panels to evaluate
All 43 code fences properly closed across 16 pages
Can an agent trust that URLs will stay predictable?
All 15 sampled pages return proper error codes for bad URLs
No redirects detected across 15 sampled pages
Can an agent tell whether the docs are fresh and trustworthy?
llms.txt covers 100% of 157 sitemap doc pages; 4 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
2 of 15 pages have substantive content differences between markdown and HTML (avg 5% missing) 2 pages have substantive content differences between markdown and HTML (avg 5% missing). Agents receiving the markdown version are getting outdated or incomplete content. Regenerate markdown from source or fix the build pipeline.
All 16 endpoints have appropriate cache headers
Can an agent access the docs without getting blocked?
All 15 sampled pages are publicly accessible
All docs pages are publicly accessible; no alternative access paths needed
Can a long-context agent ingest a full docs snapshot directly?
Found llms-full.txt.
llms-full.txt size is within the expected range.
llms-full.txt has a recognizable markdown structure.
llms-full.txt links resolve successfully.
Do these docs publish explicit operating guidance for agents?
Found an agent skill definition.
Can an agent discover first-class tools instead of scraping pages?
Found an MCP server.
The MCP server exposes tools.
Save the report to a work email now, or tell us what kind of ongoing monitoring would be useful for this docs site.
Compare related benchmark reports, then move into the guides and tools that improve documentation benchmark scores.
99/100 score in Productivity. Open the full documentation benchmark report.
91/100 score in Productivity. Open the full documentation benchmark report.
91/100 score in Productivity. Open the full documentation benchmark report.
Compare this documentation benchmark report with other public docs benchmark results.
Score your own API docs or developer docs and open the full public report.
Use this guide when you want to improve the same categories this benchmark scores.
One of the fastest ways to improve docs discoverability for agents.
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.