Review Schema Markup: How to Show Star Ratings in Search Results
Review schema is structured data markup that enables star ratings, review counts, and reviewer information to appear directly in Google search results. These star ratings — visible as yellow stars next to your listing title — consistently increase click-through rates and are one of the most visually compelling rich results available to content publishers and e-commerce sites.
Implementing review schema correctly requires understanding both the technical markup format and Google's eligibility policies — which have specific rules about which types of review markup qualify for rich results.
⠀
What Is Review Schema and What Does It Unlock?
⠀
Review schema uses Schema.org vocabulary to provide machine-readable review and rating information. When correctly implemented and eligible, Google displays this information as "rich results" — specifically, star ratings shown beneath your title in organic search listings.
The visual impact:
A typical organic search result shows your title, URL, and meta description. With star rating rich results, you also show:
Yellow star rating (1-5 stars)
Numerical rating value (e.g., 4.8)
Number of ratings/reviews (e.g., "1,247 ratings")
⠀
Studies consistently show star rating rich results improve CTR by 15-30% compared to identical listings without stars. The visual differentiation makes your listing stand out in competitive SERPs.
Schema types for reviews:
Two primary schema types handle review data:
`Review` — A single individual review from one person
`AggregateRating` — An average rating calculated from multiple reviews
⠀
For rich results, Google primarily uses AggregateRating with a meaningful review count.
⠀
Google's Review Schema Eligibility Rules
⠀
Google has strict policies about which pages can display star rating rich results. Understanding these rules prevents wasted implementation effort and potential manual actions.
Eligible content types:
Products (e-commerce product pages with customer reviews)
Books
Courses
Local businesses (when reviews are from your own users/customers)
Movies and TV shows
Music albums
Recipes
Software Apps
⠀
Not eligible for review rich results:
Businesses or organizations themselves (you cannot add star ratings for your company's homepage, "About us" page, or contact page)
People (individual persons)
General information pages that aggregate reviews from third-party platforms
⠀
The most commonly misused application is adding aggregate ratings to a company homepage or a service page. Google explicitly prohibits this and may apply a manual action if discovered.
⠀
Implementing AggregateRating Schema
⠀
⠀
⠀
AggregateRating is the most common review schema type for rich results. It represents an average score derived from multiple reviews.
Required properties:
ratingValue — The average rating (number)
reviewCount or ratingCount — Number of reviews or ratings
⠀
Recommended properties:
bestRating — The highest possible rating (defaults to 5 if omitted)
worstRating — The lowest possible rating (defaults to 1 if omitted)
⠀
Full AggregateRating example for a product page:
{ "@context": "https://schema.org", "@type": "Product", "name": "Blue Leather Laptop Bag", "image": "https://example.com/images/laptop-bag.jpg", "description": "Premium leather laptop bag for 15-inch laptops", "brand": { "@type": "Brand", "name": "BrandName" }, "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.7", "reviewCount": "248", "bestRating": "5", "worstRating": "1" } }
⠀
Where to place it:
Place the JSON-LD in the <head> or <body> of the page. The schema must be on the same page as the visible review content — you cannot add rating schema to a page that doesn't visibly show reviews or ratings.
⠀
Implementing Individual Review Schema
⠀
For pages displaying individual customer reviews, the Review type captures individual reviewer information and ratings.
Review schema example:
{ "@context": "https://schema.org", "@type": "Review", "itemReviewed": { "@type": "Product", "name": "Blue Leather Laptop Bag" }, "reviewRating": { "@type": "Rating", "ratingValue": "5", "bestRating": "5" }, "name": "Excellent quality and craftsmanship", "author": { "@type": "Person", "name": "Customer Name" }, "datePublished": "2026-03-15", "reviewBody": "Bought this for daily commuting and couldn't be happier with the quality of the leather and the number of compartments." }
⠀
Combining Review with AggregateRating:
Most e-commerce product pages display both an aggregate rating and individual reviews. Combine both schema types in the same Product schema:
{ "@type": "Product", "name": "Product Name", "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.7", "reviewCount": "248" }, "review": [ { "@type": "Review", "reviewRating": {"@type": "Rating", "ratingValue": "5"}, "author": {"@type": "Person", "name": "Customer Name"}, "reviewBody": "Review text here." } ] }
⠀
⠀
Review Schema for Different Page Types
⠀
⠀
⠀
E-commerce product pages:
This is the primary use case. Every product page with customer reviews should have AggregateRating schema reflecting the actual displayed reviews.
Recipe pages:
Recipe schema supports AggregateRating. Include ratings from users who have made and rated the recipe.
Software/App review pages:
SoftwareApplication schema supports AggregateRating. Use for app landing pages where user ratings are displayed.
Book review pages:
Book schema supports AggregateRating. Add to book detail pages.
Local business on your own site:
You can add LocalBusiness schema with an AggregateRating IF the reviews displayed on the page are from your own customers writing on your own site — not pulled from Google or Yelp. Third-party aggregation into your schema without proper attribution violates Google's policies.
⠀
Common Review Schema Mistakes to Avoid
⠀
Displaying hidden reviews:
The reviews and ratings in your schema must be visible on the page. If you display 10 reviews visually but schema claims 500, Google considers this deceptive.
Self-reviews:
Do not mark up reviews written by the business about itself, or by employees without disclosure. Google's policies require reviews to be from independent third parties.
Fake or incentivized reviews:
Adding schema to artificially inflated ratings (from fake reviews or incentivized reviewers who weren't disclosed) can result in manual action and loss of rich result eligibility.
Applying star ratings to ineligible pages:
Company pages, service description pages, and "About us" pages are not eligible. Adding AggregateRating to these pages is a policy violation.
Blakfy implements review schema as part of technical SEO audits for e-commerce clients, ensuring correct implementation and compliance with Google's review schema policies.
⠀
Frequently Asked Questions
⠀
Can I use star ratings from Google Reviews or Yelp in my schema?
No. You cannot pull star ratings from Google Business Profile, Yelp, TripAdvisor, or other third-party platforms and add them to your website schema as if they were your own site's ratings. Each platform's reviews must stay attributed to that platform. Google's review rich results only apply to reviews that are natively displayed on your own website.
Why am I not getting star ratings in search results even though my schema is valid?
Valid schema is necessary but not sufficient for rich results. Google uses additional quality signals to determine eligibility: your domain needs to have a solid reputation, the reviews must be genuine and from real users, the rating count must be significant (single-digit review counts rarely qualify), and the page must demonstrate that reviews are genuinely user-generated rather than self-created. Check the Rich Results Test for detected schema and monitor GSC Enhancements for any warnings.
Does review schema affect my search rankings?
Not directly. Review schema doesn't add ranking points. However, the star ratings displayed as rich results significantly improve CTR — more clicks mean more engaged traffic, which can indirectly support ranking signals over time. The primary value is the visual prominence in search results that drives higher click-through from your existing position.
