Star ratings next to a search result are one of the highest-leverage trust signals a page can earn, because they appear before the visitor ever clicks through. Getting there requires structured data that is both technically correct and honestly representative of what's actually on the page.
What Is Review Schema Markup?
Structured data added to a page's code that describes review content — rating value, author, and review count — in a format search engines can parse and potentially display as star ratings in search results.
It's typically written as JSON-LD embedded in the page head or body, following a shared vocabulary so any search engine or crawler can read the same fields consistently rather than trying to scrape rating text out of visible HTML.
Why Does Review Schema Matter for Rich Results?
Because a visible star rating in a search result increases the perceived credibility of a listing before a click, which tends to improve click-through rate compared to a plain blue link.
This is the same underlying psychology behind star rating psychology on a product page — a visible aggregate score gives a shortcut for quality assessment, and that shortcut works just as well in a search results page as it does on-site.
What's the Difference Between AggregateRating and Review Schema?
AggregateRating summarizes many reviews into one score for star display, while Review schema describes individual review entries — most rich results are driven by the aggregate, not the individual items.
Sites sometimes mark up individual testimonials as Review schema expecting stars to appear, without ever including an AggregateRating — that markup is valid but usually won't produce the star snippet on its own, since search engines look specifically for an aggregate score tied to the page's main entity.
How Do You Implement Review Schema Correctly?
Attach the AggregateRating to the correct entity type (Product, LocalBusiness, or similar), use the real rating value and count currently shown on the page, and keep the markup in sync whenever reviews update.
A common failure mode is markup that's added once at launch and never updated as new reviews arrive, so the structured data and the visible page drift apart. Automating the sync — pulling live values from wherever reviews are stored — avoids this without needing manual edits every time a review comes in.
What Are the Eligibility Rules for Star Rating Rich Results?
The ratings must reflect real, on-page or verifiably sourced reviews, the entity being rated must match the page's primary subject, and self-serving or fabricated ratings aren't eligible for display.
A services page rating "how good our own company is" using a company-controlled aggregate with no independent review source is exactly the pattern search engines exclude from rich results — the intent of the rule is that the star rating reflects independent customer opinion, not marketing copy.
What Can Get a Site Penalized for Review Markup?
Marking up reviews that aren't genuinely present on the page, applying self-serving ratings, or aggregating reviews the site doesn't actually host — all of which violate structured data guidelines.
Manual actions for spammy structured data typically remove rich result eligibility sitewide, not just for the offending page, which makes this a high-stakes area to get precisely right rather than approximately right. If in doubt, it's safer to under-mark-up than to guess at a favorable interpretation of the rules.
How Do You Test That Your Markup Is Valid?
Run the page through a structured data testing tool before and after any template change, and check search console's enhancement reports periodically for new warnings or eligibility drops.
Validation checks syntax and required fields but not honesty — a technically valid AggregateRating can still be non-compliant if the numbers don't reflect a real, visible set of reviews. Both checks matter, and neither substitutes for the other.
Do Third-Party Review Widgets Handle Schema for You?
Many do, but the site owner is still responsible for verifying the output is valid, visible, and matches guideline requirements — outsourcing display doesn't outsource compliance.
When embedding reviews via review widgets for websites, check the rendered HTML rather than assuming the vendor's schema is correct — some widgets render ratings visually without emitting any structured data at all, which means no rich result regardless of how the page looks. Combining a compliant widget with review aggregation from multiple platforms also requires keeping the aggregate calculation itself transparent and accurate.
Summary
Review schema can earn valuable star-rating rich results, but only when the markup accurately reflects real, visible reviews on the page. Keep it in sync automatically, validate it regularly, and treat honesty as a stricter requirement than technical correctness.