Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

programmatic-seo

Estrellas2

Forks0

Actualizado29 de marzo de 2026 a las 18:06

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

yel-hadd

yel-hadd/scrimbaguide.tech

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de investigación de mercados y especialistas en marketingOperaciones empresariales y financieras·SOC 13-1161

Explorador de archivos

2 archivos

SKILL.md

readonly

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":"1.1.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 .cursor/product-marketing-context.md exists (or .claude/product-marketing-context.md 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-markup: For adding structured data
site-architecture: For page hierarchy, URL structure, and internal linking
competitor-alternatives: For comparison page frameworks

Más de este repositorio

mismo repositorio

ab-test-setup

yel-hadd/scrimbaguide.tech

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

2026-03-292

ad-creative

yel-hadd/scrimbaguide.tech

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

2026-03-292

ai-seo

yel-hadd/scrimbaguide.tech

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

2026-03-292

analytics-tracking

yel-hadd/scrimbaguide.tech

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

2026-03-292

churn-prevention

yel-hadd/scrimbaguide.tech

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

2026-03-292

cold-email

yel-hadd/scrimbaguide.tech

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

2026-03-292