Review Snippets: 2026 Guide to Star Ratings

Administrator in Search Engine Optimization Oct 18 / 7 hours ago

A review snippet is the short rating line that can appear under a search result, and the first mistake to avoid is marking up reviews that the visitor cannot see on the page. The second mistake is a business that marks up reviews about itself and then wonders why stars never show. This guide covers which pages qualify, which properties Google needs and how to test before you ship. The examples are fictional and come from Chicago, Hamburg and Seoul.

What is a review snippet and what does it look like in Google?

A review snippet is a short excerpt of a review or a rating that Google may show with a search result. It is usually an average of combined scores on a numeric scale such as 1 to 5. Google may display it as a rich snippet with stars, and it can also appear in Knowledge Panels.

Think of it as a small trust label. A shopper scanning results sees a score and a review count before opening anything. Google does not guarantee that it will show it, so the markup is an invitation and never a promise. Google can also rewrite the headline shown above your stars, as our post on Google title link rewrites explains. The official review snippet documentation lists every supported type.

Which types of pages can show star ratings?

Google supports review snippets for Book, Course list, Event, Local business (only for sites that capture reviews about other local businesses), Movie, Product, Recipe and Software App pages. Google also supports other schema.org types such as Episode, Game and MusicRecording, and it supports Organization too, but Organization only for sites that capture reviews about other organizations. Employer reviews use a separate type called EmployerAggregateRating.

Our take: collect fewer, genuine reviews with a visible author and real text instead of chasing a high count. A page with 20 honest reviews that a visitor can read is stronger than a big number nobody can verify. For stores, pair this with the price and stock details in our Product schema guide. Recipe publishers should read the food blog SEO guide, and organizers can use the event listings guide.

Should you use a single Review or AggregateRating?

Google describes four patterns: a simple review, a nested review, an aggregate rating and a nested aggregate rating. Use Review for one opinion and AggregateRating for the average of many. A nested version sits inside the item it describes, such as a Product or Book, so you can leave out itemReviewed.

Picture a fictional bookshop in Chicago, Illinois. Its page for one novel shows twelve reader reviews with names and text. The owner adds AggregateRating with the average and the count, and nests it inside the Book. When a page holds several individual reviews, Google asks you to include an aggregate too. You must supply the average yourself, so calculate it from the reviews on the page. The basics of the format are in our JSON-LD schema markup guide.

Which properties does Google require for review markup?

A Review needs an author, a reviewRating and an itemReviewed unless it is nested. An AggregateRating needs a ratingValue, a ratingCount or reviewCount, and an itemReviewed unless nested. The item also needs a name. Dates and scale limits are recommended, and they remove guesswork for Google.

Here is a compact view of the properties you will use most often.

The status column is copied from the Google review snippet documentation. The author name must be valid and shorter than 100 characters. The ratingValue can be a number or a fraction, and the default scale runs from 1 to 5. If your scale differs, set bestRating and worstRating. Google gives an example with a ratingValue of 88, a bestRating of 100 and a ratingCount of 20. Use a dot for decimals, so write 4.4 and avoid the comma version.

Which reviews are allowed on a marked-up page?

The reviews must be readily available to users on the page you mark up, and the rating must refer to one specific item. A category or a list does not qualify. Google recommends accepting only ratings that come with a review comment and an author name. Never combine reviews collected from other websites.

Visibility is the rule that trips up most teams. If the stars live in markup but visitors see no reviews, you have built the first mistake from our opening. Healthy review text usually comes from real customers, which ties into our user-generated content strategy. Named reviewers also support trust, as we explain in the E-E-A-T and helpful content guide.

Why are self-serving reviews a problem for local businesses?

A self-serving review is a review about a business that sits on that business's own website. If the reviewed entity controls the reviews about itself, its LocalBusiness or Organization pages are not eligible for the star review feature. That covers ratings pulled in through an embedded third-party widget.

This surprises many owners. A plumber who pastes a Google Business or Facebook reviews widget onto the home page has created self-serving markup. Ratings must come directly from users, and Google also says not to rely on human editors to create, curate or compile ratings for local businesses. Our take: a local business is better off leaving star markup off its own pages and investing in its profile. Start with the Google Business Profile guide, and if the listing itself is in trouble, read the suspended profile guide.

How do you add review markup to a page step by step?

Add the required properties, follow the guidelines, then validate the page with the Rich Results Test. Deploy a few pages first and check them with URL Inspection. The page must not be blocked by robots.txt, noindex or a login. Allow time for a recrawl, and submit a sitemap to help Google find the update.

Here is a fictional case in Hamburg. A small tea shop sells loose blends and shows real customer reviews under each product. The developer adds the markup to three product pages, tests them and only then rolls the pattern out to the full catalog. A short checklist keeps the rollout honest.

• Show every reviewed rating and its text on the page itself.
• Name one specific item in itemReviewed or nest the markup inside it.
• Supply the average and the count for AggregateRating.
• Run the Rich Results Test before you deploy.
• Check that robots.txt, noindex and logins do not block the page.
• Submit an updated sitemap after the rollout.

How do you test review markup with the Rich Results Test and Search Console?

