Honest answer: it’s a partial oversight, not a structural one — and it doesn’t require rebuilding the location pages. Here’s the precise diagnosis.
What’s actually fine
The service coverage is already correct. All 18 services are present on every location page with their own sections, descriptions, and links. The architecture is right. Google can read the full service scope from every city page.
The “outdoor living services” framing in each page title and opening paragraph is deliberately service-agnostic — it doesn’t lock the pages to artificial grass.
What the artificial grass emphasis actually affected
Three specific elements across the location pages lean heavier on artificial grass than the pages should carry long-term:
1. The opening H2 (“Why [city] homeowners are switching / rethinking / making the switch”)
Every location page opens with a section built around the artificial grass argument — water restrictions, climate effects on natural lawns, SAWS/SFWMD/CSU framing. That section is correctly localized and genuinely good content, but it positions artificial grass as the primary service story of each page rather than the full outdoor living range.
2. The FAQ answers
Most location pages carry four to five FAQ answers, and two or three of them are artificial grass-specific — hail performance on turf, SFWMD and artificial grass, caliche and turf installation. The FAQ block was built from the artificial grass lens because that’s the only pillar that existed at the time.
3. The cost section
Each location page’s cost section opens with artificial grass as the cost reference point and references the artificial grass cost cluster post. That’s not wrong — it’s the highest-search-volume service — but it’s narrower than the section should be at full pillar buildout.
What it doesn’t require
A full rewrite of the location pages. That would be wasted effort at this stage. The pages are production-ready as they stand — artificial grass is the highest-search-volume service in every one of the seven markets, the emphasis isn’t wrong for the current state of the site, and the pages are already stronger than most location pages that exist in this space.
The right approach: progressive updates tied to pillar buildout
Each time a new pillar goes live, make two targeted updates to every relevant location page:
Update 1 — Add a FAQ answer for the new service. When the pergola pillar is live, each location page gets one additional FAQ answer that’s specific to pergolas in that market — permits in Collier County, snow load specs in Romeoville, wind ratings in Colorado Springs. This progressively balances the FAQ block across services rather than concentrating it on artificial grass.
Update 2 — Expand the cost section reference. As each Tier 1 pillar goes live (pergolas, decks, pavers, fence), add a sentence in the cost section that references that service’s cost cluster post. Over six pillar launches the cost section naturally becomes a multi-service reference block rather than an artificial grass block with other services listed below it.
That’s it. Two targeted additions per location page per new pillar — a 20-minute update per city page rather than a rewrite.
One proactive fix worth making now
The opening H2 on each location page is the element most worth revisiting before the pergola pillar launches — because once a second high-profile pillar exists, a location page that opens with a four-paragraph section on natural grass lawn problems starts to read as an artificial grass page with other services appended, rather than a full outdoor living page.
The fix is straightforward: rename the opening H2 from “Why [city] homeowners are switching to artificial grass” (or equivalent) to “Why [city] homeowners are investing in outdoor living” and broaden the first paragraph to reference the full service range before narrowing to the climate and water context that follows. The local detail sections beneath it — water restrictions, climate, HOA — stay exactly as written. Only the framing of the entry point changes.
That’s a one-paragraph edit per location page. Eight pages, eight paragraphs, and the location pages are properly framed for a multi-pillar site rather than a single-service site.
In summary
| Element | Action needed | When |
|---|---|---|
| Service list sections | Nothing — already complete | — |
| Opening H2 framing | Light reframe, one paragraph per page | Before pergola pillar launches |
| FAQ answers | Add one per service as each pillar goes live | Rolling, tied to pillar schedule |
| Cost section | Add service reference per Tier 1 pillar | Rolling, tied to pillar schedule |
| Internal links | Update as new pillar URLs go live | Rolling, tied to pillar schedule |
The playbook holds. The location pages are solid. The refinement is incremental and tied to the production schedule you already have — not a remediation exercise.
