AEO · Answer Engine Optimisationintermediate3 min read

What is Review Schema?

Review schema is structured data markup that enables star ratings, review counts, and reviewer information to appear directly in Google search results. Implemented via JSON-LD using the Review or AggregateRating types, it turns your SERP listing into a visually prominent result with star ratings — one of the most effective CTR improvements available. It applies to products, services, recipes, apps, books, local businesses, and more.

15–30%

higher CTR for listings with star rating rich results vs standard listings

Source: Moz / Search Engine Land studies

Fact-checked against 3 sourcesLast updated 8 June 2026

Key Takeaways

AggregateRating (average across multiple reviews) is more valuable than a single Review — Google prefers aggregate ratings in rich results.
Review schema requires genuine reviews on your site — not a rating you've given yourself or pulled without user input.
Google has strict policies against fake reviews and self-serving ratings — markup violations can result in manual actions.
For local businesses, star ratings come from Google Business Profile, not site markup — review schema applies to product/content pages.
Review rich results are one of the fastest CTR wins for e-commerce — implement on every product page with reviews.

In this article

01Review Schema vs AggregateRating
02Implementing Review Schema Correctly

Review Schema vs AggregateRating

Review schema marks up a single review: the reviewer's name, the content of the review, the rating (1–5), and the date.

AggregateRating marks up an average rating across many reviews: the average rating value, the best/worst possible rating, and the total number of ratings.

For SERP rich results, AggregateRating is what generates the star display. A single review with no aggregate doesn't typically trigger star ratings in SERPs.

Both types can coexist: a product page might have an AggregateRating block (showing the overall 4.2/5 from 847 reviews) and multiple individual Review blocks (for the review content displayed on the page).

Implementing Review Schema Correctly

Apply schema to the right content types: Google supports review rich results for Books, Courses, Events, How-tos, Local Businesses, Movies, Products, Recipes, Software Apps.

Critical policy rules: only show ratings from genuine users. Don't self-review. Don't embed hidden ratings. Don't show aggregate ratings without individual reviews available on the page. Don't use review schema for editorial content (your own opinions about something).

For e-commerce: every product page with a reviews section should have both AggregateRating (the overall star average) and individual Review blocks. Generate this dynamically from your reviews database.

Validate with Google's Rich Results Test and monitor the Enhancements section in Search Console for any violations.

Stay sharp

Most guides are already outdated.

One email a week. The search stuff that actually matters — what shifted, what died, and what to do about it.

Subscribe free →

15–30%

Average CTR increase from star ratings in SERPs

847B+

Structured data entities indexed by Google

Content types eligible for Review rich results

1–5

Rating scale required by Google's schema spec

✓ DO

✓

Use AggregateRating with ratingValue, bestRating, worstRating, and reviewCount properties

✓

Generate Review and AggregateRating markup dynamically from your live reviews database

✓

Ensure individual review content is visible on the same page as your AggregateRating markup

✓

Validate implementation with Google's Rich Results Test before deploying

✓

Apply review schema only to supported types: Products, Recipes, Local Businesses, Software Apps, Books, Movies, Courses, Events, How-tos

✗ DON'T

✗

Don't mark up self-written reviews or editorial opinions as user reviews

✗

Don't embed hidden or invisible review data in schema that isn't shown to users

✗

Don't display an AggregateRating if no individual reviews are accessible on the page

✗

Don't apply review schema to employment, financial, or legal service pages — Google explicitly excludes these

✗

Don't hardcode a static rating that doesn't update as new reviews are submitted

REVIEW VS AGGREGATERATING: WHEN TO USE EACH

Review (Single)	AggregateRating (Aggregate)
Marks up one individual review	Marks up the averaged result of many reviews
Requires: author, reviewRating, datePublished	Requires: ratingValue, reviewCount, bestRating
Does NOT trigger star ratings in SERPs alone	Triggers visible star ratings in Google SERPs
Useful for structured review content on-page	Essential for rich result eligibility
Can reference a single reviewBody text	References a numerical aggregate only
Can coexist with AggregateRating on same page	Should always be paired with visible reviews on-page

REVIEW SCHEMA PRE-LAUNCH CHECKLIST

0/8 complete

Confirm the content type is on Google's supported list (Product, Recipe, Book, App, etc.)

Include ratingValue, bestRating, worstRating, and reviewCount in every AggregateRating block

Ensure every Review block contains author (name), reviewRating, and datePublished

Verify that all schema data matches the visible content displayed to users on the page

Individual review text or summaries must be readable on the page — not schema-only

Run the URL through Google's Rich Results Test and resolve all errors

Monitor the 'Review Snippets' report in Google Search Console Enhancements tab post-launch

Set up dynamic schema generation so ratings update automatically as new reviews come in

REAL-WORLD EXAMPLE

E-Commerce Product Page: Combined Review + AggregateRating JSON-LD

A running shoe product page implements two schema blocks. The AggregateRating block specifies: ratingValue: 4.6, bestRating: 5, worstRating: 1, reviewCount: 1243 — this is what triggers the gold stars in the SERP listing. Below it, three individual Review blocks each contain the reviewer's name, a datePublished, and a reviewRating of 5, 4, and 5 respectively, matching the visible reviews on the page. Result: Google displays '★★★★½ 4.6 · 1,243 reviews' directly in the search result, increasing CTR by an estimated 20% compared to the non-schema listing. The key compliance factor: all 1,243 reviews are accessible via pagination on the product page itself — not hidden or schema-only.

⚠️

Google Manual Action: Misuse of Review Schema

Google issues manual penalties for review schema abuse. Specific violations that trigger enforcement include: marking up aggregate ratings on pages with no visible reviews, using schema for self-promotional editorial content disguised as user reviews, and inflating review counts or scores beyond what real users submitted. Penalties result in rich result eligibility being revoked for the affected pages. Check the 'Manual Actions' report in Google Search Console if your star ratings suddenly disappear from SERPs.

Free Tool

How does your site score on AEO?

Paste your URL. Get a score and a fix list across all three disciplines. No form, no email.

Run Free Audit →

Frequently Asked Questions

Technically possible but against Google's intent for rich results. Google's review schema is designed for page-specific reviews of the item on that page — not general business testimonials. Testimonials on a homepage also violate the 'reviews for the item on the page' requirement. Using review schema on testimonials may trigger a manual action for misleading structured data.

Common causes: Google updated its eligibility criteria for your content type, your schema contains errors (check Search Console → Enhancements), you have too few reviews to display, or Google determined your ratings don't meet quality guidelines. Check the Search Console Enhancements report — it shows detected items and any errors. Also verify your schema is still valid using the Rich Results Test.

Sources & Further Reading

1.Google — Review snippet documentation
2.Schema.org — Review and AggregateRating types
3.Google Rich Results Test

What is Review Schema?

Review Schema vs AggregateRating

Implementing Review Schema Correctly

Most guides are already outdated.

How does your site score on AEO?

Frequently Asked Questions

Read next

Click-Through Rate (CTR)

Rich Results

Schema Markup

FAQPage Schema