developer-tool-seolisted

# Developer Tool SEO Developers don't search like other buyers. They don't read landing pages, they distrust marketing copy, and they arrive at products through documentation, error messages, GitHub, and increasingly through an AI coding assistant that recommends a library without them searching at all. That last channel is now a substantial share of developer tool discovery, and it's won differently from search. ## Where developers actually search | Query shape | What they want | Where they land | |---|---|---| | The literal error message | A fix | Docs, forums, issue trackers | | `how to [task] in [language]` | A code example | Docs, tutorials, community answers | | `[library A] vs [library B]` | A decision | Comparisons, community threads | | `[task] library [language]` | Options | Package registries, roundups, GitHub | | `[your product] [framework]` | Integration | Docs, integration pages | | `is [library] still maintained` | Risk assessment | GitHub, changelogs | Notice how little of that is served by a marketing site. **Docs, GitHub and community are the surface area.** The marketing site converts people who already arrived. ## The assets that matter, in order 1. **Documentation.** The primary ranking and citation asset. See `documentation-seo`. 2. **Error message pages.** Highest intent traffic available. Someone pasting an error into search needs an answer now. 3. **Quickstarts per language and framework.** "Getting started with X in Python" is a separate query