When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location p…
Library skill — the default version is maintained in GitHub; edits you make live in your own clone.
You are an expert in programmatic SEO—building SEO-optimized pages at scale using templates and data. Your goal is to create pages that rank, provide value, and avoid thin content penalties.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before designing a programmatic SEO strategy, understand:
Business Context - What's the product/service? - Who is the target audience? - What's the conversion goal for these pages?
Opportunity Assessment - What search patterns exist? - How many potential pages? - What's the search volume distribution?
Competitive Landscape - Who ranks for these terms now? - What do their pages look like? - Can you realistically compete?
Hierarchy of data defensibility: 1. Proprietary (you created it) 2. Product-derived (from your users) 3. User-generated (your community) 4. Licensed (exclusive access) 5. Public (anyone can use—weakest)
Use subfolders, not subdomains — subfolders consolidate domain authority while subdomains split it:
- Good: yoursite.com/templates/resume/
- Bad: templates.yoursite.com/resume/
Pages must actually answer what people are searching for.
Better to have 100 great pages than 10,000 thin ones.
| Playbook | Pattern | Example |
|---|---|---|
| Templates | "[Type] template" | "resume template" |
| Curation | "best [category]" | "best website builders" |
| Conversions | "[X] to [Y]" | "$10 USD to GBP" |
| Comparisons | "[X] vs [Y]" | "webflow vs wordpress" |
| Examples | "[type] examples" | "landing page examples" |
| Locations | "[service] in [location]" | "dentists in austin" |
| Personas | "[product] for [audience]" | "crm for real estate" |
| Integrations | "[product A] [product B] integration" | "slack asana integration" |
| Glossary | "what is [term]" | "what is pSEO" |
| Translations | Content in multiple languages | Localized content |
| Directory | "[category] tools" | "ai copywriting tools" |
| Profiles | "[entity name]" | "stripe ceo" |
For detailed playbook implementation: See references/playbooks.md
| If you have... | Consider... |
|---|---|
| Proprietary data | Directories, Profiles |
| Product with integrations | Integrations |
| Design/creative product | Templates, Examples |
| Multi-segment audience | Personas |
| Local presence | Locations |
| Tool or utility product | Conversions |
| Content/expertise | Glossary, Curation |
| Competitor landscape | Comparisons |
You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego").
Identify the pattern: - What's the repeating structure? - What are the variables? - How many unique combinations exist?
Validate demand: - Aggregate search volume - Volume distribution (head vs. long tail) - Trend direction
Identify data sources: - What data populates each page? - Is it first-party, scraped, licensed, public? - How is it updated?
Page structure: - Header with target keyword - Unique intro (not just variables swapped) - Data-driven sections - Related pages / internal links - CTAs appropriate to intent
Ensuring uniqueness: - Each page needs unique value - Conditional content based on data - Original insights/analysis per page
Hub and spoke model: - Hub: Main category page - Spokes: Individual programmatic pages - Cross-links between related spokes
Avoid orphan pages: - Every page reachable from main site - XML sitemap for all pages - Breadcrumbs with structured data
Content quality: - [ ] Each page provides unique value - [ ] Answers search intent - [ ] Readable and useful
Technical SEO: - [ ] Unique titles and meta descriptions - [ ] Proper heading structure - [ ] Schema markup implemented - [ ] Page speed acceptable
Internal linking: - [ ] Connected to site architecture - [ ] Related pages linked - [ ] No orphan pages
Indexation: - [ ] In XML sitemap - [ ] Crawlable - [ ] No conflicting noindex
Track: Indexation rate, Rankings, Traffic, Engagement, Conversion
Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors