Location Pages Google Will Actually Keep

Why the template approach stopped working

The classic version is one page, a list of thirty town names, and a script that swaps the name in. The result is thirty pages that are ninety-five per cent identical, each targeting a town the business may or may not meaningfully serve.

Google calls these doorway pages and has had explicit guidance against them since 2015. The treatment is not usually a penalty in the dramatic sense. It is quieter and more annoying: the pages get crawled, judged as near-duplicates, and either dropped from the index or kept at a position where nobody will ever see them. You end up with thirty URLs, a bloated sitemap, and no traffic.

The deeper problem is that a page claiming to serve a town, with nothing on it demonstrating any connection to that town, is making an assertion with no evidence behind it. That is the same failure mode as a profile claiming a service area it cannot cover, and the fix is the same: make the claim true, then show the proof.

The three tests before you build a single page

I will not build a location page unless it passes all three of these, and applying them usually cuts a list of thirty proposed towns down to five or six.

First, can you serve it profitably and regularly? Not once last year. If a job in that town is an exception you would rather decline, the page has nothing honest to say.

Second, is there enough distinct demand to justify a page? A town of four thousand people fifteen minutes from your base generally does not need its own page; it is better covered by the page for the larger area it sits inside. A city of four hundred thousand does.

Third, and this is the test that fails most pages: can you write four hundred words about working in that specific place that would be wrong if you pasted them onto another town's page? If every sentence survives a find-and-replace, you do not have a location page, you have a template with a variable in it.

A worked example. A client wanted eighteen location pages. Applying the three tests left six. We built those six properly over about two months, and they outperformed what the eighteen would have done, because six pages that each say something true and specific beat eighteen that say the same thing with different proper nouns. The other twelve towns were covered by mentioning them honestly on the parent service pages, which costs nothing and risks nothing.

What has to genuinely differ between pages

If you pass the third test, you already know what to write. These are the elements that reliably make a location page specific, in rough order of how much they help.

Real jobs in that area. Two or three short accounts of actual work: the problem, the neighbourhood, what it took, how long. No business names if the client prefers not, but real detail. This is the single strongest differentiator and nobody can copy it.

Reviews from customers in that area, pulled through onto the page. These corroborate the claim in somebody else's words.

Conditions specific to that place. Housing stock and the plumbing or heating that comes with it. Water hardness. Soil type for anyone doing groundwork. Traffic and access constraints that affect your call-out times. Local regulations or permit requirements. A roofer writing about the roof types common in one suburb versus another is writing something no template can generate.

Genuine logistics. Which depot covers it, typical response time, parking or access notes, which days you are usually in that area. Useful to the reader, impossible to fake convincingly.

And the things that help but do not differentiate on their own: a map, directions, area-specific service lists, and schema markup. Mark these pages up properly with LocalBusiness and Service schema so the areas served are machine-readable rather than just stated in prose, which is the whole purpose of adding local schema markup to a site.

Structure, URLs and internal linking

Keep location pages at a predictable depth and give them real URLs containing the service and the place, not an ID. A page targeting a service in a named city should say so in the URL.

Link them from somewhere persistent. A footer column or a locations section on the parent service page is enough. Pages that exist only in the sitemap and are linked from nowhere are telling Google you do not consider them important, and Google tends to agree.

Link them to each other sparingly and only where it makes sense, and link each one up to the parent service page. The pattern that works is a shallow hub: service page at the top, location pages beneath it, each location page pointing back up and across to one or two neighbours.

And resist the urge to build the hub page that is nothing but a list of links to the location pages. If the hub has no content of its own it is another thin page, and you have added a problem rather than solved one.

How to tell whether they are working

Check indexation first, before anything else. In Search Console, confirm each page is actually indexed. If several are showing as crawled but not indexed, that is Google telling you directly that it judged them not worth keeping, and no amount of waiting fixes it. Rewrite or remove them.

Then watch impressions per page rather than position. A location page that is indexed and accumulating impressions for queries combining your service and that place is working, even while position is still poor. A page with no impressions after two months is not in the running at all.

Expect three to six months for these to mature in a competitive market. They are among the slower things in local SEO because they are competing on content quality rather than configuration, and content takes time to be assessed.

Done honestly, a small set of location pages is one of the most durable assets a local business can build, because the thing making them work, real specific knowledge of real places, is exactly what a competitor cannot copy in an afternoon. It is the approach behind the location pages on my own site, including local SEO services in Toronto and the Lahore market, and it is the same standard I hold client pages to as a local SEO expert in Pakistan working mostly with businesses overseas. If you want the full picture of how this fits alongside profile work, that is set out in the way an engagement runs.