service-area-pages

Installation
SKILL.md

Service Area Pages

A town page earns its place only when it says something true about the business in that town that the other town pages can't. Google's spam policies name the alternative directly: "multiple domain names or pages targeted at specific regions or cities that funnel users to one page" is doorway abuse. This skill decides which towns qualify, writes those pages, folds the rest into one honest areas-we-serve page, and proves the set isn't duplicates before anyone publishes it. The method is a floor. The no-invented-facts rule and the duplicate check don't flex.

Context

Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run: python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for service-area-pages (${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/service-area-pages. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads:. If none exist, proceed standalone and ask only for what the task needs.)

If ./campaigns/local-seo/plan.md exists, read it first. Its market map already says which towns get a page, which get a line, and why. Don't redo that work. Use its capability ledger as the source of every claim. The ledger is input only: its rows, IDs and tiers never appear in the pages or in the handoff. Claim sources go to ./campaigns/service-area-pages/notes.md.

Modes

Situation Mode
No town pages yet NEW SET, all phases
Town pages exist and look alike, or slid in rankings FIX EXISTING, start with the duplicate check in Phase 6 on the live pages, then Phases 1-7
One named town SINGLE PAGE, Quick Mode: qualify that town, write it, run the duplicate check against the existing pages
Installs
197
GitHub Stars
767
First Seen
6 days ago