What review markup is
Review markup is a way of describing a page’s review information in a structured, machine-readable form, so that search engines can understand it. A product page might have a rating average, a count of reviews and the text of individual reviews. Visitors can see those. The markup states the same facts in a standard vocabulary that software can read without guessing.
It belongs to the wider topic of structured data, which describes pages to machines using agreed formats. The markup is added to the page’s code, often by the store platform or a plugin, and is invisible to shoppers.
Search engines may use it to show ratings alongside a result. Whether they do so depends on their own policies and the quality of the page, and it can change. Marking up reviews makes a page eligible for such displays; it does not promise them, and it should never be the main reason for collecting reviews.
The core pieces
A typical product review setup involves three parts:
- The product being reviewed: its name and other basic details.
- An aggregate rating: the average score, the number of ratings and the scale (for example, out of five).
- Individual reviews: each with an author, a rating and the text, where displayed.
The exact property names are set out in publicly available vocabulary documentation, and platforms differ in how they generate them. As an auditor, you rarely need to write the markup by hand; you need to check that it is present, valid and truthful.
The honesty rules
This is the most important part. The general principle is simple: the markup must describe what real visitors can see on the page, and it must reflect real customer experiences. Common requirements and expectations include:
- Mark up only what is visible. If the page shows no reviews, the markup should not claim there are some.
- Use genuine reviews. Reviews should come from real customers. Writing your own, paying for favorable ones, or filtering out all the negative ones misleads shoppers, and in many places can break consumer protection law. If you are unsure of the rules where you operate, seek qualified advice.
- Review the right thing. A rating should relate to the item on that page. Applying one store-wide rating to every product page, or copying a rating from a different product, misrepresents the page.
- Do not review yourself. Self-serving ratings about your own business, placed on your own pages, are generally treated with suspicion by search engines.
- Keep numbers accurate. The average and the count should match what is shown. If the visible text says 4.2 from 18 reviews, the markup should not say 4.8 from 50.
- Stay current. When reviews are removed or updated, the markup should follow.
Search engines publish guidelines on structured data and may take action, such as ceasing to show the enhanced result, against pages that break them. Because policies change, review the current guidelines rather than relying on a summary like this one.
Where reviews come from
Honest collection matters as much as honest markup. Sensible practices include sending a review request after purchase to all customers (not only the happy ones), allowing both positive and critical feedback, and moderating only for abuse, spam or irrelevance, not for tone toward you. Replying politely to criticism can show future shoppers that the business is responsive.
Reviews imported from a third party service should be handled according to that service’s terms, and content that is loaded in a way search engines cannot see may be treated differently from content in the page itself.
Checking your markup
Audit steps, in a sensible order:
- Open a product page with reviews and note what a visitor sees: average, count, review text.
- Use a public structured data testing tool, of which several kinds exist, to see what the page’s markup says. Compare it field by field with the visible content.
- Check that products with no reviews do not display or declare a rating.
- Check that variants (sizes, colors) do not each claim their own copy of the same reviews inconsistently; this connects to product variants.
- Look for markup errors or warnings, and fix those that matter.
- Confirm the markup stays in sync after reviews are added or removed.
Remember that valid markup is not the same as eligible markup. A page can be technically correct and still not receive any enhanced display.
Beyond search
The best argument for collecting reviews is not the stars in results. Shoppers rely on other buyers’ experiences when deciding, and genuine reviews often contain details that product text lacks, such as how an item fits or lasts. Reviews also act as trust signals during the purchase, which ties in with checkout friction. For physical businesses with local audiences, the broader topic of customer reviews in local search has its own considerations.
Treat review markup as an accurate label on something real, not as a tactic. Results vary, and honest data is the only approach that holds up if guidelines or search engine behavior change.