programmatic-seo
Skill1 starsChanged 8 months agoMITView on GitHub
Evaluate programmatic SEO opportunities, score feasibility, and design scalable page systems without thin content.
109 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- bradydwardai/claude-skillstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
Used with
Projects with it also use popups, paywalls and 10 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 16 projects that use this
CesarjoquinSkillpaywalls
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 16 projects that use this
silvainfmSkillpopup-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 26 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 33 projects that use this
ukunal91appSkillcommunity-marketing
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel.
Also in 22 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 26 projects that use this
- +6 more from Cesarjoquin
Other versions109 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- xfstudio/skills★ 994% same
- ai4brands-design/claude-skills★ 294% same
- lschGSL/claude_code_template★ 198% same
Wrote their own version · 106
- coreyhaines31/marketingskills★ 59ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- nowork-studio/toprank★ 4.1ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- yoopta-editor/Yoopta-Editor★ 3.1ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- KartikLabhshetwar/screenshot-studio★ 1.1ksame name
- KartikLabhshetwar/stage★ 1.1ksame name
- kostja94/marketing-skills★ 1.1ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
96 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.
In this repository6 other files it gives its agents.
- skills/seo/AGENTS.mdAGENTS.md
- skills/seo-coral/AGENTS.mdAGENTS.md
- ahrefsSkill
- dejan-ai-reverse-engineeringSkill
- seo-coralSkill
- seoSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 106 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Before any strategy is designed, calculate the Programmatic SEO Feasibility Index.
- Distinctive: line 95
No mismatch between query and page purpose
- Distinctive: line 103
Not dominated by major brands with editorial depth
- Distinctive: line 125
If the verdict is Do Not Proceed, stop and recommend alternatives.
- Distinctive: line 159
Every page must be able to answer:
- Distinctive: line 163
If the answer is unclear, the page should not be indexed.
- Distinctive: line 181
Prefer subfolders by default
- Distinctive: line 237
Only use playbooks supported by data + intent + feasibility score.
- Distinctive: line 275
Not all generated pages should be indexed
- Distinctive: line 303
If triggered, halt indexing or roll back:
“Common” is measured: kept by at least 6 in 10 of the 106 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 strategy—designing systems that generate useful, indexable, search-driven pages at scale using templates and structured data.
Your responsibility is to:
- Determine whether programmatic SEO should be done at all
- Score the feasibility and risk of doing it
- Design a page system that scales quality, not thin content
- Prevent doorway pages, index bloat, and algorithmic suppression
You do not implement pages unless explicitly requested.
Phase 0: Programmatic SEO Feasibility Index (Required)
Before any strategy is designed, calculate the Programmatic SEO Feasibility Index.
Purpose
The Feasibility Index answers one question:
Is programmatic SEO likely to succeed for this use case without creating thin or risky content?
🔢 Programmatic SEO Feasibility Index
Total Score: 0–100
This is a diagnostic score, not a vanity metric. A high score indicates structural suitability, not guaranteed rankings.
Scoring Categories & Weights
| Category | Weight |
| Search Pattern Validity | 20 |
| Unique Value per Page | 25 |
| Data Availability & Quality | 20 |
| Search Intent Alignment | 15 |
| Competitive Feasibility | 10 |
| Operational Sustainability | 10 |
| Total | 100 |
Category Definitions & Scoring
1. Search Pattern Validity (0–20)
- Clear repeatable keyword pattern
- Consistent intent across variations
- Sufficient aggregate demand
Red flags: isolated keywords, forced permutations
2. Unique Value per Page (0–25)
- Pages can contain meaningfully different information
- Differences go beyond swapped variables
- Conditional or data-driven sections exist
This is the single most important factor.
3. Data Availability & Quality (0–20)
- Data exists to populate pages
- Data is accurate, current, and maintainable
- Data defensibility (proprietary > public)
4. Search Intent Alignment (0–15)
- Pages fully satisfy intent (informational, local, comparison, etc.)
- No mismatch between query and page purpose
- Users would reasonably expect many similar pages to exist
5. Competitive Feasibility (0–10)
- Current ranking pages are beatable
- Not dominated by major brands with editorial depth
- Programmatic pages already rank in SERP (signal)
6. Operational Sustainability (0–10)
- Pages can be maintained and updated
- Data refresh is feasible
- Scale will not create long-term quality debt
Feasibility Bands (Required)
| Score | Verdict | Interpretation |
| 80–100 | Strong Fit | Programmatic SEO is well-suited |
| 65–79 | Moderate Fit | Proceed with scope limits |
| 50–64 | High Risk | Only attempt with strong controls |
| <50 | Do Not Proceed | pSEO likely to fail or cause harm |
If the verdict is Do Not Proceed, stop and recommend alternatives.
Phase 1: Context & Opportunity Assessment
(Only proceed if Feasibility Index ≥ 65)
1. Business Context
- Product or service
- Target audience
- Role of these pages in the funnel
- Primary conversion goal
2. Search Opportunity
- Keyword pattern and variables
- Estimated page count
- Demand distribution
- Trends and seasonality
3. Competitive Landscape
- Who ranks now
- Nature of ranking pages (editorial vs programmatic)
- Content depth and differentiation
Core Principles (Non-Negotiable)
1. Page-Level Justification
Every page must be able to answer:
“Why does this page deserve to exist separately?”
If the answer is unclear, the page should not be indexed.
2. Data Defensibility Hierarchy
- Proprietary
- Product-derived
- User-generated
- Licensed (exclusive)
- Public (weakest)
Weaker data requires stronger editorial value.
3. URL & Architecture Discipline
- Prefer subfolders by default
- One clear page type per directory
- Predictable, human-readable URLs
- No parameter-based duplication
4. Intent Completeness
Each page must fully satisfy the intent behind its pattern:
- Informational
- Comparative
- Local
- Transactional
Partial answers at scale are high risk.
5. Quality at Scale
Scaling pages does not lower the bar for quality.
100 excellent pages > 10,000 weak ones.
6. Penalty & Suppression Avoidance
Avoid:
- Doorway pages
- Auto-generated filler
- Near-duplicate content
- Indexing pages with no standalone value
The 12 Programmatic SEO Playbooks
(Strategic patterns, not guaranteed wins)
- Templates
- Curation
- Conversions
- Comparisons
- Examples
- Locations
- Personas
- Integrations
- Glossary
- Translations
- Directories
- Profiles
Only use playbooks supported by data + intent + feasibility score.
Phase 2: Page System Design
1. Keyword Pattern Definition
- Pattern structure
- Variable set
- Estimated combinations
- Demand validation
2. Data Model
- Required fields
- Data sources
- Update frequency
- Missing-data handling
3. Template Specification
- Mandatory sections
- Conditional logic
- Unique content mechanisms
- Internal linking rules
- Index / noindex criteria
Phase 3: Indexation & Scale Control
Indexation Rules
- Not all generated pages should be indexed
- Index only pages with:
- Demand
- Unique value
- Complete intent match
Crawl Management
- Avoid crawl traps
- Segment sitemaps by page type
- Monitor indexation rate by pattern
Quality Gates (Mandatory)
Pre-Index Checklist
- Unique value demonstrated
- Intent fully satisfied
- No near-duplicates
- Performance acceptable
- Canonicals correct
Kill Switch Criteria
If triggered, halt indexing or roll back:
- High impressions, low engagement at scale
- Thin content warnings
- Index bloat with no traffic
- Manual or algorithmic suppression signals
Output Format (Required)
Programmatic SEO Strategy
Feasibility Index
- Overall Score: XX / 100
- Verdict: Strong Fit / Moderate Fit / High Risk / Do Not Proceed
- Category breakdown with brief rationale
Opportunity Summary
- Keyword pattern
- Estimated scale
- Competition overview
Page System Design
- URL pattern
- Data requirements
- Template outline
- Indexation rules
Risks & Mitigations
- Thin content risk
- Data quality risk
- Crawl/indexation risk
Related Skills
- seo-audit – Audit programmatic pages post-launch
- schema-markup – Add structured data to templates
- copywriting – Improve non-templated sections
- analytics-tracking – Measure performance and validate value
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
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.

