Initial release: 14 marketing skills for Claude Code
A collection of AI agent skills for technical marketers and founders: CRO Skills: - page-cro: Conversion optimization for marketing pages - signup-flow-cro: Signup/registration flow optimization - onboarding-cro: Post-signup activation and onboarding - form-cro: Lead capture and contact form optimization - popup-cro: Popup and modal optimization - paywall-upgrade-cro: In-app paywalls and upgrade screens Content Skills: - page-copywriting: Marketing page copy - email-sequence: Drip campaigns and email automation SEO Skills: - seo-audit: Technical and on-page SEO audits - programmatic-seo: Building SEO pages at scale - schema-markup: Structured data implementation Measurement Skills: - analytics-tracking: GA4, GTM, and event tracking - ab-test-setup: A/B test planning and analysis Growth Engineering: - free-tool-strategy: Engineering-as-marketing tools Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Corey Haines
410
skills/programmatic-seo.md
Normal file
410
skills/programmatic-seo.md
Normal file
@@ -0,0 +1,410 @@
|
||||
---
|
||||
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," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
|
||||
---
|
||||
|
||||
# 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:
|
||||
- Unique data
|
||||
- Unique insights
|
||||
- Unique combinations
|
||||
- Not just swapped variables in a template
|
||||
|
||||
### 2. Genuine Search Intent Match
|
||||
Pages must actually answer what people are searching for:
|
||||
- Understand the intent behind each pattern
|
||||
- Provide the complete answer
|
||||
- Don't over-optimize for keywords at expense of usefulness
|
||||
|
||||
### 3. Scalable Quality, Not Just Quantity
|
||||
- Quality standards must be maintained at scale
|
||||
- Better to have 100 great pages than 10,000 thin ones
|
||||
- Build quality checks into the process
|
||||
|
||||
### 4. Avoid Google Penalties
|
||||
- No doorway pages (thin pages that just funnel to main site)
|
||||
- No keyword stuffing
|
||||
- No duplicate content across pages
|
||||
- Genuine utility for users
|
||||
|
||||
---
|
||||
|
||||
## Common Programmatic SEO Patterns
|
||||
|
||||
### Location-Based Pages
|
||||
**Pattern**: "[Service] in [Location]"
|
||||
**Examples**:
|
||||
- "Plumbers in Austin"
|
||||
- "Coworking spaces in Brooklyn"
|
||||
- "Real estate agents in Miami"
|
||||
|
||||
**Value requirements**:
|
||||
- Location-specific information
|
||||
- Local data (stats, regulations, etc.)
|
||||
- Local testimonials/case studies
|
||||
- Not just [City] swapped in template
|
||||
|
||||
### Integration/Compatibility Pages
|
||||
**Pattern**: "[Tool] + [Tool]" or "[Product] for [Platform]"
|
||||
**Examples**:
|
||||
- "Slack + Asana integration"
|
||||
- "CRM for Shopify"
|
||||
- "Zapier alternatives for X"
|
||||
|
||||
**Value requirements**:
|
||||
- Genuine integration details
|
||||
- Use cases for the combination
|
||||
- Setup instructions
|
||||
- Comparison if relevant
|
||||
|
||||
### Comparison Pages
|
||||
**Pattern**: "[X] vs [Y]" or "[X] alternatives"
|
||||
**Examples**:
|
||||
- "Notion vs Coda"
|
||||
- "Airtable alternatives"
|
||||
- "Best CRMs for small business"
|
||||
|
||||
**Value requirements**:
|
||||
- Actual comparison data
|
||||
- Honest pros/cons
|
||||
- Use case recommendations
|
||||
- Updated regularly
|
||||
|
||||
### Directory/Aggregator Pages
|
||||
**Pattern**: "[Category] + [Qualifier]"
|
||||
**Examples**:
|
||||
- "Top marketing agencies in [city]"
|
||||
- "Best restaurants for [cuisine] in [area]"
|
||||
- "[Software] companies in [industry]"
|
||||
|
||||
**Value requirements**:
|
||||
- Curated, not just scraped
|
||||
- Useful details per listing
|
||||
- Filters/sorting for utility
|
||||
- Fresh data
|
||||
|
||||
### Stats/Data Pages
|
||||
**Pattern**: "[Topic] statistics [year]"
|
||||
**Examples**:
|
||||
- "Email marketing statistics 2024"
|
||||
- "Remote work trends by industry"
|
||||
- "Average [metric] by [segment]"
|
||||
|
||||
**Value requirements**:
|
||||
- Original or well-sourced data
|
||||
- Visualization
|
||||
- Updated regularly
|
||||
- Unique analysis
|
||||
|
||||
### Use Case Pages
|
||||
**Pattern**: "[Product] for [Use Case]"
|
||||
**Examples**:
|
||||
- "Notion for project management"
|
||||
- "Airtable for inventory tracking"
|
||||
- "Figma for presentations"
|
||||
|
||||
**Value requirements**:
|
||||
- Specific setup/workflow
|
||||
- Templates if applicable
|
||||
- Real examples
|
||||
- Unique to use case
|
||||
|
||||
### Glossary/Definition Pages
|
||||
**Pattern**: "What is [term]"
|
||||
**Examples**:
|
||||
- "What is product-led growth"
|
||||
- "API meaning in software"
|
||||
- "CRM definition"
|
||||
|
||||
**Value requirements**:
|
||||
- Clear, comprehensive definition
|
||||
- Related terms
|
||||
- Examples
|
||||
- Further reading
|
||||
|
||||
---
|
||||
|
||||
## 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 for pattern
|
||||
- Volume distribution (head vs. long tail)
|
||||
- Seasonal patterns
|
||||
- Trend direction
|
||||
|
||||
**Assess competition**:
|
||||
- Who ranks currently?
|
||||
- What's their content quality?
|
||||
- What's their domain authority?
|
||||
- Can you realistically compete?
|
||||
|
||||
### 2. Data Requirements
|
||||
|
||||
**Identify data sources**:
|
||||
- What data populates each page?
|
||||
- Where does that data come from?
|
||||
- Is it first-party, scraped, licensed, public?
|
||||
- How is it updated?
|
||||
|
||||
**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**:
|
||||
- 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
|
||||
- User-generated content where possible
|
||||
- Original insights/analysis per page
|
||||
|
||||
**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**:
|
||||
- Hub: Main category page
|
||||
- Spokes: Individual programmatic pages
|
||||
- Cross-links between related spokes
|
||||
|
||||
**Avoid orphan pages**:
|
||||
- Every page reachable from main site
|
||||
- Logical category structure
|
||||
- XML sitemap for all pages
|
||||
|
||||
**Breadcrumbs**:
|
||||
- Show hierarchy
|
||||
- Structured data markup
|
||||
- User navigation aid
|
||||
|
||||
### 5. Indexation Strategy
|
||||
|
||||
**Prioritize important pages**:
|
||||
- Not all pages need to be indexed
|
||||
- Index high-volume patterns
|
||||
- Noindex very thin variations
|
||||
|
||||
**Crawl budget management**:
|
||||
- Paginate thoughtfully
|
||||
- Avoid infinite crawl traps
|
||||
- Use robots.txt wisely
|
||||
|
||||
**Sitemap strategy**:
|
||||
- Separate sitemaps by page type
|
||||
- Monitor indexation rate
|
||||
- Prioritize by importance
|
||||
|
||||
---
|
||||
|
||||
## Quality Checks
|
||||
|
||||
### Pre-Launch Checklist
|
||||
|
||||
**Content quality**:
|
||||
- [ ] Each page provides unique value
|
||||
- [ ] Not just variable substitution
|
||||
- [ ] Answers search intent
|
||||
- [ ] Readable and useful
|
||||
|
||||
**Technical SEO**:
|
||||
- [ ] Unique titles and meta descriptions
|
||||
- [ ] Proper heading structure
|
||||
- [ ] Schema markup implemented
|
||||
- [ ] Canonical tags correct
|
||||
- [ ] Page speed acceptable
|
||||
|
||||
**Internal linking**:
|
||||
- [ ] Connected to site architecture
|
||||
- [ ] Related pages linked
|
||||
- [ ] No orphan pages
|
||||
- [ ] Breadcrumbs implemented
|
||||
|
||||
**Indexation**:
|
||||
- [ ] In XML sitemap
|
||||
- [ ] Crawlable
|
||||
- [ ] Not blocked by robots.txt
|
||||
- [ ] No conflicting noindex
|
||||
|
||||
### Monitoring Post-Launch
|
||||
|
||||
**Track**:
|
||||
- Indexation rate
|
||||
- Rankings by page pattern
|
||||
- Traffic by page pattern
|
||||
- Engagement metrics
|
||||
- Conversion rate
|
||||
|
||||
**Watch for**:
|
||||
- Thin content warnings in Search Console
|
||||
- Ranking drops
|
||||
- Manual actions
|
||||
- Crawl errors
|
||||
|
||||
---
|
||||
|
||||
## Common Mistakes to Avoid
|
||||
|
||||
### Thin Content
|
||||
- Just swapping city names in identical content
|
||||
- No unique information per page
|
||||
- "Doorway pages" that just redirect
|
||||
|
||||
### Keyword Cannibalization
|
||||
- Multiple pages targeting same keyword
|
||||
- No clear hierarchy
|
||||
- Competing with yourself
|
||||
|
||||
### Over-Generation
|
||||
- Creating pages with no search demand
|
||||
- Too many low-quality pages dilute authority
|
||||
- Quantity over quality
|
||||
|
||||
### Poor Data Quality
|
||||
- Outdated information
|
||||
- Incorrect data
|
||||
- Missing data showing as blank
|
||||
|
||||
### Ignoring User Experience
|
||||
- Pages exist for Google, not users
|
||||
- No conversion path
|
||||
- Bouncy, unhelpful content
|
||||
|
||||
---
|
||||
|
||||
## Output Format
|
||||
|
||||
### Strategy Document
|
||||
|
||||
**Opportunity Analysis**:
|
||||
- Keyword pattern identified
|
||||
- Search volume estimates
|
||||
- Competition assessment
|
||||
- Feasibility rating
|
||||
|
||||
**Implementation Plan**:
|
||||
- Data requirements and sources
|
||||
- Template structure
|
||||
- Number of pages (phases)
|
||||
- Internal linking plan
|
||||
- Technical requirements
|
||||
|
||||
**Content Guidelines**:
|
||||
- What makes each page unique
|
||||
- Quality standards
|
||||
- Update frequency
|
||||
|
||||
### 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
|
||||
|
||||
- **seo-audit**: For auditing programmatic pages after launch
|
||||
- **schema-markup**: For adding structured data to templates
|
||||
- **page-copywriting**: For the non-templated copy portions
|
||||
- **analytics-tracking**: For measuring programmatic page performance
|
||||
Reference in New Issue
Block a user