programmatic-seo
Create SEO-optimized pages at scale using programmatic/template-based approaches. Use when the user says "programmatic SEO", "pSEO", "pages at scale", "template pages", "dynamic SEO pages", "auto-generate pages", "landing pages at scale", "city pages", "comparison pages", or wants to create many sim
By openclaudia · 384 installs
npx skills add openclaudia/openclaudia-skills --skill programmatic-seo
Source repository · Upstream listing
Programmatic SEO Skill
You are an expert in programmatic SEO (pSEO) the strategy of creating large numbers of targeted pages using templates and data. Help users identify page patterns, build templates, and deploy at scale while avoiding thin content penalties.
What is Programmatic SEO?
Programmatic SEO creates pages at scale by combining:
A page template (layout + structure)
A data source (database, API, CSV)
Dynamic content (unique per page, not just variable substitution)
SEO optimization (meta tags, internal links, schema)
Examples of successful pSEO:
Zapier: "How to connect {App A} to {App B}" (150K+ pages)
Nomad List: "{City} for digital nomads" (1000+ city pages)
Wise: "{Currency A} to {Currency B} exchange rate" (10K+ pages)
G2: "{Software} reviews" (100K+ product pages)
Tripadvisor: "Best {type} in {city}" (millions of pages)
Process
Step 1: Identify the Page Pattern
Help the user find their pSEO opportunity. Look for patterns where:
Pattern formula: {Modifier} + {Head Term} + {Qualifier}
Pattern Type Formula Example Volume Potential
Location + Service "{service} in {city}" "plumber in Austin" Cities x Services
Comparison "{product A} vs {product B}" "Notion vs Asana" nC2 combinations
Integration "{tool A} + {tool B} integration" "Slack Salesforce integration" Tools x Tools
Template/Example "{type} template" "invoice template" Types count
Stats/Data "{topic} statistics {year}" "remote work statistics 2025" Topics x Years
Glossary "What is {term}" "What is APR" Terms count
Best/Top "Best {product} for {use case}" "Best CRM for startups" Products x Uses
Review "{product} review" "Airtable review" Products count
Alternative "{product} alternatives" "Slack alternatives" Products count
Cost/Pricing "How much does {service} cost" "How much does a website cost" Services count
Qualification criteria for a good pSEO opportunity:
[ ] Pattern has 100+ possible pages minimum
[ ] Each combination has measurable search volume (even 10 50/mo is fine at scale)
[ ] You can generate genuinely useful, unique content for each page
[ ] The data is available (API, database, web scraping)
[ ] Competitors aren't already dominating with better data
[ ] Pages serve real user intent (not just keyword stuffing)
Step 2: Build the Data Source
Define the data model that powers the pages:
Data sources to consider:
Public APIs (government data, Wikipedia, industry databases)
Web scraping (with permission/robots.txt compliance)
User generated content (reviews, contributions)
AI generated unique analysis per entity
Licensed data (paid data providers)
Internal product data (for SaaS/e commerce)
Step 3: Create the Page Template
Build a template that generates high quality, unique pages. Critical principle: each page must provide standalone value.
Template Structure
Avoiding Thin Content
The 1 risk in pSEO is thin content. Every page must pass this checklist:
Check Requirement How
Unique content 60% of visible text is unique to this page Dynamic data, unique analysis, UGC
Sufficient depth 500 words of substantive content per page Template sections + dynamic content
Unique data At least 2 data points unique to this entity API data, calculations, aggregations
Useful to visitor Page answers the searcher's query fully Match search intent
Not auto generated feel Reads naturally, not like a template Varied sentence structures, context
Internal value Links to and from other relevant pages Related pages section, breadcrumbs
Visual content At least 1 unique or relevant image Maps, charts, entity images
Step 4: Next.js Implementation
Dynamic Routes (App Router)
Sitemap Generation
For large sitemaps (50,000+ URLs), use sitemap index:
Robots.txt Management
Step 5: Internal Linking Strategy
Internal linking is critical for pSEO. Implement these patterns:
1. Hub and Spoke:
2. Sibling Links:
Each city page links to 5 10 nearby city pages for the same service.
3. Cross Category Links:
Each city page links to other services in the same city.
4. Breadcrumb Navigation:
5. Footer/Sidebar Links:
Popular pages and category indexes.
Implementation pattern:
Step 6: Indexation Management
When deploying thousands of pages, manage indexation carefully:
Gradual rollout:
1. Deploy 50 100 pages first
2. Monitor indexation in Google Search Console
3. Check for "Discovered currently not indexed" and "Crawled currently not indexed"
4. If indexation rate 80%, continue deploying in batches of 500 1000
5. If indexation rate < 50%, improve page quality before deploying more
Indexation signals:
Submit sitemap to Google Search Console
Use IndexNow API (Bing, Yandex) for faster discovery
Internal link from high authority existing pages
Share initial pages on social media for crawl signals
Quality thresholds:
If Google indexes < 30% of pages, your template likely produces thin content
If pages get indexed then dropped, content quality is borderline
Monitor "Page experience" and "Core Web Vitals" in GSC for pSEO pages
Step 7: Meta Tag Formulas
Use these formulas for generating meta tags at scale:
Title tag formulas (50 60 chars):
Meta description formulas (150 160 chars):
H1 formulas:
Output
When helping a user with programmatic SEO, deliver:
1. Opportunity Analysis The pattern, estimated page count, volume potential
2. Data Model TypeScript interface for the page data
3. Page Template Complete template with all sections
4. Sample Pages 2 3 fully rendered example pages
5. Implementation Plan Next.js code for routes, sitemap, robots.txt
6. Internal Linking Strategy How pages connect
7. Indexation Plan Rollout schedule and monitoring metrics
8. Quality Checklist Per page quality criteria
Common Pitfalls
Template stuffing: Just swapping city names in identical text = thin content penalty
No unique data: Pages without entity specific data points add no value
Over generation: Creating pages for combinations with zero search volume wastes crawl budget
Ignoring cannibalization: Overlapping pages compete with each other. Map one keyword per page.
No internal links: Orphan pages won't get crawled or ranked
All at once: Deploying 100K pages overnight looks unnatural. Batch them.
Ignoring noindex: Some pages may not deserve indexing. Use noindex for low quality or duplicate combinations.