How to Add Reviews to WooCommerce: Store Reviews Are Not Product Reviews

WooCommerce is the one platform in this series that already has reviews, and that is exactly why store owners get this wrong. WooCommerce's built-in product reviews answer is this item any good. A Google or Trustpilot store review answers will this shop actually ship it. Those are different questions asked by different people at different moments, and a first-time visitor to a store they have never heard of is overwhelmingly asking the second one. Adding third-party store reviews is not duplicating what WooCommerce gives you. It is filling the gap WooCommerce leaves. The install itself takes a minute: a Custom HTML block, no plugin. The decisions worth thinking about are where the block goes and why.

What Is the Difference Between Product Reviews and Store Reviews?

WooCommerce product reviews are left by people who bought that specific item, and they sit on that item's page. They are excellent at what they do: resolving whether a jacket runs small, whether a tool is sturdy, whether a print looks like the photograph.

They are useless for the question a stranger arrives with. Someone who found your store through a search result has no idea whether you exist as a business, whether the parcel arrives, or what happens if it does not. Product reviews cannot answer that, because a shopper knows a store controls its own on-site review display.

Third-party store reviews answer it precisely because you do not control them. A Google or Trustpilot review sits on a platform the shopper can open independently, which is what makes it worth more than any testimonial on your own domain. On a small store, that is the single biggest conversion lever you have.

Where Should Each Kind of Review Go?

Product reviews stay where WooCommerce puts them: on the product page, below the item. Do not move them and do not bury them, because a shopper who has scrolled that far is evaluating the product and that is what they need.

Store reviews belong where merchant trust is being weighed rather than product quality: the homepage, the cart, and the checkout page if your theme lets you put anything there. The cart is the highest-value spot on most small stores and the one almost nobody uses, because that is the exact moment a shopper decides whether to hand over card details.

A compact rating badge in the header or near the add-to-cart button is worth adding site-wide. It does not need to be a wall, it needs to be present at the moment of hesitation.

Why Does the Block Type Matter?

Use the Custom HTML block. Paste the widget snippet into it and it runs. This is the single most common failure in WordPress and WooCommerce alike: the code goes into a Paragraph block instead, WordPress escapes it as text, and the visitor sees the raw snippet printed on the page.

In the block editor, add a block, search HTML, and pick Custom HTML. If you are using the Classic Editor instead, switch to the Text tab rather than Visual before pasting, for the same reason.

The block works on any shop page, product page or landing page. There is no plugin to install and nothing to configure in WooCommerce itself, which is the advantage of being built on WordPress.

Why Did the Widget Stop Working After a Few Days?

Caching, almost every time. WooCommerce stores run heavier performance stacks than content sites, because a slow store loses money: page caching, object caching, a CDN, and usually a script-optimisation plugin that defers, combines or minifies JavaScript.

Script optimisation is the one that breaks embeds. A plugin that defers all JavaScript, or combines third-party scripts into one bundle, can stop a widget script from executing in the order it expects. The symptom is distinctive: the widget works while you are logged in and editing, because caching is bypassed for logged-in users, and shows an empty space to everyone else.

The fix is to exclude the widget script from JavaScript optimisation in whichever plugin is doing it, then purge the cache and check the page in a private window. Always test logged out. A store owner checking their own site while logged in is the reason this bug survives for weeks.

Which Review Platforms Matter for a Store?

Google first, because it is where a shopper checks a business they do not recognise, and it is the review set that shows up beside your name in search results. For most small stores this is the whole game.

Trustpilot second if you have any volume, because ecommerce shoppers recognise it specifically as a retailer review platform and it carries weight in that context that a general platform does not. If you sell on a marketplace as well, those reviews are worth surfacing too: an Etsy shop rating on your own store is proof from a system shoppers already trust.

Resist adding more than two or three. A row of platform badges beyond that starts reading as padding, and the point is credibility rather than quantity.

What Are the Steps?

Build the widget: paste your review profile URL into the builder, choose a layout, match the colors to your theme, and copy the embed code. For a cart or checkout placement pick something compact rather than a full wall.

In WordPress, edit the page, add a Custom HTML block where you want the reviews, paste the snippet and update. On the Classic Editor, use the Text tab rather than Visual.

Then purge your cache and open the page in a private browser window. If the block is empty when logged out, exclude the widget script from your optimisation plugin and purge again.