# Canonical NotFair workflow Human Guide

## What This Is For
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 gives the agent a clearer input/output frame for search and SEO workflows: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Canonical NotFair workflow agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for canonical NotFair workflow.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Canonical NotFair workflow guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **Plan** — user wants to design a new programmatic set. Collect the query
- **Audit** — pages already exist. Collect the URL pattern and sample URLs.
- Does the query pattern have **real, distributed search demand** across the
- Estimate addressable patterns vs. patterns worth publishing — not every
- **Unique data** per page (real stats/inventory/specifics), not just the variable
- A **minimum value bar**: would this page help a user who landed on it cold? If a
- Plan for the **long tail of empty pages** (combinations with no data): noindex or
- **Internal linking / hubs** — pages must be reachable and interlinked (hub pages
- **Indexation management** — publish high-value pages; `noindex` thin ones; submit
- **URL pattern**, titles, H1s, and meta templated but de-duplicated.
- **Render** — ensure content is in the HTML / properly rendered, not client-only.

## Decision Points And Nuance
The original skill emphasizes: Supporting file: seo/programmatic-seo/SKILL.md, Step 0 — Scope, Phase 0 — Preflight & data, Phase 1 — Demand validation, Phase 2 — Uniqueness & value threshold (pass/fail gate), Phase 3 — Architecture, Phase 4 — Deliverable.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- **Internal linking / hubs** — pages must be reachable and interlinked (hub pages

## Copy-And-Paste Prompt
```text
Use the Canonical NotFair workflow human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the nowork-studio/notfair-plugin skill entry for `programmatic-seo`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Canonical NotFair workflow

Read [`../../seo/programmatic-seo/SKILL.md`](../../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.