Choosing a Review Widget: 9 Things to Check First

Short answer: check that it isolates its CSS, doesn't expose an API key in your page source, renders real text, loads asynchronously, and doesn't hold your data hostage. Everything else is styling.

A review widget is a piece of someone else's code running on your website, forever. It's worth ten minutes of scrutiny.

1. Does It Isolate Its Styles?

The most common complaint about widgets is "it looks broken on my site". Almost always the cause is CSS collision: your theme's styles leak into the widget, or the widget's styles leak into your page.

The robust fix is a shadow root — the widget renders in an isolated DOM subtree where your CSS can't reach it and its CSS can't reach you. Ask, or check: if the widget's markup appears inside a "#shadow-root" in dev tools, you're fine.

Second best: heavily namespaced classes. Worst: an iframe (isolated, but slow and awkward to resize).

2. Does It Expose a Database Key?

Some widgets ship with a public API key for the vendor's database embedded in your page source. Even a "public" key with row-level security is more surface area than you need. Prefer a widget that reads from a dedicated read-only endpoint returning only the reviews meant to be public.

Open the page source after installing. If you see something that looks like a database URL and a long token, ask the vendor what it grants.

3. Real Text or Pictures?

The widget's reviews should be actual text in the DOM. That means search engines can read it, screen readers can announce it, and AI answer engines can quote it. Widgets that render reviews as images or into an iframe give you none of that.

4. How Heavy Is It?

Check the network tab. A reviews widget should be tens of kilobytes, not hundreds. Also check that it loads asynchronously — a synchronous script in the head can block your page from rendering, which is a real performance and ranking issue.

5. Does It Track Your Visitors?

Some widgets set cookies or load third-party analytics. That drags you into consent-banner territory and privacy obligations you didn't sign up for. Ask what it stores and whether it loads anything from a third domain.

6. What Happens If the Vendor Goes Down?

Two failure modes: the widget shows an error box in the middle of your page, or it renders nothing and the section collapses gracefully. You want the second. Ask, or test by blocking the vendor's domain in dev tools.

Related: what happens if you stop paying? Does the widget disappear, show a "trial expired" badge, or keep working in a limited form?

7. Can You Control What It Shows?

You want:

• Filter by rating or hand-pick which reviews appear.
• Control the number shown and the layout.
• Choose whether to show dates (old dates are worse than no dates).
• Turn off the vendor's branding, usually on a paid tier — know the price before you design around it.

8. Does It Update Itself?

The whole point is that new reviews appear without you touching anything. Check the refresh interval and whether the import from Google is automatic or manual. A widget you have to re-sync by hand becomes stale within a month.

9. Can You Leave?

If you export your reviews, do you get usable data? If you swap widgets, does your page break in an obvious way or a subtle one? Vendors don't advertise this, but it's the question that matters most in year two.

The Placement Advice Nobody Gives

Once you've picked one:

• Three reviews on the home page, not twenty. Volume belongs on a dedicated page.
• Next to the price — the highest-value placement most sites never use.
• On service pages, filtered to reviews about that service, if the widget supports it.
• Not in the footer. Footer reviews are decoration; nobody reads them.

Frequently Asked Questions

Do review widgets slow down a website?
A well-built one adds negligible load time. Test with your browser's performance tools before and after installing.

Will a widget help me rank?
Indirectly — real, updating text on the page and better conversion. It won't put stars in search results; that's your Business Profile.

Can I build my own?
If you have a developer, yes — Google's Places API returns a limited number of reviews and is billed per request. Most businesses find a widget cheaper than the maintenance.

Should the widget show negative reviews?
Including one thoughtful critical review with a reply usually makes the page more believable. A wall of complaints doesn't.

What about WordPress plugins instead?
Fine if you maintain WordPress properly. A script tag is less to go wrong and works on any platform.

A Widget That Stays Out of Your Way

Kudo's widget renders inside a shadow root, reads from a public read-only endpoint rather than exposing any database key, and updates automatically as new reviews come in.

Start free at getkudo.co.