When Does a County Deserve Its Own Page?

**TL;DR:** A county does **not** deserve its own URL because it is on a sales map or within driving distance. It deserves a page when **service-line fit, proof, operational coverage, buyer research behavior, and maintenance ownership** all clear a scorecard — and the page will not cannibalize stronger practice-area content. Most counties should stay a **mention + proof module** on a service-line page until those gates pass.

Env and geotech firms often get the same advice:

> List every county in the MSA. More location pages = more local SEO.

That advice is cheap to implement and expensive to own.

**What it costs you:**

A county page is a **commitment**, not a checkbox. Treat it like opening a field office in content form: only when the economics of attention and proof make sense.

For the full four-layer model (service lines → jurisdiction → proof → optional county page), see the hub: *Stop Building Thin County Pages* (same cluster).

Score the candidate county **1–5** on each gate. Be honest. A “3” is not a failure — it means **not yet a full page**.

**1. Service-line fit**

Do you actively pursue **named service lines** here (Phase I, Phase II, remediation, geotech investigation, etc.), or is the county a logo on a coverage map?

• **1–2:** Opportunistic only; no line you want to grow there
• **3:** One line, occasional
• **4–5:** Two or more lines you regularly pursue and can describe in buyer language

**2. Proof depth**

Can a senior engineer defend **why you belong** in this county without inventing work?

• **1–2:** No projects, no close analogs, no staff story
• **3:** Comparable adjacent-market work only
• **4–5:** Multiple defensible patterns (project types, scopes, constraints) you can publish without overclaiming

**3. Operational coverage**

Will delivery look routine, or like a special exception?

• **1–2:** “We could drive there”
• **3:** Select engagements only
• **4–5:** Staffed or routine field/PM coverage principals accept

**4. Buyer research behavior**

Do buyers in this market **research firms online** with geo + scope (pre-RFP), or is almost everything relationship/referral?

• **1–2:** Pure network market; search is irrelevant
• **3:** Mixed
• **4–5:** Commercial/municipal buyers regularly shortlist via search and referrals together

You do not need perfect analytics. BD usually knows whether owners, lenders’ counsel, and PMs Google for fit.

**5. Cannibalization risk**

Will a county page **steal internal links and attention** from stronger practice-area URLs without a clear unique job?

• **1–2:** Would restate the same service content under a county H1
• **3:** Overlap manageable with careful linking
• **4–5:** Clear unique angle (jurisdiction + service mix + proof) that practice-area pages should not carry alone

**6. Maintenance owner**

Who updates claims when coverage or service lines change?

• **1–2:** “Marketing will handle it” with no technical reviewer
• **3:** Ad hoc reviews
• **4–5:** Named BD + technical owner and a review cadence

If gate 6 is weak, do not publish a full page. Unsupported location claims are worse than silence.

**Candidate county:** _______________________

**Date / scored by:** _______________________

**Service lines in scope:** _______________________

**Decision rules**

Print this table. Score with BD and one senior technical person in the same room. Disagreement on proof or coverage is a signal to stop, not to average away the conflict.

When the scorecard says “not yet,” publish this stack on existing **service-line** pages:

1. **Market mention** — 2–4 sentences: counties/regions you support for *this* service line (no radius theater).
2. **Jurisdictional note** — only what is accurate and useful (program/region context buyers use).
3. **Proof module** — project *patterns* or scopes you will stand behind (no invented metrics).
4. **Internal path** — link to contact / qualifications process, not a hollow county URL.

That combination often captures geo-qualified research **without** a weak satellite page.

Deeper architecture for practice-area pages: Engineering firm service page SEO architecture.

Promote mention → full URL when **all** of the following are true:

1. Scorecard now passes (re-score; do not rely on last quarter’s optimism).
2. Proof module has been live long enough that technical staff are comfortable expanding it.
3. You have a distinct H1 job: *this county + these service lines + this buyer type* — not a clone of the statewide service page.
4. You can place **internal links** from the relevant service-line pages and (if used) hub resources without orphaning the URL.
5. Someone owns the 6-month update.

**Cadence suggestion:** re-score top expansion counties quarterly; promote **one per cycle; two only when both pass cleanly.** Speed of publishing is not a strategy.

Do not invent project counts to force a pass. A failed scorecard is a BD plan, not a content emergency.

• Stop Building Thin County Pages (hub)
• Why County Pages Fail Without Jurisdictional Proof
• Map Service Lines Before You Add Markets
• One-Page Service-Area Plan