A multi-location business does not have one local SEO problem. It has one per location, plus a consistency problem that grows with the count. Distance is measured from each address, so every branch competes in its own market on its own merits, and a brand’s overall strength does not carry a weak location.
That is the structural fact everything below follows from.
One profile per location, always
Every location with an address customers visit, or that staff work from, needs its own Google Business Profile. There is no configuration in which one profile ranks across several markets, because distance is calculated from the listed location.
The common failure is a business with six branches running one profile at head office and service areas covering the region. It ranks near head office and nowhere else, and the owner concludes local SEO does not work.
Each profile then needs the full treatment independently: correct primary category, complete hours, real photos of that branch, and its own phone number where possible. A shared central number is workable but weakens the local signal and makes call attribution harder.
Location pages that are actually different
Every location needs a page, and the page has to justify itself. The test is simple: if you removed the city name, would anything on the page identify which branch it describes?
Things only that location can supply:
- Its address, hours and a map, in text a machine can read
- The team who work there, by name
- Photos of that building, inside and out
- Services that branch actually offers, which often differ
- Detail about the area: the neighbourhoods served, response times, parking, access
- Reviews from that location’s customers
- Work completed nearby, described specifically
Things that do not count: the same three paragraphs of company copy with a different city in them. That pattern produces pages competing with one another, and at scale it is the exact shape of scaled low-value content. The same rule we set out for programmatic pages applies here, because a location page set is programmatic whether or not it was generated by a script.
Reviews do not pool
This is the fact operators find most inconvenient. Reviews attach to the profile they were left on. A flagship with four hundred reviews contributes nothing to the prominence of a branch that opened last month.
The practical consequence is that review generation has to be local and continuous. The staff at each location ask their own customers, at the moment the work is delivered. Centralising the request into a monthly email from head office reliably underperforms, because the ask arrives detached from the experience and from the person who provided it.
Replies can be centralised, provided they do not read as templates. A reply that names the specific service and the branch does the job; a reply pasted identically across forty locations undermines the credibility it was meant to build.
Consistency at scale needs a standard, not goodwill
Three locations can be kept consistent by paying attention. Thirty cannot. Drift arrives through small, well-intentioned local edits: a manager abbreviates the street, another adds “& Sons,” a third updates hours in one place and not another.
The control is a documented standard and a single source of truth. One exact format for the business name, matching what is on the signage and prohibited from carrying keywords under Google’s representation guidelines. One format for addresses. One owner of the record. Local managers request changes rather than making them directly.
This is unglamorous and it is the difference between a multi-location programme that compounds and one that quietly fragments.
Measure per location, not in aggregate
Aggregate reporting hides the thing you need to see. A group total that looks healthy can contain three strong locations and nine invisible ones, and the average conceals which is which.
Report calls, direction requests and form submissions by location, and compare each against its own market rather than against the flagship. A branch in a dense competitive city and one in a quiet suburb are not comparable, and treating them as such produces the wrong intervention every time.
The order to work in
Profiles first, because they are the strongest lever and show fastest. Location pages second, built properly for a few branches rather than thinly for all of them. Review processes third, per location, established as a habit rather than a campaign. Consistency standards alongside all of it, before the count grows past what attention can manage.
The single-location version of this sequence is our local SEO checklist, and the profile work is covered in Google Business Profile optimization. If running it across every market sounds like a job rather than a project, that is ours.
