programmatic-seo
Plan programmatic SEO pages. Use when: building template engines, URL patterns, thin content safeguards, or quality gates.
What this skill does
# /digital-marketing-pro:programmatic-seo
## Purpose
Plan and audit SEO pages generated at scale from structured data sources (databases, APIs, CSV/JSON files). Enforces quality gates to prevent thin content penalties, index bloat, and Google's Scaled Content Abuse policy.
## Input Required
The user must provide (or will be prompted for):
- **URL or data source**: Existing programmatic pages to audit, or data source details for planning
- **Page type**: What kind of pages are being generated (location, product, integration, glossary, template, tool)
- **Data source**: CSV/JSON files, API endpoints, database queries — or existing pages to analyze
- **Target scale**: How many pages will be generated
- **Current status**: New build or auditing existing programmatic pages
## Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply industry context and compliance rules. Check for brand guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json`.
2. **Data source assessment**: Evaluate the data powering programmatic pages — row count, column uniqueness, missing values, duplicate detection (>80% field overlap), data freshness
3. **Template engine planning**: Design templates that produce genuinely unique pages — variable injection points, content blocks (static vs dynamic), conditional logic, supplementary content. Validate each page passes the "standalone value test"
4. **URL pattern strategy**: Design URL hierarchy — lowercase hyphenated slugs, logical structure, uniqueness enforcement, under 100 characters, consistent trailing slash
5. **Internal linking automation**: Hub/spoke model, related items (3-5 per page), breadcrumbs with BreadcrumbList schema, cross-linking by shared attributes, varied anchor text
6. **Thin content safeguard check**: Apply quality gates (see below)
7. **Canonical strategy**: Self-referencing canonicals, parameter handling, pagination strategy, manual page priority
8. **Sitemap integration**: Auto-generate entries, split at 50K URLs, `<lastmod>` from actual data timestamps, exclude noindexed pages
9. **Index bloat prevention**: Noindex low-value pages, pagination handling, faceted navigation canonicalization, crawl budget monitoring for 10K+ pages
10. **Score and report**: Score each dimension, produce prioritized action plan
## Quality Gates
### Scale Thresholds
| Metric | Threshold | Action |
|--------|-----------|--------|
| Pages without content review | 100+ | WARNING: require content audit before publishing |
| Pages without justification | 500+ | HARD STOP: require explicit user approval and thin content audit |
| Unique content per page | <40% | Flag as thin content (penalty risk) |
| Unique content per page | <30% | HARD STOP: scaled content abuse risk |
| Word count per page | <300 | Flag for review (may lack sufficient value) |
### Scaled Content Abuse Context (2025-2026)
Google's Scaled Content Abuse policy (introduced March 2024) saw major enforcement escalation:
- **June 2025**: Wave of manual actions targeting AI-generated content at scale
- **August 2025**: SpamBrain update enhanced pattern detection for AI-generated link schemes and content farms
- **Result**: 45% reduction in low-quality, unoriginal content in search results
**Enhanced quality gates for programmatic pages:**
- **Content differentiation**: 30-40%+ of content must be genuinely unique between any two programmatic pages (not just city/keyword string replacement)
- **Human review**: Minimum 5-10% sample review of generated pages before publishing
- **Progressive rollout**: Publish in batches of 50-100 pages. Monitor indexing and rankings for 2-4 weeks before expanding. Never publish 500+ simultaneously without quality review.
- **Standalone value test**: Each page should pass: "Would this page be worth publishing even if no other similar pages existed?"
- **Site reputation abuse**: Publishing programmatic content under a high-authority domain (not your own) may trigger site reputation abuse penalties (enforced aggressively since November 2024)
### Safe vs Risky Programmatic Pages
**Safe at scale:**
- Integration pages (with real setup docs, API details, screenshots)
- Template/tool pages (with downloadable content, usage instructions)
- Glossary pages (200+ word definitions with examples, related terms)
- Product pages (unique specs, reviews, comparison data)
- Data-driven pages (unique statistics, charts, analysis per record)
**Penalty risk at scale:**
- Location pages with only city name swapped in identical text
- "Best [tool] for [industry]" without industry-specific value
- "[Competitor] alternative" without real comparison data
- AI-generated pages without human review and unique value-add
- Pages where >60% of content is shared template boilerplate
### Uniqueness Calculation
Unique content % = (words unique to this page) / (total words on page) x 100
Measured against all other pages in the programmatic set. Shared headers, footers, and navigation excluded. Template boilerplate IS included.
## URL Pattern Library
### Common Patterns
- `/tools/[tool-name]`: Tool/product directory pages
- `/[city]/[service]`: Location + service pages
- `/integrations/[platform]`: Integration landing pages
- `/glossary/[term]`: Definition/reference pages
- `/templates/[template-name]`: Downloadable template pages
- `/compare/[product-a]-vs-[product-b]`: Comparison pages
### URL Rules
- Lowercase, hyphenated slugs derived from data
- Logical hierarchy reflecting site architecture
- No duplicate slugs — enforce uniqueness at generation time
- Keep URLs under 100 characters
- No query parameters for primary content URLs
- Consistent trailing slash usage (match existing site pattern)
## Output
A structured programmatic SEO assessment containing:
### Programmatic SEO Score: XX/100
| Category | Status | Score |
|----------|--------|-------|
| Data Quality | score | /100 |
| Template Uniqueness | score | /100 |
| URL Structure | score | /100 |
| Internal Linking | score | /100 |
| Thin Content Risk | score | /100 |
| Index Management | score | /100 |
- Critical issues (fix immediately)
- High priority (fix within 1 week)
- Medium priority (fix within 1 month)
- Recommendations: data source improvements, template modifications, URL pattern adjustments, quality gate compliance actions
- Progressive rollout plan with batch sizes and monitoring checkpoints
## Agents Used
- **seo-specialist** — Programmatic page analysis, quality gate enforcement, URL strategy, template evaluation
- **content-creator** — Template content design, uniqueness optimization
## Scripts Used
- **tech-seo-auditor.py** — Check technical SEO issues across programmatic page samples
- **content-scorer.py** — Score content quality and uniqueness per template
- **competitor-scraper.py** — Analyze competitor programmatic page patterns
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".