Dustin Ogle**TL;DR:** County pages fail when they claim a place without **jurisdictional and delivery proof**. A phone number, stock skyline, and “proudly serving X County” do not survive pre-RFP scrutiny. Pages that work state **which service lines**, in **which regulatory/place context**, with **proof a senior engineer will approve**. Radius language is not a substitute.
What “thin” really means on a county page
Thin is not “under 1,000 words.” Thin is **no answer to the buyer’s real question:**
> Have firms like yours done work like ours, under constraints like ours, in a place like this?
A long page can still be thin if it is:
- generic service copy with the county name find-and-replaced,
- a map pin with no service-line depth,
- or marketing claims legal/engineering will not defend.
Related scorecard for *whether* the page should exist: *When Does a County Deserve Its Own Page?* (same cluster).
Jurisdiction vs. radius
| Approach | What it signals | Typical result |
|---|---|---|
| **Radius** (“within 75 miles”) | Sales coverage fantasy | Easy to write; hard to believe; weak for search specificity |
| **Jurisdiction** (county/city + real program/place context) | You operate in the buyer’s world | Stronger trust + clearer relevance when accurate |
For environmental and geotechnical work, buyers and internal reviewers think in **places and programs**, not circles:
- County and municipality of the site
- Relevant state environmental region or program *when it actually shapes scope*
- Local permitting or design norms your staff recognize
- Corps district or similar **only when it is real for the work** — never decorative name-dropping
You do not need a regulatory white paper on every county page. You need **enough place-and-program truth** that a PM scanning on a phone does not bounce.
Texas permitting-market vocabulary and regional context (deeper guide): Local SEO for Texas engineering firms.
Five failure modes (and the fix)
**1. Geography without service lines**
**Failure:** “Environmental consulting in X County” with no Phase I / remediation / geotech distinction.
**Fix:** Lead with the lines you actually sell there; link to deep practice-area pages.
**2. Service lines without place**
**Failure:** Statewide brochure pasted under a county H1.
**Fix:** One short jurisdictional block: how work is framed *here* (site types, common constraints), without inventing exclusivity.
**3. Claims without proof modules**
**Failure:** “Trusted local partner” with zero project patterns or scope language.
**Fix:** Publish patterns seniors will sign (facility types, investigation phases, deliverable types) — not fake logos or made-up stats.
**4. Proof seniors will not approve**
**Failure:** Marketing ships “#1 in the county” or implied licenses/coverage that operations cannot support.
**Fix:** Proof gate before publish. If a PE will not initial it, it does not go live.
**5. Orphan URL**
**Failure:** County page with no internal links from service lines or resources.
**Fix:** County pages are satellites. Practice-area pages are the spine (service page architecture).
Minimum proof stack (per county page)
Use this as a pre-publish checklist. If a row is empty, the page is not ready.
| Stack item | Required? | Pass looks like |
|---|---|---|
| **Service lines in scope** | Yes | Named lines matching real BD pursuit |
| **Place context** | Yes | County/city + accurate program/context notes (no decoration) |
| **Project or pattern proof** | Yes | At least one defensible pattern or anonymized composite seniors accept |
| **Operational coverage** | Yes | How delivery is staffed or routinely supported |
| **Who this is / isn’t for** | Strongly recommended | Filters wrong RFQs early |
| **FAQ (geo + scope)** | Recommended | Answers shortlist questions in plain language |
| **Links to deep service pages** | Yes | No single page tries to rank for every line alone |
| **Named update owner** | Yes | BD + technical reviewer on a cadence |
Broader proof-asset craft: Build proof assets that help buyers trust technical claims.
Before / after pattern (copy shape)
**Before (thin)**
> We proudly serve [County] and surrounding areas. Our experienced team provides full-service environmental and geotechnical solutions. Contact us today for a free consultation.
**After (proof-oriented)**
> In [County], we support [service line 1] and [service line 2] for [buyer types: e.g. commercial acquisition teams, industrial facility managers, municipal PMs].
>
> Work here is typically framed around [1–2 accurate place or program constraints — only if true for your firm].
>
> Recent patterns include [project type / phase / deliverable language seniors approve — no invented metrics].
>
> If you need [out-of-scope line], we will say so early rather than force-fit a proposal.
That is not longer for its own sake. It is **legible fit**.
How unsupported claims die in pre-RFP research
Before an RFP, buyers often:
- Search scope + geography,
- Open two or three firm sites,
- Check whether experience looks real,
- Build a mental shortlist of who to invite.
Unsupported location claims fail at step 3. You are not losing at proposal — you were never invited.
Positioning for that window: Engineering Services SEO.
Frequently Asked Questions
Our Editorial Process: Our expert team uses AI tools to help organize and structure our initial drafts. Every piece is then extensively rewritten, fact-checked, and enriched with first-hand insights and experiences by expert humans on our Insights Team to ensure accuracy and clarity.
By: About the BVM Insights Team
The BVM Insights Team is our dedicated engine for synthesizing complex topics into clear, helpful guides. While our content is thoroughly reviewed for clarity and accuracy, it is for informational purposes and should not replace professional advice.
