# Service-Area Proof Routing Playbook

Use this playbook when local pages exist but the business has no disciplined way to feed reviews, photos, job stories, and local signals back into them.

## Local Proof Intake Sources

Start with the proof sources the business already creates:

- reviews mentioning location or neighborhood
- before-and-after or field photos
- team notes from notable jobs
- repeat local questions from calls or forms
- service stories worth compressing into proof modules

The goal is not to create new proof from scratch. It is to route existing proof more intelligently.

## Routing Rules

For each new piece of proof, decide:

- which location or service-area page it strengthens
- whether it belongs in a general hub instead
- whether it is strong enough for a results or case-story surface
- whether it should feed an FAQ or answer block

Simple routing rules prevent proof from disappearing into folders no one revisits.

## Page-Level Proof Blocks

Useful local proof blocks include:

- nearby review strip
- recent local service note
- location-specific FAQ answer
- trust strip tied to response expectations
- proof tile linked to a broader result or story

These blocks keep service-area pages feeling current without forcing each page to carry long-form content.

## Coverage Gaps

Track where proof is thin:

- important service areas with no fresh reviews
- areas with weak photo coverage
- high-value pages with stale FAQ blocks
- locations where trust signals lag behind demand

That gap map tells the business where to deepen next.

## Ownership Rules

Assign owners:

- dispatch or office lead logs local proof
- marketer or content owner routes and publishes
- operator reviews whether the proof actually reflects current service reality

Without ownership, proof routing becomes sporadic.

## Monthly Coverage Review

Monthly:

- review top local pages
- note proof freshness by area
- move the strongest new proof into page-level blocks
- identify under-supported markets

Quarterly:

- merge weak local pages
- deepen only the areas with the strongest proof and demand fit

## Failure Modes

- publishing local pages but never updating them
- forcing every review into every page
- routing proof without checking relevance
- letting local evidence sit only in GBP or social feeds