/programmatic-seo

name: programmatic-seo
description: When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
metadata:
  version: 1.4.1

SEO: Programmatic SEO

Guides programmatic SEO—creating large numbers of SEO-optimized pages automatically using templates and structured data, rather than writing each page manually. **Classic “mail merge” pSEO** (one rigid template + swapped variables) often produced **low differentiation** and thin-feeling URLs. **With AI used responsibly on top of the same data spine**, you can scale **per-URL customization**—intent-aligned copy, section depth, FAQs, tone, localization—while still following **evidence blocks**, **data tiers**, and **QA** (see **Data strength hierarchy** and **AI-assisted generation** below).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

**Project context:** Read root `{project}.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Definition

**Programmatic SEO** = Building a single template and populating it with data from a database, API, or spreadsheet to generate hundreds or thousands of unique pages. Each page targets a long-tail keyword (e.g., "best SEO tool in [city]," "[App A] + [App B] integration").

**Key differences from traditional SEO**: Technical (SEOs + engineers); long-tail focus; data-driven (data quality = success); automation; built for scale.

Classic limits vs AI-enhanced differentiation

| Era | What breaks | What helps | |-----|-------------|------------| | **Rigid pSEO** | One template, minimal variance → similar titles/bodies, weak **E-E-A-T**, “obvious mail merge” | Still needs **unique evidence per URL** and selective indexation | | **AI-enhanced pSEO** | Same **structured rows** (facts, SKUs, metrics) drive the page, but models add **per-URL narrative**: intros, FAQ depth, persona angles, localization, internal-link suggestions—**higher differentiation** at scale | **Facts stay in your data layer**; AI shapes **phrasing and structure**, not invented numbers—see **AI-assisted generation** |

**Best-practice stance**: AI is an **accelerator and customizer**, not a substitute for **data defensibility** (Tiers 1–5) or **technical SEO** (URLs, schema, CWV). Used well, it aligns with **quality over quantity**: fewer thin URLs, more **distinct** useful pages.

Three-Part Framework

| Component | Role | |-----------|------| | **Templates** | Reusable page structures: layout, headings, internal links, content blocks; conditional logic for empty fields | | **Data** | Structured information: locations, products, prices, features—must be accurate, complete, and add genuine value | | **Automation** | Systems connecting data to templates; pages generated dynamically or published in bulk | | **AI layer (optional)** | On **grounded inputs** (row JSON + rules), generates **varied copy**, FAQ expansions, and section emphasis **per URL**—reduces “same template” fatigue while staying auditable |

Page Playbook Matrix (`skills/pages`)

Page types in this library live under `pages/{brand|content|legal|marketing|utility}/`. Use the matrix below to map **search pattern → playbook → which `*-page-generator` skill** to open for structure, copy, and schema—not every folder is a good fit for mass-generated URLs.

| Playbook | Example intent / keyword pattern | Page skill (`name`) | Path (reference) | |----------|----------------------------------|---------------------|------------------| | **Alternatives / comparisons** | "[Competitor] alternatives", "X vs Y" | alternatives-page-generator | `pages/marketing/alternatives` | | **Integrations** | "[Product A] [Product B] integration" | integrations-page-generator | `pages/marketing/integrations` | | **Category / catalog** | Faceted listings, product grids | category-page-generator, products-page-generator | `pages/marketing/category-pages`, `products` | | **Glossary / definitions** | "what is [term]", term landings | glossary-page-generator | `pages/content/glossary` | | **FAQ / Q&A** | Question banks, PAA-style pages | faq-page-generator | `pages/content/faq` | | **How-to / procedures** | Step libraries, "[how to] [task]" blocks in templates | howto-section-generator | `components/content/howto-section` | | **Comparison matrix (blocks)** | Feature/criteria grids, "vs" cells from data feed | comparison-table-generator | `components/content/comparison-table` | | **Tools & lead magnets** | "free [x] tool/calculator" | tools-page-generator | `pages/content/tools` | | **Template gallery** | Browse → detail (your templates) | template-page-generator | `pages/content/template-page` | | **Resource hub** | Guides, hubs, download centers | resources-page-generator | `pages/content/resources` | | **Use cases / solutions** | "for [role]", "by industry" | use-cases-page-generator, solutions-page-generator | `pages/marketing/use-cases`, `solutions` | | **Migration / switching** | "migrate from [X]" | migration-page-generator | `pages/marketing/migration` | | **Campaign landing** | Paid/segment LPs | landing-page-generator | `pages/marketing/landing-page` | | **Blog / article** | Long-tail articles