Stars shown under a search result clearly increase the click-through rate, at equal position. They are not obtained by ticking a box: they require correct markup, real reviews, and compliance with rules that Google has tightened in recent years.
What Google displays, and for what
One clarification that saves months of wasted work. Google has restricted review rich results on certain entity types. Reviews a business displays about itself, attached to an organisation or local business entity, no longer produce stars.
Reviews about a product, however, remain eligible. That is the only route on a shop: mark up reviews at the level of each product page, not at site level.
Practical consequence: merchant reviews, the ones about service and delivery quality, will not produce stars on your pages, whatever their volume. They have their uses, this is not one of them.
The two markup structures, and how they fit together
Two structures coexist inside the product markup, and they do not serve the same purpose.
The aggregate rating carries the average and the review count. It is what produces the stars. It requires at minimum the rating value, the scale used, and the number of reviews or ratings.
The individual review describes a single review with its author, date and content. It is not mandatory to get the stars, but it strengthens the page’s comprehensibility and lets Google display a review excerpt.
A frequent mistake is declaring an aggregate rating without any individual review, on a page that nevertheless displays only three reviews. Consistency between what is marked up and what is visible is the main checkpoint.
DataFirefly Verified Reviews — PrestaShop 8 and 9 customer reviews with rich snippets and AI summaryVerified reviews, photos, rich snippets, AI summary and reward discount — no subscription.€89.00
The properties not to forget
Beyond the rating, the product itself must be correctly identified. Three elements matter.
A product identifier: barcode, manufacturer reference, or internal reference. Without an identifier, Google cannot link your page to the product and rich results are less reliable.
The exact product name, identical to the one shown on the page.
The offer, with price, currency and availability. Review markup on a product without a declared offer is incomplete.
If you also feed a product feed to Google, the identifiers must be strictly identical on both sides. An inconsistency between the feed and the page markup produces faulty matching.
The five rules to follow
- Reviews must be visible on the page. Marking up a rating the visitor cannot read is the most common reason for a manual action on this topic.
- They must be written by users, not by you. A review written in-house, even a sincere one, does not belong in this markup.
- No aggregating reviews from other sites without the right to do so and without declaring it.
- No rating without corresponding reviews. A 4.8 rating on a page with no review displayed is an unverifiable claim.
- The markup covers the main element of the page. On a category page, marking up the ratings of the twenty displayed products is not compliant: the page is not about a single product.
The mistakes that lose the stars
Four situations encountered regularly.
Reviews loaded in JavaScript after the initial render. If the markup arrives with the reviews at a later stage, it may not be seen. Server-side markup remains the safest solution.
The rating rounded in the markup but not in the display, or the reverse. Both values must match.
A review counter that includes reviews pending moderation. The marked-up number must match the reviews actually published.
Duplicated markup. A theme that already declares product markup, plus a review module that adds a second one, produces two competing declarations on the same page. It is a frequent cause of rich results disappearing right after installing a module.
Checking
Two tools, in this order.
Google’s Rich Results Test, on a product page URL. It tells you whether the markup is detected, valid, and eligible. Test several pages, including one without reviews, to check that the markup does not declare an empty rating.
The rich results report in Search Console, which surfaces errors at site scale and shows how many pages are actually eligible.
When the stars do not appear despite valid markup
It is the most frustrating situation, and it is normal. Valid markup makes the page eligible, it does not guarantee display.
Three factors are at play. Review volume, since a single five-star review does not inspire confidence in the algorithm. The trust granted to the domain, which takes time to build. And the query type, since Google does not display the same enrichments depending on the detected intent.
Allow several weeks between implementation and appearance, and do not modify the markup in the meantime on the grounds that nothing is moving.
The Verified Reviews module for PrestaShop produces this markup on PrestaShop 8 and 9: aggregate rating and individual reviews declared server-side, consistency with the reviews actually published, complete product identifiers and detection of duplicate markup with the theme.
