programmatic-seo
Skill870 starsChanged 3 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 78 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Common: line 17
Before designing a programmatic SEO strategy, understand:
- Common: line 39
Every page must provide value specific to that page
- Common: line 40
Not just swapped variables in a template
- Common: line 151
Every page reachable from main site
“Common” is measured: kept by at least 6 in 10 of the 78 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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?
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
Other versions103 projects use a version of this.
Word for word · 22
- Cesarjoquin/Marketing-Skills★ 190100% same
- open-fox/agents★ 55100% same
- SZcalligrapher/slash-skills-subscription★ 32100% same
- TommyBez/skillsboard★ 10100% same
- arsalang75523/contextkit★ 4100% same
- JustineDevs/premortem★ 2100% same
- agrivisionai/claude-skills★ 1100% same
- Hugovdd/skills★ 1100% same
- ngothanhtung/claude-code-skills★ 1100% same
- patinaproject/skills★ 1100% same
12 more not listed
Edited · 57
- coreyhaines31/marketingskills★ 58k87% same
- TheCraigHewitt/seomachine★ 7.5k94% same
- yoopta-editor/Yoopta-Editor★ 3.1k94% same
- VladSez/easy-invoice-pdf★ 1.1k99% same
- KartikLabhshetwar/screenshot-studio★ 1.1k94% same
- KartikLabhshetwar/stage★ 1.1k94% same
- LeoYeAI/openclaw-marketing-skills★ 1k97% same
- mysticaltech/marketingskills★ 35295% same
- boraoztunc/skills★ 33794% same
- theexperiencecompany/gaia★ 32494% same
47 more not listed
Wrote their own version · 24
- nowork-studio/notfair-plugin★ 4.1ksame name
- nowork-studio/toprank★ 4ksame name
- kostja94/marketing-skills★ 1.1ksame name
- indranilbanerjee/digital-marketing-pro★ 920same name
- OpenClaudia/openclaudia-skills★ 724same name
- vercel-labs/marketing-team-eve-template★ 459same name
- GTMify/aigtm★ 25same name
- dalroot/agentic-seo★ 23same name
- xfstudio/skills★ 9same name
- scayver/marketing-skills★ 8same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use popups, paywalls and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 14 projects that use this
- CesarjoquinSkill
paywalls
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
Also in 14 projects that use this
silvainfmSkillsignup-flow-cro
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
Also in 25 projects that use this
- silvainfmSkill
popup-cro
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
Also in 24 projects that use this
ukunal91appSkillrevops
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
Also in 31 projects that use this
OpenClaudiaSkillpodcast-marketing
Plan, produce, and market a podcast. Use when the user says "podcast strategy", "start a podcast", "podcast marketing", "podcast growth", "podcast SEO", "show notes", "podcast monetization", "guest outreach", or asks about launching, growing, or promoting a podcast.
Also in 3 projects that use this
- +1 more from Cesarjoquin
- +3 more from silvainfm
In this repository30 other files it gives its agents.
- AGENTS.MDAGENTS.md
- ai-seoSkill
- analyticsSkill
- attributionSkill
- churn-preventionSkill
- co-marketingSkill
- community-marketingSkill
- competitor-profilingSkill
- competitorsSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- imageSkill
- influencer-marketingSkill
- launchSkill
- marketing-councilSkill
- marketing-ideasSkill
- marketing-loopsSkill
- marketing-planSkill
- marketing-psychologySkill
- offersSkill
- onboardingSkill
- pricingSkill
- product-marketingSkill
- seo-auditSkill
- seoSkill
- site-architectureSkill
- videoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.