Skip to content
Searchpedia SEO field notes Callum Bennett Callum

Local desk

Multi Location SEO

For multi-location SEO, I prioritise dedicated location pages over a single store locator because each branch needs its own search identity, not a shared one.

Beginner5 min readUpdated 2026-07-27Notes by Callum Bennett

What I’d do first

  • Create a unique, content-rich location page for each branch instead of a single 'locations' page.
  • Set up and verify a separate Google Business Profile for every eligible location with matching NAP and URL.
  • Implement LocalBusiness schema on each location page to help search engines understand the entity.
  • Track rankings at city or ZIP-code level to catch local shifts that metro-level data hides.

The path I'd take

I start with the Google Business Profile for every physical branch. For a chain of 15 dental practices across three counties, I would claim or create each listing, verify it, and ensure the business name, address and phone match exactly what appears on the website. Every GBP gets its own URL pointing to the dedicated location page — never the homepage. I have seen GBP eligibility rules change, so I double-check the guidelines for service-area businesses versus storefronts on the [Google My Business](/google-my-business/) help pages.

Once the profiles are live, I build the location pages. Each one gets its own page under a subfolder structure like /locations/manchester/ rather than a query parameter. I write unique copy for each branch: the address, opening hours, a map embed, staff photos with bios, local testimonials, and FAQs that reflect actual queries from that neighbourhood. I avoid boilerplate text — swapping only the city name is a fast path to thin content. For the dental chain I mentioned, I interviewed each practice manager to get five specific questions patients had asked that month and turned those into an FAQ block.

Next comes structured data. I add LocalBusiness schema with the @id pointing to the specific location page. I include the branch name, geo-coordinates, telephone, openingHoursSpecification, and sameAs links if applicable. I have found that marking up the parentOrganization helps Google connect branches without confusing them. After schema, I move to [citation SEO](/citation-seo/). I list each branch on the major aggregators (Yell, Foursquare, Yelp) and on industry-specific directories, always using the same NAP. I also pursue local backlinks from chambers of commerce or community event pages.

Finally, I set up tracking. In a multi-city campaign, metro-level data is useless — it averages out performance. I use a tool that tracks rankings by ZIP code or at least by city. For the dental chain, I created a spreadsheet that captured the local pack position for 'dentist near me' in each postcode area. That showed me that one branch was losing visibility because a new competitor had opened nearby, which I would have missed with a blanket report. I run a [local SEO audit](/local-seo-audit/) quarterly to check for duplicate listings or address changes across all branches.

Watch-outs

The biggest trap with multi-location SEO is duplicate or templated content. I have seen agencies produce 50 location pages by copying one template and swapping the city name. Google catches that and either ignores those pages or devalues the whole domain. I avoid this by ensuring that each location page contains genuinely local information: a neighbourhood description, a photo of the actual storefront, a staff interview, or a local event mention. If you have 20 branches, that means 20 unique paragraphs — not just 20 different suburbs in the H1.

Another watch-out is keyword cannibalisation. If two branches both target 'plumber in London', they compete against each other. I map each location to its most relevant service keywords and use distinct phrases. A plumbing company with branches in Clapham and Brixton might optimise one for 'emergency plumber Clapham' and the other for 'boiler repair Brixton'. I check the search volume per phrase — sometimes a suburb has very low demand and is better served by a combined page. I use a [local SEO checklist](/local-seo-checklist/) to avoid overlapping targets.

NAP inconsistency is a classic failure point. When you manage ten branches, one wrong address on a directory can scatter your signals. I maintain a master spreadsheet of each location's NAP and run a monthly citation audit using a [local SEO tool](/local-seo-tools/). I also watch for Google-suggested edits — sometimes users or Google add a wrong phone number. I reject those promptly.

A subtler watch-out is ignoring local link building. Many practitioners focus only on on-page and GBP, but a mention from a local newspaper or a community group can be the tiebreaker when two businesses are equally optimised. For the dental chain, I built a simple process: each practice manager submits one local event sponsorship per quarter, and my team secures a backlink from the event page. Finally, don't point all GBPs to the same page. I see this often: all listings link to the homepage. That confuses Google about which page is relevant for which location. Each profile must link to its own location page.

What I got wrong

Early in my career, I managed SEO for a law firm with five offices across the South East. I thought a single 'locations' page with an embedded Google Map and a list of addresses was sufficient. That page had thin text — maybe 150 words — and no unique content per office. Rankings were flat. None of the offices appeared in the local pack for any competitive query. I assumed the domain authority would carry the page. It did not. I later split each office into its own page under /locations/, wrote a 600-word profile for each with local case examples, and within three months three of the five offices started appearing in the local pack. The lesson: do not consolidate location content on one page.

I also made the mistake of pointing all five Google Business Profiles to the firm's homepage. I thought it would consolidate authority and help the homepage rank for all areas. Instead, Google could not figure out which page was relevant for which city. The profiles had low engagement and the local pack performance was scattered. When I changed each GBP to link to its own location page, the listings started generating more direction requests and phone calls. I now insist that every profile has a dedicated URL, even if the page is still new and thin — I can improve the page later, but the URL must be correct from day one.

Another thing I got wrong was under-investing in local citations beyond the big three. I focused on Google, Yell and Yelp, but ignored local business directories and niche sites. For a chain of independent pharmacies, I skipped the local health authority listings. A competitor who appeared on those directories started outranking us in the local pack. I eventually added those citations and reclaimed some ground. I also used to ignore geo-targeted internal linking. Now I link from each location page to other relevant location pages using natural anchor text like 'our Manchester branch also offers same-day appointments' — that spreads link equity sensibly without confusing the user.

Finally, I once accepted a default metro-level tracking report from a client's tool. It showed average rankings across Birmingham as a whole. One branch in a northern suburb was actually dropping while two others were climbing. The average masked the drop. I now insist on city-level or postcode-level tracking for every branch, and I review the data monthly to spot outliers.

Next step

Quick answers

How many location pages should a multi-location site have?

One per physical address that is eligible for a Google Business Profile. If a branch shares a building but has a separate entrance and phone, it likely qualifies. Avoid pages for PO boxes or virtual offices — they won't rank locally.

What happens if a location closes? Should I delete the page?

Do not delete it immediately. Mark the Google Business Profile as closed, redirect the location page to a nearby branch or a 'closed' notice, and update citations. Removing it abruptly can create 404s that hurt the site's authority.

Is subfolder architecture always better than subdomain for location pages?

In my practice, yes. Subfolders keep all pages under the same root domain, which passes authority more easily. Subdomains are treated as separate sites and require separate link building. Start with subfolders unless you have a technical constraint.

Sources

Primary documentation is linked directly. Anything commercial is marked nofollow.

  • Google Search Central — Official guidance on local business structured data and location page best practices.
  • Google Business Profile Help — Authoritative source for GBP eligibility, verification and multi-location management.
  • BrightLocal — Practical insights on scalable multi-location optimisation including duplicate content risks.
  • Go Fish Digital — Useful practitioner guidance on location page architecture and tracking at city level.

Notes from Callum Bennett.