Service Area Pages That Rank: One Page Per Town, Built Properly

A service area page earns its place when it tells somebody in a specific town something true and specific about the work you do there. Most of them do not. They are one paragraph of copy with a town name pasted into it, produced twenty times over, and they are the single most common reason a trade website has dozens of pages and no local visibility at all. This is how to build the ones that work.

What a service area page is actually for

A service area page exists to answer one question from one person: do you come here, and do you do the thing I need doing? Everything else on the page is in service of that answer.

The reason this matters is that the alternative is worse in a way that is easy to miss. A single page that lists forty towns in a footer strip tells a search engine almost nothing and tells a visitor even less. It reads as a radius rather than as a commitment. Somebody in one of those forty towns has no way to tell whether you are actually working two streets away every Tuesday or whether you once drove there in 2019 and added it to a list.

A real area page removes that doubt. It says which of your services run in that town, what a normal response looks like there, and, where you have it, shows work you finished in that area. That is a genuinely different page from your main service page, which is what makes it worth having.

The failure mode everyone has seen

The cheap version of this idea is well known and still widely sold: take one block of copy, insert a variable for the town name, generate fifty pages. It does not work, and the reason is not mysterious. Google’s own guidance on helpful content asks whether a page provides substantial value compared with other pages, and describes automatically generated content that adds nothing as something to avoid. Fifty pages that are the same page fail that test fifty times.

There is also a mechanical consequence beyond quality judgement. When pages are near-identical, search engines pick one as canonical and consolidate the rest onto it, which is described plainly in Google’s documentation on consolidating duplicate URLs. The practical result is that your forty-nine other town pages are not ranking badly. They are not really in the running at all.

Start with the towns you actually work in

Before writing a word, write down the places a crew genuinely went in the last three months. Not the radius on the van. The actual list.

For a plumbing company that is usually a core town and three or four neighbouring ones. For a cleaning company running recurring routes it is often tighter than the owner expects, because a route is a geographic thing and a crew that drives forty minutes each way is a crew losing an hour a day. For a landscaping company it can be seasonal: a maintenance route covers a small area, but an install crew will travel much further for a job worth ten times a mow.

That list is your first set of pages. It is usually between four and ten. It is almost never forty.

The temptation is to build for the towns you want rather than the towns you have. Resist it for the first round, because an area page for a town where you have never worked has no local detail in it, which means it will be the thin page that drags the set down. Add those towns after you have won work there, and then the page writes itself.

Ordering the build

Work outward from where you are strongest. The first page should be for the town where you already have the most finished jobs, the most reviews and the clearest sense of what the work involves. That page will be the best one you write, and it becomes the template for tone rather than for text.

Then take the neighbouring towns in order of how much work you actually do there. By the fourth or fifth page you will have discovered the thing that makes this exercise worthwhile: each town is genuinely different, and the differences are the content.

What goes on the page

A service area page that works has six things on it. None of them are decorative.

The direct answer, in the first sentence. Somebody landed here from a search that included a place name. The first line should confirm you work there and what you do. Not a welcome message, not a paragraph about your commitment to excellence. The answer.

Which services run in that town. This is the part most sites skip, and it is the part that makes the page real. A heating and cooling company might do full system replacement across the whole county but only run a maintenance plan route in three towns. A cleaning company might take commercial contracts anywhere within an hour but only have residential recurring capacity in two areas. Saying so is more useful than pretending to offer everything everywhere, and it is also true, which matters.

The local specifics that change the job. This is where the page stops being generic. Older housing stock means different plumbing problems. A downtown with restricted parking changes how a crew loads in. A town with a lot of short-term rentals changes what a cleaning company gets asked for. An area of new construction changes what an electrician spends the week doing. You know these things. Almost none of them are on your website.

How dispatch actually works for that area. Do you have a crew that is normally in that town on particular days? Is it a short drive from your base or the far edge of the run? Can somebody get a same-day appointment there or is it usually next-day? A homeowner deciding between two companies would like to know this and cannot find it anywhere on either site.

Finished work from that area. A photo of a job you did two streets from where the reader is standing does more than any amount of copy. If you have it, use it. If you do not have it yet, that is a reason to start collecting it rather than a reason to invent something.

One clear next step. The same one as everywhere else on the site, phrased for this context. For most trades that is a quote request. For emergency work it is a phone number with the hours you actually answer stated beside it.

Writing a page per town without writing the same page twice

The practical worry is real: writing eight genuinely different pages is more work than generating eighty identical ones. Here is how to make it manageable without cheating.

Interview yourself, once, per town

Set a timer for ten minutes per town and answer five questions out loud into a phone:

1. What is the most common job we get called for here, and why that one?
2. What is different about the buildings or the properties in this town?
3. When did we last work here, and what was the job?
4. How long does it take a crew to get there, and on which days are we usually nearby?
5. What do customers here ask that customers elsewhere do not?

