Canonical NotFair workflow

01What is it?
Programmatic SEO planning and audit, building or evaluating large sets of template-generated pages that target long-tail query patterns at scale (e.g. It stands out by giving search and SEO workflows a defined shape, so the agent asks for better context and returns a more usable result.
02Inputs
Context for search and SEO workflows: your goals, audience, constraints, and any source material the skill asks for.
03Output
A ready-to-use result for search and SEO workflows: the analysis, copy, or recommendations the agent produces.
Install-only

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal
$ npx skills add nowork-studio/notfair-plugin --skill programmatic-seo

Skill instructions

The instruction file for this skill. The skill also includes other files you need to install to use it.

SKILL.md

Canonical NotFair workflow

Read ../../seo/programmatic-seo/SKILL.md completely, then follow it as the active workflow. Resolve every relative reference from that file against ../../seo/programmatic-seo/.


Supporting file: seo/programmatic-seo/SKILL.md

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 page (real stats/inventory/specifics), not just the variable swapped into otherwise-identical boilerplate.
  • A minimum value bar: would this page help a user who landed on it cold? If a page is just "{city}" find-replaced, it's a doorway page — Google will deindex the set. State this bluntly if the plan fails the bar.
  • Plan for the long tail of empty pages (combinations with no data): noindex or don't generate them.

Phase 3 — Architecture

  • Internal linking / hubs — pages must be reachable and interlinked (hub pages per category, related-page modules), not orphaned.
  • Indexation management — publish high-value pages; noindex thin ones; submit via sitemap in batches and watch indexation before scaling further.
  • URL pattern, titles, H1s, and meta templated but de-duplicated.
  • Render — ensure content is in the HTML / properly rendered, not client-only.

Phase 4 — Deliverable

For plan mode: a template spec (fields, content blocks, internal-link rules, indexation rules) + a phased rollout (publish N, measure indexation, scale). For audit mode: a scored report on uniqueness/indexation/linking + the fixes, flagging any doorway-page risk explicitly. Write in the user's language.

How do I install Canonical NotFair workflow in Cursor, Claude Code, or Codex?

Run npx skills add nowork-studio/notfair-plugin --skill programmatic-seo in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Canonical NotFair workflow, not every skill in the repository.

Where does Canonical NotFair workflow come from and what license is it under?

Canonical NotFair workflow comes from the nowork-studio/notfair-plugin repository on GitHub. That repository has 3.4K GitHub stars. The skill is published under the MIT license.

Prefer plain text? Read the Canonical NotFair workflow guide as markdown.