Review Schema Markup: What's Allowed and What Isn't

Review schema markup covers two distinct things: Review schema for an individual customer review, and AggregateRating schema for the overall summary — average score and total count. The rule most businesses unknowingly break: Google explicitly prohibits marking up third-party review data, like a Google Reviews widget or a Yelp feed, as if it were your own on-site AggregateRating. The reviews behind this schema have to be genuine, collected directly on your own website, not pulled in from somewhere else and re-presented as your own.

Review Schema vs. AggregateRating Schema

Review schema describes one individual review — the actual text, the author, the date, and that specific reviewer's rating. AggregateRating schema describes the summary across all your reviews — an average rating value and a total count. Both can appear together, nested within a description of your business, but they're answering different questions: one describes a single voice, the other describes the overall pattern.

The Rule Most Businesses Unknowingly Break

This is worth taking seriously, not as a minor technicality but as a genuine policy violation risk: Google requires that any reviews marked up with Review or AggregateRating schema be real customer reviews collected through your own website, representing actual customer experiences. Embedding a widget pulling in your Google or Yelp reviews, then adding schema on top of it as though those are first-party, on-site reviews, is explicitly against the rules — not a gray area. If your reviews genuinely live on Google and Yelp rather than your own site, the schema shouldn't claim otherwise.

The Exact-Match Requirement

Whatever your schema states — the rating value, the total review count — has to match exactly what's visibly displayed on that same page. If your page shows 4.8 stars from 127 reviews, the schema markup needs to state precisely that, not a rounded or approximate version. A mismatch between the visible page and the underlying schema is treated as a policy violation, regardless of whether it was intentional or just a sync error between systems.

What Actually Works

If you're collecting real reviews directly on your own website — through a dedicated review or testimonial system — Review and AggregateRating schema is genuinely worth implementing correctly. If your review activity mostly lives on Google and Yelp instead, the honest, compliant approach is to lean on LocalBusiness schema's connection to your Google Business Profile rather than attempting to claim those third-party reviews as your own first-party schema.

Where to Go From Here

This connects directly to the broader schema foundation covered in LocalBusiness Schema: Choosing the Right Subtype, and the review-building tactics covered in How to Get More Google Reviews.

Not sure whether your own site's review schema is set up correctly, or accidentally violating this rule? Get in touch and we'll check it.