Service-area pages

What a service-area page is

A service-area page is a page for one town or district you travel to, written for the searches people there make, and honest about the fact that you are coming from somewhere else. It carries what a person in that place needs to know before they call you rather than the firm down their own street: how far away you are, what the travel charge is, how soon you can be there, and why you are worth the drive.

The distinction from a local SEO page is the whole point, and it decides what can honestly go on the page. A local SEO page is for a place you are in: you have an address there, a door, a sign, staff who live locally, photographs of your own building. A service-area page is for a place you travel to: you have jobs there, customers there, roads you know, and nothing else. The first can claim presence. The second can only claim coverage, and a page that pretends otherwise is both dishonest and easy to catch.

When you need them

You need them when a real share of your work comes from towns outside the one you are based in, and people in those towns search with their own place name attached. A mobile welder in Red Deer taking regular jobs in Sylvan Lake and Innisfail is the standard case. So is any trade, clinic or contractor with vans.

You do not need them if every customer comes to you. A shop, a salon or a clinic with one door needs local SEO pages for the place it sits in, and nothing else. You also do not need them if your business has actual branches in those towns, because then they are not service areas at all — they are locations, and each deserves the fuller treatment.

And here is the warning that governs the whole service. A town you cannot say anything true and specific about does not get a page. If you have never worked in Vulcan, do not know what the drive is like, cannot name a job you have done there and would charge a travel fee you have not worked out, there is nothing to write. A page built anyway is a template with a name swapped in, which is exactly the thing search engines have spent years learning to ignore and customers have learned to distrust. Four honest town pages beat nineteen stamped-out ones every time, and the nineteen can drag the rest of the site down with them.

What goes in one

The test for every line is whether it would be false if you pasted it onto a different town's page. If it would not be false, it is filler.

• The travel terms. The callout or mileage charge for this town specifically, the minimum job size if there is one, and whether it changes after hours or in winter. This is the single most-wanted fact on the page and the one most sites hide.
• Response time from where you are. How long the drive really takes, what “same day” means for this town as opposed to your own, and what happens on an emergency call.
• Jobs you have actually done there. Described, not named: the housing stock, the well water, the age of the wiring, the two industrial parks, the ferry. Local knowledge is the only genuine proof a travelling business has.
• The boundary, stated plainly. Which neighbouring places are included and which are not, so nobody phones expecting coverage you do not offer.
• Where you are based, named clearly, with a link to the main location page. Trying to look local to somewhere you are not is the failure mode.

What you get

The pages. Usually 500 to 800 words each, one per town, as editable documents, with title tag, meta description and internal links marked. Entered by you, or as CMS content entry.

The coverage table. One sheet listing every town you named as a service area, what is true and specific about each, the travel charge, and a plain verdict: gets a page, gets a line on the coverage map only, or should be dropped. Most people find the third column is longer than they expected.

The listing check. Whether the service radius declared on your business listing agrees with the towns the pages claim, with each mismatch marked.

A worked example

An illustration, not a client. A septic service based outside Peterborough lists 22 towns on one “Areas served” page. Asked which produce actual work, the owner names five without hesitating and is unsure about the rest. Two of the 22 are three hours away and were added because a competitor listed them.

Five service-area pages are written, one per town that produces work. Each names the travel charge for that distance, the seasonal access problem specific to the area — spring road bans in two of them, cottage-road access in another — and a described job from that township. The remaining seventeen towns are reduced to a plain coverage list with a phone number, no page each. The two distant towns are removed entirely, and the owner stops quoting for work he did not want in the first place.

How it runs

1. A half-hour call. Where you are based, where you actually travel, and what you charge to get there. No charge.
2. A fixed price in writing. Per town or per set, agreed once the coverage table has settled how many towns genuinely qualify.
3. The coverage review. Every town on your current list tested against the question of whether anything true and specific can be said about it.
4. The interview. Forty-five minutes with whoever drives the van, because the specific detail lives with them and nowhere else.
5. Drafts and delivery. Two to three weeks for a set of four to six pages, delivered with the coverage table and listing check.

What it costs

Quoted as a fixed price in CAD after the half-hour call. The number depends on how many towns survive the coverage review, not how many you started with, and a set costs less per page than single pages because the interview is shared. The pricing page shows how fixed pricing works here and the published bands for the services that have them.

What happens next

The listing usually comes next, because it declares the service radius these pages claim: that is Google Business Profile copy. Then local FAQs, since callout fees and catchment are what people in these towns type. If the old thin town pages are still live, pruning and de-indexing deals with them. A set of service-area pages is finished work on its own and nothing further is assumed.