agentleFS
YerayRodriYerayRodri/claude-skills/skills/seo-programmatic/SKILL.md

seo-programmatic

Skill0 starsChanged 3 days agoMITView on GitHub

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".

32 other projects use a version of this, 18 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-image-gen and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 4 projects that use this

  • timruebenachSkill

    seo-image-gen

    AI image generation for SEO assets: OG/social preview images, blog hero images, schema images, product photography, infographics. Powered by Gemini via nanobanana-mcp. Requires banana extension installed. Use when user says \"generate image\", \"OG image\", \"social preview\", \"hero image\", \"blog image\", \"product photo\", \"infographic\", \"seo image\", \"create visual\", \"image-gen\", \"favicon\", \"schema image\", \"pinterest pin\", \"generate visual\", \"banner\", or \"thumbnail\".

    Also in 11 projects that use this

  • timruebenachSkill

    seo-flow

    FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

    Also in 9 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 12 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 10 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 13 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

11 rules. 10 are common, 1 is distinctive, and 0 are very specific to this project.

  • 10

    Common

    Most of the 22 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Verify data freshness — stale data produces stale pages

    line 25
  2. Common:

    No duplicate slugs — enforce uniqueness at generation time

    line 51
  3. Common:

    Keep URLs under 100 characters

    line 52
  4. Common:

    No query parameters for primary content URLs

    line 53
  5. Common:

    Anchor text: Use descriptive, varied anchor text — avoid exact-match keyword repetition

    line 62
  6. Distinctive:

    Site reputation abuse: If publishing programmatic content under a high-authority domain (not your own), this may trigger site reputation …

    line 89
  7. Common:

    Every programmatic page must have a self-referencing canonical tag

    line 114
  8. Common:

    If programmatic pages overlap with manual pages, the manual page is canonical

    line 117
  9. Common:

    No canonical to a different domain unless intentional cross-domain setup

    line 118
  10. Common:

    Use sitemap index if multiple sitemap files needed

    line 124
  11. Common:

    Update sitemap dynamically as new records are added to data source

    line 128

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

MetricThresholdAction
Pages without content review100+⚠️ WARNING — require content audit before publishing
Pages without justification500+🛑 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 content remains 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

CategoryStatusScore
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.