Google Reviews for Multiple Locations: A Branch-by-Branch Setup

Keep the Profile, Request Link and Website Page Together

To manage Google reviews for multiple locations, keep a separate record for each eligible Business Profile. Send customers to the profile for the branch they used, and display that branch’s reviews on its website page. A shared brand name does not make one branch’s rating evidence about every location.

Start by connecting three things: the customer’s experience, the correct Google profile, and the page where a future customer makes a decision. Head office can coordinate the work, but every request link and embed still needs a named location. This guide provides a checklist you can run manually before buying software.

Confirm profile eligibility before treating every town you serve as a branch. Google’s guidelines prohibit duplicate profiles for the same location and set specific conditions for service-area businesses with separate locations. A single operation covering several towns should not create extra profiles simply to collect local reviews.

Related reading: Google’s location and service-area eligibility guidelines, Check whether separate service-area profiles are appropriate.

Create a Location Register Your Team Can Actually Use

Use a spreadsheet with one row per real branch. Give it a stable internal label, such as BR01 — Riverside, rather than relying on the brand name that all search results share. This label belongs in your internal register; it is not a reason to rename the public profile.

Record the public profile URL and check its address, phone number and operating status. Then record the direct review link separately. A directions link, a website link and a write-a-review link serve different jobs, even when they all mention the same business.

Add the website page and widget identifier once the embed exists. If your provider uses a saved widget ID, record that ID and the connected location. Keep credentials and private customer records out of this shared checklist.

Illustrative row, not a customer account: “BR01 — Riverside | [checked public profile URL] | [tested review link] | /locations/riverside | [Riverside widget ID] | Maya, site manager | checked 14 October 2026.” Leave an unknown URL blank with an assigned next action. A guessed destination is harder to spot than an unfinished field.

• Internal branch label and customer-facing address
• Public Google profile URL and direct review-request URL
• Website location page and widget/source identifier
• Owner, backup contact and last destination-check date
• Request templates and printed signs that use this branch’s link

Route Requests by the Experience, Not by Customer Sentiment

Copy a fresh review link from each branch’s Business Profile. Google’s current desktop instructions are Read reviews → Get more reviews → Copy. Open each saved destination on a phone and confirm the branch before adding it to an email template or printing a QR code.

Choose the location from the completed booking, purchase or service record. An illustrative message is: “Hi [Name], thanks for visiting [Brand] at [Branch]. If you would like to share an honest review of your experience, here is the link: [branch review link]. Thanks, [Team].” Check that the branch name and URL come from the same record.

If location data is missing, hold the request for a person to check. Do not silently default to headquarters. For jobs involving more than one operation, establish a consistent rule based on which eligible business actually provided the experience, rather than whichever profile needs more stars.

• Use the same neutral invitation for comparable customers
• Keep private feedback available regardless of satisfaction
• Avoid rewards, prescribed wording and pressure to post on-site
• Measure correct delivery instead of giving staff review-number targets

Related reading: Google’s review-link and QR code instructions, Google’s current rating manipulation rules, Create a QR code for the checked branch, Adapt neutral email and SMS request scripts.

Put Branch Reviews on the Matching Location Page

Choose one branch page as your pilot. Put its review section near the booking or enquiry decision, alongside the address and service information a visitor needs. A heading such as “Reviews of our Riverside branch” explains the scope before anyone reads a quote.

Create or configure the widget using that branch’s source. When duplicating a website page, check the source again: copying a layout can also copy the original embed identifier. The new page can look correct while still showing the first branch’s rating and reviews.

Preserve genuine review wording and attribution. If you show selected examples or an excerpt, label that choice; do not call a curated section every review. Keep a clear route to the original profile so readers can inspect the wider record.

RevuKit’s widget preview lets you search a business and compare layouts before installation. Its Collect widgets add optional Google review requests to sites that accept a script tag; connect each to the correct branch. Check branches separately and confirm plan allowances before rollout: a preview or request button is not an automated location router or a complete review audit.

