To enable WooCommerce product reviews, turn on reviews under WooCommerce → Settings → Products, allow reviews for the individual product, and check moderation and the active product template. If only the stars or submission form are missing, investigate that feature separately rather than replacing the entire review system.
This guide is for WordPress stores using WooCommerce. Menu labels vary with language, editor and version. The calculation and classic-template details below were checked against WooCommerce 11.2.1 core source; extensions and custom code can change them. These are diagnostic instructions, not a claim that your store has been tested.
Identify what is missing before changing settings
| Symptom | First checks | Useful distinction |
|---|---|---|
| No review section anywhere on the product page | Global and product settings, active template, theme controls | Missing output versus output hidden by layout |
| Review text appears without stars | Rating setting, saved rating, rating component | A text review need not contain a rating |
| Visitors can read reviews but cannot submit | Login, verified-owner restriction, product review status, form errors | Displaying existing reviews and accepting a new one are separate |
| A review exists in admin but is not public | Moderation, spam/trash status, product assignment, pagination and cache | The submitter's pending preview is not public approval |
| Stars appear on the site but not in Google | Rendered structured data, access, eligibility and processing | Working site ratings do not guarantee search-result stars |
Record the product URL and ID, software versions, active theme, review extensions, user state and when the problem began. Compare an affected product with a working one using the same template. A single-product failure and a site-wide failure after an update call for different investigations.
Enable the right review and rating controls
- Open WooCommerce → Settings → Products, find Reviews, enable product reviews and save.
- Edit the affected product. In the classic Product data panel, open Advanced → Enable reviews, then update the product. If you use another product editor, locate its equivalent control for that item.
- Enable star ratings if you want them. Decide separately whether a rating should be required; the rating-enabled and rating-required options are different.
- Visit the actual product page and inspect the section, existing reviews and form. Enabling the global option does not prove that every previously closed product was changed.
The official product review instructions and Products settings reference describe these controls. Verify one product before applying a carefully scoped bulk change. A selected page in the product list is not necessarily the whole catalog.
A verified-owner label is not the same as restricting submission to verified owners. The label communicates purchase verification; the restriction determines who can submit. Neither certifies that every claim in a review is accurate. With the restriction enabled, test an account associated with the purchase. The 11.2.1 classic form and submission check use the current logged-in user's purchase eligibility, so entering a matching email as a guest is not a universal bypass. Order-specific review links and extension forms need their own checks.
Find the review in moderation before troubleshooting its display
Use the review-management screen available in your version, such as Products → Reviews. Find the correct product and inspect the review's status, text and rating. Pending, spam, trashed and approved records are different states. Approve legitimate feedback through the normal interface; do not bulk-approve everything just to make a star appear.
WordPress Discussion settings can affect login requirements, moderation, links and blocked content. The default permission for new posts does not rewrite every existing product's setting. Threaded comments and email notifications are not prerequisites for displaying a product rating.
After approval, check the correct language and product URL as a logged-out visitor. Examine pagination, sorting and expandable review panels. A private window helps separate browser state, but it does not clear server or CDN caches. If an import attached the review to another product or omitted its rating metadata, reloading cannot repair that mapping.
Follow the template your store actually uses
Block themes: inspect the active Single Product template
For a block theme, check Appearance → Editor → Templates → Single Product, including any more-specific template assigned to the affected product. Inspect the actual Product Details and review-related blocks, their settings and product context. The official product-page editing guide distinguishes shared templates from product-specific ones.
If the Editor menu is unavailable, confirm theme type and permissions. Block names and combinations depend on the installed version. Copying a classic PHP template does not automatically repair a block layout. An expandable panel is not inherently inaccessible content: test whether its text exists, whether the control works and whether a click is required to fetch the text for the first time.
Classic themes: inspect tabs, callbacks and overrides
In the checked 11.2.1 classic path, the default product tabs add Reviews when comments_open() permits it. The single-product-reviews.php template also returns early when reviews are closed. Theme settings, filters and custom callbacks can change what gets displayed.
A theme does not need its own copy of single-product-reviews.php merely to show reviews. The plugin supplies a default template; a theme copy is an override. If an override exists, compare its version and changes against the installed WooCommerce template. Follow the classic template documentation for intentional customization rather than editing core plugin files or forcing a direct PHP include.
If review markup exists but is hidden, inspect it and its ancestors in browser developer tools: display, visibility, height, overflow and tab state are useful starting points. A blanket display:block!important rule can break an accordion and cannot create output that was never generated.
Understand rating averages, review counts and update timing
In WooCommerce 11.2.1, WC_Comments::get_average_rating_for_product() divides the sum of the product's approved positive rating values by its corresponding rating count, formatting the result to two decimal places. With no ratings, the calculation returns zero. The classic product rating summary requires a positive rating count before it outputs the summary. There is no built-in 3.5-star starting score, Bayesian prior or 0.3 smoothing term in this calculation.
The rating count and review count are not interchangeable. The checked review-count method counts approved top-level product reviews and excludes replies from that count; a text-only review can increase review count without contributing a rating. Custom filters, extensions or malformed imported data need separate examination.
This is a fictional arithmetic example, not a customer dataset. All records belong to one product and have normal record structure:
| Records | Average calculation | Result |
|---|---|---|
| Approved ratings of 5, 4 and 3; one additional approved text-only review | 12 points / 3 ratings; 4 top-level reviews | 4.00 stars |
| An additional 1-star review is pending | Still 12 points / 3 approved ratings | 4.00 stars |
| That 1-star review is approved | 13 points / 4 ratings; 5 top-level reviews | 3.25 stars |
Core reviews use WordPress comments and comment metadata, with product data also holding aggregate values. Table prefixes vary. Do not assume a universal wp_woocommerce_reviews table or run an SQL repair copied from a generic tutorial. Compare the underlying records, product ID, approval state and product-object values before interpreting a visual star-fill width as a calculation failure.
The checked code recalculates and saves rating counts, average rating and review count through clear_transients() on relevant rating-save and comment-count update paths. A cache duration for an administrative pending counter is not a universal 24-hour delay for public ratings. Full-page caches, persistent object caches, CDNs and extensions can introduce separate stale layers.
Test cache and conflicts without guessing
- Confirm the approved record and expected rating for the correct product in admin.
- Compare logged-in and anonymous output, then origin and CDN output where access allows. Record actual cache evidence.
- Purge the affected product's appropriate cache layer using the host or plugin's supported process and repeat the same request. If this restores the review, investigate why approval or editing did not invalidate that layer.
- For failed submissions, capture the visible error, request response and matching server log time. Check the specific form, security rule, script optimization or extension involved.
Use the official theme and plugin conflict procedure in a backed-up staging environment. Keep the product, account and steps constant, then restore components one at a time. Isolate test payments and customer notifications. Turning off every plugin on a live store can also disable checkout and security.
Do not globally remove jQuery or WooCommerce scripts to see whether reviews improve. Locate the dependency or error first. The JavaScript rendering and crawlability guide, in Chinese is relevant when visible review content and fetched content differ; it is not a universal jQuery-conflict fix.
Choose extensions for a missing capability, not a promised cure
Core functionality usually covers basic review text and star ratings. Consider extensions when you genuinely need photos, video, helpfulness voting, richer filtering, questions, cross-system sync or a more specialized invitation workflow. Verify the current version, license scope, storage and export format, theme integration and generated structured data. Do not assign every review plugin the same API limit or table layout.
The current official product-review documentation also describes a Customer review request beta. Confirm availability, email enablement, sending conditions and the review-entry route in your installation. Neither “core never supports invitations” nor “every store already has them enabled” is a reliable assumption.
Request honest feedback about real purchases rather than selecting only satisfied customers. Retain legitimate negative experiences and respond appropriately. Customer photos and quotations need appropriate permission and context; a merchant-written test must not be presented as an independent buyer endorsement.
Check Google stars separately from storefront stars
The checked WC_Structured_Data implementation can output AggregateRating when ratings exist and star ratings are enabled, with related review data under its conditions. Core WooCommerce is not categorically missing rating markup. The final output still depends on the active rendering path, theme, SEO plugins and filters.
Inspect the page's actual Product, Review and AggregateRating entities. Values must describe the real product and accessible review content. Multiple JSON-LD scripts are not automatically wrong; conflicting identities or values need investigation. Validate supported markup with Google's tools and inspect Google's fetched version when you have Search Console access.
Google's review snippet guidelines require real, relevant review information and say not to aggregate ratings from other websites. Do not copy a shop's overall service score to every SKU. Validation and eligibility do not guarantee a rich result. For a different context, the Chinese guide to Google reviews and local SEO discusses business-profile reviews; those local-search considerations do not define WooCommerce's product-average algorithm.
Verify the original failure, then record what changed
On an isolated test product, submit a clearly identified test review and observe submission, moderation, approval and removal of approval. Check the text, rating, counts, form messages and cache refresh at each stage. Remove the test record according to the test plan and verify that the aggregates recover. Test applicable buyer and non-buyer permissions, desktop and phone layouts, expanded panels and pagination.
A working review form, public review display, Google stars and sales results are separate outcomes. Record the environment, affected URLs, exact change, repeatable checks and any unresolved failures. Do not turn one successful display test into a conversion-growth claim.
Chinese-speaking colleagues can use the same-topic Chinese troubleshooting guide; it explains the same method rather than supplying an independent study. For broader product-page work, Guangsuan's Google SEO service scope, in Chinese covers technical and content work around the store's actual pages and goals.