AggregateRating schema

What the type represents

A summary of genuine ratings associated with an item.

Use it when

The aggregate is calculated from visible or legitimately represented ratings
The rating scale and count are accurate

Properties to evaluate

ratingValue
ratingCount
reviewCount
bestRating
worstRating
itemReviewed

JSON-LD example

{
  "@context": "https://schema.org",
  "@type": "AggregateRating",
  "ratingValue": 4.6,
  "ratingCount": 125,
  "bestRating": 5,
  "worstRating": 1
}

Common mistakes

Selecting the type only because a search feature is desired.
Publishing facts that are not visible or supported by the site.
Creating conflicting copies of the same entity instead of using a stable @id.
Failing to update markup when the visible page or source data changes.

Official references

Schema.org defines the vocabulary. Search platforms publish separate documentation for the structured-data features they currently support.

Entity fit for AggregateRating

Use AggregateRating only when the page visibly represents the corresponding entity or relationship. Begin with the page purpose and the entity graph, then select the most specific supported type. Do not let the available vocabulary dictate claims the page does not make.

Visible support

Every material property should be supported by visible, current, and accurate page content.

Stable identity

Use consistent identifiers when the same organization, person, place, product, service, or webpage appears across the graph.

Consumer requirements

Treat Schema.org validity and search-consumer eligibility as related but separate checks.

Deployment record for AggregateRating

Syntax validation, type/property validation, consumer testing, and post-deployment inspection.
Record the page template, generator, source fields, responsible owner, and release reference.
Avoid publishing properties that are unsupported, hidden, stale, or inconsistent with visible content.
Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
Schedule review when visible content, offers, ownership, locations, products, or consumer documentation changes.

Next useful action

Turn aggregaterating into an accountable record.

A justified type-selection decision for AggregateRating with visible-content support and validation evidence.

Run a free website audit Read the schema guide

AggregateRating schema