SEO for Solos
schema.org/AggregateRatingRich result eligible

AggregateRating schema

A summary of many ratings, valid only where the underlying reviews are real and visible.

Where to use it

Only where real reviews exist and are visible.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

aggregate-rating.json
{
  "@context": "https://schema.org",
  "@type": "AggregateRating",
  "ratingValue": 4.8,
  "reviewCount": 42,
  "bestRating": 5,
  "worstRating": 1,
  "itemReviewed": {
    "@type": "Product",
    "name": "Acme Reference"
  }
}

Properties

AggregateRating properties
PropertyStatus
ratingValueRequired
reviewCountRequired
bestRatingRecommended
worstRatingRecommended
itemReviewedRecommended

The three mistakes this type attracts

  1. 01Inventing it. This is the most commonly penalised structured data on the web.
  2. 02reviewCount that does not match the number of visible reviews.
  3. 03Omitting bestRating when the scale is not out of 5.

Related types

Where this appears in the playbook

Questions

What is the AggregateRating schema type for?

A summary of many ratings, valid only where the underlying reviews are real and visible. Use it on: only where real reviews exist and are visible.

Which AggregateRating properties are required?

AggregateRating requires 2 properties: ratingValue, reviewCount. It also recommends 3: bestRating, worstRating, itemReviewed.

Does AggregateRating produce a rich result?

AggregateRating is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.

What is the most common AggregateRating mistake?

The most common AggregateRating mistake is: Inventing it. This is the most commonly penalised structured data on the web.