Back to leaderboard
developer docs benchmark

Notion benchmark.

Report for

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.

Last checked: May 4, 2026Category: ProductivityBenchmark type: developer docs benchmarkSource: Mintlify score
Score your docs
Benchmark score
92Grade A

This report passes 23 of 29 checks, with 2 warnings, 2 failed checks, and 2 skipped checks still shaping the next score lift.

Checks passed
23/29
Warnings
2
Failed checks
2
Key takeaways

What stands out in this benchmark.

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

Working now

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.
Improve next

What to improve next.

  • Page Size Html in Page Size and Truncation Risk.
  • Markdown Content Parity in Observability and Content Health.
  • Page Size Markdown 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.

Content Discoverability
5 passed1 warnings

Can an agent find the right starting point?

1 warning across 6 AFDocs checks.
LLMS TXT Exists

llms.txt found at 1 location(s)

LLMS TXT Valid

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 Size

llms.txt is 24,913 characters (under 50,000 threshold)

LLMS TXT Links Resolve

All 15 same-origin sampled links resolve (162 total links)

LLMS TXT Links Markdown

15/15 same-origin sampled links point to markdown content (100%) (1 external link excluded)

LLMS TXT Directive

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

Markdown Availability
2 passed

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

2 AFDocs checks pass.
Markdown Url Support

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

Content Negotiation

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

Page Size and Truncation Risk
2 passed1 warnings1 failed

Can an agent read the page without losing important context?

1 failed and 1 warning across 4 AFDocs checks.
Rendering Strategy

All 15 sampled pages contain server-rendered content

Page Size Markdown

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.

Page Size Html

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 Start Position

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

Content Structure
2 passed1 skipped

Can an agent understand how the page is organized?

1 skipped across 3 AFDocs checks.
Tabbed Content Serialization

50 tab group(s) across 13 of 15 sampled pages; all serialize under 50K chars

Section Header Quality

13 page(s) with tabs found, but no section headers inside tab panels to evaluate

Markdown Code Fence Validity

All 43 code fences properly closed across 16 pages

URL Stability and Redirects
2 passed

Can an agent trust that URLs will stay predictable?

2 AFDocs checks pass.
Http Status Codes

All 15 sampled pages return proper error codes for bad URLs

Redirect Behavior

No redirects detected across 15 sampled pages

Observability and Content Health
2 passed1 failed

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

1 failed across 3 AFDocs checks.
LLMS TXT Freshness

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

Markdown Content Parity

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.

Cache Header Hygiene

All 16 endpoints have appropriate cache headers

Authentication and Access
1 passed1 skipped

Can an agent access the docs without getting blocked?

1 skipped across 2 AFDocs checks.
Auth Gate Detection

All 15 sampled pages are publicly accessible

Auth Alternative Access

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

Full Content Discoverability
4 passed

Can a long-context agent ingest a full docs snapshot directly?

llms-full.txt passes all checks.
LLMS Full Exists

Found llms-full.txt.

LLMS Full Size

llms-full.txt size is within the expected range.

LLMS Full Valid

llms-full.txt has a recognizable markdown structure.

LLMS Full Links Resolve

llms-full.txt links resolve successfully.

Agent Skills
1 passed

Do these docs publish explicit operating guidance for agents?

skill.md passes all checks.
Skill MD

Found an agent skill definition.

MCP Server
2 passed

Can an agent discover first-class tools instead of scraping pages?

MCP passes all checks.
MCP Server Discoverable

Found an MCP server.

MCP Tool Count

The MCP server exposes tools.

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.

Keep exploring

Use this report as a real search entry point.

Compare related benchmark reports, then move into the guides and tools that improve documentation benchmark scores.

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.