Programmatic SEO

Production-grade framework for building SEO page sets at scale. Covers the full lifecycle from keyword pattern discovery through template design, data pipeline construction, quality assurance, and post-launch optimization. Designed for deployments ranging from 50 to 100,000+ pages.

Table of Contents

• When to Use vs When Not To
• Initial Assessment
• The 14 Playbooks
• Playbook Selection Matrix
• Keyword Pattern Mining
• Data Pipeline Architecture
• Template Design System
• Quality Control Framework
• Internal Linking Architecture
• Indexation Strategy
• Launch Sequence
• Post-Launch Optimization
• Anti-Patterns and Penalty Avoidance
• Decision Matrix: Build vs Skip
• Output Artifacts
• Related Skills

When to Use vs When Not To

Use this skill when:

• You have a repeating keyword pattern with 50+ variations
• You have (or can acquire) structured data to populate pages
• The search intent is consistent across variations
• Your domain has sufficient authority to compete

Do NOT use when:

• Each page requires unique editorial content (use content-creator instead)
• Total addressable pages < 30 (manual content is more effective)
• You lack a data source and would be generating thin placeholder content
• Your domain authority is below DR 20 and competitors are DR 60+

Initial Assessment

Before designing any pSEO strategy, answer these questions. Skip nothing.

1. Opportunity Validation

2. Data Source Evaluation

Rate your data source on this scale:

Rule: Do not build pSEO on Tier F data. Google penalizes commodity rewrites. If your only data source is public and easily replicable, invest in acquiring Tier A-C data first.

3. Competitive Moat Assessment

For 5 sample queries in your pattern, analyze page 1 results:

• What is the average Domain Rating of ranking pages?
• Are existing results programmatic or editorial?
• What unique data do ranking pages provide?
• What is the content depth (word count, data richness, UX quality)?

Go/No-Go threshold: If the average DR gap between you and page 1 is > 30 AND existing results have proprietary data, the opportunity requires either a differentiated approach or domain authority building first.

The 14 Playbooks

Playbook Selection Matrix

Layering rule: Combine up to 2 playbooks per page set. Example: "Best coworking spaces in [city]" = Curation + Locations.

Keyword Pattern Mining

Step 1: Pattern Identification

Extract the repeating structure from seed keywords:

Seed: "react developer salary san francisco"
Pattern: [role] salary [city]
Variables: role (200+ options), city (500+ options)
Max pages: 200 x 500 = 100,000

Step 2: Volume Distribution Analysis

Not all variable combinations have search volume. Map the distribution:

Step 3: Intent Classification

For each pattern, verify intent consistency:

Data Pipeline Architecture

Pipeline Design

[Data Source] → [Extraction] → [Transformation] → [Enrichment] → [Validation] → [Template Population] → [Quality Check] → [Publish]

Data Quality Gates

Every record must pass these gates before page generation:

Update Cadence

Template Design System

Page Architecture

Every programmatic page must have these zones:

┌─────────────────────────────────────┐
│ Zone 1: Unique Header               │  H1 with target keyword, unique intro paragraph
├─────────────────────────────────────┤
│ Zone 2: Primary Data Section         │  The core data/content for this specific page
├─────────────────────────────────────┤
│ Zone 3: Contextual Analysis          │  Insights, comparisons, trends specific to this entity
├─────────────────────────────────────┤
│ Zone 4: Related Data                 │  Adjacent data points that add depth
├─────────────────────────────────────┤
│ Zone 5: Internal Navigation          │  Related pages, breadcrumbs, category links
├─────────────────────────────────────┤
│ Zone 6: CTA                         │  Conversion element matched to intent
└─────────────────────────────────────┘

Uniqueness Requirements

Each page MUST have at least 3 of these 5 uniqueness sources:

1. Unique data points -- Numbers, facts, or attributes specific to this entity
2. Conditional content blocks -- Sections that appear/disappear based on data attributes
3. Calculated insights -- Derived metrics (percentages, comparisons, rankings)
4. Contextual recommendations -- "If X, then Y" advice blocks based on the data
5. User-generated content -- Reviews, comments, or community contributions

URL Structure

Always use subfolders. Never subdomains for pSEO.

/[service]/[city]/

/coworking/austin/

/compare/[a]-vs-[b]/

/compare/notion-vs-confluence/

/integrations/[partner]/

/integrations/slack/

/glossary/[term]/

/glossary/churn-rate/

/[product]-for-[audience]/

/crm-for-real-estate/

Quality Control Framework

Pre-Publication QA Checklist

Content Quality:

• Each page has > 300 words of unique content (not counting shared template elements)
• H1 is unique and contains the target keyword
• Meta title is unique (< 60 chars) and meta description is unique (< 155 chars)
• No broken data references (empty fields rendered as "N/A" or blank)
• At least 2 conditional content blocks triggered per page
• No duplicate pages targeting the same keyword

Technical SEO:

• Canonical tag points to self
• Hreflang tags if multilingual
• Schema markup renders without errors
• Page loads in < 3 seconds
• Mobile responsive

Internal Linking:

• Breadcrumb trail is complete
• 3-5 related pages linked contextually
• Hub page links to this page
• No orphan pages in the set

Thin Content Detection

Run this check against every generated page:

Internal Linking Architecture

