Playbook · Developer products
SEO & AI search playbook for docs-led devtools
For many developer tools, the docs site has more pages, more links and more search traffic than the marketing site. It's also usually built on a docs framework or hosted platform with defaults nobody reviewed for search.
This playbook is about the docs site itself: structure, versions, titles and rendering. For acquisition pages like comparisons and launches, see the developer tools playbook.
Updated By the LaunchRanked team6 sources checked
Searches to plan around
Query patterns and the intent behind them. We don’t quote search volumes: check your own Search Console for the ones you already appear for.
Exact config keys, flags and function names
Look upDevelopers search the precise identifier. Put it in the page title and first heading.
“[tool] [feature] example”
Copy a working examplePages with a complete example rank and get used. Fragments don't.
“[tool] [version] migration”, “[tool] breaking changes”
UpgradeOne migration page per major version.
Error strings
DebugAn error reference page per error your tool throws.
Page families that work
Reference pages
/docs/config/cache-dir
One option or function per page, with type, default, example and version added.
How-to guides
/docs/guides/deploy-to-cloudflare
Task-based pages that combine features. These match “how to” searches.
Migration pages
/docs/migrate/v3-to-v4
Breaking changes, codemods and a checklist.
Error reference
/docs/errors/E1024
Cause, fix and the versions affected.
Risky page types
Every version indexed in full
Five copies of each page compete for the same query. Keep the latest indexable and canonicalise or noindex old versions that duplicate it.
Docs search result pages
Internal search URLs create endless near-empty pages. Keep them out of the index.
Technical pitfalls
Duplicate titles like “Overview” or “Introduction”
Docs frameworks often use the sidebar label as the title. Include the product and section: “Caching overview – YourTool docs”.
Soft 404s in single-page docs
A missing page that returns 200 with a “not found” message is a soft 404. Google's JavaScript SEO guide suggests redirecting to a URL that returns a real 404, or adding noindex.
Anchors used as pages
Long single pages with #anchors for each option can't rank per option. Split high-traffic options into their own pages.
“Ask AI” widgets with no crawlable answers
Chat widgets help visitors, but nothing inside them is indexable. The answers still need to exist as docs pages.
How AI assistants answer questions in this category
Assistants and coding agents read docs pages directly when they need current details, which is the case the llms.txt proposal was written for. They do best with pages that name the version, show a complete example and keep one topic per page. Old versions that look identical to current ones are a common source of wrong answers.
What tends to earn a citation
- Version labels at the top of every page and a clear “latest” path.
- Complete, runnable examples rather than fragments.
- An llms.txt that lists your most important pages, and optionally Markdown versions of docs pages, for tools that read them.
Check whether the AI crawlers you want can reach your site with our AI crawler checker.
Where links come from
Docs as link targets
Other projects link to specific docs pages, not your homepage. Stable URLs keep those links working, so redirect whenever you move a page.
Examples in other ecosystems
Getting a working example into a framework's docs or starter templates is worth more than most directory links.
Developer directories
Link your listings in developer tool directories straight to the quickstart.
Directory lists that fit docs-led devtools
- Developer tool directories
- Open-source directories
- Where to submit: Developer tools
- Where to submit: Developer newsletters
- All directories
Each directory is checked on its own site: price, link type and review process. We never sell links.
A 90-day plan
Days 1–30
Audit
- Export all docs titles and find duplicates.
- Check how missing pages respond (real 404 or soft 404).
- Decide the canonical policy for versions.
Days 31–60
Fix
- Rewrite titles with product and section.
- Apply canonicals or noindex to old versions.
- Split the most-searched options into their own pages.
Days 61–90
Extend
- Add error reference pages.
- Publish llms.txt and Markdown copies if your framework supports it.
- Use Search Console queries to find missing how-to guides.
What to watch in Search Console
The Performance report gives clicks, impressions, CTR and average position by query, page, country, device and date. Traffic from Google's AI features is counted there too, under the Web search type (Google).
- “Duplicate, Google chose different canonical than user”
- In the Page indexing report, this often means old doc versions are winning over new ones.
- Queries with exact identifiers
- Shows which options people search for, and whether they land on the right page.
- Soft 404 count
- Should fall to near zero after the fix.
Frequently asked questions
Should old docs versions be noindexed?
Where they duplicate the current version, yes, or canonicalise them. Keep them reachable for people on old versions.
Do docs frameworks handle SEO for us?
They handle the basics. Titles, versions, 404s and search pages usually need configuring.
Is llms.txt worth adding to docs?
It's cheap and aimed at exactly this use case. It's a proposal, not a Google requirement, so treat it as an extra.
One long page or many short ones?
Many focused pages for things people search for by name. A long page can't rank for each option.
Sources
Checked on September 23, 2026. Search patterns and page advice are our own judgement from running this playbook; we don’t quote search volumes or third-party statistics.