Google Reviews Widget for Multi-Location Businesses

Illustration of three business location pages, downtown, uptown, and airport, each needing its own distinct Google Place ID and matching reviews widget — Three locations, three Google Business Profiles, three Place IDs — one widget setup per page.

If your business has more than one physical location, there is a good chance each one has its own Google Business Profile — its own address, its own reviews, its own star rating. Yet a surprisingly common setup mistake is treating reviews as if they belonged to the brand as a whole: one widget, pointed at one location's Place ID, copy-pasted across every location page on the site. It looks fine at a glance. It is quietly wrong, and it costs you trust with exactly the visitors doing the most research — people trying to decide whether to visit their specific nearby branch.

The common trap: one widget, every location page

Why it happens: it is the path of least resistance. Someone sets up a widget for the flagship or head-office location, copies the embed code onto every other location page during a site build, and nobody revisits it — until a customer at the airport branch notices the reviews on that page are clearly about the downtown store.

The damage is subtle but real. A visitor comparing your downtown and uptown locations, trying to decide which one to book with, sees identical reviews on both pages — either because it is obviously the same feed, or worse, because they don't notice and make a decision based on reviews that were never actually about the location they are looking at. Either outcome undermines the entire point of showing reviews in the first place: specific, verifiable proof about the exact place someone is considering.

The correct setup: one Place ID, one widget, one page

Every physical location with its own Google Business Profile has its own unique Place ID and its own independent set of reviews. The fix is straightforward in concept, if it requires a bit of setup work: create a separate widget for each location, each one bound to that location's specific Place ID, and place each widget only on that location's own page.

Diagram comparing an incorrect setup where one Place ID feeds every location page versus a correct setup where each location page has its own matching Place ID — The fix is purely a mapping problem — one widget, one Place ID, one page, every time.

Incorrect setup One widget created from the flagship location's Place ID, embedded on every /locations/[city] page across the site — every page shows the same reviews regardless of which branch it represents.

Correct setup A separate widget per location, each bound to that specific branch's Place ID, embedded only on that branch's own page — every page shows reviews that are actually about it.

Multi-location widget setup checklist

Before you embed anything

List every physical location and confirm each has its own claimed, verified Google Business Profile listing with its own address.
Look up the unique Place ID for each individual location — do not reuse one across locations even if the listings look similar.
Create one widget per location, each connected to its own Place ID, and give each a clear internal name (e.g. "Downtown branch widget") so you don't mix them up later.
Embed each location's widget only on that location's own page — homepage, "find us" pages, or a location directory can either omit reviews entirely or show an aggregate, but individual location pages should show that location's own reviews.
Re-check the setup any time you open a new location, retire one, or restructure your location pages — this is the step most businesses forget after the initial setup.
Spot-check each live page periodically to confirm the reviews shown actually match the location the page represents.

Visual checklist of five multi-location widget setup steps ending with a confirmation to spot-check that live pages match their location — Do this once per location, and revisit it whenever a location opens, closes, or moves.

Keeping multiple widgets fast

Running several widgets across a site does not have to mean loading several scripts at once — each page should only load the single widget relevant to it. A well-built embed loads asynchronously and does not block page rendering, so having ten locations, each with its own widget on its own page, has effectively the same performance profile as having one. The mistake to avoid is loading multiple location widgets on a single shared page "for completeness"; keep it strictly one Place ID's worth of reviews per page.

What about a shared homepage or "find a location" page?

A directory-style page listing every branch does not need to embed every individual widget at once — that is exactly the kind of shared page where loading multiple location feeds together causes both the performance problem and the confusion problem described above. Either keep that page free of embedded reviews (a simple star rating and link per location is enough) or, if your plan supports it, show one clearly-labelled aggregate view rather than stacking several independent per-location widgets in the same scroll.

Why this is a real product capability, not just advice

GR Widget is built around exactly this per-location model: each widget you create binds to its own Google Place, and you can place as many independent widgets as you need across your site and domains, depending on your plan. That means the setup described above is not a workaround — it is simply how the product is meant to be used for multi-location businesses. Plans include 6 free layouts and 13 in total, with no API key required to connect any location's listing. If you have not connected your first location yet, our guide on setting your Google location for reviews walks through finding and connecting a Place ID step by step. Curious how customer count affects each location's conversions? See our guide on how many Google reviews customers read before booking.

Frequently asked questions

Should I use one Google reviews widget for all my locations?

No — if you use the same widget, pointed at a single Place ID, across every location page, you are showing every visitor the reviews for only one branch, regardless of which location page they are actually reading. This dilutes trust (a customer researching your downtown branch sees reviews about your airport branch) and can look careless or even misleading if noticed.

How do I find the Google Place ID for each of my business locations?

Each location that has its own Google Business Profile listing has its own unique Place ID. Search for the specific location by name and address using Google's Place ID finder tool, or look it up from within your Google Business Profile manager for that listing — do this separately for every location, even if the listings look nearly identical.

What if two of my locations share one Google Business Profile listing?

Then you likely need to split them into separate, individually verified listings first — Google's guidelines generally expect one listing per physical location. Until that is fixed, any widget setup will inherit the same mixed-up review problem, because there is only one Place ID and one set of reviews to pull from regardless of the widget configuration.

Will adding a separate widget per location slow down my website?

Not if each page only loads the single widget relevant to that page. The mistake that actually causes slowdowns is loading multiple widgets or review scripts on the same page "just in case" — keep it to one widget, one Place ID, one page.

Give every location page its own honest, verified reviews — not a copy-pasted feed from somewhere else.

Set up your first location widget free

No credit card · 6 free layouts · Live in minutes

Compare plans on pricing, explore every layout on features, or browse more guides on the GR Widget blog. Questions? Email hello@grwidget.com.

Google reviews widgets for multi-location businesses, done right