Review + AggregateRating schema — what it does & how to ship it
Review marks up an individual review; AggregateRating aggregates many reviews into an average score. Both drive the star rating displayed in the SERP — one of the highest-CTR SERP features available.
What it does
Review carries reviewRating, author, itemReviewed and datePublished. AggregateRating carries ratingValue, reviewCount and bestRating. Reviews must be on the reviewed item's page and must be genuine.
SERP / AI benefit
Star ratings in the SERP deliver a 20-35% CTR uplift on commerce and comparison queries. Answer engines cite Review pages when users ask 'is X worth it' style questions.
Where to use it
Testimonial pages, product pages, case studies, service pages.
JSON-LD example
{
"@context": "https://schema.org",
"@type": "Review",
"itemReviewed": { "@type": "SoftwareApplication", "name": "WBP Omni SEO Pro" },
"reviewRating": { "@type": "Rating", "ratingValue": "5", "bestRating": "5" },
"author": { "@type": "Person", "name": "Verified Customer" },
"datePublished": "2026-06-01"
}Copy, edit for your site, and drop into your page head inside a<script type="application/ld+json">block. Validate with Google's Rich Results Test.
In WBP Omni SEO Pro
Emitted on /pricing, /case-studies/*, service pages and every testimonial with genuine reviewer identity and date.
Ship Review + AggregateRating without touching codeFrequently asked
Review vs AggregateRating — which do I need?›
Both. Individual Reviews on the reviewed item page + AggregateRating summarising them.
Can I mark up third-party reviews I show on my site?›
Yes, but the reviews must be visibly rendered on your page and attributed correctly.
What kills Review rich results?›
Fake reviews, self-authored reviews of your own product, or AggregateRating without on-page reviews. Any of these can earn a manual action.
