How to manage Google reviews for multiple locations without losing a branch

To manage Google reviews for multiple locations, put every branch's Business Profile into one Google business group, then read and answer reviews branch by branch against a reply deadline that a named person owns. Treat the group average with suspicion, because that is where a struggling site hides.

Most operators with more than a handful of sites start the same way. One person has the login, replies when they remember, and checks the overall star rating once a month. That works at three branches. At twenty it fails without anyone noticing, since the overall rating barely moves when one location goes wrong.

Put every location in one business group

Google's own answer to multi-site access is the business group. Its help page describes a group as "like a shared folder for your profiles" and says that if you share a username and password with colleagues, you "should transition to a business group as a safer way to work together" (Google Business Profile Help).

Two details matter when you set it up. Anyone you add as an owner or manager of the group can access all current and future profiles placed in it, so think twice before giving an agency the whole estate. If regional teams should only see their own sites, Google lets you create several groups, at the cost of losing the single dashboard and the single spreadsheet import. You can also add owners and managers to individual profiles inside a group, which is usually the tidier answer for branch managers.

Replying needs a verified profile. Google says you must verify your business before you can reply to reviews, so an unverified branch is one that nobody can answer for (Manage customer reviews).

Read each branch on its own

An average across locations is a blend, and blends flatten outliers. Take ten branches with similar review counts. Nine sit at 4.7 stars and one at 3.8. The group figure works out at 4.61, which rounds to a respectable 4.6, and the head office report says all is well.

The customer looking at the tenth branch sees 3.8. BrightLocal's Local Consumer Review Survey 2026, run with a panel of 1,002 US adults, found that 68% will only use a business rated four stars or more, up from 55% in 2025. That one branch is below the line for roughly two in three of the people surveyed, while the group dashboard shows a number most of them would accept.

Fixing this is a reporting habit. Every review report should open with a per-branch list sorted by rating, lowest first, with the review count and the number of unanswered reviews beside each one. Put the review count next to the rating, because 3.8 from twelve reviews and 3.8 from three hundred are different problems. The same survey found that 47% of consumers will not use a business with fewer than 20 reviews, so a thin profile is a risk even when its rating looks fine.

Decide who replies, and how fast

There are two workable models. A central team replies to everything, which keeps the tone consistent but loses local knowledge: head office does not know the car park outside one branch was shut last Tuesday. Or branch managers reply for their own site, which is quicker and better informed but drifts in tone and quality. Many groups split the work. Branches answer routine praise and simple questions, and anything involving a refund, an injury, a complaint about a named colleague or a legal threat goes to one central person.

Whichever you pick, put a deadline on it. BrightLocal found that 19% of consumers expect a reply on the day they post, 32% by the following day, and 81% within a week. Expectations moved quickly: the same-day figure was 6% a year earlier. A week is the outer limit, and two working days is a realistic standard for a team that checks every day.

Allow for Google's moderation in that timing. Replies are checked against Google's content policies before they go live, and Google says they "usually take up to 10 minutes" to review, though some take up to 30 days. The reviewer is notified when you reply and can still change their review afterwards (Manage customer reviews).

Answer in a voice that sounds like the branch

Google and customers disagree a little on how many reviews need an answer. Google's reply tips say you "don't need to thank every reviewer publicly" and suggest replying when you have something new or relevant to add (Tips to get more reviews). BrightLocal's respondents lean the other way: 80% say they are likely to use a business that responds to all of its reviews, against 45% for one that only answers the positive ones.

Answering everything across an estate pushes teams towards templates, and templates carry their own cost. The same survey found that generic or templated replies make 50% of consumers unlikely to choose a business. A short reply that picks up one specific detail from the review will do better than a long one that could sit under any review in the group. Google's guidance points the same way: keep it short and polite, never share the reviewer's private details, and sign with a name or initials.

For negative reviews, Google suggests checking your records about the visit first, admitting what went wrong and explaining what you can and cannot do. Offer a way to sort it out by phone or email. Then fix the cause at the branch, since the next customer reads the review and your reply together.

Track topics and names across branches

A reply deals with one review. Tagging shows what the reviews have in common. Pick a short list of topics that match how your business runs, such as waiting time, booking, cleanliness, price and staff, and tag every review against them. A rise in waiting-time complaints at one site points to a rota problem. The same rise at every site points to the booking system, and polite replies will not fix that.

Staff names are worth tracking with care. Reviews that praise a team member by name are some of the best feedback a branch manager gets, but Google's prohibited and restricted content policy lists "Merchants requesting that staff solicit reviews that include specific content, including content that identifies a staff member." We set out what that means for counter cards and scripts in Google's rule on staff-name review requests. Read the names customers volunteer, and keep the asking out of your scripts.

A weekly routine for the review queue

• Monday: the per-branch list, lowest rating first. Flag any branch that dropped since last week or sits under four stars.
• Every day: clear new reviews inside your reply target, and escalate refunds, safety issues and complaints about named staff to the central owner the same day.
• Friday: count the tagged topics per branch and send each manager their most common complaint with a few example reviews.
• Monthly: check who has owner or manager access in the business group, and remove anyone who has left or no longer needs it.
• Quarterly: report review counts per branch next to the rating, so thin profiles get attention before their rating does.

Running the routine in Loculens

Loculens is the review workspace Braivex built for this job. Every branch's Google reviews sit in one workspace with counts, averages and filters per location, so the weak site is the first thing you see. Each review is marked positive, neutral or negative, carries the topics you choose to track, and has names matched against your own team roster, never guessed. For the reviews that need an answer, Loculens drafts a reply measured from the replies you have already posted and opens the right Google panel. A person reads the draft and presses send, so nothing goes out unseen.

It reads Google reviews only. They arrive through your connected Business Profile, or through a scraping run billed to your own Apify account, and a nightly sync fetches only what is new. Plans are priced by locations and reviews: $39 a month for up to 5 locations, $99 for up to 25 and $299 for up to 100, billed in US dollars and excluding tax, with larger estates on enterprise terms.

The quickest test is your own estate. Start a 14-day Loculens trial with no card, add your locations, run the first sync and look at your branches sorted lowest first. If you would rather see it walked through, book the 20-minute demo on the same page and send your location list beforehand, so the workspace is already set up on your branches when the call starts.