Back to leaderboard
Documentation benchmark

Linear benchmark

Report for

Linear scored 91/100 on the DocsAlot benchmark report across 22 published checks. This Documentation 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: Documentation benchmarkSource: DocsAlot benchmark
Score your docs
Benchmark score
91Grade A

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

Checks passed
18/22
Warnings
0
Failed checks
3
Search page context

Why Linear matters as a documentation surface

Documentation quality now affects implementation speed, support load, and whether an agent or buyer can stay self-serve. This benchmark shows where the docs already work well and where they still introduce friction.

Good documentation is discoverable, readable in plain text, clear about structure and instructions, and specific enough in examples and next steps that real workflows can keep moving.

What this report means

What this documentation benchmark says about Linear.

These are the clearest signals behind the current score. Start with the strengths that already support discovery and implementation, then use the gaps below to prioritize the fixes most likely to improve AI readability and self-serve onboarding.

Working well

Where the docs already help.

  • Page size and truncation risk is already a strength, with a 100/100 score.
  • URL stability and redirects is already a strength, with a 100/100 score.
  • Authentication and access is already a strength, with a 100/100 score.

For the broader pattern behind these wins, review AI-readable documentation and compare this page with the full docs benchmark leaderboard.

Improve next

What to fix for better self-serve.

  • Improve lLMS TXT freshness in observability and content health.
  • Improve markdown content parity in observability and content health.
  • Improve lLMS TXT directive (HTML) in content discoverability.

If you want to improve the system behind these gaps, start with API docs automation, the OpenAPI to CLI generator, and this guide to making docs AI-readable.

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 6K, max 9K)

Page Size Html

All 10 sampled pages convert under 50K chars (median 6K, 0% boilerplate)

Content Start Position

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

Observability and Content Health
1 passed2 failed

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

2 failed checks still shape this area.
LLMS TXT Freshness

llms.txt covers 98/130 sitemap doc pages (75%); 32 missing

Markdown Content Parity

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

Cache Header Hygiene

All 11 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 22 code fences properly closed across 11 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
5 passed1 failed

Can an agent find the right starting point?

1 failed check still shape this area.
LLMS TXT Exists

llms.txt found at 1 location(s)

LLMS TXT Valid

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

LLMS TXT Size

llms.txt is 9,026 characters (under 50,000 threshold)

LLMS TXT Links Resolve

All 10 same-origin sampled links resolve (126 total links)

LLMS TXT Links Markdown

10/10 same-origin sampled links point to markdown content (100%) (2 external links excluded)

LLMS TXT Directive (HTML)

No llms.txt directive found in any of 10 sampled pages

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.