Ten minutes of that produces more usable, specific, un-fakeable material than an afternoon of writing from a template. It also produces the sentences that would become false if you swapped the town name, which is exactly the material the page needs.

Keep the structure shared and the substance local

Use the same page structure across every area page. Shared structure is not duplication: it is what makes a site feel coherent, and it means a returning visitor knows where to look. What must differ is the substance inside that structure.

A useful rule of thumb is that the headings can repeat and the sentences underneath them cannot.

Do not pad

A short page that says three true, specific things beats a long page that says one generic thing at length. Padding an area page out to a word count with paragraphs about the history of the town is a well-worn tactic and a transparent one. Nobody searching for an electrician in a town wants to read about its founding, and a page stuffed with that material reads as exactly what it is.

Where area pages sit in the site

Area pages should hang off the service architecture rather than floating in their own silo.

The pattern that works for most trades is a services level and an area level that cross-link. Each service page links to the areas where that service runs. Each area page links to the services that run there. A visitor who arrives on either one can get to the other in one click, and the internal linking makes the relationship explicit rather than leaving a crawler to guess it.

Avoid the two extremes. A flat list of sixty area pages linked only from a footer strip gives no signal about which matter. A deep nest where an area page is four clicks from anywhere is a page nobody will find.

Naming the URLs

Keep them readable and stable. A path that names the service and the place is self-explanatory in a search result and in a text message a crew lead sends to a customer. Once published, do not rename them casually: a URL that changes loses whatever position it had earned, and redirect chains accumulate.

Structured data, carefully

An area page can carry structured data describing the service offered and the breadcrumb trail that leads to it. That is uncontroversial and useful, and Google’s structured data documentation covers the general mechanism.

The care is needed around local business markup. LocalBusiness structured data describes a business with a location, and Google’s local business documentation and its Business Profile guidance both treat a service area business as its own case, with its own rules about how a service area is expressed. A trade that works out of one depot and drives to twelve towns has one location and a service area, not twelve locations. Marking up twelve addresses you do not occupy is not an optimisation, it is a misrepresentation, and it is the kind of thing that causes trouble later.

The honest version is simpler and works: one accurate business entity, a correctly described service area, and service plus breadcrumb markup on the pages themselves.

What to do about the towns you want but do not have

Every operator has a list of towns where they would like more work. The instinct is to publish pages for them immediately. A better sequence exists.

Start by making the pages for the towns you do work in genuinely good, because those are the ones that can rank now, and ranking there brings in work that sometimes comes from just over the boundary. Then, when you have done two or three jobs in a target town, that town has earned a page, and the page has something to say.

In the meantime, a target town can appear honestly elsewhere: named in the service area statement, included in the list of places you cover, mentioned on the pages for the adjacent towns you do work in. That is truthful, it gets the name onto the site, and it does not create a thin page that dilutes the rest.

Keeping them alive

Area pages go stale quietly. A crew stops covering a town, a service gets dropped, the photo on the page is four years old, and nobody notices because nobody reads their own website.

Two habits fix this. First, when a job finishes somewhere notable, the photos and a two-line description go to whoever maintains the site, the same week. On a managed plan that is a revision request and takes minutes. Second, once a quarter, read the area pages as if you were a customer in that town and check whether anything on them has become untrue.

A page that is quietly wrong is worse than no page. Somebody will call about a service you stopped offering, or expect a same-day visit to a town you no longer cover, and the call will end in disappointment on both sides.

What good looks like, end to end

Put together, a working set of area pages for a trade business looks like this.

Six to ten pages, one for each town where crews genuinely work, each opening with a direct confirmation that you work there and what you do. Each listing the services that actually run in that town rather than the full catalogue. Each carrying two or three paragraphs of material that could only have been written by somebody who has worked there. Each showing finished work from that area where it exists. Each linking up to the relevant service pages and back down again. Each ending in the same clear next step as the rest of the site.

No spun copy. No town histories. No addresses you do not occupy. No pages for places you have never been.

That set of pages will be smaller than the forty-page version a cheap provider would have generated, and it will do more, because every page in it is a page a person would find useful. That is the whole standard, and it is the one Google’s own guidance keeps returning to.

The order of work, if you are starting today

1. Write down the towns crews actually worked in over the last three months.
2. Pick the strongest one and do the ten-minute interview for it.
3. Draft that page and get it right. It sets the tone for the rest.
4. Repeat for the next town in order of how much work you do there.
5. Link each area page to the services that run there, and each service page to its areas.
6. Add finished work to the relevant area page every time a notable job completes.
7. Once a quarter, read them all and fix anything that has become untrue.

None of that requires new software, an agency retainer or a keyword tool. It requires knowing your own business and being willing to write down what you know, which is the part that cannot be automated and is exactly why the pages that do it well are the ones that win.