Hub-and-Spoke Model

                    ┌─────────┐
                    │  HUB    │  /coworking/
                    │  PAGE   │  (ranks for "coworking spaces")
                    └────┬────┘
          ┌──────────────┼──────────────┐
     ┌────┴────┐    ┌────┴────┐    ┌────┴────┐
     │ SPOKE 1 │    │ SPOKE 2 │    │ SPOKE 3 │
     │ /austin/│    │ /denver/│    │ /seattle/│
     └────┬────┘    └────┬────┘    └────┬────┘
          │              │              │
     Cross-links between related spokes

Linking rules:

• Hub links DOWN to every spoke (or top 50 spokes if > 200 pages)
• Every spoke links UP to the hub
• Spokes link ACROSS to 3-5 related spokes (geographic proximity, thematic similarity)
• Deep pages link UP to their spoke AND the hub
• Cross-silo links only when contextually genuine

Pagination for Large Sets

If a hub page has > 50 spokes, implement paginated sub-hubs:

/coworking/                     → Top cities + browse by state
/coworking/california/          → All California cities
/coworking/california/page/2/   → Paginated if > 25 cities

Indexation Strategy

Crawl Budget Management

Indexation Priority

IndexNow Integration

For large-scale updates, use IndexNow to notify search engines immediately:

POST https://api.indexnow.org/indexnow
{
  "host": "yoursite.com",
  "key": "your-api-key",
  "urlList": ["https://yoursite.com/page1", "https://yoursite.com/page2"]
}

Launch Sequence

Phase 1: Pilot (Week 1-2)

• Deploy 20-50 pages from head-volume tier
• Submit sitemap with pilot pages only
• Monitor indexation rate daily
• Check for crawl errors in Search Console

Phase 2: Scale (Week 3-6)

• Deploy remaining torso-volume pages in batches of 100-500
• Add cross-links between deployed pages
• Monitor thin content warnings
• Track impressions in Search Console

Phase 3: Long-Tail (Week 7-12)

• Deploy long-tail pages
• Noindex zero-volume pages (keep them crawlable but not indexed)
• Begin link acquisition outreach for hub pages

Phase 4: Optimization (Ongoing)

• A/B test template variations on head-volume pages
• Refresh stale data quarterly
• Add conditional content blocks based on engagement data
• Monitor for keyword cannibalization across the set

Post-Launch Optimization

Metrics Dashboard

Optimization Playbook

Anti-Patterns and Penalty Avoidance

Decision Matrix: Build vs Skip

Score each dimension 1-5, then apply the threshold.

Scoring guide:

• 4.0+ weighted average: Build immediately
• 3.0-3.9: Build if resources allow, validate with pilot first
• 2.0-2.9: Invest in data quality or authority first
• < 2.0: Do not build

Output Artifacts

Related Skills

• seo-audit -- Run after pSEO pages are live to diagnose indexation issues, thin content warnings, or ranking problems across the page set.
• schema-markup -- Add structured data to pSEO templates (Product, FAQ, LocalBusiness) for rich snippet eligibility at scale.
• site-architecture -- Plan hub-and-spoke structure and crawl budget management for large pSEO deployments (500+ pages).
• competitor-alternatives -- Use the Comparisons playbook when building "[X] vs [Y]" pages; competitor-alternatives has dedicated comparison page frameworks.
• content-creator -- Use when individual pages in the set need editorial-quality unique content beyond template generation.

Troubleshooting

Success Criteria

• Indexation rate: 90%+ of submitted pages indexed within 60 days of deployment
• Content uniqueness: Every page has 500+ unique words with <40% similarity to any other page in the set (2026 Google threshold)
• Head keyword rankings: Top 10% of pages (by volume) ranking in top 30 within 90 days
• Organic traffic growth: Page set generating measurable organic traffic within 60 days of full deployment
• Thin content rate: Zero pages flagged as thin content in Google Search Console
• Bounce rate: Below 70% average across the page set (indicating intent match)
• Conversion rate: 1%+ for transactional intent pages, measurable lead capture for informational pages

Scope & Limitations

In scope:

• Keyword pattern mining and volume distribution analysis
• Data pipeline design (source > extraction > transformation > validation > publication)
• Template architecture with uniqueness requirements
• Quality control frameworks including thin content detection
• Hub-and-spoke internal linking for pSEO page sets
• Phased indexation strategy and crawl budget management
• Post-launch optimization and monitoring dashboards

Out of scope:

• Individual editorial content creation (use Content Production)
• Data collection or web scraping implementation
• CMS or static site generator setup and configuration
• Server infrastructure for large-scale deployments
• Paid acquisition for pSEO pages
• Legal compliance for data usage rights

Known limitations:

• Google's 2026 helpful content system can deindex large page sets retroactively if quality drops below threshold
• Programmatic SEO at Tier F data (public/scraped) carries high penalty risk regardless of template quality
• Engagement metrics (bounce rate, time on page) now influence indexation decisions for pSEO pages
• AI content detection is improving — fully automated content generation without human oversight is increasingly risky
• Travel site case study: 50,000 city-swap pages had 98% deindexed within 3 months (per 2025 industry data)

Scripts

# Analyze keyword patterns for pSEO opportunities
python scripts/keyword_pattern_miner.py --keywords keywords.csv --json

# Score page templates for content quality and uniqueness
python scripts/template_scorer.py --template template.html --data sample_data.json

# Validate data quality for pSEO data pipeline
python scripts/data_validator.py --file data.csv --rules rules.json --json