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 contextus.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
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
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.
Usually not mass programmatic (single primary URL or compliance-heavy): pages/brand/* (home, about, contact), pages/legal/*, most pages/utility/* (404, status, signup-login, etc.)—treat as one-off or policy-driven, not template×data scale.
Choosing a Playbook
Template Structure (Recommended)
Evidence block = Real, structured data per page (business listings, pricing, reviews, verified stats). Ensures each page delivers genuine value, not recycled boilerplate with swapped variables.
Data strength hierarchy (defensibility)
Strongest programmatic pages are fueled by what only your product (or your customers inside your product) can produce—especially templates, exports, and generated artifacts. Third-party or scraped lists alone are the weakest foundation.
Why Tier 1 (templates & generated content) wins: Pages built from your template system carry proprietary structure, variables, and brand-safe blocks—harder for competitors to copy verbatim and easier to prove uniqueness (embeds, downloads, IDs). Pair with template-page-generator when the UX is “browse gallery → use template.”
Tier 2 — Product-derived (practical)
AI here: Use models to turn structured aggregates into prose (intro paragraphs, “what this means for [segment]”)—input must be verified numbers/tables from your pipeline, not free-form invention. Keep a machine-readable table or JSON on-page or in appendix so claims stay auditable.
Tier 3 — UGC / customer (practical)
AI here: Summarize long reviews into bullets; generate draft alt text for images; cluster submissions into topic pages—always human approve before publish. Do not fabricate testimonials.
Tier 4 — Licensed / partner (practical)
AI here: Draft comparison copy and FAQs from a fixed attribute table (license + partner rules); never invent SKUs or prices—pull from feed, let AI phrase and shorten.
Tier 5 — Public / scraped (practical)
AI here: Use models to structure messy public text into tables, outline sections, suggest internal links—then fact-check names, numbers, and dates. Do not use AI to invent statistics or citations; treat output as draft until verified.
AI-assisted generation (cross-tier)
Why AI fits modern pSEO: Early programmatic SEO earned a bad reputation because templates were frozen and copy was interchangeable—little real differentiation per query. LLMs, when grounded on each row’s facts and your brand rules, make it practical to customize headlines, intros, FAQs, and “why this page matters” per URL without hand-writing thousands of pages. That moves execution closer to best practices (intent match, helpful content, unique value) at scale, provided you do not let the model invent data.
When AI generation is a strong lever: Tiers 2–5—where raw material is already tabular or repetitive but needs readable, differentiated copy at scale. Tier 1 still benefits from AI (drafts from export JSON), but the differentiator remains the product artifact itself.
Operational requirements (all tiers)
Ideal Use Cases
For which page-generator skill to use, see Page Playbook Matrix above. Generic patterns:
Avoid when: Site structure is weak; page differences are superficial (city/name swaps only); content requires original expertise or UGC participation.
Real-World Examples
Examples are illustrative; no endorsement implied.
Content Requirements
Technical Considerations
Critical Pitfalls
Pages with only a title, one paragraph, and swapped city names will not rank and may incur Google penalties.
Remediating Already-Built Homogenized Pages
If programmatic pages are already published and feel interchangeable — shared closing sentences, identical value propositions across URLs, cloned section endings — fix the content before it triggers quality signals.
Diagnostic approach
Run regex scans across rendered or source files to surface shared sentence tails and repeated paragraph structures. Look for patterns that appear in more than 30% of same-category pages. Common telltales: every tool page ending with "X is the ideal choice for Y," every category page sharing the same technology summary, every location page using identical FAQ tails.
Scan at three scopes: within a single page (do its sections repeat the same closing formula?), within a category (do all video tool pages share a template?), and across categories (is the same value statement on every page site-wide?).
Prioritize fixes into three levels
Execute in rounds
Fix P0 patterns first, one category at a time. After each round, re-scan to confirm patterns are cleared and no new ones appeared. A common trap: replacing one template with another by applying the same fix uniformly. Distribute rewrites so pages processed in sequence get different treatments.
For single-page internal duplicates — where all use cases or tool descriptions within one file share identical closing sentences — use functional endings instead of evaluative ones. A functional ending describes what bottleneck the entry solves in practice; an evaluative ending just declares it's a good choice.
Prevention in the pipeline
Add structural-variety requirements to AI generation prompts (vary section endings, forbid repeated closing formulas). Batch-generate pages from different categories together rather than all from one category at once. Run N-gram overlap checks across same-category pages before publishing.
Step-by-Step Workflow
- Research — Niche, intent; include low-volume keywords; SEO tools, question databases
- Collect data — Provenance log, freshness rules; first-party/licensed; define template fields
- Choose stack — Next.js + DB, Webflow CMS, WordPress, headless; API + template reuse
- Design template — Intro, Evidence, Decision, FAQ, CTA; schema; conditional logic
- Build database — Map fields to template slots; hide empties
- Generate pages — Descriptive URLs; optimize performance
- Deploy & monitor — Sitemaps; indexation, rankings, CTR, bounce, conversions
- Optimize — Prune weak pages; refresh data; A/B test layout, CTA
Best Practices
Timeline & Expectations
- Typical time to ranking: ~6 months
- Reported gains: 40%+ traffic increases from well-designed topic clusters
- AI search: Structured, data-rich content performs better in AI Overviews and citation layers
Output Format
- Template design (Intro, Evidence, Decision, FAQ, CTA; required data fields)
- Data requirements (provenance, freshness, accuracy)
- Internal linking (hub-and-spoke, related pages)
- Indexation strategy (selective indexation, sitemap segmentation)
- Checklist for audit
Related Skills
- template-page-generator: Template structure; aggregation (gallery) + detail pages; Tier 1 product-generated template URLs
- landing-page-generator: Conversion-focused programmatic pages; LP structure for campaign CTA
- tools-page-generator: Free tools pages; toolkit hub; programmatic tool pages; lead gen
- alternatives-page-generator: Alternatives/comparison pages at scale; competitor brand traffic
- category-page-generator, products-page-generator: Category / catalog grids
- glossary-page-generator, faq-page-generator, howto-section-generator, comparison-table-generator, resources-page-generator: Definitions, Q&A banks, HowTo step blocks, comparison matrices, content hubs
- use-cases-page-generator, solutions-page-generator, migration-page-generator: ICP/industry matrix, migration SEO
- integrations-page-generator: Integration pair pages at scale
- blog-page-generator, article-page-generator, docs-page-generator, features-page-generator, api-page-generator: Long-form and product surface scale
- press-coverage-page-generator, customer-stories-page-generator, showcase-page-generator: Proof at scale
- startups-page-generator, contest-page-generator, download-page-generator, affiliate-page-generator, media-kit-page-generator, pricing-page-generator, services-page-generator: Programs and offers (use selectively for pSEO)
- content-strategy: Content clusters, pillar pages; programmatic pages as cluster nodes
- website-structure: Site IA before scaling URL sets
- url-structure, domain-architecture: Paths, subfolder strategy
- schema-markup: Structured data (Product, Place, FAQ, ItemList)
- internal-links: Linking programmatic pages
- xml-sitemap: Sitemap segmentation for large programmatic sites
- canonical-tag: Duplicate/thin content handling
- seo-strategy, seo-audit: Roadmap and post-launch audits
