Service Area Pages: Fixing Coverage on Your Website

Two ways service-area websites go wrong

The first failure is silence. The site has a homepage, a services page and a contact form, and the only clue to where the business works is a phone number with a local dialling code. Search engines are left to infer coverage from the Business Profile alone, and people searching for a service in a neighbouring town find nothing on the site that says you go there.

The second failure is the opposite, and more common after someone has read that "location pages help". A template is written once, then duplicated forty times: "Looking for a reliable plumber in Town? Our Town plumbers are available 24/7 across Town and the surrounding areas." Some sites go further and create a page for every postcode district. These pages rarely rank for long, they dilute the site, and they risk being treated as spam.

The fix sits between the two: a small number of area pages, each built around real information about working in that place, supported by a clear coverage page that lists everywhere else you go. The profile side of the same problem, hiding your address and setting service areas on Google, is covered separately in the service-area Business Profile guide.

The doorway test in practice

Google's spam policies describe doorway abuse as creating sites or pages to rank for specific, similar searches, where the pages lead visitors to something less useful than the search promised. Among the examples it gives are pages targeted at particular regions or cities that funnel people to one place, and substantially similar pages that are closer to search results than to a clearly organised part of a site. Its separate policy on scaled content abuse covers producing many pages with little value, however they were made, including with AI tools.

No rule says "more than X area pages is spam". The question is whether each page would be worth reading if search engines did not exist. These signals help you judge:

Deciding which areas earn a page

Start from your own records, not a map of every town within 30 miles. Export the last year or two of jobs from your invoicing or job-management software and count jobs by town or postcode district. Then score each area on four questions:

1. Do you get, or want, a meaningful amount of work there? Areas you would happily take more work from score higher than places you only go reluctantly.
2. Do people search for your service with that place-name? Search Console's Performance report, filtered by query, shows whether you already get impressions for searches that include the town.
3. Can you say something specific? Jobs done, conditions particular to local properties, access or parking quirks, a team member based there.
4. Is the area distinct? Two adjoining suburbs that people treat as one place do not need two pages.

A sole trader might end up with three or four area pages and one coverage page. A firm with several vans and a wider patch might justify ten or fifteen. The number is an outcome of the scoring, not a target.

What goes on an area page that stands on its own

Take a fictional drainage firm, Brightwater Drains, covering towns around Leeds. Its Horsforth and Wetherby pages share a layout: coverage, recent jobs, what to expect, prices and call-outs, reviews and questions. The substance is different on each:

None of that is padding. A reader in Wetherby learns when to expect someone and whether the firm understands private drainage; a reader in Horsforth learns about parking and the engineer nearby. Each page is short enough to read in two minutes, and neither could be rewritten for the other town by changing its name.

Material that tends to be genuinely local

• Recent jobs in the area, described in a few sentences with before-and-after photos (with customer permission, and without house numbers).
• Property types and their usual problems: Victorian terraces, 1960s estates, new-builds, farms, flats with shared systems.
• Travel realities: response times, any extra charge beyond a distance, days you cover the area.
• Local rules that affect the job, stated cautiously and linked to the council or authority where relevant, such as permits for parking a works van or skip.
• Questions customers from that area have actually asked you.

The coverage page and site structure

Every service-area site benefits from one page that answers "do you cover my area?" at a glance. It lists every town and village you serve, grouped sensibly, shows any limits or travel charges, and links to the area pages that exist. People can check coverage in seconds, and search engines get a clear map of how the area pages fit together.

• URL pattern. Keep area pages together, for example /areas/ for the coverage page and /areas/horsforth/ for each area page.
• Links in. Link to the coverage page from the main navigation or footer, and to each area page from the coverage page and from relevant job write-ups. A footer that lists sixty town links on every page is a doorway signal, not navigation.
• Links out. Each area page links to the service pages it mentions and to the coverage page, so readers can go deeper.
• No invented addresses. Area pages describe where you work, not where you are. Do not give them a street address, a local phone number that forwards elsewhere or a pin on a map suggesting premises you do not have.
• Service plus place pages. Pages such as "boiler repair in Horsforth" alongside "drain unblocking in Horsforth" multiply fast. Only create a service-plus-place page when both the service and the place need separate, specific treatment; otherwise cover services within the one area page.

Marking up the areas you serve

Your business-level LocalBusiness block, usually on the homepage, can list your main service areas with areaServed. On an area page, the page is about your service in that place, so a Service block with its own areaServed, pointing back to the business through provider, describes it well without inventing a new business per town.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "@id": "https://example.co.uk/areas/wetherby/#service",
  "name": "Drain unblocking and surveys in Wetherby",
  "serviceType": "Drainage",
  "url": "https://example.co.uk/areas/wetherby/",
  "provider": { "@id": "https://example.co.uk/#business" },
  "areaServed": [
    { "@type": "Place", "name": "Wetherby, West Yorkshire" },
    { "@type": "Place", "name": "Boston Spa, West Yorkshire" }
  ]
}
</script>

• provider uses the same @id as your main LocalBusiness block, so every area page points to one business.
• Do not add a LocalBusiness block with a local address to each area page. That describes premises you do not have.
• A radius can be expressed with a GeoCircle (a geoMidpoint plus geoRadius in metres) on the business block if that is how you define coverage, but a list of named places is easier for everyone to read.
• Keep it consistent. The places in areaServed should match the places listed on the page and, broadly, the service areas on your Business Profile.

There is no rich result for this markup. Its job is to state your coverage plainly; the page content does the persuading.

Cleaning up an existing set of thin area pages

If the site already has dozens of cloned town pages, deleting them all at once can remove the few that do bring enquiries. Work through them with data.

1. In Search Console's Performance report, open the Pages tab for the last 12 months and export clicks and impressions for every area URL. Add conversions from your analytics if you track calls or forms.
2. Mark each page: keep and rewrite (it brings enquiries, or the area scored well above), merge (a neighbouring page or regional page can absorb it), or retire (no traffic, no work wanted).
3. Rewrite the keepers first, using the material described above.
4. For merged pages, move any genuinely useful sentences into the target page, then 301 redirect the old URL to it.
5. For retired pages with no links or traffic, a 301 to the coverage page is usually tidiest; returning a 410 or 404 is also acceptable when there is no sensible destination.
6. Remove the old URLs from the XML sitemap and from any footer or sidebar link blocks, and update internal links to point at the final URLs rather than through redirects.

The fix, step by step