programmatic-seo
Verifiedby coreyhaines31 · Updated Apr 16, 2026
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
See It In Action
Now I have a full picture of the codebase, data, and constraints. Let me build the pSEO plan.
The plan is written to pseo-plan.md. Here's a quick rundown of what it covers:
Key Decisions
Tiering (index vs. noindex):
- Tier 1 (6 apps — full build): Slack, Google Sheets, Notion, HubSpot, GitHub, Salesforce — highest volume, strongest proof points. These get maximum content investment and day-1 index requests.
- Tier 2 (10 apps — standard build): Asana through ClickUp — indexable but with lighter workflow depth.
- Tier 3 (2 apps — noindex for now): Linear (33 workspaces) and Microsoft Teams (27 workspaces) fall below the 40-workspace threshold. They stay live for partner links but are withheld from the index and sitemap until they have enough proof.
Critical technical fixes (today, April 14):
- Add missing canonical tags on 6 pages
- 301 redirect all 18 legacy
/app-integrations/*URLs →/integrations/{app-slug}/ - Split the sitemap — create a dedicated
/sitemaps/integrations.xmlwith 16 indexable pages - Fix the 14 blog posts linking to legacy URLs
- Handle
?ref=and?category=parameter variants via canonicals
Content differentiation strategy: Every page gets unique content through conditional template blocks (auth type, sync direction, setup time) plus app-specific workflow descriptions written in trigger → action → outcome format (min 60 words each). This directly addresses the SERP gaps — Zapier wins because they show concrete examples while our pages are generic.
Timeline:
| Date | Milestone |
|---|---|
| Apr 14 | Technical SEO fixes |
| Apr 15 | Hub page overhaul + Tier 1 content builds |
| Apr 16–17 | Tier 2 content builds |
| Apr 18 | QA pass (full pre-launch checklist in the plan) |
| Apr 19 | Content freeze + GSC index requests |
| Apr 21 | Campaign launch |
30-day targets: Move Tier 1 average rank from 25 → ≤18, Tier 2 from 34 → ≤28, +40% non-brand organic sessions to /integrations/*.
The full plan with per-app content gap fixes, internal linking clusters, JSON-LD specs, and the complete QA checklist is in the file. Ready for review.
Permissions
| Scope | Description |
|---|---|
| filesystem:read |
SKILL.md
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:
-
Business Context
- What's the product/service?
- Who is the target audience?
- What's the conversion goal for these pages?
-
Opportunity Assessment
- What search patterns exist?
- How many potential pages?
- What's the search volume distribution?
-
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:
- Proprietary (you created it)
- Product-derived (from your users)
- User-generated (your community)
- Licensed (exclusive access)
- 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)
| Playbook | Pattern | Example |
|---|---|---|
| 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" |
| Translations | Content in multiple languages | Localized 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 data | Directories, Profiles |
| Product with integrations | Integrations |
| Design/creative product | Templates, Examples |
| Multi-segment audience | Personas |
| Local presence | Locations |
| Tool or utility product | Conversions |
| Content/expertise | Glossary, Curation |
| Competitor landscape | Comparisons |
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
- What keyword patterns are you targeting?
- What data do you have (or can acquire)?
- How many pages are you planning?
- What does your site authority look like?
- Who currently ranks for these terms?
- 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
FAQ
What does programmatic-seo do?
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
When should I use programmatic-seo?
Use it when you need a repeatable workflow that produces text report.
What does programmatic-seo output?
In the evaluated run it produced text report.
How do I install or invoke programmatic-seo?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does programmatic-seo support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does programmatic-seo need?
It uses no extra tools; channels commonly include text; permissions include filesystem:read.
Is programmatic-seo safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is programmatic-seo different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does programmatic-seo outperform not using a skill?
About programmatic-seo
When to use programmatic-seo
You want to plan or generate many similar SEO pages such as location, comparison, or integration pages. You need a structured pSEO strategy covering keyword patterns, template design, internal linking, and indexation. You want guidance on avoiding thin content and building unique value into template-driven pages.
When programmatic-seo is not the right choice
You need a technical SEO audit of existing pages rather than a pSEO creation strategy. You need direct integrations with keyword tools, CMSs, or publishing platforms to execute changes automatically.
What it produces
Produces text report.