Programmatic Seo
Design template-and-data SEO page systems—city, comparison, integration URLs—with QA tiers so solo builders scale landing pages without thin duplicate mail-merge content.
Overview
Programmatic SEO is an agent skill most often used in Launch (also Validate landing, Grow content) that guides scaled SEO pages from templates and data with differentiation and QA—not thin mail-merge URLs.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill programmatic-seoWhat is this skill?
- Playbook matrix aligned to companion skills under skills/pages for page-type recipes
- Contrasts rigid mail-merge pSEO with AI-assisted per-URL differentiation on the same data spine
- Data strength hierarchy, evidence blocks, and QA gates to avoid thin URLs
- Covers location pages, X vs Y comparisons, integration pages, and data-driven landing templates
- Points template galleries and browse-to-use marketplaces to template-page-generator
- metadata version 1.4.1
- Playbook matrix aligned to skills under skills/pages
Adoption & trust: 1k installs on skills.sh; 586 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have structured data and URL patterns but fear creating thousands of near-duplicate pages that hurt rankings and trust.
Who is it for?
Solo builders with datasets (locations, SKUs, integrations) who will invest in evidence blocks and per-URL quality gates.
Skip if: Founders who only want a single marketing landing page or a browsable template marketplace without SEO scale.
When should I use this skill?
Programmatic SEO, template pages at scale, location/city/comparison/integration pages, pages from data, or automated landing pages.
What do I get? / Deliverables
You get a governed pSEO plan—playbook choice, data tiers, AI-assisted customization rules, and QA—ready to implement with your pages skill stack.
- Page-type playbook selection
- Data tier and evidence-block requirements
- AI-assisted generation and QA checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Programmatic SEO is how you compound organic reach after you have a site architecture and data spine worth publishing at scale. The seo subphase holds playbook matrices, intent templates, and evidence/data-tier rules for URL patterns—not one-off blog posts.
Where it fits
Prototype a small batch of integration comparison URLs to test demand before full crawl budget spend.
Lock playbook matrix, evidence blocks, and QA checklist before generating hundreds of city pages.
Expand long-tail integration or versus pages using the same data spine with per-URL AI copy passes.
How it compares
SEO scale playbook with data spine and QA; use template-page-generator for gallery/marketplace UX, not URL farms.
Common Questions / FAQ
Who is programmatic-seo for?
Technical marketers and solo founders shipping many intent-specific URLs from templates plus structured or API-backed data.
When should I use programmatic-seo?
At Launch seo when designing page-type matrices; at Validate landing when testing scalable comparison or city pages; at Grow content when expanding localized or integration catalogs.
Is programmatic-seo safe to install?
Review the Security Audits panel on this Prism page; implementing pSEO may later require build/deploy agents with network access.
Workflow Chain
Then invoke: template page generator
SKILL.md
READMESKILL.md - Programmatic Seo
# 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**: If `.claude/project-context.md` or `.cursor/project-context.md` exists, read product/ICP sections before proposing playbooks or page types. ## 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 e