Programmatic SEO
Corey HainesCommunityCreated by Corey Haines
- Skill
- Workflow
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to programmatic SEO (pSEO), enabling users to generate large volumes of search-optimized pages using templates and data. It emphasizes creating unique value per page to avoid thin content penalties, utilizing proprietary or product-derived data, and maintaining a clean URL structure. The skill includes twelve distinct playbooks for common patterns like location-based pages, comparisons, and directories, along with guidance on selecting technical platforms and managing indexation.
What it does
- Guides the selection of appropriate programmatic SEO playbooks based on data and business goals.
- Provides a framework for keyword pattern research and data requirement analysis.
- Outlines best practices for template design to ensure unique content per page.
- Advises on internal linking architecture and sitemap management for large page sets.
- Offers a pre-launch checklist covering content quality, technical SEO, and indexation.
- Assists in evaluating technical platforms for hosting and managing programmatic content.
When to use it
- When you need to create many similar pages targeting different keywords, locations, or user segments.
- When you have structured data that can be used to populate templates at scale.
- When you are planning to build directory, comparison, or location-based landing pages.
- When you need to assess the feasibility of a programmatic SEO strategy against your current site architecture.
Advantages
- Provides a systematic approach to scaling content production without sacrificing quality.
- Helps avoid common pitfalls like duplicate content, keyword cannibalization, and thin pages.
- Offers clear playbooks for diverse use cases ranging from integrations to local services.
- Focuses on defensible data strategies to improve search relevance.
Usage examples
- “I want to build 500 location-based pages for my dental practice. How should I start?”
- The agent will guide you through the location playbook, helping you identify the necessary local data, define the URL structure, and ensure each page provides unique value beyond just swapping city names.
- “We have a list of 1,000 software integrations. How do we turn these into SEO pages?”
- The agent will help you map this data to the integration playbook, advise on template design, and suggest an internal linking strategy to connect these pages to your main site.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/coreyhaines31/programmatic-seo/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip programmatic-seo.zip -d .agents/skills
Documentation by Corey Haines
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.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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
Prefer subfolders to subdomains. Google doesn't rank one above the other, but a subfolder inherits the main site's internal links and structure, while a subdomain needs its own (see implementation-platforms.md):
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
6. Choose the Build Platform
Check that the platform can hold the page count, refresh the data, render server-side HTML, branch on data for conditional sections, and control indexation per page. Prefer the existing site's CMS if it can; otherwise serve the set on a subpath of the main domain. Options and tradeoffs: references/implementation-platforms.md.
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: For adding structured data
site-architecture: For page hierarchy, URL structure, and internal linking
competitors: For comparison page frameworks
Files
- ATTRIBUTION.mdAdded by AutoGineer893 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md7.5 KiB
- evals/evals.json8.0 KiB
- references/implementation-platforms.md5.5 KiB
- references/playbooks.md8.1 KiB
references/playbooks.md
The 12 Programmatic SEO Playbooks
Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO.
Contents
Templates
Curation
Conversions
Comparisons
Examples
Locations
Personas
Integrations
Glossary
Translations
Directory
Profiles
Choosing Your Playbook (Match to Your Assets, Combine Playbooks)
1. Templates
Pattern: "[Type] template" or "free [type] template" Example searches: "resume template", "invoice template", "pitch deck template"
What it is: Downloadable or interactive templates users can use directly.
Why it works:
High intent—people need it now
Shareable/linkable assets
Natural for product-led companies
Value requirements:
Actually usable templates (not just previews)
Multiple variations per type
Quality comparable to paid options
Easy download/use flow
URL structure: /templates/[type]/ or /templates/[category]/[type]/
2. Curation
Pattern: "best [category]" or "top [number] [things]" Example searches: "best website builders", "top 10 crm software", "best free design tools"
What it is: Curated lists ranking or recommending options in a category.
Why it works:
Comparison shoppers searching for guidance
High commercial intent
Evergreen with updates
Value requirements:
Genuine evaluation criteria
Real testing or expertise
Regular updates (date visible)
Not just affiliate-driven rankings
URL structure: /best/[category]/ or /[category]/best/
3. Conversions
Pattern: "[X] to [Y]" or "[amount] [unit] in [unit]" Example searches: "$10 USD to GBP", "100 kg to lbs", "pdf to word"
What it is: Tools or pages that convert between formats, units, or currencies.
Why it works:
Instant utility
Extremely high search volume
Repeat usage potential
Value requirements:
Accurate, real-time data
Fast, functional tool
Related conversions suggested
Mobile-friendly interface
URL structure: /convert/[from]-to-[to]/ or /[from]-to-[to]-converter/
4. Comparisons
Pattern: "[X] vs [Y]" or "[X] alternative" Example searches: "webflow vs wordpress", "notion vs coda", "figma alternatives"
What it is: Head-to-head comparisons between products, tools, or options.
Why it works:
High purchase intent
Clear search pattern
Scales with number of competitors
Value requirements:
Honest, balanced analysis
Actual feature comparison data
Clear recommendation by use case
Updated when products change
URL structure: /compare/[x]-vs-[y]/ or /[x]-vs-[y]/
See also: competitors skill for detailed frameworks
5. Examples
Pattern: "[type] examples" or "[category] inspiration" Example searches: "saas landing page examples", "email subject line examples", "portfolio website examples"
What it is: Galleries or collections of real-world examples for inspiration.
Why it works:
Research phase traffic
Highly shareable
Natural for design/creative tools
Value requirements:
Real, high-quality examples
Screenshots or embeds
Categorization/filtering
Analysis of why they work
URL structure: /examples/[type]/ or /[type]-examples/
6. Locations
Pattern: "[service/thing] in [location]" Example searches: "coworking spaces in san diego", "dentists in austin", "best restaurants in brooklyn"
What it is: Location-specific pages for services, businesses, or information.
Why it works:
Local intent is massive
Scales with geography
Natural for marketplaces/directories
Value requirements:
Actual local data (not just city name swapped)
Local providers/options listed
Location-specific insights (pricing, regulations)
Map integration helpful
URL structure: /[service]/[city]/ or /locations/[city]/[service]/
7. Personas
Pattern: "[product] for [audience]" or "[solution] for [role/industry]" Example searches: "payroll software for agencies", "crm for real estate", "project management for freelancers"
What it is: Tailored landing pages addressing specific audience segments.
Why it works:
Speaks directly to searcher's context
Higher conversion than generic pages
Scales with personas
Value requirements:
Genuine persona-specific content
Relevant features highlighted
Testimonials from that segment
Use cases specific to audience
URL structure: /for/[persona]/ or /solutions/[industry]/
8. Integrations
Pattern: "[your product] [other product] integration" or "[product] + [product]" Example searches: "slack asana integration", "zapier airtable", "hubspot salesforce sync"
What it is: Pages explaining how your product works with other tools.
Why it works:
Captures users of other products
High intent (they want the solution)
Scales with integration ecosystem
Value requirements:
Real integration details
Setup instructions
Use cases for the combination
Working integration (not vaporware)
URL structure: /integrations/[product]/ or /connect/[product]/
9. Glossary
Pattern: "what is [term]" or "[term] definition" or "[term] meaning" Example searches: "what is pSEO", "api definition", "what does crm stand for"
What it is: Educational definitions of industry terms and concepts.
Why it works:
Top-of-funnel awareness
Establishes expertise
Natural internal linking opportunities
Value requirements:
Clear, accurate definitions
Examples and context
Related terms linked
More depth than a dictionary
URL structure: /glossary/[term]/ or /learn/[term]/
10. Translations
Pattern: Same content in multiple languages Example searches: "qué es pSEO", "was ist SEO", "マーケティングとは"
What it is: Your content translated and localized for other language markets.
Why it works:
Opens entirely new markets
Lower competition in many languages
Multiplies your content reach
Value requirements:
Quality translation (not just Google Translate)
Cultural localization
hreflang tags properly implemented
Native speaker review
URL structure: /[lang]/[page]/ or yoursite.com/es/, /de/, etc.
11. Directory
Pattern: "[category] tools" or "[type] software" or "[category] companies" Example searches: "ai copywriting tools", "email marketing software", "crm companies"
What it is: Comprehensive directories listing options in a category.
Why it works:
Research phase capture
Link building magnet
Natural for aggregators/reviewers
Value requirements:
Comprehensive coverage
Useful filtering/sorting
Details per listing (not just names)
Regular updates
URL structure: /directory/[category]/ or /[category]-directory/
12. Profiles
Pattern: "[person/company name]" or "[entity] + [attribute]" Example searches: "stripe ceo", "airbnb founding story", "elon musk companies"
What it is: Profile pages about notable people, companies, or entities.
Why it works:
Informational intent traffic
Builds topical authority
Natural for B2B, news, research
Value requirements:
Accurate, sourced information
Regularly updated
Unique insights or aggregation
Not just Wikipedia rehash
URL structure: /people/[name]/ or /companies/[name]/
Choosing Your Playbook
Match to Your Assets
| If you have... | Consider... |
|---|---|
| Proprietary data | Directory, Profiles, Curation |
| 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 |
| International potential | Translations |
| Competitor landscape | Comparisons |
Combine Playbooks
You can layer multiple playbooks:
Locations + Personas: "Marketing agencies for startups in Austin"
Curation + Locations: "Best coworking spaces in San Diego"
Integrations + Personas: "Slack for sales teams"
Glossary + Translations: Multi-language educational content
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Corey Haines
- Publisher
- Corey Haines (Community)
- Source
- coreyhaines31/marketingskills · skills/programmatic-seo · commit 96798cf
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Corey Haines or Corey Haines.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download programmatic-seo.zip