How to Rank for Plumber Searches Across Multiple Service Areas
Nobody drives forty minutes to a burst pipe. Plenty will drive forty minutes to fit a bathroom. So a plumber has two service radii rather than one. Almost every plumbing website is built as though there were only one.
The Problem
You cover twenty five miles in every direction. You appear in one town. Work arrives from the streets around your yard while three towns you would happily drive to produce nothing at all.
Almost every trade describes some version of that. Almost every one assumes the website is at fault. It usually is not.
The reason is structural rather than technical. Local map results are calculated partly from how far you are from the person searching. Your business address is a fixed point. No amount of work on a website moves a van's registered address closer to somebody standing eight miles away.
Worth understanding before spending anything, since the two commonest responses both make it worse. A page for every village produces thin content performing worse than the four pages it replaced. Thirty towns in a footer achieves nothing.
The demand is worth having. In our own pull of 10,003 UK plumbing keywords in July 2026, 1,156 terms carried a place name and 206,470 searches a month between them, which is 14% of the workable demand in that dataset.
Why The Map Results Will Not Follow You
Distance is measured from the person searching. Not from the centre of the town they typed. Not from where your van happens to be parked. From the handset.
Which produces the grid effect. Your visibility is not a position. It is a field varying continuously across your area, strongest around your address and weakening outward at a rate set by how many competitors sit between.
Which is why checking from the van tells you nothing. Worth saying bluntly, since nearly every trade does it and draws the wrong conclusion.
Standing at your own address is the most favourable point on the entire map, since you are by definition the closest plumber to yourself. A search there tells you what one person in the single best spot sees.
Two Radii, Not One
Every other trade has one service area. Plumbing has two, since the customer's tolerance for waiting changes completely depending on what has gone wrong.
The emergency radius is set by drive time and patience. Somebody standing in water waits perhaps half an hour. Say you can be there in ninety minutes and they will ring somebody else while you are still talking.
That radius is measured in minutes rather than miles. Four miles across a city at five in the afternoon is a longer journey than fifteen miles of open road.
The planned radius is set by whether the job is worth the journey. A customer commissioning a bathroom waits three weeks for the right fitter and does not care that you are forty minutes away.
So it extends until travel stops being worth it to you rather than until the customer loses interest.
The consequence, which almost nobody acts on. Two different town lists. The emergency list is tight and dense, the planned list wide and sparse. They overlap in the middle and diverge sharply at the edges.
What happens when a plumber runs one list for both. Two failure modes, not equally costly.
Using the planned list for emergency work advertises cover you cannot reach in time. Somebody rings, you say ninety minutes, then you have wasted their time at the worst possible moment. Some say so publicly.
Using the emergency list for planned work is quieter. You are invisible for bathroom and boiler work in towns you would gladly have driven to. You never find out, since nothing arrives to tell you.
The first mistake damages your name. The second costs you the most valuable work in the trade without leaving a trace.
What The Service Area Setting Does
Nearly every trade holds the same belief about this setting, so it is worth correcting plainly rather than gently.
What it does. It tells Google which areas you are willing to travel to. For a business without premises the public can visit, it allows the address to be hidden while coverage is stated.
What it does not do. It does not place you in the map results for those towns.
Listing forty towns does not make you appear when somebody in the fortieth searches. The distance calculation still runs from where they stand to where your business is. A declared willingness to travel does not shorten it.
Why it persists. The setting looks exactly like the control that would do this. It is called a service area and you type town names into it, so the inference is obvious. Reasonable, yet wrong.
One point specific to your trade. Since this setting states willingness rather than capability, it should reflect your planned radius rather than your emergency one.
The emergency limit then belongs on the page itself, where a customer with water on the floor will actually read it. A setting nobody sees cannot manage anybody's expectations.
What A Town Page Has To Contain To Earn Its Place
A town page earns its place by containing evidence that you work there. Everything below is a form of evidence. A page with none of it is a page with a town name on it.
Named jobs in that town. What the property was, what the work involved, roughly when. A real job a local reader recognises as local.
Photographs taken there. Your own work, not anything generic. The housing stock in a photograph establishes local presence better than any sentence about serving the area.
References a local reader would notice. Districts, landmarks, the names people use for parts of the town. A page written by somebody who has never been reads as one.
The services that town wants. Older housing generates different work from a new estate. A town of flats differs again. If the stock means leaks and old pipework, the page should be about that rather than a general list.
Which of your two radii it sits in. If a town is inside your planned radius but outside your emergency one, the page should say what you cover there rather than implying everything.
The standard to hold to. Could this page have been written about anywhere else by changing one word? If so, it is a template with a variable in it.
How Many Towns Is Too Many
Twenty near identical town pages perform worse than four genuine ones. Thin pages do active harm rather than sitting there neutrally.
What they cost you. They compete with each other, since twenty pages about the same service in twenty places are largely the same page. They dilute the site's authority across twenty destinations instead of four. And in quantity they change how the whole site is judged. A site that is mostly thin pages is assessed as a mostly thin site, including the good pages.
Which side of the line is a page on? Two quick tests.
The substitution test. Swap the town name for a different one. If the page still makes complete sense, it contains nothing about that town and it is thin.
The local reader test. Would somebody who lives there recognise it as written about their town, rather than merely mentioning it?
A page failing both is not worth publishing. Deleting weak ones produces movement quickly. Almost nobody will do it.
Choosing Which Towns
Four things decide it, applied twice: once to the emergency list and once to the planned one, since the same town can be right for one and wrong for the other.
Demand. How much searching happens there, measurable rather than assumed.
Drive time. Decisive for the emergency list, close to irrelevant for the planned one.
Competition. How many plumbers already hold that ground.
Margin. What the work there is worth once travel is accounted for. This reverses between the lists, since a callout twelve miles away can lose money while a bathroom at that distance does not.
Why the biggest town is frequently the wrong first target, which the data makes unusually clear for this trade.
In our July 2026 pull, London carried 49,570 monthly searches for plumbing terms at an average difficulty of 25, Birmingham 9,090 at 25, Edinburgh 9,950 at 13 and Leicester 3,680 at 34.
Edinburgh offers slightly more volume than Birmingham at roughly half the difficulty. Size does not predict contest at all. Leicester is considerably smaller than both and is the hardest ground in that set.
So the ordering is not a matter of population. It is demand weighed against how contested that place happens to be. The only way to know is to look rather than assume.
What Else Moves Visibility Outward
Proximity is fixed. Relevance is largely settled once your profile and pages are right. Prominence is the one that keeps moving. It is why two plumbers the same distance from a searcher do not get the same result.
Reviews, in volume and recency. The most direct prominence signal and the one most within your control. A steady flow of recent reviews outranks a better average that stopped two years ago.
Citations and consistency. Your name, address and telephone number identical everywhere. Old addresses and dead numbers across directories are one of the quietest reasons a business cannot extend its reach.
Genuine local presence. Mentions from things that are themselves local. A sponsorship, a supplier listing, a news mention, a trade association entry.
Why the outward movement comes from here. Distance works against you at the edge of your area by definition. Prominence does not weaken the same way, so a business genuinely more prominent than its neighbours holds visibility further out than proximity alone would give it.
That is the whole mechanism by which a trade extends its reach. It is slower and less satisfying than publishing pages. It is also the part that works. The mechanics of each lever sit in our local SEO guides.
How We Approach It
Both town lists are drawn before anything is built. The four factors from block seven, applied separately to emergency and planned work, against your real catchment.
What gets built when. The home town first, since a business not established where it sits will not establish itself elsewhere. Then outward, one at a time, each page finished before the next begins.
What runs alongside. The prominence work from block eight, continuously rather than as a phase, since that is what extends reach.
How coverage is measured. Across a grid of points spread over your service area rather than from a single location, which produces a picture of where you are visible and where you are not.
For this trade the grid is read twice. Tight, for whether emergency coverage holds where claimed. Then wide, for whether planned work reaches the towns worth having.
Common Mistakes
A page per village. The commonest and most expensive. Somewhere between a town and a hamlet the demand stops justifying a page. Past that, every addition is dilution.
The same content with the town name swapped. Covered in block six. It fails the substitution test by construction, since it was built by substitution.
Thirty towns listed in the footer. This does nothing and has done nothing for a long time. It persists because it is easy and looks like coverage.
Claiming emergency coverage across an area you cannot reach in time. The one with a real cost attached and the one specific to your trade.
An enquiry from a town you reach in ninety minutes is not one you can serve. The caller is told a time they will not accept, so the call is lost anyway and the goodwill goes with it.
Do that often enough and it produces the review saying the business advertises cover it does not provide, which is considerably worse than never appearing in that town at all.
The pattern underneath all four is the same. Each is an attempt to declare coverage rather than earn it. The map results respond to evidence rather than statements.
Two town lists.
Not one.
We draw the emergency list and the planned list separately, because the towns worth chasing for a burst pipe are not the towns worth chasing for a bathroom. Coverage is measured across a grid, never from your yard.
What is included every month:
£350 per month, one target area. No setup fee, nothing billed separately.
Nine guides.
One trade.
This guide covers covering more ground. The rest of the series covers the whole picture, emergency plumbing, blocked drains, boilers, bathrooms, leak detection, power flushing and the lead platforms.
