Most tree surgeons serve more than one town. The problem is that your Google Business Profile is anchored to a single address, so the further a searcher is from that pin, the harder it is to show up for them. Service-area pages on your website are how you extend your reach into neighbouring towns — but only if you build them properly. Done badly, they’re the single most common way trade websites get penalised. This is part of our complete local SEO guide for tree surgeons.
What is a service-area page?
A service-area page (also called a location page or town page) is a single page on your website dedicated to one town or area you cover — for example, “Tree Surgeon in Witney” or “Tree Removal in Banbury”. Its job is to rank in the standard search results when someone in that town searches for tree work, and to give that searcher a relevant page to land on.
It’s different from a service page, which targets what you do (crown reduction, stump grinding, hedge work) across your whole patch. A service-area page targets where you work. The best sites have both — and combine them for your highest-value towns.
These pages matter because Google ranks local results partly on distance from the searcher. Your Google Business Profile helps you win the map pack near your base, but the blue-link results below the map are where well-built town pages earn their keep — especially in towns a few miles from your registered address.
Why do most service-area pages fail?
Because they’re thin or duplicate content. The classic mistake is writing one template and swapping the town name in:
“Looking for a reliable tree surgeon in [Banbury]? We offer tree removal, crown reduction and stump grinding in [Banbury] and the surrounding area. Call our [Banbury] team today.”
Publish that 30 times for 30 towns and Google sees 30 near-identical pages. It will typically pick one to rank, filter the rest out of results, and — if the pattern is bad enough — lose trust in the whole site. Google’s own guidance on doorway pages explicitly calls out “multiple pages targeted at specific regions or cities that funnel users to one page” as a spam pattern.
The fix isn’t to avoid town pages. It’s to make each one genuinely useful and genuinely different.
What makes a town page genuinely unique?
A page passes the “is this real?” test when a local would read it and think they actually work here. The raw material is specific to each town:
| Ingredient | Generic (thin) | Specific (ranks) |
|---|---|---|
| Jobs done | ”We do tree removal" | "We removed a storm-damaged ash off the High Street near St Mary’s last winter” |
| Local council | ”Get a permit first" | "West Oxfordshire District Council handles TPO applications for Witney; allow 8 weeks” |
| Tree species | ”All tree types" | "Lots of mature beech and oak in the older estates here; we see a lot of ash dieback” |
| Landmarks / areas | ”And surrounding areas" | "From Cogges to Madley Park and out toward Ducklington” |
| Conservation rules | (none) | “Much of the town centre is a conservation area — six weeks’ notice is needed for any work” |
| Access / logistics | ”We cover this town" | "We’re 12 minutes from the centre via the A40, so we handle emergency call-outs here fast” |
You don’t need all of these on every page, but you need enough that the page could only have been written about that specific town. A page about a town where you’ve genuinely done work writes itself; a page about a town you’ve never visited is exactly the one you shouldn’t be building yet.
The local detail also feeds your keyword targeting. If you haven’t already, do proper local keyword research for tree surgeons first — it tells you which towns and which “[service] [town]” phrases actually get searched, so you build pages people are looking for rather than guessing.
How many town pages should you build?
Start small and prove the model. A common failure is launching 40 pages in one go to “cover the county” — most are thin, none rank, and you’ve buried the few good ones.
A sensible sequence:
- List the towns you genuinely serve. Be honest — a place you’d drive 45 minutes to for a big removal isn’t really a service area.
- Rank them by demand and by where you already win jobs. Your busiest two or three towns plus your home town are the priority.
- Build your strongest three to five pages first. Write them properly, publish, and watch what happens for a few weeks.
- Scale only into towns you can write real content for. If you can’t fill a page with genuine local detail, that town isn’t ready for a page yet.
For most tree surgeons the right number is somewhere between five and fifteen pages — the towns where you do real volume — not every parish within 30 miles.
How do you structure a service-area page that ranks?
Use a consistent skeleton across all your town pages so they’re easy to build and maintain — but fill each section with town-specific content. A reliable structure:
- H1 with the town: “Tree Surgeon in Witney” — clear and exact-match for the search.
- A real intro (not a template): two or three sentences mentioning the town, the areas within it you cover, and a specific detail (a recent job, a local feature).
- Services you offer there: link each to its full service page rather than re-explaining it. List tree removal, crown reduction, pruning, stump grinding, hedge work and emergency call-outs.
- Local detail block: the council, Tree Preservation Order and conservation-area rules, common local tree species, landmarks and access.
- Proof: real photos from jobs in or near that town, and reviews from customers there.
- An embedded Google Map centred on the area.
- A town-specific FAQ: “Do I need permission to remove a tree in [town]?” with the actual local answer.
- A clear call to action: phone number and quote form, ideally referencing the town.
This is also where good web design pays off — a fast, well-structured page converts the visitor once they land. If your site can’t easily support clean, consistent location pages, that’s worth fixing; see how we approach tree surgeon websites built for local ranking and lead capture.
A pre-publish checklist for each town page
Before any town page goes live, run it past this list:
- Unique title tag and meta description containing the town name
- One H1, including the town
- An intro written specifically for this town (no swapped-name template)
- At least one detail only a local would know (job, landmark, council rule)
- The correct council and its TPO / conservation-area process
- Real photos with town-specific alt text
- An embedded map and at least one local review
- A town-specific FAQ section
- LocalBusiness or Service schema with the area served
- Internal links to your service pages and home page (not a footer wall of 50 links)
How do service-area pages work with the rest of your local SEO?
Town pages are one lever, not the whole machine. They live alongside, and reinforce, the rest of your local setup:
- Your Google Business Profile still does most of the heavy lifting for the map pack. Strong town pages support it; they don’t replace it. If you’re not yet ranking in the three-pack, that’s the priority — see how to rank in the Google map pack.
- Consistent business details matter even more once you have many pages. Your name, address and phone should be identical on every town page and everywhere off-site — our guide to local citations and NAP consistency covers why and where.
- Each page should be a real landing page, with its own phone number tracking or form so you can see which towns actually produce leads.
That last point is where measurement separates guesswork from a system. With GA4 and call tracking in place, you can see that your Banbury page generated four quote requests last month while your Bicester page generated none — and act on it (improve Bicester, or quietly merge it). It’s exactly the kind of lead-to-click tracking we built into the Jax Tree Removal rebuild, and it’s the difference between “we have town pages” and “we know which town pages pay.”
When should you merge or remove a page?
Not every page will work, and that’s fine — as long as you prune. Watch Search Console and GA4 for a few months after publishing. A page is a candidate for merging or removal if, after a fair window, it has:
- No impressions or rankings for its target “[service] [town]” terms
- No leads or meaningful traffic
- Content you can’t realistically improve because you don’t actually work there
Merging a weak page into a stronger neighbouring one (with a redirect) is usually better than leaving thin pages live. Quality across the site beats quantity every time.
The short version
Service-area pages let a tree surgeon rank in multiple towns — but only when each page is genuinely about that town. Build for the places you really serve, write real local content, structure each page consistently, and measure which ones produce work. Skip the find-and-replace approach entirely; it’s the fast route to a penalty.
If you’d rather have this built and tracked for you, our local SEO service for tree surgeons covers town-page strategy end to end — and you can get a free audit to see exactly which town pages are worth building first.