Programmatic SEO planning and analysis for pages generated at scale from data sources.
Library skill — the default version is maintained in GitHub; edits you make live in your own clone.
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: - CSV/JSON files: Row count, column uniqueness, missing values - API endpoints: Response structure, data freshness, rate limits - Database queries: Record count, field completeness, update frequency - Data quality checks: - Each record must have enough unique attributes to generate distinct content - Flag duplicate or near-duplicate records (>80% field overlap) - Verify data freshness; stale data produces stale pages
Design templates that produce unique, valuable pages: - Variable injection points: Title, H1, body sections, meta description, schema - Content blocks: Static (shared across pages) vs dynamic (unique per page) - Conditional logic: Show/hide sections based on data availability - Supplementary content: Related items, contextual tips, user-generated content - Template review checklist: - Each page must read as a standalone, valuable resource - No "mad-libs" patterns (just swapping city/product names in identical text) - Dynamic sections must add genuine information, not just keyword variations
/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: - 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+ programmatic pages simultaneously without explicit 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: Google clarified site reputation abuse language on 2024-11-19; treat third-party/hosted programmatic content as a policy risk. Since 2026-08-28 enforcement depends on the searcher: manual actions apply outside the EEA, while for EEA users the third-party section may be categorized separately from the main domain. Report the risk for both audiences.
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.
Metadata is scored separately. This calculation covers body copy only, so a set that passes it can still carry one generated title/description shape on every URL. Run "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run metadata_template.py --pairs-file <file> --json (heuristic, deterministic string comparison) over the whole set and treat a site_risk of high as a gate failure regardless of body uniqueness.
<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. |