Does Google still show a rich result for this?

Supported, but with a restriction that disqualifies most business websites. Google states that where the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any Organization type are ineligible for the star feature. That covers both your own markup and embedded third-party review widgets.

When to use it

When you are reviewing something other than yourself — a product you sell but did not make, a book, a film. Not for testimonials about your own business.

Required properties

Review: author, itemReviewed, itemReviewed.name, reviewRating.ratingValue
AggregateRating: itemReviewed, itemReviewed.name, ratingValue, and at least one of ratingCount or reviewCount

Recommended properties

datePublished
reviewRating.bestRating
reviewRating.worstRating

Example

{
  "@context": "https://schema.org",
  "@type": "Review",
  "itemReviewed": { "@type": "Product", "name": "Example Wool Jumper" },
  "author": { "@type": "Person", "name": "Jane Smith" },
  "datePublished": "2026-07-28",
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": 4,
    "bestRating": 5,
    "worstRating": 1
  }
}

Common mistakes

Marking up testimonials on your own site to get stars. This is the self-serving case Google excludes.
Assuming an embedded review widget avoids the rule. Google names embedded third-party reviews explicitly.
Writing ratings yourself. Google states ratings must be sourced directly from users.
Applying it to a type Google does not support it on. The types confirmed are Book, Course, Event, LocalBusiness, Movie, Product, Recipe and SoftwareApplication.

Check what your own pages are missing

Our free checker reads the markup already on a page and names the types it is missing for its page type. No account needed.

Run the schema checker →

Verified against Google’s structured data documentation and its changelog on 28/07/2026. Google changes what it supports without much notice — if you are reading this long afterwards, check the current documentation before acting on it. Background on why this markup matters beyond rich results is in the answer engine optimisation guide.

Review and AggregateRating schema markup