菜单
Template-based page generation at scale for SEO. Data-driven content, internal linking architecture, and automated optimization for large-scale content operations. Use when the user asks about programmatic SEO, pSEO, scaled content, template pages, or automated page generation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | programmatic-seo |
| description | Template-based page generation at scale for SEO. Data-driven content, internal linking architecture, and automated optimization for large-scale content operations. Use when the user asks about programmatic SEO, pSEO, scaled content, template pages, or automated page generation. |
| license | MIT |
| origin | custom |
| author | Rebecca Rae Barton |
| author_url | https://github.com/thatrebeccarae |
| metadata | {"version":"1.0.0","category":"seo","domain":"programmatic-seo","updated":"2026-03-18T00:00:00.000Z","tested":"2026-03-18T00:00:00.000Z","tested_with":"Claude Code v2.1"} |
Generate thousands of targeted pages from data templates at scale.
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/programmatic-seo ~/.claude/skills/
Creating large numbers of search-optimized pages from structured data + templates. Instead of writing each page manually, you define a template and populate it with data variations.
Examples of successful pSEO:
| Pattern | Template | Data Source | Pages |
|---|---|---|---|
| Integration pages | "[Your product] + [Partner]" | Partner/integration list | 100-5,000 |
| Location pages | "[Service] in [City/State]" | Location database | 500-50,000 |
| Comparison pages | "[Your product] vs [Competitor]" | Competitor list | 20-200 |
| Glossary/definitions | "What is [Term]?" | Industry term database | 200-2,000 |
| Template/example pages | "[Type] template" or "[Type] examples" | Template library | 100-1,000 |
| Tool pages | "[Metric] calculator" | Calculator variations | 50-500 |
| Stats pages | "[Topic] statistics [Year]" | Data sources | 50-500 |
[H1: Dynamic title with primary keyword]
[Intro paragraph: 2-3 sentences with entity-specific context]
[Key data section: structured data unique to this entity]
[Comparison or context section: how this entity relates to others]
[FAQ section: 3-5 entity-specific questions]
[Related pages: internal links to related entities]
[CTA: conversion action relevant to search intent]
Every programmatic page MUST have:
Hub page: "[Category] Guide" (high authority)
└── Spoke 1: "[Entity A] in [Category]"
└── Spoke 2: "[Entity B] in [Category]"
└── Spoke 3: "[Entity C] in [Category]"
(Each spoke links back to hub and to 3-5 related spokes)
| Approach | Best For | Stack |
|---|---|---|
| Static Site Generation (SSG) | <10,000 pages, infrequent data updates | Next.js, Astro, Hugo |
| Incremental Static Regeneration (ISR) | 10,000-100,000 pages, periodic updates | Next.js |
| Server-Side Rendering (SSR) | Dynamic data, real-time pricing | Next.js, Nuxt |
| Database-driven CMS | Non-technical team needs to manage | WordPress + custom post types |
noindex on thin pages until they have sufficient contentKlaviyo marketing operations and analyst expertise. Audit flows, segments, campaigns, deliverability, and revenue attribution. Use when the user asks about Klaviyo marketing strategy, email/SMS automation, customer segmentation, flow optimization, or lifecycle marketing. For API integration, SDK, webhook, or developer questions, see the klaviyo-developer skill.
Klaviyo API and developer integration expertise. Event tracking, SDKs, webhooks, rate limits, OAuth, catalog sync, and code patterns. Use when the user asks about Klaviyo API, integrating with Klaviyo, tracking events, building custom integrations, webhook handling, or developer implementation. For marketing strategy, flow optimization, and campaign auditing, see the klaviyo-analyst skill.
Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.
Google Tag Manager expertise. Audit GTM containers, design tag and trigger architecture, debug firing issues, implement consent mode v2, and advise on server-side tagging. Use when the user asks about GTM, tag management, container audits, consent mode, server-side tagging, or tracking implementation.
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or developing content strategy. For deep SEO writing optimization, see the seo-content-writer skill.