.github/skills/marketing/programmatic-seo/SKILL.md
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.
npx skillsauth add thesethrose/peptidecalc programmatic-seoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, 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
Opportunity Assessment
Competitive Landscape
Hierarchy of data defensibility:
Always use subfolders, not subdomains:
yoursite.com/templates/resume/templates.yoursite.com/resume/Pages must actually answer what people are searching for.
Better to have 100 great pages than 10,000 thin ones.
| 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
| 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").
Identify the pattern:
Validate demand:
Identify data sources:
Page structure:
Ensuring uniqueness:
Hub and spoke model:
Avoid orphan pages:
Content quality:
Technical SEO:
Internal linking:
Indexation:
Track: Indexation rate, Rankings, Traffic, Engagement, Conversion
Watch for: Thin content warnings, Ranking drops, Manual actions, Crawl errors
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
tools
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
testing
Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
testing
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.