📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
@@ -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.
|
||||
@@ -0,0 +1,296 @@
|
||||
---
|
||||
name: developer-seo
|
||||
description: 'SEO strategy for technical queries and developer audiences. Covers keyword research for "how to X in language" queries, error message SEO, Stack Overflow-style content, technical long-tail keywords, and competing with official documentation sites. Use when asked about: - SEO for...'
|
||||
risk: unknown
|
||||
source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-seo
|
||||
source_repo: jonathimer/devmarketing-skills
|
||||
source_type: community
|
||||
date_added: 2026-07-01
|
||||
license: MIT
|
||||
license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
|
||||
---
|
||||
|
||||
# Developer SEO
|
||||
## When to Use
|
||||
|
||||
Use this skill when you need sEO strategy for technical queries and developer audiences. Covers keyword research for "how to X in language" queries, error message SEO, Stack Overflow-style content, technical long-tail keywords, and competing with official documentation sites. Use when asked about: - SEO for...
|
||||
|
||||
|
||||
## Overview
|
||||
|
||||
Developer SEO differs fundamentally from traditional SEO. Developers search with precise technical intent—error messages, API questions, "how to X in Y language" queries. They bounce immediately from thin content and respect sites that actually solve problems. Your competition isn't other marketing sites; it's Stack Overflow, official docs, and GitHub issues.
|
||||
|
||||
This skill covers SEO strategies that work for technical audiences without compromising on substance.
|
||||
|
||||
## Understanding Developer Search Behavior
|
||||
|
||||
### How Developers Search
|
||||
|
||||
Developers search differently than general audiences:
|
||||
|
||||
**Query patterns:**
|
||||
- Error messages (often copy-pasted verbatim)
|
||||
- "How to [action] in [language/framework]"
|
||||
- "[Tool A] vs [Tool B]"
|
||||
- "[Concept] tutorial"
|
||||
- "[Library] [specific function] example"
|
||||
|
||||
**Behavioral signals:**
|
||||
- High bounce rates on superficial content
|
||||
- Long dwell time on genuinely helpful pages
|
||||
- Multiple tabs open comparing solutions
|
||||
- Quick scroll to code examples
|
||||
- Immediate exit if content doesn't match query intent
|
||||
|
||||
### Search Intent Categories
|
||||
|
||||
1. **Troubleshooting**: Developer has an error, needs a fix
|
||||
2. **Learning**: Developer wants to understand a concept
|
||||
3. **Evaluating**: Developer comparing tools or approaches
|
||||
4. **Implementing**: Developer needs working code examples
|
||||
5. **Reference**: Developer needs quick syntax or API lookup
|
||||
|
||||
## Keyword Research for Developers
|
||||
|
||||
### Finding Technical Long-Tail Keywords
|
||||
|
||||
Technical long-tail keywords have lower volume but extremely high intent. A developer searching "axios interceptor refresh token react" knows exactly what they need.
|
||||
|
||||
**Research approaches:**
|
||||
|
||||
1. **Mine your support channels**
|
||||
- Extract questions from support tickets
|
||||
- Review Discord/Slack community questions
|
||||
- Analyze GitHub issues for common problems
|
||||
|
||||
2. **Stack Overflow mining**
|
||||
- Search for questions mentioning your tool category
|
||||
- Look at related questions on popular threads
|
||||
- Note the exact phrasing developers use
|
||||
|
||||
3. **Google Search Console analysis**
|
||||
- Find queries you rank positions 5-20 for
|
||||
- Identify question-based queries
|
||||
- Spot error message searches hitting your site
|
||||
|
||||
4. **Competitor content gaps**
|
||||
- What questions do competitors' docs not answer?
|
||||
- Where are forum threads unsatisfied with existing answers?
|
||||
|
||||
### Error Message SEO
|
||||
|
||||
Error messages are SEO gold—developers copy-paste them directly into search.
|
||||
|
||||
**Strategy:**
|
||||
1. Create dedicated pages for common errors
|
||||
2. Use exact error text in titles and H1s
|
||||
3. Include the full error message early in content
|
||||
4. Provide the actual fix, not generic troubleshooting
|
||||
5. Add related errors users might also encounter
|
||||
|
||||
**Content structure for error pages:**
|
||||
```
|
||||
Title: [Exact Error Message] - How to Fix
|
||||
|
||||
## The Error
|
||||
[Full error message and where it appears]
|
||||
|
||||
## Quick Fix
|
||||
[The solution that works in most cases]
|
||||
|
||||
## Why This Happens
|
||||
[Brief technical explanation]
|
||||
|
||||
## Other Solutions
|
||||
[Alternative fixes for edge cases]
|
||||
|
||||
## Related Errors
|
||||
[Links to similar issues]
|
||||
```
|
||||
|
||||
### Competing with Official Documentation
|
||||
|
||||
Official docs have domain authority advantages but often have weaknesses:
|
||||
|
||||
**Where docs often fail:**
|
||||
- No "why" explanations, just "what"
|
||||
- Missing real-world examples
|
||||
- No troubleshooting guides
|
||||
- Outdated content
|
||||
- No comparative context
|
||||
|
||||
**Your opportunities:**
|
||||
- "Getting started with X" tutorials that hold your hand
|
||||
- "X vs Y" comparison content (docs never compare)
|
||||
- Migration guides between versions or tools
|
||||
- Real-world implementation examples
|
||||
- Common gotchas and how to avoid them
|
||||
|
||||
## Content Formats That Rank
|
||||
|
||||
### How-To Guides
|
||||
|
||||
Structure for technical how-to content:
|
||||
|
||||
```markdown
|
||||
# How to [Action] in [Technology]
|
||||
|
||||
## Prerequisites
|
||||
- What you need before starting
|
||||
- Required versions/dependencies
|
||||
|
||||
## Quick Version (TL;DR)
|
||||
- Code snippet that works for common case
|
||||
|
||||
## Step-by-Step
|
||||
1. Step with explanation
|
||||
2. Step with code example
|
||||
3. Step with expected output
|
||||
|
||||
## Complete Example
|
||||
[Full working code]
|
||||
|
||||
## Common Issues
|
||||
- Problem 1: Solution
|
||||
- Problem 2: Solution
|
||||
|
||||
## Next Steps
|
||||
[What to learn next]
|
||||
```
|
||||
|
||||
### Comparison Content
|
||||
|
||||
Developers actively search "[Tool A] vs [Tool B]" when evaluating options.
|
||||
|
||||
**Guidelines:**
|
||||
- Be genuinely objective (developers will check)
|
||||
- Include actual code comparisons
|
||||
- Cover specific use cases where each wins
|
||||
- Mention your tool's limitations honestly
|
||||
- Update when tools change significantly
|
||||
|
||||
### Tutorial Series
|
||||
|
||||
In-depth tutorials build topical authority and capture multiple related queries.
|
||||
|
||||
**Planning approach:**
|
||||
1. Identify a topic cluster (e.g., "authentication in Node.js")
|
||||
2. Create pillar content covering the broad topic
|
||||
3. Build supporting content for specific subtopics
|
||||
4. Interlink strategically
|
||||
|
||||
## Technical SEO for Developer Sites
|
||||
|
||||
### Code Snippet Optimization
|
||||
|
||||
Google can read and understand code. Optimize for it:
|
||||
|
||||
- Use semantic HTML (`<code>`, `<pre>`)
|
||||
- Add language hints for syntax highlighting
|
||||
- Ensure code is actual text, not images
|
||||
- Test that code actually works (broken examples hurt credibility)
|
||||
|
||||
### Page Speed for Developer Sites
|
||||
|
||||
Developers expect fast sites. They also often use ad blockers and privacy tools.
|
||||
|
||||
**Priorities:**
|
||||
- Minimize JavaScript for documentation pages
|
||||
- Ensure content loads without JS when possible
|
||||
- Optimize for low-bandwidth scenarios (conference Wi-Fi)
|
||||
- Test with developer-typical browser extensions enabled
|
||||
|
||||
### Documentation Site Architecture
|
||||
|
||||
Good IA helps both users and search engines:
|
||||
|
||||
- Clear hierarchy (Guides > Category > Specific Topic)
|
||||
- Breadcrumbs for navigation
|
||||
- Consistent URL structures
|
||||
- Proper use of canonical tags for versioned docs
|
||||
- XML sitemaps for large doc sites
|
||||
|
||||
## Building Authority
|
||||
|
||||
### Technical Backlinks
|
||||
|
||||
High-quality technical backlinks matter more than quantity.
|
||||
|
||||
**Sources that work:**
|
||||
- GitHub repository READMEs
|
||||
- Technical blog posts citing your content
|
||||
- Stack Overflow answers linking to your guides
|
||||
- Developer newsletter mentions
|
||||
- Conference talk resource lists
|
||||
|
||||
**What doesn't work:**
|
||||
- Generic guest posting
|
||||
- Link exchanges
|
||||
- Directory spam
|
||||
- Forum signature links
|
||||
|
||||
### Content Freshness
|
||||
|
||||
Developer content becomes outdated quickly:
|
||||
|
||||
- Review and update major guides quarterly
|
||||
- Add "last updated" dates (developers check these)
|
||||
- Create processes for updating when dependencies change
|
||||
- Remove or redirect genuinely obsolete content
|
||||
|
||||
## Measuring Developer SEO
|
||||
|
||||
### Metrics That Matter
|
||||
|
||||
- Organic traffic to documentation and guides
|
||||
- Rankings for target technical queries
|
||||
- Time on page for tutorial content
|
||||
- Search Console impressions for error message queries
|
||||
- GitHub referrals from technical content
|
||||
|
||||
### Metrics to Interpret Carefully
|
||||
|
||||
- Bounce rate (developers often find answer and leave—that's success)
|
||||
- Pages per session (for reference content, one page is fine)
|
||||
- Conversion rate (long attribution windows for developer tools)
|
||||
|
||||
## Budget and Resources
|
||||
|
||||
### Minimum Viable Approach
|
||||
- **Time investment**: 5-10 hours/week for content creation
|
||||
- **Tools needed**: Google Search Console (free), basic keyword research tool
|
||||
- **Timeline**: 3-6 months to see meaningful organic growth
|
||||
|
||||
### Scaled Approach
|
||||
- Dedicated technical content writer
|
||||
- SEO tools subscription (Ahrefs, Semrush)
|
||||
- Content management system optimized for docs
|
||||
- Regular content audits and updates
|
||||
|
||||
## Tools
|
||||
|
||||
- **Google Search Console**: Track rankings and discover query opportunities
|
||||
- **Ahrefs/Semrush**: Keyword research and competitor analysis
|
||||
- **Screaming Frog**: Technical SEO audits for documentation sites
|
||||
- **Algolia**: Search analytics revealing what developers look for
|
||||
- **Octolens**: Monitor developer discussions to find content opportunities and questions your content should answer
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
1. **Writing for search engines, not developers**: Keyword-stuffed content that doesn't actually help
|
||||
2. **Ignoring search intent**: Ranking for queries but not matching what developers actually need
|
||||
3. **Thin content**: Short posts that don't provide real value
|
||||
4. **Outdated examples**: Code that no longer works in current versions
|
||||
5. **No unique value**: Rehashing what official docs already cover
|
||||
|
||||
## Related Skills
|
||||
|
||||
- **developer-content-strategy**: Overall content planning for developer audiences
|
||||
- **dev-tool-directory-listings**: Building domain authority through directory presence
|
||||
- **developer-lead-gen**: Converting organic traffic into leads
|
||||
|
||||
## Limitations
|
||||
|
||||
- Use this skill only when the task clearly matches its upstream source and local project context.
|
||||
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
|
||||
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
|
||||
Reference in New Issue
Block a user