Catalog
coreyhaines31/programmatic-seo

coreyhaines31

programmatic-seo

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 pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

global
version:1.1.0
0installs0uses~1.8k
v1.1Saved Apr 20, 2026

Programmatic SEO

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.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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:

  1. Business Context

    • What's the product/service?
    • Who is the target audience?
    • What's the conversion goal for these pages?
  2. Opportunity Assessment

    • What search patterns exist?
    • How many potential pages?
    • What's the search volume distribution?
  3. Competitive Landscape

    • Who ranks for these terms now?
    • What do their pages look like?
    • Can you realistically compete?

Core Principles

1. Unique Value Per Page

  • Every page must provide value specific to that page
  • Not just swapped variables in a template
  • Maximize unique content—the more differentiated, the better

2. Proprietary Data Wins

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)

3. Clean URL Structure

Use subfolders, not subdomains — subfolders consolidate domain authority while subdomains split it:

  • Good: yoursite.com/templates/resume/
  • Bad: templates.yoursite.com/resume/

4. Genuine Search Intent Match

Pages must actually answer what people are searching for.

5. Quality Over Quantity

Better to have 100 great pages than 10,000 thin ones.

6. Avoid Google Penalties

  • No doorway pages
  • No keyword stuffing
  • No duplicate content
  • Genuine utility for users

The 12 Playbooks (Overview)

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


Choosing Your Playbook

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").


Implementation Framework

1. Keyword Pattern Research

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

2. Data Requirements

Identify data sources:

  • What data populates each page?
  • Is it first-party, scraped, licensed, public?
  • How is it updated?

3. Template Design

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

4. Internal Linking Architecture

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

5. Indexation Strategy

  • Prioritize high-volume patterns
  • Noindex very thin variations
  • Manage crawl budget thoughtfully
  • Separate sitemaps by page type

Quality Checks

Pre-Launch Checklist

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

Post-Launch Monitoring

Track: Indexation rate, Rankings, Traffic, Engagement, Conversion

Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors


Common Mistakes

  • Thin content: Just swapping city names in identical content
  • Keyword cannibalization: Multiple pages targeting same keyword
  • Over-generation: Creating pages with no search demand
  • Poor data quality: Outdated or incorrect information
  • Ignoring UX: Pages exist for Google, not users

Output Format

Strategy Document

  • Opportunity analysis
  • Implementation plan
  • Content guidelines

Page Template

  • URL structure
  • Title/meta templates
  • Content outline
  • Schema markup

Task-Specific Questions

  1. What keyword patterns are you targeting?
  2. What data do you have (or can acquire)?
  3. How many pages are you planning?
  4. What does your site authority look like?
  5. Who currently ranks for these terms?
  6. What's your technical stack?

  • seo-audit: For auditing programmatic pages after launch
  • schema-markup: For adding structured data
  • site-architecture: For page hierarchy, URL structure, and internal linking
  • competitor-alternatives: For comparison page frameworks
Files3
3 files · 15.9 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Safety

95

Quality

88

Clarity

86

Completeness

81

Summary

This skill guides users in building SEO-optimized pages at scale using templates and data. It provides a framework for choosing playbooks (Templates, Curation, Comparisons, etc.), designing page templates with unique value, structuring URLs and internal linking, and avoiding thin content penalties. The skill emphasizes proprietary data, genuine user value, and quality over quantity.

Detected Capabilities

Playbook selection and matching to business assetsKeyword pattern research and demand validationTemplate design for programmatic pagesURL structure and internal linking architectureContent differentiation strategies to avoid thin contentData sourcing and quality assessmentIndexation strategy and crawl budget planningPre-launch and post-launch quality checklists

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

scale pages with templatescomparison pages at scalelocation-based landing pagesintegration page strategyglossary at scalepersona-specific pagestemplate pages for SEOdirectory pages for rankingsprogrammatic landing pagesdata-driven page generation

Risk Signals

INFO

Skill references external context file (.agents/product-marketing-context.md or .claude/product-marketing-context.md) but does not enforce its presence or handle missing file gracefully

SKILL.md, Initial Assessment section
INFO

Cross-references three related skills (seo-audit, schema-markup, site-architecture, competitor-alternatives) but does not explicitly define what content each skill covers or when to defer

SKILL.md, Related Skills section
INFO

Evaluation 6 (audit existing pages for technical issues) expects the skill to defer to seo-audit, but the skill does not include explicit guidance on when to hand off technical audits

evals/evals.json, eval #6

Use Cases

  • Creating 'best [category]' comparison pages for multiple competitors
  • Building '[service] in [location]' pages for geographic markets
  • Scaling '[product] for [audience]' persona-specific landing pages
  • Generating '[tool A] + [tool B] integration' pages for an integration ecosystem
  • Building a '[term] definition' glossary at scale for 100+ terms
  • Creating '[type] template' downloadable assets across product variations

Quality Notes

  • Excellent structure: clear playbook taxonomy with 12 distinct patterns, each with example searches, value requirements, and URL templates. This makes it easy for agents to map user intent to implementation.
  • Strong pedagogical approach: Core Principles section establishes guardrails (avoid thin content, match search intent, prioritize unique value) before diving into implementation. This prevents the common mistake of blindly scaling without substance.
  • Comprehensive implementation framework: Keyword research → Data requirements → Template design → Internal linking → Indexation strategy covers the full lifecycle and prevents orphan pages or indexation failures.
  • Well-organized reference material: references/playbooks.md provides deep implementation details for each of the 12 playbooks without cluttering the main skill document.
  • Practical quality checks: Pre-launch and post-launch checklists with specific items (unique titles/meta, heading structure, schema markup, crawlability) give agents concrete acceptance criteria.
  • Useful evaluation suite: evals.json covers persona playbooks, comparisons, integrations, glossary, and diagnostic scenarios (e.g., low indexation rate), testing both happy-path implementation and troubleshooting.
  • Minor documentation gap: Initial Assessment section assumes product-marketing-context.md may exist but does not specify what happens if it's absent or how the skill proceeds. Could be more explicit about fallback behavior.
  • Minor scope ambiguity: Skill description mentions 'auditing existing SEO issues' and defers to seo-audit, but the skill body does not include explicit language for when to refuse an audit request. Evaluation 6 expects this deferral, but it's not in the main content.
  • Strong contextualization: Metadata includes helpful trigger phrases in the description itself ('programmatic SEO,' 'template pages,' 'pages at scale,' 'pSEO,' 'generate 100 pages'), making discovery intuitive.
Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest
v1.0

No changelog

2026-04-19

Add coreyhaines31/programmatic-seo to your library

Command Palette

Search for a command to run...