The Radius Test: Proving You Actually Serve the Towns You Claim
There's a line near the bottom of an awful lot of UK service websites that reads something like: 'We cover Leeds, Bradford, Wakefield, Halifax, Huddersfield, Dewsbury, Batley, Morley and the surrounding areas.' Forty towns, one comma-spliced paragraph, a slightly sad map graphic, and nothing at all to make a customer in any of those places believe you have ever been there.
Coverage lists are the web design equivalent of a van with no livery. They take up space, they suggest something is happening, and they give a passer-by no reason to ring the number.
A list is not a promise
If you claim Bradford, a customer in Bradford is entitled to ask a reasonable question: when? Not in a legal sense — in a practical one. Can you get to me before lunch, or am I looking at Thursday week? A comma in a paragraph doesn't answer that. A proper service-area page can.
The good news is that this is one of the few corners of SEO that rewards being genuinely better at your job rather than being clever with keywords. The bad news is that most firms have taken the lazy route for so long that 'areas we cover' has become a template line item, like a cookie banner or a VAT number.
What Google is actually marking
Worth clearing something up. Google has no problem with location pages. It has a problem with pages that exist only to catch a search query and offer nothing a searcher could use. The March 2024 spam policy update on scaled content abuse was aimed squarely at pages mass-produced from a template with the town name swapped out — the same three paragraphs about 'quality workmanship' with 'Doncaster' bolted on.
If your Chesterfield page and your Mansfield page differ only in the word Chesterfield or Mansfield, you've built a doorway, not a service page. Google's systems are decent at spotting that now, and more to the point, so are customers. A page that says nothing specific reads like a page that says nothing specific, whatever the heading claims.
The radius test
Here's a working test. Pick a town you claim to cover. Ask whether you could write three hundred words about serving that town that nobody else in your trade could write. If you can, build the page. If you can't, don't — either fix the underlying claim or leave the town off the list. Half the coverage pages on the UK web fail this at the first question.
Four things that pass it:
Travel time, honestly stated
Distance on a map is a fiction. The M60 at half eight is a different road from the M60 at eleven. If you're a two-van operation in Stockport, say what a job in Macclesfield realistically means — travel time from the unit, the window you can hold, whether you'll do an evening call. Customers trust a firm that admits the motorway exists far more than one that claims 'rapid response across the North West'.
Named proof
A photo of your van outside a real building in the town beats a stock image of a smiling man with a clipboard every single time. Case studies don't need to be grand — 'replaced a boiler for a family on the east side of town, three-bed semi, done in a day' is plenty. Add the month and year. If you can name the estate, the road or the council ward, even better, as long as the customer is happy for you to.
Local friction
This is the overlooked one. Every town has its own practical annoyances: parking permits, restricted-access streets, conservation areas where you can't touch the front elevation, awkward one-way systems, a market day that closes the high street. A page that mentions these tells the reader you've actually worked there. It also does something no keyword-stuffed paragraph can — it saves you and the customer a wasted phone call.
Response windows
Be specific about when you can get there, not just that you can. Same day before noon, next working day, two to three days for surveys. Vague promises read as no promise. Specific ones read as a business that knows its own diary.
Where the doorway trap actually is
It's rarely a deliberate scheme. It usually starts with good intentions: someone in the office says 'we should have a page for each town', a freelancer builds forty of them from a template, and within a year you've got forty pages of near-identical text competing with each other, none of them ranking. The homepage absorbs every internal link, the money pages get starved, and crawl budget is spent on URLs nobody would ever link to.
If you already have a set of these, don't panic-delete them. Run the test above. Keep the eight or ten where there's real proof and a real trading history, rewrite the rest into a single genuinely useful coverage page, and 301 the retired URLs to the nearest sensible destination. Then update the sitemap so you aren't inviting Google to keep checking.
How many pages should you have?
Fewer than you think, and better than the ones you've got. A workable rule for most UK SMEs: one page per town where you complete regular work, plus one hub page setting out the overall patch, the travel policy and the response windows. That hub is also where the map lives, and where you explain honestly what happens if someone sits just outside the boundary.
Making the pages earn their keep
A service-area page isn't finished when it goes live, because its whole job is to prove something. Two measurements are worth the effort. First, add a town field to your enquiry form — a dropdown rather than free text, or you'll get twenty spellings of the same place. Second, if you use call tracking, give each area page its own number. Within a quarter you'll know which towns actually convert and which are decoration.
Then use the pages internally. Link from the hub, link from relevant service pages, and put the area name in the enquiry confirmation email so the customer sees it was read. Schema helps too — LocalBusiness with an areaServed list is a reasonable signal, though it won't rescue a page with nothing on it.
Start with a spreadsheet, not a template
The most useful thing you can do this month is open a spreadsheet, list every town you claim, and add three columns: jobs completed in the last twelve months, can we name a customer or a street, and what's annoying about parking there. Whatever rows come back full, build properly. Whatever comes back empty is a claim you're making on a comma's authority.
Coverage is a promise. Make the pages sound like one.