Crawlability & indexability
HTTP responses, crawler permissions, index directives, and canonical signals.
20 pointsDocs Discoverability Score
How discoverable
is your documentation?
Find the signals that make your product answers easier to crawl, understand, connect, and act on.
A free, evidence-backed check across seven areas. Built for software documentation.
All free toolsStart with your documentation.
Paste a public docs or help-center URL. Get your score and up to three findings before sharing your email.
Up to 15 public pages. No login required. Recent scans may be reused for 24 hours.
Docs discoverability leaderboard
Publicly listed assessments, highest score first. One latest score per documentation site. Company names are supplied by submitters; this is not a verified ranking or endorsement.
| Company name | Docs URL | Score |
|---|---|---|
| Loading scores… | ||
What goes into your score?
Methodology 1.0. Transparent, rule-based checks against the HTML and discovery files our scanner can read.
Structure & URLs
Readable URLs, breadcrumbs, and navigable documentation collections.
15 pointsOn-page search signals
Page titles, descriptions, and clear topic headings.
15 pointsAI readability
Extractable article text, descriptive sections, and structured instructions.
15 pointsInternal linking
Contextual connections between documentation pages and next steps.
15 pointsConversion paths
Relevant links from product answers to product exploration or action.
10 pointsCoverage signals
Getting started, features, integrations, workflows, and troubleshooting found in the sample.
10 pointsA sample, with clear boundaries.
We discover URLs from sitemaps and public navigation, then select up to 15 HTML pages across recognizable documentation roles. A sitemap helps discovery; a missing sitemap is not an automatic failure. robots.txt permissions are checked before crawling. Relevant llms.txt files are informational and carry no points.
Checks measure signals such as nonempty titles, descriptions, headings, extractable content, breadcrumb markup, contextual links, and recognizable product actions. Role patterns use URLs, titles, and headings. Missing signals mean “not found in this sample,” not “absent from your entire library.” We do not execute website JavaScript or measure actual search indexation.
Each area is scored from its applicable measured checks and weighted as shown above. Unknown checks are not treated as failures. If required areas or sampled article content cannot be measured reliably, we show an incomplete assessment instead of an overall number. Sample choice, page roles, and methodology changes can affect comparisons.
A rule-based heuristic of sampled documentation, not a prediction of rankings, AI citations, traffic, or signups. We check indexability signals, not actual search-engine indexation.
Google’s guidance on AI search features · The llms.txt proposal
A few useful answers.
Understand the scope before you compare scores or act on a finding.
What does the Docs Discoverability Score measure?
It checks observable documentation signals across seven areas. Every finding links to a page or file and states what the scanner observed. The weights describe our methodology, not search-engine ranking factors.
How many pages do you scan?
Up to 15 public HTML pages, selected from documentation navigation and sitemap discovery. We try to include different documentation roles. A sample does not establish complete topic coverage or identify every issue in a large library.
Does this confirm that my docs are indexed by Google?
No. We examine crawl permissions, HTTP responses, noindex directives, and canonical signals. Actual indexation requires access to search-engine records such as your Search Console property.
Does missing llms.txt lower my score?
No. We report whether a relevant llms.txt file is available. Its presence is informational and does not predict AI recommendations or citations.
What happens if my documentation cannot be scanned?
We explain the limitation instead of assigning a zero. Login requirements, bot protection, robots restrictions, and pages that require JavaScript can prevent a reliable HTML assessment.
What is free, and why do you ask for an email?
The score and up to three prioritized findings are available without an email. Your name, company, and work email unlock the page-level report and let our team review your documentation needs. This does not subscribe you to marketing emails.
Will my company appear on the leaderboard?
Complete assessments appear automatically after you unlock the report. The leaderboard shows your supplied company name, documentation URL, and calculated score, highest first. Names are self-reported; listing does not imply endorsement or verified ownership. Your email and full report stay private.
Can I improve and rerun my score?
Yes. Recent assessments may be reused for 24 hours to avoid repeatedly requesting the same documentation. Scores can change with the sampled pages, published content, and methodology version.