XooCode(){

Rating

Rating is an Intangible for the numerical score given in ratings and reviews. It is the parent of AggregateRating (aggregated multiple ratings) and EndorsementRating (formal endorsement scores).

It adds 6 direct properties:

  • ratingValue (Number or Text): the score itself.
  • bestRating (Number or Text): the maximum of the scale (default 5).
  • worstRating (Number or Text): the minimum of the scale (default 1).
  • ratingExplanation (Text): free-text justification.
  • reviewAspect (StructuredValue or Text): which dimension the rating evaluates.
  • author (Organization or Person): the rater.

Full example of schema.org/Rating json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/Rating
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Rating",
  "ratingValue": 4,
  "bestRating": 5,
  "worstRating": 1,
  "author": { "@type": "Person", "name": "Jane Xoo" },
  "reviewAspect": "Value for money",
  "ratingExplanation": "Consistently good value; four stars rather than five reflects limited seating on busy nights."
}
</script>

When to use Rating vs Review

Use bare Rating inside reviewRating of a Review, or inside starRating of a LodgingBusiness. Use AggregateRating at the product/place level when you are summarising many ratings.

Minimal valid version

The smallest markup that still produces a valid Rating entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/Rating (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Rating",
  "ratingValue": 4,
  "bestRating": 5
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

  • Review / rating rich result (via containing entity)
    Google docs

Common Rating mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    ratingValue with scale implied

    Wrong
    "ratingValue": 4 with no bestRating
    Right
    Always populate bestRating (and ideally worstRating) so consumers know the scale

    A '4' on a 5-point scale is very different from a '4' on a 10-point scale. bestRating eliminates the ambiguity.

  2. 02

    Using Rating for a review text

    Wrong
    Rating with reviewBody-like text
    Right
    Review for the review text; Rating just for the numerical score

    Rating is the score; Review is the authored evaluation. Keep them separate.

Schema properties in this example

RatingIntangibleratingValuebestRatingworstRatingratingExplanationreviewAspectauthorPersonAggregateRatingEndorsementRating

Also mentioned in 16 other examples

Rating also appears in AssessAction, ClaimReview, CriticReview, DietarySupplement, EmployerReview, EndorsementRating, FoodEstablishment, Hotel, and 8 more. See the full Rating schema page for every reference.

About the example data

A 4-star rating by Jane Xoo for the Riverfront Food Hall, capturing the value-dimension only.

Comments

Loading comments...

Leave a comment