Multi-location SEO goes wrong in the same way at almost every business that attempts it. Someone writes one good service page, copies it once per branch, swaps the town name, and publishes twelve pages that are ninety-five percent identical. It feels like scale. It behaves like duplication, and it tends to suppress every location rather than help any of them.

The instinct is understandable, because writing twelve genuinely different pages about the same service is hard and expensive. But the shortcut produces pages a search engine has no reason to prefer over each other, so it picks one, ranks it inconsistently, and ignores the rest.

The rule that resolves most of it: a location page has to contain something true only of that location. Not the town name inserted into generic copy, but the actual staff, the actual parking, the actual opening hours, the areas genuinely covered, and work genuinely done nearby. If nothing on the page would change were it a different branch, the page has no reason to exist.

Why Duplicated Branch Pages Suppress Everything

Search engines deduplicate. Faced with a dozen near-identical pages, they consolidate to whichever one seems most representative and largely disregard the others. The business sees this as one branch inexplicably outranking the rest.

The knock-on effects are worse than the direct one. Internal link equity is spread across pages that will never rank. Crawl attention is spent revisiting duplicates. And the overall quality picture of the site drops, which is a site-wide cost paid for a page-level shortcut.

It also fails commercially even when it half-works. Someone searching for a service in their town wants evidence you are actually there. A page that is obviously templated communicates the opposite, and a visitor who senses that leaves before the enquiry form.

What Actually Belongs on a Location Page

Start with the things that are verifiably specific.

The people. Who works at this branch, with names and photographs. This is the single strongest differentiator available and almost nobody uses it, because it requires coordination rather than copywriting.

Practical detail. Parking, public transport, accessibility, which entrance to use, what the building looks like. This reads as trivial and it is exactly what someone deciding between two nearby providers wants.

Genuine catchment. The areas this branch actually serves, described honestly. A list of forty surrounding villages stuffed into a footer is the oldest local SEO trick and it does not work any more.

Local evidence. Work done, clients served or cases handled near that location, within whatever confidentiality allows. Reviews specific to the branch rather than a company-wide feed.

Real hours and contact details, per branch, matching what is published everywhere else.

The service explanation itself can be shared across locations. That is not the part that needs to differ, and trying to rewrite it twelve times is where teams exhaust themselves before reaching the parts that matter.

The Technical Layer

Structured data does real work here. The LocalBusiness type and Google’s local business structured data guidance cover address, opening hours, contact details and geographic information, and each branch page should carry its own marked-up entity rather than inheriting the head office’s.

Consistency across sources matters more than it should. The details on your location page, your business profile and the major directories need to agree exactly. A branch that moved two years ago and still shows the old address somewhere is a common and quietly damaging problem.

URL structure should be predictable and shallow. A pattern of service then location, or location then service, applied consistently, beats an ad hoc structure that grew as branches opened.

Internal linking should connect each location page to the services offered there and to nearby branches, so the crawler can see the structure rather than inferring it from a sitemap.

Watch for the near-duplicate problem returning through the back door. A new branch is often created by copying the last one, so the discipline has to survive the opening of location thirteen. Our technical SEO audit checklist covers how duplication is detected across a site.

How Many Location Pages Should You Have

One per location where you have a genuine physical presence. Not one per town you would like customers from.

This is where most businesses over-reach. Pages for towns with no premises, no staff and nothing specific to say are the definition of thin content, and creating fifty of them to cover a county is a reliable way to damage the pages that were working.

If you serve an area without premises there, the honest structure is a single page describing the coverage area from the branch that serves it, rather than a page pretending to be local.

When Multi-Location SEO Is Worth Investing In

Multi-location work pays off where the purchase is genuinely local and the customer chooses partly on proximity: clinics, practices, trades, hospitality, retail with physical stock, professional services with walk-in clients.

It pays off much less where the service is delivered remotely and location is incidental to the buying decision. A software consultancy with three offices does not need three sets of location pages, it needs one credible company.

The cost tracks the number of locations rather than the complexity of the service. Expect the first location page to take real effort to define the template and the content standard, and each subsequent one to be mostly a coordination exercise: getting the branch to supply its own staff, photographs and specifics.

Where to Start

The quickest diagnostic is to open two of your location pages side by side and read them. If the only differences are the town name and the phone number, that is your finding, and no amount of additional pages will help until it changes.

Mecanik runs technical SEO audits that measure duplication across location and service pages specifically, rather than testing a homepage, and rebuilds the templates through our website development team. If one branch outranks the rest for no apparent reason, duplication is almost always why.

Related reading: White Label Web Development for Agencies , Enterprise SEO Agency: Why Large Sites Fail Differently , Ecommerce SEO Agency: What to Expect and What to Pay and Medical SEO Agency: What Actually Moves Patient Bookings .

Frequently Asked Questions

Why do duplicated location pages hurt rankings? Search engines deduplicate near-identical pages, consolidating to whichever seems most representative and largely disregarding the rest. That is why one branch inexplicably outranks the others. It also spreads internal link equity across pages that will never rank and wastes crawl attention on duplicates.

What should be different on each location page? Anything verifiably specific to that branch: the staff who work there with names and photographs, parking and access detail, the areas genuinely served, local work or reviews, and real per-branch hours and contact details. The service explanation itself can be shared.

Should I create a page for every town I want customers from? No. Create one page per location where you have a genuine physical presence. Pages for towns with no premises, no staff and nothing specific to say are thin content, and creating dozens of them reliably damages the pages that were already working.

What structured data do location pages need? Each branch page should carry its own LocalBusiness entity covering address, opening hours, contact details and geographic information, rather than inheriting the head office’s markup. The details must also match your business profile and directory listings exactly.

When is multi-location SEO not worth the investment? When the service is delivered remotely and location is incidental to the buying decision. A consultancy with three offices needs one credible company presence, not three sets of location pages. The work pays off where customers genuinely choose partly on proximity.