Create SEO-driven pages at scale using templates and data

Programmatic SEO

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

When the user wants to create SEO-driven pages at scale using templates and data.

---
name: programmatic-seo
description: 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.
metadata:
  version: 2.0.0
---

# 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:

Overview

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.

Manual install (npx, ZIP)

Claude Codenpx skills add coreyhaines31/marketingskills --skill programmatic-seo -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \
  | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/programmatic-seo

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/6f726e1b1225be1d1448/programmatic-seo.zip" -OutFile "$env:TEMP\programmatic-seo.zip"; Expand-Archive "$env:TEMP\programmatic-seo.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md6.9 KB
evals/1 file · 6.7 KB
references/1 file · 8.1 KB

Read the files here

coreyhaines31/5b2c0003 files

SKILL.md6.9 KB

SKILL.md

Show the full text239 lines

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

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?

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

1	---
2	name: programmatic-seo
3	description: 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.
4	metadata:
5	version: 2.0.0
6	---
7
8	# Programmatic SEO
9
10	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.
11
12	## Initial Assessment
13
14	Check for product marketing context first:
15	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.
16
17	Before designing a programmatic SEO strategy, understand:
18
19	1. Business Context
20	- What's the product/service?
21	- Who is the target audience?
22	- What's the conversion goal for these pages?
23
24	2. Opportunity Assessment
25	- What search patterns exist?
26	- How many potential pages?
27	- What's the search volume distribution?
28
29	3. Competitive Landscape
30	- Who ranks for these terms now?
31	- What do their pages look like?
32	- Can you realistically compete?
33
34	---
35
36	## Core Principles
37
38	### 1. Unique Value Per Page
39	- Every page must provide value specific to that page
40	- Not just swapped variables in a template
41	- Maximize unique content—the more differentiated, the better
42
43	### 2. Proprietary Data Wins
44	Hierarchy of data defensibility:
45	1. Proprietary (you created it)
46	2. Product-derived (from your users)
47	3. User-generated (your community)
48	4. Licensed (exclusive access)
49	5. Public (anyone can use—weakest)
50
51	### 3. Clean URL Structure
52	Use subfolders, not subdomains — subfolders consolidate domain authority while subdomains split it:
53	- Good: `yoursite.com/templates/resume/`
54	- Bad: `templates.yoursite.com/resume/`
55
56	### 4. Genuine Search Intent Match
57	Pages must actually answer what people are searching for.
58
59	### 5. Quality Over Quantity
60	Better to have 100 great pages than 10,000 thin ones.
61
62	### 6. Avoid Google Penalties
63	- No doorway pages
64	- No keyword stuffing
65	- No duplicate content
66	- Genuine utility for users
67
68	---
69
70	## The 12 Playbooks (Overview)
71
72	\| Playbook \| Pattern \| Example \|
73	\|----------\|---------\|---------\|
74	\| Templates \| "[Type] template" \| "resume template" \|
75	\| Curation \| "best [category]" \| "best website builders" \|
76	\| Conversions \| "[X] to [Y]" \| "$10 USD to GBP" \|
77	\| Comparisons \| "[X] vs [Y]" \| "webflow vs wordpress" \|
78	\| Examples \| "[type] examples" \| "landing page examples" \|
79	\| Locations \| "[service] in [location]" \| "dentists in austin" \|
80	\| Personas \| "[product] for [audience]" \| "crm for real estate" \|
81	\| Integrations \| "[product A] [product B] integration" \| "slack asana integration" \|
82	\| Glossary \| "what is [term]" \| "what is pSEO" \|
83	\| Translations \| Content in multiple languages \| Localized content \|
84	\| Directory \| "[category] tools" \| "ai copywriting tools" \|
85	\| Profiles \| "[entity name]" \| "stripe ceo" \|
86
87	For detailed playbook implementation: See [references/playbooks.md](references/playbooks.md)
88
89	---
90
91	## Choosing Your Playbook
92
93	\| If you have... \| Consider... \|
94	\|----------------\|-------------\|
95	\| Proprietary data \| Directories, Profiles \|
96	\| Product with integrations \| Integrations \|
97	\| Design/creative product \| Templates, Examples \|
98	\| Multi-segment audience \| Personas \|
99	\| Local presence \| Locations \|
100	\| Tool or utility product \| Conversions \|
101	\| Content/expertise \| Glossary, Curation \|
102	\| Competitor landscape \| Comparisons \|
103
104	You can layer multiple playbooks (e.g., "Best coworking spaces in San Diego").
105
106	---
107
108	## Implementation Framework
109
110	### 1. Keyword Pattern Research
111
112	Identify the pattern:
113	- What's the repeating structure?
114	- What are the variables?
115	- How many unique combinations exist?
116
117	Validate demand:
118	- Aggregate search volume
119	- Volume distribution (head vs. long tail)
120	- Trend direction
121
122	### 2. Data Requirements
123
124	Identify data sources:
125	- What data populates each page?
126	- Is it first-party, scraped, licensed, public?
127	- How is it updated?
128
129	### 3. Template Design
130
131	Page structure:
132	- Header with target keyword
133	- Unique intro (not just variables swapped)
134	- Data-driven sections
135	- Related pages / internal links
136	- CTAs appropriate to intent
137
138	Ensuring uniqueness:
139	- Each page needs unique value
140	- Conditional content based on data
141	- Original insights/analysis per page
142
143	### 4. Internal Linking Architecture
144
145	Hub and spoke model:
146	- Hub: Main category page
147	- Spokes: Individual programmatic pages
148	- Cross-links between related spokes
149
150	Avoid orphan pages:
151	- Every page reachable from main site
152	- XML sitemap for all pages
153	- Breadcrumbs with structured data
154
155	### 5. Indexation Strategy
156
157	- Prioritize high-volume patterns
158	- Noindex very thin variations
159	- Manage crawl budget thoughtfully
160	- Separate sitemaps by page type
161
162	---
163
164	## Quality Checks
165
166	### Pre-Launch Checklist
167
168	Content quality:
169	- [ ] Each page provides unique value
170	- [ ] Answers search intent
171	- [ ] Readable and useful
172
173	Technical SEO:
174	- [ ] Unique titles and meta descriptions
175	- [ ] Proper heading structure
176	- [ ] Schema markup implemented
177	- [ ] Page speed acceptable
178
179	Internal linking:
180	- [ ] Connected to site architecture
181	- [ ] Related pages linked
182	- [ ] No orphan pages
183
184	Indexation:
185	- [ ] In XML sitemap
186	- [ ] Crawlable
187	- [ ] No conflicting noindex
188
189	### Post-Launch Monitoring
190
191	Track: Indexation rate, Rankings, Traffic, Engagement, Conversion
192
193	Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors
194
195	---
196
197	## Common Mistakes
198
199	- Thin content: Just swapping city names in identical content
200	- Keyword cannibalization: Multiple pages targeting same keyword
201	- Over-generation: Creating pages with no search demand
202	- Poor data quality: Outdated or incorrect information
203	- Ignoring UX: Pages exist for Google, not users
204
205	---
206
207	## Output Format
208
209	### Strategy Document
210	- Opportunity analysis
211	- Implementation plan
212	- Content guidelines
213
214	### Page Template
215	- URL structure
216	- Title/meta templates
217	- Content outline
218	- Schema markup
219
220	---
221
222	## Task-Specific Questions
223
224	1. What keyword patterns are you targeting?
225	2. What data do you have (or can acquire)?
226	3. How many pages are you planning?
227	4. What does your site authority look like?
228	5. Who currently ranks for these terms?
229	6. What's your technical stack?
230
231	---
232
233	## Related Skills
234
235	- seo-audit: For auditing programmatic pages after launch
236	- schema: For adding structured data
237	- site-architecture: For page hierarchy, URL structure, and internal linking
238	- competitors: For comparison page frameworks
239