Multi-location SEO: why Google only sees one of your branches

We audited a care provider last week that serves five towns and ranks in one

They cover a good chunk of Hampshire. Five distinct areas, real staff on the ground in each one, a genuinely strong service. On paper they should show up when someone two towns over searches for what they do. They don't. For four of those five areas, they may as well not exist.

Google didn't know the other four places were even there.

That's not a ranking problem you fix by writing more blog posts or chasing backlinks. It's a structural one. And it's one of the most common — and most fixable — things we see on multi-location sites.

One address, five towns, one problem

Here's what their site actually told Google. One homepage. One address block in the footer. One phone number. A single "Areas we cover" paragraph listing the five towns as a run of text near the bottom.

To a human, that reads as "we serve all these places." To Google, it reads as one business, at one location, that happens to mention some other town names. So Google does the logical thing: it files them under their head-office town and shows them there. The other four areas go to whoever bothered to tell Google, clearly, that they operate there.

The competitor winning those searches wasn't better at the actual service. They were just legible. Google could read where they worked, so Google could send people to them.

Google isn't guessing where you work. It's reading.

It helps to stop thinking of local search as a popularity contest and start thinking of it as a reading comprehension test. Google builds an understanding of who you are and where you operate from explicit signals: the pages on your site, the structured data in your code, and your Google Business Profile. If every one of those signals describes a single location, then a single location is the only thing Google can confidently show you for.

If a place you serve isn't described somewhere Google can read it, that place doesn't exist as far as search is concerned. Not "ranks lower." Doesn't exist.

That's the uncomfortable bit. It's not that the other towns rank badly. It's that you never entered the race for them.

Why one page can't do the job of five

The fix starts with pages. Every location you genuinely serve needs its own page — a real one, with a reason to exist beyond ranking.

And this is where a lot of businesses go wrong, because they've heard "make a page per town" and turned it into a template with the town name swapped in fifty times. Google has a name for that. It calls them doorway pages, and it actively filters them out. A page that only changes the place name and funnels everyone back to the homepage isn't a location page. It's spam with a postcode.

A real location page earns its place. That means things only true of that branch:

• The specific services available at that location — not the full group menu copied across

• Real photos of that place, that team, that street. Not stock, not the head-office shot on every page

• Reviews from people who actually used that branch

• Answers to local questions — parking, catchment, travel, the things that town's customers actually ask

Do that, and each page becomes a distinct thing Google can index, rank, and trust. Skip it, and you've built five copies of the same page arguing with each other for the same rankings.

Where schema markup comes in

Pages tell people where you work. Schema markup tells machines — precisely, and in a format they can't misread.

Schema (or structured data) is a small block of code that sits behind your page and labels what everything means. Not "here's some text a search engine has to interpret," but "this is the business name, this is the street address, this is the phone number, these are the opening hours, this is the map pin." Spelled out, unambiguous, in a language built for exactly this.

Schema is how you tell Google "this is a real place, here's the address, here's the phone, here's the location" in a language it can't misread.

For a multi-location business, the rule is simple: every location page gets its own LocalBusiness schema block, describing that location and only that location — name, address, local phone, hours, and the geographic coordinates of that specific site. You link each one to its matching Google Business Profile so Google can join the dots between your page and your verified listing.

The classic mistake is putting one generic block on the homepage and calling it done. That describes the company, not the branches — so the branches stay invisible. If you're on Wix, the platform now handles a lot of this automatically, which we broke down in our piece on automatic structured data.

If you travel to customers, name the towns — don't draw a circle

Not every business has a shopfront. Plenty of the ones we work with go to the customer — trades, care, mobile services. The instinct there is to set a radius: "we cover 20 miles around Bordon." Don't. Google doesn't serve a circle on a map; it serves named places people actually type in.

List the specific towns and postcode areas you genuinely work in, on your site and in your Google Business Profile's service-area settings. Name them. That's the difference between being findable in a place and vaguely gesturing at it — a trap we've written about before in the context of location and trade businesses.

The three things that have to say the same thing

None of this works if your own signals contradict each other. Three places have to agree, character for character:

1. Your Google Business Profile for each location

2. The LocalBusiness schema in your page code

3. The name, address and phone number visible on the page itself

When those three match, Google can confidently tie every mention of you across the web back to one real place. When they drift — an old phone number here, an abbreviated street there — you make Google's job harder, and a search engine that isn't sure where you are will quietly send the customer to someone it is sure about.

This isn't just a Google Maps problem anymore

It matters more now than it did two years ago, because it's no longer only classic search reading these signals. AI assistants answering "who does this near me" pull from the same well — your structured data, your profiles, your reviews. A location you've described cleanly is a location an AI can recommend. An incomplete one gets skipped entirely. We've gone deeper on that shift in why ranking on Google no longer gets you mentioned by AI.

The good news: it's all fixable

SEO Consultation

20min

Book Now

Here's the part worth holding onto. Nothing about this is a lost cause. The care provider we audited isn't losing four towns because their service is weak or their competition is untouchable. They're losing them because their website never told Google those towns existed. That's a build problem, and build problems get fixed.

Give each location a real page. Add the schema so Google reads it as five present, distinct places instead of one with four ghosts attached. Make your profiles, your code and your pages agree. Do that, and you stop competing for one town and start showing up in all five.

If you're running a business across more than one location and you're not sure Google can see all of them, that's exactly the kind of thing worth checking before you spend another penny on ads. Drop us a line and we'll take a look at what your site is actually telling Google.

---

Multi-location SEO: common questions

Do I really need a separate page for every location?

For every location you genuinely serve, yes — provided each page has real, distinct content. A page with only the town name changed doesn't help; Google treats that as a doorway page and filters it out. A page with that branch's own services, photos, reviews and local details is what actually gets indexed and ranked. Quality over quantity: five real pages beat twenty templated ones.

What is LocalBusiness schema markup, in plain English?

It's a small block of code behind your page that labels your business details in a way search engines read directly rather than interpret: the exact name, address, phone number, opening hours and map coordinates of a specific location. On a multi-location site, each location page carries its own block describing that one place. It removes the guesswork about where you are and what you do.

We travel to customers and don't have a shopfront — does this still apply?

Yes, and it matters even more. Service-area businesses should list the specific towns and postcode areas they cover, both on the site and in their Google Business Profile settings, rather than setting a mileage radius. Google matches searches to named places, so naming them is what makes you findable in each one.

Will adding schema markup instantly boost my rankings?

Schema isn't a ranking booster you switch on for a bump. It's how you make sure Google understands your locations correctly in the first place. The gain comes from becoming eligible to appear for places you were previously invisible in, and from richer, more trustworthy listings. It works alongside real location pages and consistent profiles, not instead of them.

How do I know if my site has this problem right now?

A quick tell: search for your service plus a town you cover but aren't based in, and see if you appear. If you only ever show up around your head office, your site is very likely describing one location where it should describe several. An audit of your pages, schema and Google Business Profiles will confirm exactly where the gaps are.

Matt