ElasticFlow
AI SkillPlan pSEO ProgramMarketingv1.1.0

Programmatic SEO — Scale to Hundreds of SEO Pages

Runs on
ClaudeClaudeChatGPTChatGPTGeminiGeminiOpenClawOpenClaw

Build SEO page templates and data models that scale to hundreds of pages

  • Identify the right pSEO pattern: location, integration, use case, or comparison
  • Design page templates with dynamic variable slots for each content type
  • Build the data model and source plan for populating pages at scale
  • Write the template copy sections that stay consistent across pages
  • Define URL structure, internal linking, and canonicalization rules

Who this is for

SEO Specialist

You live in Search Console and think in crawl budgets. These skills automate audits, generate schema markup, plan site architecture, and build programmatic SEO pages.

See skills for this role
Growth Marketer

You run experiments, optimize funnels, and own the numbers from signup to revenue. These skills handle the audit, analysis, and testing setup — so you spend time on strategy, not spreadsheets.

See skills for this role
Content Marketer

You plan content calendars, write for SEO, and measure what works. These skills handle strategy, copywriting, editing, and social distribution.

See skills for this role

What it does

Building location pages for local SEO

Designs the page template, data fields, and URL structure for scaling [product] + [city] pages across target markets

Creating integration pages for an app marketplace

Plans a programmatic page structure for each integration or connector, with template copy and data requirements

Scaling comparison pages at the category level

Builds a template for '[Product] vs [Competitor]' or 'Best [Category] tools' pages that can be generated from a structured data source

How it works

1

Describe the page type and keyword pattern you want to scale

2

Share example URLs or competitor programs if available

3

Skill identifies the data model and dynamic variables needed

4

Designs the page template structure with copy and layout guidance

5

Delivers URL structure, data schema, and CMS implementation notes

Metrics this improves

Lead Generation
High-intent programmatic pages convert organic traffic directly into trial signups and leads
Marketing
Indexed Pages
Systematically building and indexing many on-topic pages expands the total indexed page count
Marketing
Organic Traffic
Programmatic pages targeting long-tail keyword patterns generate significant incremental organic traffic
Marketing
Keyword Rankings
Template-based pages targeting keyword variations capture rankings across hundreds of related terms
Marketing

Works with

Ahrefs
manual

Identify programmatic SEO keyword patterns and validate search volume at scale

Google Search Console
manual

Monitor indexation status and search performance of programmatic pages

Google Sheets
manual

Manage data sources and keyword databases that power programmatic page templates

Screaming Frog
manual

Crawl and audit programmatic page health, duplicates, and technical issues

Semrush
manual

Research template keyword structures and competitive landscape for pSEO topics

View on GitHub

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)

PlaybookPatternExample
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"
TranslationsContent in multiple languagesLocalized 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 dataDirectories, Profiles
Product with integrationsIntegrations
Design/creative productTemplates, Examples
Multi-segment audiencePersonas
Local presenceLocations
Tool or utility productConversions
Content/expertiseGlossary, Curation
Competitor landscapeComparisons

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?

Related Skills

  • 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

Reference documents

The 12 Programmatic SEO Playbooks

Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO.

Contents

    1. Templates
    1. Curation
    1. Conversions
    1. Comparisons
    1. Examples
    1. Locations
    1. Personas
    1. Integrations
    1. Glossary
    1. Translations
    1. Directory
    1. Profiles
  • Choosing Your Playbook (Match to Your Assets, Combine Playbooks)

1. Templates

Pattern: "[Type] template" or "free [type] template" Example searches: "resume template", "invoice template", "pitch deck template"

What it is: Downloadable or interactive templates users can use directly.

Why it works:

  • High intent—people need it now
  • Shareable/linkable assets
  • Natural for product-led companies

Value requirements:

  • Actually usable templates (not just previews)
  • Multiple variations per type
  • Quality comparable to paid options
  • Easy download/use flow

URL structure: /templates/[type]/ or /templates/[category]/[type]/

2. Curation

Pattern: "best [category]" or "top [number] [things]" Example searches: "best website builders", "top 10 crm software", "best free design tools"

What it is: Curated lists ranking or recommending options in a category.

Why it works:

  • Comparison shoppers searching for guidance
  • High commercial intent
  • Evergreen with updates

Value requirements:

  • Genuine evaluation criteria
  • Real testing or expertise
  • Regular updates (date visible)
  • Not just affiliate-driven rankings

URL structure: /best/[category]/ or /[category]/best/

3. Conversions

Pattern: "[X] to [Y]" or "[amount] [unit] in [unit]" Example searches: "$10 USD to GBP", "100 kg to lbs", "pdf to word"

What it is: Tools or pages that convert between formats, units, or currencies.

Why it works:

  • Instant utility
  • Extremely high search volume
  • Repeat usage potential

Value requirements:

  • Accurate, real-time data
  • Fast, functional tool
  • Related conversions suggested
  • Mobile-friendly interface

URL structure: /convert/[from]-to-[to]/ or /[from]-to-[to]-converter/

4. Comparisons

Pattern: "[X] vs [Y]" or "[X] alternative" Example searches: "webflow vs wordpress", "notion vs coda", "figma alternatives"

What it is: Head-to-head comparisons between products, tools, or options.

