Google Reviews Widget Not Showing on Website: A Triage Walkthrough

A blank space where your reviews should be is frustrating, and the temptation is to rip out the embed and start over. Before you do, slow down: a google reviews widget not showing on website pages almost always has one of two causes, and they live in different places. Either the widget itself is not rendering on the page (script, placement, container or CSS), or the widget is working fine but the reviews it pulls are not publicly available. This walkthrough separates those layers so you can fix the right one.

What the widget does and does not do

Start by calibrating expectations. A Google reviews widget displays review content you are entitled to show. It does not restore reviews that Google has removed, does not bypass Google's review policies, and does not make policy-affected reviews visible again. If reviews were flagged as misleading content, they may no longer appear at the source. The official guidance on tips to get more reviews explains that reviews and user contributions must reflect a genuine experience, and that offering incentives to post, change or remove reviews is considered fake misleading content. So an empty widget is not always a widget bug.

First check: the embed on the registered domain

Widgets like WidgetJar's are configured in a panel and then activated by installing the embed script on the registered website domain. The most common silent failure is a script that never loaded: a missing snippet, a snippet pasted into the wrong template, or a site that changed domains. Confirm three things:

1. The widget is saved and active in the panel for this site.
2. The embed script appears in the rendered page source, not just in a design preview.
3. The domain you are testing matches the registered domain.

If you are unsure how embeds attach to a page without back-end changes, the guide on embedding a widget without touching your backend covers the installation model.

Second check: are the reviews actually there?

Open Google Search or Maps and look at the Business Profile directly. Confirm the profile is verified and that the reviews you expect are publicly visible. If a review was removed for policy reasons, no widget can display it. This is the line between rendering failure and review availability, and treating them as one problem wastes the most time.

Diagnosing a rendering failure

If the review exists on Google but nothing shows on your page, you are dealing with a rendering problem. Work through these in order:

• Inspect the container. In DevTools, search the DOM for the widget's container element. Does it exist and is it empty, or is it missing entirely?
• Check console errors. Blocked scripts, Content Security Policy rejections or script conflicts with other embeds usually announce themselves in the console.
• Look for lazy loading. Aggressive lazy loading or loading="lazy" on an iframe can leave the widget unloaded until a scroll event that never fires. The same pattern is covered for images in lazy loading without slowing a static landing page.
• Check CSS. A hidden parent, display: none, zero height or overflow: hidden on the section will hide a widget that rendered correctly.

If you are running a static HTML or AI-generated site, the approach in the popup-without-JavaScript walkthrough is a useful model for how embed scripts attach to plain markup.

Performance checks after the fix

Once the widget renders, re-measure. The official web.dev guide on optimizing Largest Contentful Paint recommends targeting an LCP of 2.5 seconds or less for at least 75% of page visits, and explains that LCP can be delayed when text or images are controlled by JavaScript rather than present in the initial HTML. That is exactly the pattern a late-loading widget creates. Capture LCP and CLS in DevTools before and after re-embedding, and reserve space for the review block so layout does not shift. A repeatable baseline process is described in widget loading performance before and after an embed.

Accessibility verification

A widget that appears is not done. Tab to the review section with a keyboard and confirm every interactive element is reachable and the content is readable by a screen reader. If your review grid sits inside any overlay or popup, the WAI-ARIA guidance on modal dialogs stresses that keyboard focus must stay contained and visible close controls must exist, so a hidden review block behind an unlabelled overlay will trap users. The accessible popup keyboard and focus checklist is a good companion test.

Support versus a Google-side fix: a triage tree

Use this to decide where to send the problem:

• Reviews missing on Google itself? That is a profile or policy matter, not a widget issue.
• Reviews visible on Google, container missing or console error? Recheck the embed script and site domain in the panel.
• Container present and empty with no errors? Look at lazy loading and conditional display rules.
• Container populated but invisible? Check CSS, z-index and parent height.

When contacting support, collect the page URL, the widget identifier from the panel, the browser console output, and a screenshot of the inspect panel.

Pre-launch checklist

• Test in a private window with extensions disabled.
• Test on a real mobile device, not just a resized desktop window.
• View the page source and confirm the embed script is present.
• Re-test after every theme update, plugin change or domain migration.
• Verify LCP and the keyboard tab order after every change.

Ready to set up or re-embed properly? Start with the Google reviews widget setup page, install the script on your registered domain, and run the checklist above before you publish.