How review schema works
Review markup is a small block of structured data, usually written in JSON-LD, that describes two things: a single review of something, and the combined score of many reviews. The combined score is the part most people mean when they say review schema. Each block must state what is being reviewed, who wrote the review, the score given and the scale it sits on, so a machine can read the rating without guessing at the stars on the page.
Reading it does not oblige a search engine to display it. Markup makes a page eligible for a star rating in the results; whether stars appear is decided separately, per query, and can change without anything on your side changing. It also only applies to certain kinds of subject — products, recipes, books, courses, software and a handful of others — rather than to any page you feel like adding it to. This is one corner of the wider practice of adding schema markup to a site.
Why review schema matters
Stars are the most noticeable thing a result can gain. They give a listing physical width in a page of plain blue links, and they carry a judgement rather than a description, which is why click-through tends to improve when they appear on the right kind of page.
The eligibility rules matter just as much as the benefit. Google does not allow a business to mark up reviews about itself, collected on its own site, and show stars for them — the self-serving case is excluded deliberately. Testimonials on your homepage are still worth publishing for the reader; they are simply not a route to stars.
Common mistakes with review schema
The most common is marking up ratings that a visitor cannot see. If the score is only in the code, the markup is misleading, and this is one of the few structured data problems that reliably attracts a manual action. The rule to hold on to is that the markup describes the page; it does not add to it.
Next is adding a sitewide rating in a template, so every page claims the same score for the whole business. Then there is inventing the numbers outright, which is both dishonest and easy to check. Finally, plugins that generate markup automatically often produce a rating on pages that were never eligible, and nobody notices until the enhancement report fills with warnings.
Getting it right
Start by asking what the review is actually about. If it is a product, the markup belongs on the product page with a visible rating drawn from real customer reviews. If it is your business as a whole, publish the testimonials for readers and expect no stars.
Then validate. The Rich Results Test tells you whether a page is eligible and what was parsed, and Search Console reports the same thing at scale once pages are live. Check after any theme or plugin change, since markup is generated by templates and breaks silently. Above all, keep the score in the markup identical to the score on the page — if the two ever disagree, fix the markup rather than the display.
