Review schema is Schema.org structured data that gives Google your rating value, review count and review authors, so a page can qualify for a star rating in search. In 2026 Google supports it on 8 content types, including Product, Recipe and Local business, and rules out any page where the business controls the reviews about itself. It is not a ranking factor: the gain is a more visible result at the position you already hold.
In This Article
You search for “best noise cancelling headphones” and 1 result shows 4.5 stars from 347 reviews. The next shows nothing. Those stars come from review schema, and in 2026 Google is much pickier about which pages get them.
This guide covers what still works in September 2026: the content types Google shows stars for, the restriction that rules out most business websites, a JSON-LD block you can copy, and what Google has just retired. Every rule was checked against Google’s own documentation.
It’s Schema.org markup that hands search engines your rating data in machine readable form: the score, the scale, the number of reviews and who wrote them. Google reads it to decide whether a page qualifies for a review snippet, the star line under your result.

Schema.org defines a Review as “A review of an item”, and AggregateRating as “The average rating based on multiple ratings or reviews” (vocabulary version 30.1, 16 September 2026). What Google will use is set out in its review snippet documentation, last updated 8 September 2026.
A Review is 1 person’s verdict, carrying an author, a reviewRating and usually a reviewBody. An AggregateRating is the average, so it needs a ratingValue plus a ratingCount or a reviewCount. Most teams start with aggregate rating schema: less code, and it produces the star line shoppers recognise.
Google recommends JSON-LD “if your site’s setup allows it”. Here is a valid, minimal block for a product page with 347 reviews averaging 4.5.
<script type="application/ld+json">{ "@context": "https://schema.org", "@type": "Product", "name": "Noise Cancelling Headphones X200", "aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.5", "reviewCount": "347", "bestRating": "5", "worstRating": "1" }}</script>
The rating is nested inside the Product, so the product name covers the itemReviewed requirement. Add bestRating and worstRating whenever your scale is not 1 to 5. The 4.5 and the 347 must match what a visitor sees on the page.
Google names 8 content types that can show stars: Book, Course list, Event, Local business, Movie, Product, Recipe and Software app. Reviews are also supported on Organization, Game, Episode, MediaObject, CreativeWorkSeries and the music types. A blog post or a Service page is not on the list.

Eligibility is only half the test. The rest is conduct: whose ratings these are, where they came from, and whether a visitor can see them.
| Use case | Stars? | What Google says |
|---|---|---|
| Product page with its own customer reviews | Eligible | Product is a supported type and the reviews are on the page |
| Recipe, movie, book, event, course list or software app page | Eligible | All 6 are named content types for review snippets |
| Site that rates other local businesses | Eligible | Supported “only for sites that capture reviews about other local businesses” |
| Your own business page rating itself | Not eligible | An entity that “controls the reviews about itself” is ineligible on LocalBusiness or Organization pages |
| Ratings pulled in from Google, Yelp or Trustpilot | Not eligible | “Don’t aggregate reviews or ratings from other websites” |
| Ratings that exist only in the code | Not eligible | “Don’t mark up content that is not visible to readers of the page” |
| Reviews bought with a discount or gift, undisclosed | Not eligible | 24 July 2026 guideline bans “fake or undisclosed incentivized reviews” |
| FAQ blocks marked up for a rich result | No longer shown | FAQ rich results ended on 7 May 2026 |
This is the rule that catches most service businesses. Google’s guideline: “If the entity that’s being reviewed controls the reviews about itself, their pages that use LocalBusiness or any other type of Organization structured data are ineligible for star review feature.” Your testimonials page cannot earn stars. A site that collects reviews about other local businesses still can. Ratings must also come “directly from users”, not from your editors.
This markup is not a ranking factor. It is an eligibility ticket for a richer result, and the return shows up as click through rate. Google is blunt about the ceiling: it “does not guarantee that your structured data will show up in search results, even if your page is marked up correctly”.

