From claude-seo
Programmatic SEO planning, analysis, and implementation for pages generated at scale from data sources. Covers template engines (Nunjucks-style syntax, layout inheritance), URL pattern strategy and slug generation, internal linking automation, thin content safeguards, batch processing with checkpoint/resume, parallel worker pools, per-batch quality validation, storage strategy (FS vs DB), CDN deployment, and index bloat prevention. Use when user says "programmatic SEO", "pSEO", "pages at scale", "dynamic pages", "template pages", "generated pages", "data-driven SEO", "URL structure", "slug generation", "batch generate", or "scale 100k pages".
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-seo:seo-programmatic [url or plan][url or plan]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build and audit SEO pages generated at scale from structured data sources.
Build and audit SEO pages generated at scale from structured data sources. Enforces quality gates to prevent thin content penalties and index bloat.
Evaluate the data powering programmatic pages:
Design templates that produce unique, valuable pages:
/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| 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 (likely penalty risk) |
| Word count per page | <300 | ⚠️ Flag for review (may lack sufficient value) |
Google's Scaled Content Abuse policy (introduced March 2024) saw major enforcement escalation in 2025:
Enhanced quality gates for programmatic pages:
Recommendation: The WARNING gate at
<40% unique contentremains appropriate. Consider a HARD STOP at<30%unique content to prevent scaled content abuse risk.
✅ 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)
❌ 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
Unique content % = (words unique to this page) / (total words on page) × 100
Measure against all other pages in the programmatic set. Shared headers, footers, and navigation are excluded from the calculation. Template boilerplate text IS included.
<lastmod> reflects actual data update timestamp (not generation time)| Category | Status | Score |
|---|---|---|
| Data Quality | ✅/⚠️/❌ | XX/100 |
| Template Uniqueness | ✅/⚠️/❌ | XX/100 |
| URL Structure | ✅/⚠️/❌ | XX/100 |
| Internal Linking | ✅/⚠️/❌ | XX/100 |
| Thin Content Risk | ✅/⚠️/❌ | XX/100 |
| Index Management | ✅/⚠️/❌ | XX/100 |
| Scenario | Action |
|---|---|
| URL unreachable | Report connection error with status code. Suggest verifying URL accessibility and checking for authentication requirements. |
| No programmatic pages detected | Inform user that no template-generated or data-driven page patterns were found. Suggest checking if pages use client-side rendering or if the URL points to the correct section. |
| Thin content threshold exceeded | Trigger quality gate warning. Report the unique content percentage and flag pages below 40% uniqueness. Require user acknowledgment before proceeding. |
| Quality gate violation | Halt analysis at the HARD STOP threshold (500+ pages without justification or <30% unique content). Present findings and require explicit user approval to continue. |
Load on demand (do NOT load at startup):
references/pseo-best-practices.md -- Content uniqueness strategies, thin-content red flags + fixes, keyword density rules, doorway vs value-add comparison, pre-launch checklist, JS quality validator, batch sampling for human review, post-launch KPIs.references/pseo-templates-and-urls.md -- Nunjucks template syntax (variables, loops, conditionals, filters, layout inheritance, full location/comparison templates) plus URL patterns by use case, slug sanitizer, PSEOURLGenerator class with length cap + dedup, canonical maps, hierarchy/matrix examples.references/pseo-scale-architecture.md -- Pipeline overview, 1000-row batch processing, 4-8 worker pool, checkpoint/resume manager, per-batch quality validator with 10% failure abort, performance benchmarks (1k → 1M+ pages), file-system vs SQLite storage, CDN cache headers, end-to-end pipeline sketch.npx claudepluginhub lugondev/claude-seo --plugin claude-seoProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.