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
Before designing a programmatic SEO strategy, understand:
1. Business Context
- What's the product/service?
- Who is the target audience?
- What's the conversion goal for these pages?
2. Opportunity Assessment
- What search patterns exist?
- How many potential pages?
- What's the search volume distribution?
3. Competitive Landscape
- Who ranks for these terms now?
- What do their pages look like?
- What would it take to beat them?
---
Core Principles
1. Unique Value Per Page
Every page must provide value specific to that page:
2. Proprietary Data Wins
The best pSEO uses data competitors can't easily replicate:
Hierarchy of data defensibility:
1. Proprietary (you created it)
2. Product-derived (from your users)
3. User-generated (your community)
4. Licensed (exclusive access)
5. Public (anyone can use—weakest)
3. Clean URL Structure
Always use subfolders, not subdomains:
yoursite.com/templates/resume/templates.yoursite.com/resume/Subfolders pass authority to your main domain. Subdomains are treated as separate sites by Google.
URL best practices:
4. Genuine Search Intent Match
Pages must actually answer what people are searching for:
5. Scalable Quality, Not Just Quantity
6. Avoid Google Penalties
---
The 12 Programmatic SEO Playbooks
Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
URL structure: /compare/[x]-vs-[y]/ or /[x]-vs-[y]/
See also: competitor-alternatives 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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
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:
Value requirements:
URL structure: /people/[name]/ or /companies/[name]/
---
Choosing Your Playbook
Match to Your Assets
| If you have... | Consider... |
|----------------|-------------|
| Proprietary data | Stats, 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 |
| International potential | Translations |
| Competitor landscape | Comparisons |
Combine Playbooks
You can layer multiple playbooks:
---
Implementation Framework
1. Keyword Pattern Research
Identify the pattern:
Validate demand:
Assess competition:
2. Data Requirements
Identify data sources:
Data schema design:
For "[Service] in [City]" pages:
city:
- name
- population
- relevant_stats
service:
- name
- description
- typical_pricing
local_providers:
- name
- rating
- reviews_count
- specialty
local_data:
- regulations
- average_prices
- market_size
3. Template Design
Page structure:
Ensuring uniqueness:
Template example:
H1: [Service] in [City]: [Year] Guide
Intro: [Dynamic paragraph using city stats + service context]
Section 1: Why [City] for [Service]
[City-specific data and insights]
Section 2: Top [Service] Providers in [City]
[Data-driven list with unique details]
Section 3: Pricing for [Service] in [City]
[Local pricing data if available]
Section 4: FAQs about [Service] in [City]
[Common questions with city-specific answers]
Related: [Service] in [Nearby Cities]
4. Internal Linking Architecture
Hub and spoke model:
Avoid orphan pages:
Breadcrumbs:
5. Indexation Strategy
Prioritize important pages:
Crawl budget management:
Sitemap strategy:
---
Quality Checks
Pre-Launch Checklist
Content quality:
Technical SEO:
Internal linking:
Indexation:
Monitoring Post-Launch
Track:
Watch for:
---
Common Mistakes to Avoid
Thin Content
Keyword Cannibalization
Over-Generation
Poor Data Quality
Ignoring User Experience
---
Output Format
Strategy Document
Opportunity Analysis:
Implementation Plan:
Content Guidelines:
Page Template
URL structure: /category/variable/
Title template: [Variable] + [Static] + [Brand]
Meta description template: [Pattern with variables]
H1 template: [Pattern]
Content outline: Section by section
Schema markup: Type and required fields
Launch Checklist
Specific pre-launch checks for this implementation
---
Questions to Ask
If you need more context:
1. What keyword patterns are you targeting?
2. What data do you have (or can acquire)?
3. How many pages are you planning to create?
4. What does your site authority look like?
5. Who currently ranks for these terms?
6. What's your technical stack for generating pages?
---
Related Skills
相关技能
- A
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
- A
analytics-tracking
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
- A
atxp
Access ATXP paid API tools for web search, AI image generation, music creation, video generation, and X/Twitter search. Use when users need real-time web search, AI-generated media (images, music, video), or X/Twitter search. Requires authentication via `npx atxp login`.
- B
better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
- B
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.