Why it works:

  • High purchase intent
  • Clear search pattern
  • Scales with number of competitors

Value requirements:

  • Honest, balanced analysis
  • Actual feature comparison data
  • Clear recommendation by use case
  • Updated when products change

URL structure: /compare/[x]-vs-[y]/ or /[x]-vs-[y]/

See also: competitor-alternatives skill for detailed frameworks

5. Examples

Pattern: "[type] examples" or "[category] inspiration" Example searches: "saas landing page examples", "email subject line examples", "portfolio website examples"

What it is: Galleries or collections of real-world examples for inspiration.

Why it works:

  • Research phase traffic
  • Highly shareable
  • Natural for design/creative tools

Value requirements:

  • Real, high-quality examples
  • Screenshots or embeds
  • Categorization/filtering
  • Analysis of why they work

URL structure: /examples/[type]/ or /[type]-examples/

6. Locations

Pattern: "[service/thing] in [location]" Example searches: "coworking spaces in san diego", "dentists in austin", "best restaurants in brooklyn"

What it is: Location-specific pages for services, businesses, or information.

Why it works:

  • Local intent is massive
  • Scales with geography
  • Natural for marketplaces/directories

Value requirements:

  • Actual local data (not just city name swapped)
  • Local providers/options listed
  • Location-specific insights (pricing, regulations)
  • Map integration helpful

URL structure: /[service]/[city]/ or /locations/[city]/[service]/

7. Personas

Pattern: "[product] for [audience]" or "[solution] for [role/industry]" Example searches: "payroll software for agencies", "crm for real estate", "project management for freelancers"

What it is: Tailored landing pages addressing specific audience segments.

Why it works:

  • Speaks directly to searcher's context
  • Higher conversion than generic pages
  • Scales with personas

Value requirements:

  • Genuine persona-specific content
  • Relevant features highlighted
  • Testimonials from that segment
  • Use cases specific to audience

URL structure: /for/[persona]/ or /solutions/[industry]/

8. Integrations

Pattern: "[your product] [other product] integration" or "[product] + [product]" Example searches: "slack asana integration", "zapier airtable", "hubspot salesforce sync"

What it is: Pages explaining how your product works with other tools.

Why it works:

  • Captures users of other products
  • High intent (they want the solution)
  • Scales with integration ecosystem

Value requirements:

  • Real integration details
  • Setup instructions
  • Use cases for the combination
  • Working integration (not vaporware)

URL structure: /integrations/[product]/ or /connect/[product]/

9. Glossary

Pattern: "what is [term]" or "[term] definition" or "[term] meaning" Example searches: "what is pSEO", "api definition", "what does crm stand for"

What it is: Educational definitions of industry terms and concepts.

Why it works:

  • Top-of-funnel awareness
  • Establishes expertise
  • Natural internal linking opportunities

Value requirements:

  • Clear, accurate definitions
  • Examples and context
  • Related terms linked
  • More depth than a dictionary

URL structure: /glossary/[term]/ or /learn/[term]/

10. Translations

Pattern: Same content in multiple languages Example searches: "qué es pSEO", "was ist SEO", "マーケティングとは"

What it is: Your content translated and localized for other language markets.

Why it works:

  • Opens entirely new markets
  • Lower competition in many languages
  • Multiplies your content reach

Value requirements:

  • Quality translation (not just Google Translate)
  • Cultural localization
  • hreflang tags properly implemented
  • Native speaker review

URL structure: /[lang]/[page]/ or yoursite.com/es/, /de/, etc.

11. Directory

Pattern: "[category] tools" or "[type] software" or "[category] companies" Example searches: "ai copywriting tools", "email marketing software", "crm companies"

What it is: Comprehensive directories listing options in a category.

Why it works:

  • Research phase capture
  • Link building magnet
  • Natural for aggregators/reviewers

Value requirements:

  • Comprehensive coverage
  • Useful filtering/sorting
  • Details per listing (not just names)
  • Regular updates

URL structure: /directory/[category]/ or /[category]-directory/

12. Profiles

Pattern: "[person/company name]" or "[entity] + [attribute]" Example searches: "stripe ceo", "airbnb founding story", "elon musk companies"

What it is: Profile pages about notable people, companies, or entities.

Why it works:

  • Informational intent traffic
  • Builds topical authority
  • Natural for B2B, news, research

Value requirements:

  • Accurate, sourced information
  • Regularly updated
  • Unique insights or aggregation
  • Not just Wikipedia rehash

URL structure: /people/[name]/ or /companies/[name]/

Choosing Your Playbook

Match to Your Assets

If you have...Consider...
Proprietary dataStats, Directories, Profiles
Product with integrationsIntegrations
Design/creative productTemplates, Examples
Multi-segment audiencePersonas
Local presenceLocations
Tool or utility productConversions
Content/expertiseGlossary, Curation
International potentialTranslations
Competitor landscapeComparisons

Combine Playbooks

You can layer multiple playbooks:

  • Locations + Personas: "Marketing agencies for startups in Austin"
  • Curation + Locations: "Best coworking spaces in San Diego"
  • Integrations + Personas: "Slack for sales teams"
  • Glossary + Translations: Multi-language educational content
Quality tested— 6 tests, 41 assertions verified