agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-programmatic/SKILL.md

seo-programmatic

Skill10 starsChanged 25 days agoMITView on GitHub

Programmatic SEO planning and safeguards for pages generated at scale — template design, URL patterns, internal-link automation, thin-content thresholds, and index-bloat prevention. Trigger when the user says "programmatic SEO", "pSEO", "pages at scale", "dynamic pages", "template pages", "generated pages", "data-driven SEO", or "scaled pages".

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-flow and 2 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-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

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 9 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

The file

Files
SKILL.md

seo-programmatic

Family: seo Status: Stable

Purpose

Plan SEO at template scale (city + service combos, product + use-case matrices) with the safeguards that decide whether pSEO succeeds. Most pSEO fails not from technical issues but from Google de-prioritizing thin, near-duplicate generated pages — the thin-content safeguard is the differentiator.

Triggers

  • "programmatic seo" / "pSEO" / "data-driven seo"
  • "pages at scale" / "scaled pages"
  • "dynamic pages" / "template pages" / "generated pages"

Inputs

  • The template definition (variables + content sources)
  • Expected page count and a few sample input rows
  • Existing site context

Steps

  1. Design the template so each page carries genuinely unique value, not just a swapped noun — unique data, local specifics, real media per page.
  2. Simulate output across the sample inputs and estimate the unique-content ratio; use seo-content to score representative pages for thinness.
  3. Set thin-content safeguards — a minimum unique-content threshold; pages below it get noindex (or aren't generated). State the threshold explicitly.
  4. URL + canonical strategy — slug conventions, parameter handling, and canonicalization so variants don't cannibalize.
  5. Internal-link automation — rules for how generated pages interlink (to a hub, to siblings) with sensible anchor text; align to clusters via seo-cluster.
  6. Index-bloat plan — decide which template pages Google should crawl vs. noindex; submit the worthy set via seo-sitemap.
  7. Render the plan: template spec, thresholds, link rules, index strategy.

Outputs

  • Programmatic SEO plan with explicit unique-content thresholds
  • Internal-link automation spec + URL/canonical strategy
  • Index-management (crawl vs noindex) plan

Dependencies

  • seo-content (unique-content scoring), seo-cluster (keyword-template fit), seo-sitemap (index the worthy set)

Notes

The thin-content threshold is the safeguard that keeps a pSEO project from getting the whole template pattern devalued. Decide it before generating, not after.

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.