Two Branches, Ten, or Fifty: Three Different Problems

The tactics do not change. The failure mode does

Every location needs the same things: a correct profile, a matching page, consistent details, and reviews from its own customers.

What changes with scale is what goes wrong. At two locations the risk is neglect. At eight it is inconsistency. At forty it is nobody being accountable.

So the right advice depends entirely on how many you run, which is why generic multi-location guides are useless.

Below, the three tiers I treat differently, and what actually matters in each.

Two or three locations: keep it manual, keep it personal

At this size you do not need tooling, a spreadsheet template, or a bulk upload. You need someone to actually do the work.

The specific risk is that the newest or smallest branch is treated as an afterthought, so it has four photos and no reviews while the flagship has eighty.

Give each location its own profile, its own page, and its own review ask. Never route the second branch to the first branch phone number, because that is how one profile ends up absorbing the other.

A restaurant group with three sites that I worked with had one profile carrying ninety per cent of the reviews. Nothing was wrong technically. They had simply only ever asked at one site.

Four to ten locations: this is a systems problem

Somewhere around the fourth location, memory stops working. Hours get updated at three sites and not the other two, and nobody notices for a month.

The fix is one record that defines every location: name, address, phone, hours, categories, manager. One file, one owner, updated before anything goes live.

Audit against that record quarterly. Not the profiles against each other, the profiles against the record, because drift is invisible when you only compare branches.

This is also the size where category inconsistency appears. Two branches of the same business with different primary categories will compete for different searches, usually by accident.

More than ten: this is a governance problem

At this scale the technical work is the easy part. The hard part is that twelve branch managers all have edit access and none of them have been told the rules.

Lock down who can change a profile. One or two people, with a request process for everyone else, and a written reason for every change.

Expect unauthorised edits from outside too. Google accepts suggestions from the public, and at forty locations something is being edited every week.

Review the whole estate monthly rather than quarterly, and accept that you are monitoring rather than optimising. Optimisation at this size happens by changing the standard, not by touching listings.

The location page question

Every location needs its own page. That part is not controversial. What breaks is what goes on it.

Nine locations with the same eight hundred words and a swapped city name is the most common pattern I see, and it is the weakest.

Each page needs something only that branch can say: its own staff, its own parking, its own landmarks, its own reviews, its own photos.

The reasoning and the structure I use for these are set out in my piece on location landing pages.

Reviews across locations

Reviews do not pool. A customer review of your Karachi branch does nothing for your Lahore branch, and that surprises owners every time.

So every location needs its own steady flow, which means every location manager needs to be asking. This is a staff training problem disguised as a marketing problem.

Never redirect review requests to one profile to build a stronger number. It concentrates the signal in one place and leaves the rest competing on nothing.

Respond from the location, not from head office. A templated head-office reply on forty profiles reads exactly as templated as it is.

What never changes at any size

The primary category decides which searches a location can appear for. That is true at one location and at fifty.

Proximity still dominates. No amount of brand strength makes a branch appear for a search eight kilometres away from it, so your coverage map is decided by where your doors are.

Corroboration still comes from consistent records elsewhere, which at scale means a citation footprint per location rather than one for the brand.

And the profile itself still needs the same care per location as a single business would get, which is the work described on my GMB optimization page.

The failure to watch for at your size

If you only fix one thing this quarter, fix the one that matches your tier.

Where outside help earns its money

At two locations, an owner who cares will usually outperform an agency on a retainer, because the work is small and personal.

From four upwards the argument changes, because the work becomes repetitive, easy to skip, and expensive when skipped.

Above ten it becomes a standing function rather than a project, and the question is whether you build it internally or buy it.

If you want an outside view of where your estate stands before deciding, that is the kind of engagement I take on.

What belongs in the master record

One row per location, and these columns: exact name, address as it should appear, local phone number, primary category, secondary categories, hours, holiday hours, manager, page URL.

Add two more that most people leave out: the date each profile was last audited, and the name of the person who last changed it.

Those two columns are what turn a spreadsheet into an accountability tool. Without them you can see what the details are but not whether anyone is watching them.

Keep it in one place that everyone can read and only two people can edit. A copy on someone laptop is not a master record.

The branch cannibalisation question

Owners often ask whether two nearby branches compete with each other. In the map pack, yes, and Google usually resolves it by showing only one of them.

Which one it shows depends mostly on proximity to the searcher, so in practice each branch wins its own neighbourhood and loses the other.

That is normal and not worth fighting. What is worth fixing is a case where both branches describe themselves identically, because then Google has no basis for distinguishing them at all.

Give each branch its own category emphasis where the services genuinely differ, its own photos, and its own page written about that neighbourhood rather than the brand.

Closing or moving a location

Never delete the profile of a closed branch. Mark it as permanently closed, which keeps the reviews and the history visible and tells Google what happened.

Deleting it throws away the reviews and can cause the listing to reappear later from aggregator data, which is how a closed branch ends up competing with the one that replaced it.

If the branch moved rather than closed, edit the existing profile with the new address instead of creating a new one. Editing keeps the review history; creating starts from zero.

Then update the master record, the page on your site, and the directory entries in that order, so nothing is left pointing at an address you no longer occupy.