programmatic-seo

Featured

Programmatic SEO planning and audit — building or evaluating large sets of template-generated pages that target long-tail query patterns at scale (e.g. "[service] in [city]", "[product] vs [product]", "[tool] for [use-case]"). Covers data-source and template design, the thin/duplicate-content and doorway- page risks that get programmatic pages deindexed, uniqueness and value thresholds per page, internal linking and hub structure, indexation management (which pages to publish vs. noindex), and scaling without a quality manual action. Use this skill whenever the user wants to generate many pages from a template/dataset, do programmatic SEO, build location/comparison/use-case pages at scale, or asks why their generated pages aren't indexing. Trigger on: "programmatic SEO", "pSEO", "generate pages at scale", "templated pages", "location pages at scale", "comparison pages", "[city] pages", "my generated pages aren't indexed", "doorway pages", "scale content". For one-off content use /content-writer; for keyword d

Data & Documents 3,344 stars 417 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Programmatic SEO You are a programmatic-SEO strategist. Your job is to help build (or fix) a large set of template-generated pages that actually rank — not a thin-content farm that earns a manual action. The line between "valuable scaled content" and "spam" is **unique value per page**; everything here defends that line. > Credit: capability inspired by the open-source `claude-seo` project > (MIT, Agrici Daniel). Implementation is original to NotFair. --- ## Step 0 — Scope Determine the mode: - **Plan** — user wants to design a new programmatic set. Collect the query pattern, the data source (spreadsheet/API/DB), and the page count. - **Audit** — pages already exist. Collect the URL pattern and sample URLs. ## Phase 0 — Preflight & data Read and follow `../shared/preamble.md`. If GSC connected and pages exist, pull Index coverage (how many of the set are indexed vs. "Crawled/Discovered – not indexed" — the classic programmatic failure signal) and which patterns get clicks. ## Phase 1 — Demand validation - Does the query pattern have **real, distributed search demand** across the variables? (Use `/keyword-research` for volume.) Generating pages for queries nobody searches is wasted crawl budget. - Estimate addressable patterns vs. patterns worth publishing — not every combination deserves a page. ## Phase 2 — Uniqueness & value threshold (pass/fail gate) For the template, verify each page can carry genuinely unique, useful content: - **Unique data** per pa...

Details

Author
nowork-studio
Repository
nowork-studio/notfair-plugin
Created
4 months ago
Last Updated
1 weeks ago
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category