Why Your Review Stars Aren't Showing Up in Google Search
A client asked us recently why their business — genuinely five stars, dozens of happy customers — never showed a star rating under its listing in Google search results, while a competitor with a similar review count displayed theirs prominently. The answer wasn't the reviews themselves. It was a structured data error we found by running the page through Google's own URL Inspection tool: "Review has multiple aggregate ratings."
What this error actually means
Google reads star ratings from Review and AggregateRating schema markup embedded in a page's code — structured data that tells search engines "this business has an average rating of X from Y reviews," separate from what a human visitor sees on the page. The error appears when a page emits more than one AggregateRating block referring to the same entity, or when a set of individual Review items each resolve to conflicting rating totals. Google's guidelines are explicit that a review snippet must resolve to exactly one aggregate rating — when it doesn't, Google doesn't guess which one is correct. It simply declines to show a star rating at all.
The most common cause: duplicated schema, not bad data
In our experience this error is rarely caused by dishonest or fabricated reviews — it's almost always a technical duplication issue. A common pattern: a site's global layout renders organisation schema (including AggregateRating and a full Review array) once, and then a second component — sometimes a legacy function kept "for compatibility" during a redesign, sometimes a page-specific review widget — renders an identical or near-identical block again. The result is the same review data appearing twice in a page's structured data, which is exactly what triggers the "multiple aggregate ratings" flag. It's an easy mistake to introduce during a site rebuild and an easy one to miss, because the page looks completely normal to a human visitor — the duplication is invisible unless you inspect the raw schema.
How to check if this is happening to you
Two ways to check, both free. First, Google's Rich Results Test (search "Google Rich Results Test") — paste in your URL and look at the detected items; if Review or AggregateRating appears with a warning or error rather than a green tick, that's your answer. Second, and more reliable if you have Search Console access, use the URL Inspection tool on the specific page and check the "Enhancements" or rich-results section of the report — it will name the exact error, as ours did.
Why this is worth fixing quickly
Star ratings in search results are one of the more effective click-through-rate levers available in organic search — a visible 4.8-star rating next to a competitor's plain blue link is a meaningful trust signal at the exact moment someone is deciding which result to click. Losing rich-result eligibility because of a schema bug, rather than because of genuinely weak reviews, is a fixable problem costing clicks for no real reason. It's also a reminder that a strong star rating only helps if the underlying review and reputation management work — genuine review volume, consistent responses — is actually being reflected correctly in your page's code. The fix itself is usually small — removing the duplicate schema render, not touching the actual review content — and rich results typically reappear within days of Google's next recrawl once it's corrected.
What to do if you find it
If your own audit turns up this error, the fix is almost always at the code level rather than the content level: find every place your review and rating schema is rendered on the affected page (check your site's global layout or template files, not just the page itself, since duplication often comes from a sitewide component) and ensure the AggregateRating and Review data for a given entity appears exactly once. If you're not comfortable auditing your own site's structured data, this is exactly the kind of check we run as part of every free audit — it takes minutes to identify and is one of the more satisfying fixes to make, because unlike a lot of SEO work, you can watch the rich result reappear in Search Console within days rather than waiting months for a ranking shift.