A store with no reviews at all looks to a first-time visitor like an empty restaurant in the middle of the day. The place might be excellent, the kitchen might beat the one next door, but someone walking past has no way of knowing and would rather not find out at their own expense. That is the problem customer reviews in a WordPress store solve: they show that somebody already bought here, got the parcel, and came back to write two sentences about it.
The catch is that switching the review module on does nothing by itself. I see it with clients all the time: the feature is there, the tab under the product is there, and the reviews are nowhere, because nobody ever asked a single customer for one. Or the reverse: there are plenty of reviews, but they sit in the third tab at the bottom of the product page where nobody looks, and on top of that they pull in an external script that adds half a second to every page load.
This post covers both halves: how to set up a collection process so reviews arrive on their own after every order, and how to display them so they actually convince people instead of just filling space. I write about it from the point of view of a store that has to earn its keep, not from the point of view of a plugin shortlist.
Why a store without reviews loses orders
Somebody landing on an unknown store from search makes one decision in their head: trust this, or close the tab. Price, photos and the product description answer the question “is this the thing I was looking for”. Reviews answer a different one: “will these people actually ship me a parcel”. Both matter, and on a first purchase the second one usually matters more.
Missing reviews are one of the most common reasons a store gets traffic and no orders. I took that mechanism apart in more detail when writing about why your online store is not selling, where reviews are one item on a longer list of obstacles. Here I deal with them alone, because this is an obstacle you can remove without rebuilding the whole store.
There is a second, less obvious effect. Reviews are content your competitors do not have, because your customers wrote it. A customer uses different words than a manufacturer: “came up small on me”, “arrived in two days”, “cable too short for my desk”. Those are exactly the phrases people later type into Google. A store that lets customers speak under its products gets that content for free.
What helps: before you start shopping for plugins, count how many orders you shipped last quarter. If that number runs into the dozens and you have zero reviews, this is not a technical problem, it is a missing request. No tool will rescue that.
What customer reviews cost on WordPress
There are three routes, and they differ less in price than in what you are paying for.
Built-in WooCommerce reviews cost nothing beyond the time it takes to configure them. They are part of the store, they carry a star rating, they mark reviews from people who actually ordered as verified, and they keep the data in your own database rather than at another company. What they lack: an automatic request after purchase, customer photos, and a comfortable moderation panel once the volume grows.
A plugin adds exactly those missing pieces: an email request triggered by an order status change, a reminder, photos, store replies under a review, a coupon in exchange for one. Paid plugins are usually sold as a yearly licence for a single domain, and the amount depends on the vendor and on how many stores you attach. Plugin pricing changes more often than tutorials get updated, so check the figure at the source, with the vendor, not in an article.
An external review service is a monthly subscription that typically scales with order volume or with the number of invitations sent. In return you get a public profile page for the store, mediation when a dispute comes up, and a badge people recognise. You pay twice: in cash for the subscription, and in speed, because a service like that puts its own script and its own widgets on your pages.
My own work on this is not priced per item or “from X”, because a store with five products is a different job from a store with a courier integration and a theme three different teams have already modified. I look at the store, write out the scope, and give a price in writing before anything starts. Configuring the built-in module together with a post-purchase request is a matter of hours, not weeks.
What helps: start with the built-in module and the post-purchase request. If reviews are arriving two months later and you find yourself missing one specific feature, add a plugin then - for that one feature you actually need, not for the whole list on the box.
How to collect reviews after purchase and where to show them
This is where the real work sits, because reviews have to be asked for, and asked for at the right moment.
Timing. The request goes out after the customer has received the product and had a chance to use it, not after they paid. For a courier parcel that is usually a few days after the order status flips to completed; for something that has to be unpacked and tested, a little longer. An email sent on the shipping day asks about something the customer has not seen yet.
What the request says. One short question about something specific beats a generic “rate your shopping experience”. Ask about that product, with its name and photo in the email, and give a link that goes straight to the form, with no login and no hunting for the order in an account panel. Every extra click along the way eats part of your responses.
Purchase verification. Only collect reviews from people who bought from you, and mark them as verified. The built-in WooCommerce module does this out of the box, because it knows the orders. It is also the simplest barrier against spam and bots dumping text under your products - I covered how that junk gets into a store and what blocks it when writing about fake orders and spam.
Placement on the product page. The average rating and the review count belong at the top, next to the price and the add-to-cart button, not only in a tab at the bottom. Under the product description, show three or four of the most recent reviews with a link to the rest. Two details make a real difference here: reviews should be readable on a phone without tapping into a tab, and the review section must not shove the layout around once it loads.
Structured data. Ratings are worth handing to Google in a format it understands, as structured data on the product. One thing has to be said plainly: whether stars show up in search results is Google’s call, not your code’s. Your job is to supply the data correctly and to keep it consistent with what a human actually sees on the page. How that works and where it usually breaks is in my separate post on schema.org structured data.
Negative reviews. Do not delete them and do not hide them. A store with nothing but five-star ratings reads as staged, and one factual reply under a low score sells better than ten raves. What you must not do: write reviews yourself, mark something as verified when there is no order behind it, or filter so that only the good ones survive. In the EU, consumer rules introduced with the Omnibus directive require you to state whether and how you verify reviews. That is not legal advice - have the exact wording on your site confirmed by a lawyer; my part is making sure the store displays the truth.
What helps: set the request up once and leave it alone for a quarter. Reviews compound: the first two weeks look like a failure, and three months in you have content under your products where there was none at all.
What I do differently - reviews without heavy third-party scripts
The thing I fix most often here is not missing reviews, it is what reviews cost in performance. A store runs a review module from an external service, that service pulls in its own JavaScript, its own stylesheet, a font and badge images. The result: the product page, the one screen where a customer makes up their mind, takes noticeably longer to load, and the layout jumps the moment the widget finally appears.
So I build it the other way round. Reviews and the average rating come out of the store’s own database and render with the rest of the page, with no waiting on somebody else’s server. If a store does use an external service because it wants the badge, the badge stays, but I fetch the data from it in the background and display it with my own code instead of letting the full widget onto the page. The same content for the customer, no layout shifts, and no third vendor in the critical path of a product page.
The second thing is sequence. Reviews are one element of a product page, and they only pay off once the rest of the path is clear. If the store loses people further down, in the cart and at payment, reviews will simply walk more of them into the same jam - which is what I wrote about when covering a shorter WooCommerce checkout. So before I add anything, I walk the entire purchase path on a phone and look at where orders are actually leaking. That is how every job runs on my side under optimising an existing store: measure and diagnose first, then make one targeted change in the single place that hurts.
Summary
Reviews on a WordPress store are a process, not a plugin. You need a request that goes out automatically a few days after an order is completed, verification that a real buyer is writing, a spot high up on the product page next to the price, and correct structured data for Google. The built-in WooCommerce module handles most of that for free; a plugin or an external service add requests, photos and a badge, for a yearly licence or a monthly subscription whose amount you check with the vendor. What to watch: that somebody else’s widget does not cost you product page speed, and that everything you display is true.
If you have a store people walk into and leave without ordering, send me the link. I will walk the purchase path on a phone, check whether reviews are visible and whether they are slowing the product page down, and tell you straight what is worth fixing first.
Frequently asked questions
Are built-in WooCommerce reviews enough, or do I need a plugin? They are enough to start. They give you stars, a verified-purchase mark, and they keep the data on your side. A plugin or an external service earn their place when you need an automatic post-purchase request, customer photos, or comfortable moderation at volume. Keep the order right: the collection process first, then a tool for the one thing you are missing.
How do I ask customers for a review so that somebody actually replies? Send one email a few days after the order was completed, with the name and photo of the product they bought, and a link that goes straight to the form without a login. Ask about that product, not about “your shopping experience”. One reminder a week later is fine; two is pressure.
Will review stars appear in Google results? They might, but nobody can guarantee it. Your part is supplying the ratings as structured data on the product, consistent with what a visitor sees on the page. Whether to show stars is Google’s decision, and it can change without notice even when your markup is flawless.
Can I delete negative reviews from my own store? Technically yes, in practice it is a bad trade. A store with nothing but top scores reads as rigged, and a factual reply under a critical review builds more trust than its absence. There is a formal side too: the EU rules on stating whether and how you verify reviews, introduced with the Omnibus directive, do not contemplate filtering for a better average. Have the wording on your own site confirmed by a lawyer.
Sitting on this yourself and unsure where to start? I speed up and repair existing sites and stores - Core Web Vitals, outages, the features that are missing. Let’s talk about your project.