seo-programmatic
agricidaniel/claude-seo
Plan and audit SEO pages generated at scale from data sources with quality gates to prevent thin content penalties.
What is seo-programmatic?
Programmatic SEO analysis and planning for pages built from structured data. Covers data source assessment, template design, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when generating pages at scale from databases, APIs, or CSV files.
- Evaluate data quality (row count, uniqueness, freshness) across CSV, JSON, API, and database sources
- Design templates with variable injection points and conditional logic to ensure unique, valuable pages
- Plan URL patterns (tools, locations, integrations, glossary) with slug uniqueness enforcement
- Automate internal linking via hub/spoke models, related items, breadcrumbs, and cross-linking
- Enforce thin content quality gates (≥40% unique content, ≥300 words, human review requirements)
- Generate sitemaps, canonicals, and index management strategy to prevent bloat and crawl waste
How to install seo-programmatic
npx skills add https://github.com/agricidaniel/claude-seo --skill seo-programmaticHow to use seo-programmatic
- 1.Provide the URL of your programmatic pages or describe your planned data source (CSV, API, database)
- 2.Specify your template structure and variable injection points (title, H1, body sections, meta description)
- 3.Define your intended URL pattern and data-to-slug mapping logic
- 4.Describe your internal linking strategy or request automated linking recommendations
- 5.Review the generated Programmatic SEO Score and assessment across data quality, template uniqueness, URL structure, internal linking, thin content risk, and index management
- 6.Address critical and high-priority issues before publishing; implement medium/low-priority recommendations within 1 month
Use cases
- Building 100+ tool/product pages from a database with unique specs and setup instructions
- Creating location + service pages (e.g., /city/service) without triggering scaled content abuse penalties
- Generating glossary or integration pages at scale while maintaining >40% unique content per page
- Auditing existing programmatic pages for thin content risk and Google Scaled Content Abuse compliance
- Planning progressive rollout strategy (50-100 pages per batch) with indexing monitoring
- SEO strategists planning large-scale page generation projects
- Engineering teams building template-based content systems
- Product managers launching data-driven content directories
- Content auditors reviewing programmatic pages for quality and penalty risk
seo-programmatic FAQ
Unique content = words appearing only on that page, divided by total page words. Shared headers, footers, and navigation are excluded. Template boilerplate text IS included in the calculation. Measure uniqueness against all other pages in the programmatic set.
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. Progressive rollout reduces scaled content abuse risk.
Integration pages (with real setup docs and API details), template/tool pages (with downloadable content), glossary pages (200+ word definitions with examples), product pages (unique specs and reviews), and data-driven pages (unique statistics and charts per record) are safe. Avoid location pages with only city names swapped, generic comparisons, and AI-generated pages without human review.
Yes. Noindex pages that don't meet quality gates, paginated results beyond page 1, and filtered/faceted navigation views. Use rel=next/prev for pagination series. Every programmatic page must have a self-referencing canonical tag.
Flag as thin content and conduct a content audit before publishing. If <30% unique content, apply a hard stop and require explicit user approval. Increase unique content by adding data-specific sections, user-generated content, contextual tips, or supplementary resources.
Full instructions (SKILL.md)
Source of truth, from agricidaniel/claude-seo.
name: seo-programmatic description: > Programmatic SEO planning and analysis for pages generated at scale from data sources. Covers template engines, URL patterns, internal linking automation, thin content safeguards, and index bloat prevention. Use when user says "programmatic SEO", "pages at scale", "dynamic pages", "template pages", "generated pages", or "data-driven SEO". user-invocable: true argument-hint: "[url or plan]" license: MIT metadata: author: AgriciDaniel version: "2.2.0" category: seo
Programmatic SEO Analysis & Planning
Build and audit SEO pages generated at scale from structured data sources. Enforces quality gates to prevent thin content penalties and index bloat.
Data Source Assessment
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
Template Engine Planning
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
URL Pattern Strategy
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
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)
Internal Linking Automation
- Hub/spoke model: Category hub pages linking to individual programmatic pages
- Related items: Auto-link to 3-5 related pages based on data attributes
- Breadcrumbs: Generate BreadcrumbList schema from URL hierarchy
- Cross-linking: Link between programmatic pages sharing attributes (same category, same city, same feature)
- Anchor text: Use descriptive, varied anchor text. Avoid exact-match keyword repetition
- Link density: 3-5 internal links per 1000 words (match seo-content guidelines)
Thin Content Safeguards
Quality Gates
| 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) |
Scaled Content Abuse: Enforcement Context (2025-2026)
Google's Scaled Content Abuse policy (introduced March 2024) saw major enforcement escalation in 2025:
- June 2025: Wave of manual actions targeting websites with AI-generated content at scale
- August 2025: SpamBrain spam update enhanced pattern detection for AI-generated link schemes and content farms
- Result: Google reported 45% reduction in low-quality, unoriginal content in search results post-March 2024 enforcement
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: If publishing programmatic content under a high-authority domain (not your own), this may trigger site reputation abuse penalties. Google began enforcing this aggressively in November 2024.
Recommendation: The WARNING gate at
<40% unique contentremains appropriate. Consider a HARD STOP at<30%unique content to prevent scaled content abuse risk.
Safe Programmatic Pages (OK 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 (avoid 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) × 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.
Canonical Strategy
- Every programmatic page must have a self-referencing canonical tag
- Parameter variations (sort, filter, pagination) canonical to the base URL
- Paginated series: canonical to page 1 or use rel=next/prev
- If programmatic pages overlap with manual pages, the manual page is canonical
- No canonical to a different domain unless intentional cross-domain setup
Sitemap Integration
- Auto-generate sitemap entries for all programmatic pages
- Split at 50,000 URLs per sitemap file (protocol limit)
- Use sitemap index if multiple sitemap files needed
<lastmod>reflects actual data update timestamp (not generation time)- Exclude noindexed programmatic pages from sitemap
- Register sitemap in robots.txt
- Update sitemap dynamically as new records are added to data source
Index Bloat Prevention
- Noindex low-value pages: Pages that don't meet quality gates
- Pagination: Noindex paginated results beyond page 1 (or use rel=next/prev)
- Faceted navigation: Noindex filtered views, canonical to base category
- Crawl budget: For sites with >10k programmatic pages, monitor crawl stats in Search Console
- Thin page consolidation: Merge records with insufficient data into aggregated pages
- Regular audits: Monthly review of indexed page count vs intended count
Output
Programmatic SEO Score: XX/100
Assessment Summary
| 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 |
Critical Issues (fix immediately)
High Priority (fix within 1 week)
Medium Priority (fix within 1 month)
Low Priority (backlog)
Recommendations
- Data source improvements
- Template modifications
- URL pattern adjustments
- Quality gate compliance actions
Error Handling
| 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. |
Related skills
More from agricidaniel/claude-seo and the wider catalog.
seo-schema
Detect, validate, and generate Schema.org structured data for rich search results and AI overviews.
seo-sitemap
Analyze existing XML sitemaps or generate new ones with validation and industry templates.
seo-sxo
Analyze SERP backwards to detect page-type mismatches and score pages against search intent.
seo-technical
Audit 9 technical SEO categories: crawlability, indexability, security, Core Web Vitals, mobile, structured data, and more.
day1-onboarding
AI Native Camp Day 1 onboarding: learn Claude Code through guided conversation and hands-on exercises.
day2-create-context-sync-skill
Build your own context sync skill to collect information from multiple external tools into a unified document.