📦 deps(thirdparty): update snapshots
This commit is contained in:
@@ -0,0 +1,36 @@
|
||||
# Developer SEO
|
||||
|
||||
SEO strategies for technical queries and developer audiences.
|
||||
|
||||
## What This Covers
|
||||
|
||||
- Keyword research for "how to X in Y" queries
|
||||
- Error message SEO (capturing copy-paste searches)
|
||||
- Competing with Stack Overflow and official documentation
|
||||
- Technical long-tail keyword strategy
|
||||
- Content formats that rank for developer searches
|
||||
|
||||
## Key Concepts
|
||||
|
||||
**Developer search behavior differs fundamentally** - developers search with precise technical intent, copy-paste error messages, and bounce immediately from superficial content.
|
||||
|
||||
**Error messages are SEO gold** - dedicated pages with exact error text and real fixes capture high-intent traffic.
|
||||
|
||||
**Compete where docs fail** - official documentation often lacks "why" explanations, real-world examples, and troubleshooting guides.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Planning SEO strategy for a developer tool
|
||||
- Creating technical content that should rank
|
||||
- Building error message or troubleshooting content
|
||||
- Competing for "how to" and comparison queries
|
||||
|
||||
## Quick Start
|
||||
|
||||
1. Mine support channels for real developer questions
|
||||
2. Identify error messages developers encounter
|
||||
3. Create genuinely helpful content that solves problems
|
||||
4. Structure content for quick scanning (code early, explanations after)
|
||||
5. Track rankings for specific technical queries
|
||||
|
||||
See SKILL.md for complete tactics and implementation details.
|
||||
Reference in New Issue
Block a user