Google’s introduction to structured data carries named case studies. Nestlé reported “an 82% higher click through rate than non-rich result pages”. Rotten Tomatoes “added structured data to 100,000 unique pages and measured a 25% higher click-through rate”. Food Network converted 80% of its pages and “has seen a 35% increase in visits”.
Read those as ceilings, not forecasts. None of the 3 isolates review markup. The honest promise is a better looking result at the position you already hold, which is the practical case for schema markup in SEO. A manual action for bad structured data, Google notes, “doesn’t affect how the page ranks”, so you lose the snippet, not your rankings.
FAQ rich results are gone. Google’s changelog says the feature “will no longer appear in Google Search starting May 7, 2026”, and the documentation was removed on 15 June 2026. Star ratings survived that cull, with tighter rules attached.
The pattern is consistent: Google keeps markup that helps users compare real things and drops what publishers used to decorate ordinary pages. Our technical SEO checklist tracks which features are live, and our guide to schema markup and structured data in 2026 covers the types worth your time.
Collect real reviews, publish them on the page, mark up exactly what is published, then validate. The order matters: Google checks the page before it trusts the code.

Capture a rating, a comment and an author name from genuine customers, then render those reviews on the page. Google asks that review content be “readily available to users from the marked-up page”.
Pick the parent type first: Product, Recipe, Event, Book, Movie, Course list or Software app. Build the block with our Reviews and Rating Schema Generator, then paste it before the closing head tag or let Rank Math, Yoast or a Shopify app output it.
Clear every error in Google’s Rich Results Test before you ship, and check your templates with our schema markup generator and validator. Then track impressions and click through rate in Search Console. Google re-crawls on its own schedule, so allow a few weeks before judging.
Almost every failed implementation we audit breaks 1 of these 4 rules, and 3 are about honesty rather than code.
A 4.5 rating in the code with no reviews in the HTML is the most common rejection. Google’s structured data policies say it plainly: “Don’t mark up content that is not visible to readers of the page.”
Testimonials you wrote, curated or paid for do not qualify. Between the self serving restriction and the incentivized review guideline, a business rating itself has no route to stars.
An 8.5 with no bestRating leaves Google assuming a 5 point scale. If you rate out of 10, say so. Both scale properties are recommended, not required, which is why this passes validation and still looks wrong.
Copying 1 aggregate rating onto every product or location page is inaccurate and easy to spot. Each URL needs its own rating value and count.
Review schema is Schema.org structured data that gives search engines your rating value, your review count and the author of each review. Google uses it to decide whether a page can show a star rating in search. It is not a ranking factor, so the gain is a more visible result at the position you already hold.
Google names 8: Book, Course list, Event, Local business, Movie, Product, Recipe and Software app. Ratings are also supported on Organization, Game, Episode, MediaObject and music types. Local business support is limited to sites that capture reviews about other local businesses. A blog post or a Service page will not show stars, whatever markup you add.
Not for stars. Google’s guideline says that if the entity being reviewed controls the reviews about itself, pages using LocalBusiness or any other Organization type are ineligible for the star review feature. Ratings must come directly from users, and editors cannot compile them. Publish testimonials for visitors, but expect no stars.
Publish the reviews on the page first. Then generate JSON-LD with a tool such as upGrowth’s Reviews and Rating Schema Generator and output it through Rank Math, Yoast or a Shopify review app, or paste it before the closing head tag. Use 1 block per URL with that page’s own numbers, then validate it.
Run the live URL through Google’s Rich Results Test. It reports errors, warnings and whether a review snippet is detected. Then track impressions and click through rate in Search Console. Google re-crawls on its own schedule, so allow a few weeks before deciding it has not worked.
No. Google’s documentation changelog states the FAQ rich result would no longer appear in Google Search starting 7 May 2026, and the supporting documentation was removed on 15 June 2026. FAQ and HowTo are no longer listed in Google’s search gallery. FAQPage markup can still describe your content, but it produces no rich result.
Stars pay off only when the reviews behind them are real, visible and on a page type Google still supports. Check those 3 things before you touch the code.
Build your block with the Reviews and Rating Schema Generator and test it. If you want the markup working for AI answers too, read our breakdown of schema patterns that earn AI citations.
Not sure why your stars vanished? Book a strategy call with upGrowth and bring the URL.
In This Article