The problem multi-location businesses actually have
Single-site businesses worry about ranking. Multi-location businesses worry about consistency — because the moment you have twenty branches, you have twenty people capable of editing a profile, twenty phone numbers that might be wrong, and twenty pages that will drift apart unless somebody owns them.
Almost every multi-location SEO failure traces back to governance rather than tactics: nobody decided who controls what.
Decide what is central and what is local
Get this settled before anything else. The split that works for most organisations:
| Head office controls | Branch controls | |
|---|---|---|
| Business name | Always — one exact form, everywhere | Never |
| Page template and structure | Yes | No |
| Local content | Sets the standard and reviews it | Writes it — they know the area |
| Opening hours | Sets the default | Updates the exceptions |
| Review responses | Provides the tone and escalation rules | Replies day to day |
| Profile edits | Holds ownership of every listing | Requests changes |
The most common mistake is the opposite of what people expect. Head office usually over-controls the local content, producing identical pages, while under-controlling the profile ownership, producing chaos in the listings. Reverse both.
Stopping branches competing with each other
When two branches serve overlapping areas, poorly built pages will compete for the same searches and both will underperform. Three rules prevent it:
- One page per real location, never per target town. A branch in Poole should not have separate pages for Poole, Parkstone and Broadstone.
- Each page names its own catchment explicitly and does not claim the neighbouring branch’s.
- Interlink deliberately. A branch page should link to the nearest alternative branch, which helps both users and crawlers understand the structure — see town pages vs county pages for the hierarchy.
Where coverage genuinely overlaps, pick one branch as canonical for the shared area and say so on both pages.
Making location pages survive scale
A template is necessary at twenty branches. The trick is designing one with mandatory local fields, so the page cannot be published while it is still generic:
- Named staff, or at least a named manager.
- Genuine photographs of that branch, not stock or head-office imagery.
- Real local detail: parking, access, transport, nearby landmarks.
- Services actually offered there, since these often differ between branches.
- Local proof — a job, a client, a review from that branch.
If a branch cannot supply those, that is useful information: the page will not perform, and publishing it anyway risks the doorway page problem across the whole estate rather than one page.
Listings governance, the part everyone skips
Every branch listing should be owned by a central account with branch managers added as users, never the reverse. When a manager leaves owning the profile personally, recovering it is slow and occasionally impossible — and an orphaned listing that later gets suspended is worse still.
Audit the full estate at least annually: name, address, phone, categories and hours, on every listing, against a single source of truth. The citation cleanup checklist covers the method; at scale the only difference is that you need a spreadsheet and a schedule.