domains / marketing / programmatic-seo / programmatic-seo

programmatic-seo

Skill card

combined

The copies overlap on the core pSEO workflow (assessment, data hierarchy, playbooks, template design, internal linking, and indexation), but each contains material steps the others lack. coreyhaines31 and LeoYeAI are near-identical reproductions of the same procedure, while kostja94 adds an AI-assisted generation layer, a page-skill matrix, and a Contextus context-loading step. nowork-studio is a thin wrapper that delegates to a separate WORKFLOW.md and adds an argument-hint for site URL and pattern. Crowning one copy would hide the AI-enhanced differentiation approach and the external workflow reference.

Repositories

RepositoryPath
coreyhaines31/marketingskillsskills/programmatic-seo/SKILL.md
kostja94/marketing-skillsskills/seo/programmatic-seo/SKILL.md
nowork-studio/notfair-pluginskills/programmatic-seo/SKILL.md
LeoYeAI/openclaw-marketing-skillsskills/programmatic-seo/SKILL.md

Other copies

RoleRepositoryPath
peercoreyhaines31/marketingskillsskills/programmatic-seo/SKILL.md
peerkostja94/marketing-skillsskills/seo/programmatic-seo/SKILL.md
peernowork-studio/notfair-pluginskills/programmatic-seo/SKILL.md
peerLeoYeAI/openclaw-marketing-skillsskills/programmatic-seo/SKILL.md
inferiorLeoYeAI/openclaw-master-skillsskills/marketing-skills/references/programmatic-seo/SKILL.md
inferiorsickn33/agentic-awesome-skillsplugins/agentic-awesome-skills-claude/skills/programmatic-seo/SKILL.md
adaptersickn33/agentic-awesome-skillsplugins/agentic-awesome-skills/skills/programmatic-seo/SKILL.md
adaptersickn33/agentic-awesome-skillsplugins/agentic-bundle-aas-marketing-seo-growth/skills/programmatic-seo/SKILL.md
adaptersickn33/agentic-awesome-skillsskills/programmatic-seo/SKILL.md
adapterLeoYeAI/openclaw-master-skillsskills/programmatic-seo/SKILL.md

Combined skill

# Programmatic SEO

## Initial Assessment
1. Check for product marketing context: read `.agents/product-marketing.md` (or `.claude/product-marketing.md`, or `product-marketing-context.md`) if present. Also read root `contextus.md` when present and load only relevant modules.
2. Understand business context: product/service, target audience, conversion goal.
3. Assess opportunity: search patterns, number of potential pages, search volume distribution.
4. Evaluate competitive landscape: who ranks, what their pages look like, can you compete.

## Core Principles
- Unique value per page: not just swapped variables.
- Proprietary data wins: hierarchy from proprietary (strongest) to public (weakest).
- Clean URL structure: use subfolders, not subdomains.
- Genuine search intent match.
- Quality over quantity.
- Avoid Google penalties: no doorway pages, keyword stuffing, or duplicate content.

## Playbooks
Choose from: Templates, Curation, Conversions, Comparisons, Examples, Locations, Personas, Integrations, Glossary, Translations, Directory, Profiles. Layer multiple playbooks when appropriate.

## Implementation Framework
1. Keyword Pattern Research: identify repeating structure, variables, unique combinations; validate demand.
2. Data Requirements: identify data sources, first-party vs. scraped vs. licensed vs. public, update cadence.
3. Template Design: header with target keyword, unique intro, data-driven sections, related pages, CTAs. Ensure uniqueness via conditional content and original insights.
4. AI-Assisted Generation (optional): on grounded inputs (row JSON + rules), generate varied copy, FAQ expansions, and section emphasis per URL. Facts stay in the data layer; AI shapes phrasing and structure, not invented numbers.
5. Internal Linking Architecture: hub-and-spoke model, cross-links between related spokes, avoid orphan pages, XML sitemap, breadcrumbs with structured data.
6. Indexation Strategy: prioritize high-volume patterns, noindex very thin variations, manage crawl budget, separate sitemaps by page type.
7. Choose Build Platform: ensure the platform can hold page count, refresh data, render server-side HTML, branch on data, and control indexation per page. Prefer existing CMS if capable; otherwise serve on a subpath of the main domain.

## Quality Checks
Pre-launch: unique value per page, answers search intent, unique titles/meta, proper headings, schema markup, page speed, internal linking, no orphan pages, in XML sitemap, crawlable, no conflicting noindex.
Post-launch: track indexation rate, rankings, traffic, engagement, conversion. Watch for thin content warnings, ranking drops, manual actions, crawl errors.

## Common Mistakes
- Thin content from rigid mail-merge templates.
- Ignoring data quality.
- Creating orphan pages.
- Over-indexing low-value variations.