How to manage Google reviews across multiple locations

Three things to accept first

Multi-site review management is hard because it runs against instinct. Fix these three facts first; everything else follows from them:

• Every branch is a completely separate Google Business Profile. Its own star rating, its own reviews, its own map ranking. There is no brand-level score for head office to manage.
• Customers search for “near me”, not for your brand. What they see is the rating of the branch closest to them. A 4.9 flagship does nothing for the 3.8 branch two streets away.
• Ranking is calculated per location. Same brand, branch A first and branch B ninth — that is entirely normal, because distance and location-level signals carry a lot of weight in local ranking.

One conclusion follows: reviews have to be earned branch by branch, but the system has to be set centrally. Leave each manager to work it out and you get ten methods and ten different ratings. Have head office do everything and it cannot — the people who actually speak to customers do not work at head office.

What head office owns, what the branch owns

Getting this split wrong is the most common reason multi-site programmes fail. One clean line: head office owns the system and the safety net; the branch owns the sentence said at the counter.

1. Head office: one script. One sentence, identical everywhere, written into training. Do not let each manager improvise — ten versions produce ten results, and when something goes wrong you cannot tell which step caused it.
2. Head office: the physical materials. Table tents, receipts, stickers designed and printed centrally; the branch only puts them out. Materials that vary guarantee execution that varies.
3. Head office: watch the numbers, cover the bad reviews. Look at review count and rating per branch once a week, and step in for exactly two reasons — a branch at zero for two weeks running, or a review that needs a company-level answer.
4. Branch manager: one job only — get staff to actually ask. It is the one action that cannot be done remotely, and the one that actually determines the outcome.
5. Branch manager: fix the specifics. The wait, the parking, the individual member of staff named in a review — only the site can change those.

Note the “exactly two reasons” in the third item. Head office watching daily turns it into head office’s KPI rather than the manager’s; head office never looking means finding out two months late that a branch has had no reviews in a quarter. Weekly, intervening only on an exception, is the intensity that survives long term.

How to set the account up: one dashboard for all of it

In Review Helper, one record equals one Google listing. A single account holds as many branches as you like, each independent, all under one dashboard. The rules:

So the standard setup is: one head-office account holding every branch, topped up once. Opening a new site means adding one record; it arrives with its own QR code and its own 3 free reviews, with no account to set up again. Full pricing rules on You pay in credits, only for what you use.

When one branch scores much lower

In any group of ten, one or two will sit noticeably lower. The reflex is “that branch has bad service”, and most of the time it is not. Work through it in this order:

• Look at the count before the rating. A branch on 4.2 with 12 reviews next to one on 4.7 with 200 is not a service gap, it is a sample gap. Two bad reviews out of twelve will do that on their own (for how many five stars it takes to recover, use the Star rating calculator).
• Check whether the bad reviews say the same thing. Three or more pointing at one issue — the wait, the parking, one step in the process — is a real problem, and a fixable one. That is exactly what bad reviews are worth.
• Check whether it is the site itself. Parking complaints at a mall unit, noise complaints at a street unit: those come from the location, not the manager. They have to be solved centrally and must not be scored against the manager.
• Only then look at execution. Ask that branch where the table tent is and when staff last mentioned it. A good share of low-scoring sites simply are not asking — few reviews means the ones you get are from people motivated enough to come unprompted, and that skews unhappy.

Diagnose before you act. Never score managers directly on average rating — it induces two behaviours immediately: asking only customers who look happy (that is review gating, which Google bans outright — see Why you cannot ask only your happy customers), and getting friends and family to post. Scoring on review count and reply speed is far safer, and both are genuinely within a manager’s control.

Central replies that do not read like a robot

Replying centrally is efficient and keeps the tone consistent, but it has a side effect: ten branches posting identical replies is visibly a template, and a visible template does less for you than no reply at all. The fix is not to let every manager improvise. It is to let the template carry the frame and the branch supply one concrete fact:

Frame: “Thanks for taking the time. (branch-specific fact) is now sorted — we hope to see you again.”
Main Street fills in: “Weekend queueing now runs on text alerts.”
Downtown fills in: “We have spoken with the colleague concerned.”

Nobody can supply that middle sentence for the branch, and it is the only part the customer actually reads. Replies you can copy are in How to respond to Google reviews: ten templates you can copy; what to do in the first minutes after a bad review lands is in You got a one-star note. Now what?

Five traps specific to multi-site

• The wrong code on the wrong site. Two branches’ QR codes look identical; swap them and one branch’s praise lands on the other’s page. Write the branch name on the back before printing — the cheapest insurance there is.
• Running every branch off one Google listing. Some chains create a single brand profile with the sites underneath. Then no branch has its own local ranking, which throws away “near me” — the single largest source of traffic.
• Mailing the whole contact list on opening day. Thirty reviews on a three-day-old listing is the classic way to kill a new site. Pacing is in From 0 to 50 Google reviews in 90 days.
• Head office replying in the first person about something it did not witness. “I was there at the time” — the customer works out the reply came from a contact centre, and trust goes to zero in one step. If head office replies, it should sound like head office.
• Turning ratings into a monthly manager league table. The intent is motivation; the effect is pushing everyone toward filtering customers and buying reviews. Score the count, not the rating.

A checklist

• Does every branch have its own separate Google Business Profile?
• Do all branches use the same sentence and the same materials?
• Is every branch’s QR code clearly marked with which branch it is?
• Has any branch gone two weeks without a single new review?
• Are managers measured on review count or on average rating? If the latter, change it.
• Does the central reply template leave a slot the branch must fill with a concrete fact?

The real advantage of running several sites is not that head office can standardise. It is that whatever works at one branch can be copied to the other nine immediately. So get the asking right at your busiest site first — the wording, where the stand goes, when to ask, all in How to ask customers for Google Reviews — and roll it out once it runs. Reviews are one part of local ranking; the rest is in How to climb in Google Maps, step by step.