Paste the URL or code into the Rich Results Test to catch syntax problems. After launch, use URL Inspection in Search Console to see how Google read the page. Then watch the rich result status report and the Performance report to monitor changes over time.

The Rich Results Test checks syntax. It cannot spot guideline problems such as spammy content or spammy markup, so a clean result is not a green light. The rich result status report in Search Console shows valid and invalid items and flags new errors as they appear. If you are new to the tool, our Search Console guide walks through the reports. When errors pile up, the structured data debugging guide helps you sort them.

Why are my star ratings not showing in Google?

Google does not guarantee that review snippets appear, even when the markup is valid. Possible causes include invisible reviews, an ineligible page type, a self-serving local business setup and a page that is blocked or not yet recrawled. Check each cause in order before you change the markup.

Start with the page itself. Open it as a visitor and confirm that the reviews and ratings are visible without logging in. Next, confirm that the type is on the supported list and that the markup refers to one specific item. A local business page with its own reviews is a likely culprit. Finally, remember that a structured data manual action means Google ignores the markup, although the page itself can still appear.

What counts as fake or incentivized reviews?

Google does not allow fake reviews or undisclosed incentives. A review must be based on a genuine experience. Reviews written in exchange for money, discounts, vouchers or free products need a clear and prominent disclosure, and skipping incentives entirely is the safest choice. Breaking these rules may lead to a manual action, and Google then ignores the markup.

Read Google's general structured data guidelines before you run any review campaign. Links inside reviews are a separate issue, and the nofollow, sponsored and UGC guide explains how to label them. If a violation leads to a penalty, fix the markup first and then submit a reconsideration request. Our manual actions recovery guide covers that process.

How should a Korean site handle review snippets outside Google?

A site in Seoul, South Korea should still add valid review markup, but it should not treat Google as the only audience. Korean searchers often use Naver, which has its own habits and tools. Build the markup once, then plan separate work for Naver visibility and Korean-language review text.

Take a fictional skincare shop in Seoul, South Korea. It collects Korean reviews with names and text, and it marks them up for Google. The team then reads the Naver SEO guide for Korea to decide what else matters on that engine. We do not claim that Naver reads Google markup in the same way, so test where your visitors search.

How do you keep review markup healthy over time?

Treat review markup as a living feature. Keep the count and the average in step with the visible reviews, remove markup from pages that lose their reviews, and recheck after template changes. Watch the rich result status report so you see problems before visitors do.

Review counts drift. A developer updates a template, the visible reviews vanish and the markup stays behind. That is the first mistake from our opening, arriving by accident. Schedule a monthly check of a few key pages in the Rich Results Test and the Search Console reports. Keep the process boring and repeatable, because a calm routine stops both mistakes from our opening. Show every review you mark up, and do not expect stars from reviews that your own business controls about itself.

Frequently asked questions about review snippets

Do star ratings improve my rankings?

Google's documentation does not say that stars change where a page ranks. A review snippet changes how your result looks, and that is the benefit to plan around. Treat the stars as a presentation feature, not a ranking lever. Focus on honest reviews, accurate markup and a page that answers the search. Those habits help visitors whether or not Google shows the stars on a given day.

Can I show reviews copied from another website?

No. Google says not to aggregate reviews from other websites. The reviews on your page should come from your own visitors and customers, and visitors must be able to see them. If you sell on a marketplace, keep those ratings on that platform. You can still link to the marketplace listing, but do not copy its average into your own AggregateRating markup.

Which rating scale should I use?

The default scale runs from 1 to 5, and Google assumes it when you give no limits. If your site uses another scale, such as 100 points, set bestRating and worstRating so the ratingValue makes sense. Use a dot for decimals, for example 4.4, and avoid commas. Keep the scale the same across the whole site so scores stay comparable from page to page.

Can I mark up a category or list page?

Google wants a rating to refer to one specific item, not a category or a list. A page that shows twenty running shoes should not carry one combined score for the whole group. Put review markup on each product page instead. If a collection page needs a trust signal, show real reviews on the products themselves and let the product pages earn the review snippet.

Do I need both Review and AggregateRating on one page?

When a page shows several individual reviews, Google asks you to include an aggregate rating as well. The AggregateRating carries the average and the count, while each Review carries one author and one score. If the page has only one review, a single Review is enough. Make sure the numbers match what visitors can see on the page, and update the average and the count whenever a new review arrives.

What happens if I break the review guidelines?

Breaking the guidelines can lead to a manual action. With a structured data manual action, Google ignores the markup, although the page can still appear in results. After you fix the problem, submit the site for reconsideration. Check the Manual Actions report in Search Console first, and fix every affected page before you ask. Describe the fix clearly in your request.

Should I accept ratings without a written comment?

Google recommends accepting only ratings that come with a review comment and an author name. A bare score gives visitors little supporting detail to trust, so the written comment is what makes a rating believable. Ask buyers for a short comment and a display name when they rate. You will collect fewer ratings, but the ones you keep are easier to defend and far more useful on the page.

Can a reviews widget from my Business Profile earn stars on my site?

For a local business, no. A rating about your business on your own site is self-serving, and that includes reviews shown through an embedded Google Business or Facebook widget. Those LocalBusiness and Organization pages are not eligible for the star review feature. The widget can still help visitors decide, so keep it for trust, and skip the markup for it.