Related reading: Preview the correct branch’s reviews, Choose the installation path for your website, Decide where the review section belongs, Explore Collect review-request widgets.

Use Clear Scope on the Homepage Instead of a Mystery Brand Rating

A location directory can show separate branch cards, each with its own name, rating, count and profile link. A homepage can show selected reviews from several locations if each review identifies its branch. This gives visitors useful context without pretending that feedback about one team describes another.

If a provider offers a combined score, ask exactly what it measures. Is it calculated from complete individual ratings, rounded profile averages, or only the reviews retrieved for display? Which branches are included, when were they checked, and could duplicated sources be counted twice?

Do not label a provider-calculated figure as the Google rating for a particular branch. If you cannot explain and verify the calculation, omit the combined score and show the location figures separately. A larger-looking number is not a substitute for a traceable source.

• Branch page: the named branch’s profile and reviews
• Location directory: separate, clearly labelled branch summaries
• Brand homepage: selected reviews with visible branch attribution
• New branch: its own history, with older locations’ proof labelled separately

Check the Data Source Before Promising All Reviews

A displayed rating, total review count and visible review list are different pieces of data. Google’s Places API (New) can return at most five reviews, ordered by relevance. Seeing five cards beside a larger count does not mean the other reviews vanished, and those cards cannot support a report of every recent complaint.

Google also documents an authenticated Business Profile API workflow for listing a location’s reviews. That is a different integration with different access requirements. A business search box alone is not evidence that a widget has connected to your complete managed review history.

Ask a provider about coverage, ordering, refresh behaviour and what happens when a request fails. A presentation tool may be enough for a website section; an operations team needing every new review and reply approvals may need a dedicated management workflow. Keep those buying decisions separate.

Related reading: Google’s Places review-list limit and ordering, Google’s authenticated Business Profile review workflow, Evaluate review-widget limits before expanding.

Run This Acceptance Check Before Repeating the Setup

Have someone other than the person who copied the embeds check the finished pages. Start from the customer’s email, QR print or location directory, rather than a saved editor preview. That tests the route people will actually use.

For each branch, compare the register with the public profile and rendered website page. Check the business identity, not only the review count: counts can change between checks. Follow the source link and confirm it belongs to the same branch.

On a narrow phone screen, read a long review and try every visible control. The booking button should stay accessible, text should wrap, and the review section should not create sideways scrolling. Test after clearing website caches so an old embed does not mask a change.

Record pass or fail, the checker’s name and the next action. Review the mapping after a page duplication, profile change or branch opening, and use a routine check appropriate to your team. This is an operating recommendation, not a Google-prescribed review schedule.

• Request: message names the right branch and opens its review destination
• Print: the physical QR sign scans and identifies the location
• Website: page address, widget source and source link agree
• Scope: selected reviews and any combined figures are labelled accurately
• Mobile: long text, navigation and booking controls remain usable
• Fallback: unavailable reviews leave the address and booking route usable

Treat Relocations and Search Stars as Separate Questions

Opening an additional branch is different from relocating an existing business. Do not assume that a new branch can inherit another branch’s review history, or create a replacement profile automatically when moving. Google’s transfer guidance describes eligible relocation and duplicate-profile cases, with exceptions for some categories.

After a move or profile correction, recheck the saved request destinations, printed signs and website sources. Keep the old mapping in your internal change log so the next person can understand why a widget or URL changed.

Finally, displaying reviews is a website presentation decision. Google says self-serving LocalBusiness or Organization review markup is ineligible for its star review feature, including reviews shown through a third-party widget. Do not sell a multi-location rollout as a shortcut to organic search stars or guaranteed rankings.

Related reading: Google’s review-transfer guidance for moves and duplicates, Google’s review snippet eligibility rules, Understand what review schema can and cannot do.