The Google Reviews Widget That's Been Broken for Months (and Nobody Noticed)
Nobody checks their own reviews widget. It's set up once, it looks great on launch day, and then it becomes part of the furniture — a little row of gold stars sitting quietly in the footer or on the homepage, doing its job in the background forever, or so everyone assumes. We love the idea of social proof working for us while we're off doing literally anything else 💖, but "set and forget" is exactly how a broken widget survives undetected for months: it doesn't crash the page, it doesn't send an error email, it just quietly stops updating, or stops loading at all, and sits there looking almost fine to anyone who isn't checking closely.
What most businesses get wrong
The assumption is that once a review widget is embedded, it just keeps working forever, the same way a photo on the page keeps working forever. But most of these widgets pull live data through a third-party API connection, and that connection has moving parts: API keys that expire or get regenerated, plugin versions that need updating, platform changes on Google's side that alter how the data is served. None of those moving parts are visible on the page when they fail — the widget doesn't display an error, it usually just freezes on the last reviews it successfully loaded, or renders a blank box that blends into the page design well enough that a quick glance doesn't catch it.
1. Load the live page, not the admin preview. Widgets can render fine in a CMS editor while being broken on the actual published page — always check the real, public URL.
2. Check the date of the newest review shown. If your most recent real review is from last week but the widget's newest visible review is from eight months ago, it's stuck.
3. Compare the star rating shown to your actual Google Business Profile rating. A mismatch of more than a few decimal points usually means the widget cached an old snapshot and stopped refreshing.
4. Test on mobile specifically. Widgets frequently break on mobile layouts first, since that's tested less often than desktop.
5. Check for an API key or integration expiry notice. Log into whatever platform or plugin powers the widget and look for warning banners about expiring credentials — these are often sitting unread in an admin dashboard nobody opens.
6. Note the plugin/app version and check for updates. An outdated plugin version is one of the most common silent-breakage causes after a site or CMS update.
7. Set a calendar reminder for the next check now. Quarterly is enough for most businesses; monthly if reviews are a major part of your sales page.
How to actually do this
Start by finding out exactly what powers your current widget — a native platform feature, a third-party plugin, or a manually embedded script someone copied in once. This matters because the fix is different for each: a plugin usually just needs updating and its API key refreshing inside its own settings; a manually embedded script often needs someone to regenerate the API key through Google's developer console and swap it in; a native platform feature is the lowest-maintenance option but still worth the same quarterly visual check.
Whoever owns your website — whether that's an internal person or an outside provider — should be the named owner of this check, with it written down somewhere as a recurring task rather than left as an assumption that "someone's probably looking at that." If you don't have anyone who owns website maintenance, the fifteen-minute quarterly check above is genuinely something any team member can do without technical skills — it's a visual check, not a code fix, until something's actually found broken.
- Assuming a working widget stays working forever with no maintenance.
- Only checking the CMS preview instead of the live, public page.
- Letting one person's old login be the only thing standing between the widget and an expired API key nobody else can renew.
- Skipping the mobile check, where most embed breakages actually show up first.
- Treating this as a developer-only task when a simple visual check needs no technical skill at all.
Frequently asked questions
How would we even know if our widget is broken right now?
Open your live website on your phone, find the reviews section, and check whether the newest review shown matches a review you actually know was left recently. If there's a gap of more than a month or two between your real newest review and what's displayed, it's worth investigating.
Is this something we can fix ourselves, or do we need a developer?
Plugin and native platform widgets are usually fixable without a developer — it's often just a matter of reconnecting the integration or updating the plugin inside its own settings. A manually coded embed with an expired API key is more likely to need someone comfortable in a developer console, so it's worth knowing which type you have before assuming either way.
What's the honest trade-off of relying on an embedded widget at all?
Embedded widgets are convenient and look polished, but they add a dependency you don't fully control — a third-party API, a plugin maintainer, Google's own platform changes — any of which can break your page without you touching anything. A simpler alternative, like manually updating a handful of review quotes a few times a year, is less automated but far less likely to fail silently.
Do we need to check this more often than quarterly?
If reviews are a major trust signal on a high-traffic sales page, monthly is safer than quarterly — the cost of checking is a few minutes, while the cost of a broken widget sitting there for a full quarter on your busiest page is harder to recover.
Keep reading 🤍
I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.
Work with me ✦