Review stars disappeared from Google? Why review snippets vanish

In this guide, we at Talha Aslan and team focus on one question. Your stars were there last week, and now they are gone. What happened, and in what order should you check? We do not explain structured data from scratch here. For the basics, read our guide to schema markup and structured data. Instead, you get a checklist, a decision table, and numbered steps.

One thing up front: Google does not guarantee rich results, even for perfect markup. So the real goal is not to "get the stars back." The goal is to regain eligibility and give Google a clean page it can choose to enhance.

Are review stars the same as Google Business Profile reviews?

No. These are two separate systems, and mixing them up is the most common diagnostic mistake we see. Review stars appear on the organic result for a page on your own website. They come from structured data on that page. Business Profile reviews appear in Maps and the local panel. They come from customers who rate your business directly on Google.

For example, your Maps rating may still be visible while the stars under your product page are gone. In that case, the problem sits in your site markup, not in your Business Profile. On the other hand, if one customer review is missing on Maps, structured data has nothing to do with it. For that case, see our article on why a Google review is not showing.

In short, first name what actually disappeared. The rest of this guide covers only review stars on search results for pages on your own site.

Which content types are eligible for review stars?

Google Search Central's review snippet documentation lists the supported types. Therefore, your first check is simple: is the thing you marked up on that list?

• Book, course list, event, movie, product, recipe, and software app.
• Local business and organization, both with restrictions.
• Some additional schema.org types, such as games, episodes, creative work seasons and series, media objects, music recordings, and playlists.

However, many sites mark up a service page, a blog post, or an "about us" page as a product just to earn stars. If the page does not describe a supported item, eligibility is weak even when the markup validates. Moreover, markup that does not match the page topic conflicts with Google's structured data policies.

So if your stars vanished from a service page, ask a blunt question first. Does this page really describe a supported item type?

Why don't self-serving reviews earn review stars?

Google calls this the self-serving review restriction. According to the documentation, if an entity controls the reviews about itself, its pages that use local business or organization markup cannot get the star feature. In addition, reviews shown through third-party widgets embedded on your own site count toward this restriction.

So if your home page marks up "4.9 from 200 reviews" for your company, do not expect stars. It does not matter whether those reviews come from your own form or from an embedded widget. In our experience, this explains a large share of lost stars. Many sites added organization ratings years ago and never revisited the markup.

That said, the restriction applies only to businesses and organizations. For example, an online store that marks up customer reviews of a specific product on that product page is in a different situation. For details on rating formats, our AggregateRating guide covers the fields.

What should you do first when review stars disappear?

Do not panic, and do not delete your markup yet. First, document the situation. This order helps you understand later what actually worked.

1. List the pages that lost stars. Is it one page, the whole site, or one template?
2. Note the approximate date. Ask whether a theme, plugin, or template change happened around then.
3. Open the Manual Actions report in Search Console.
4. Check the related rich result report in the same property.
5. Run a sample page through the Rich Results Test and the URL Inspection tool.
6. Confirm that users can actually see the rating and the review text on the page.

These six steps separate technical problems from policy problems and from plain display choices by Google. Also, write a short note after each step. Otherwise, three days later, you will struggle to remember what you changed.

If running this diagnosis across many templates feels like too much, our seo consulting work covers the same checks at template level. If you prefer to handle it yourself, the next sections walk through each step.

What does the Manual Actions report tell you?

A manual action is a penalty a Google reviewer applies after finding a policy violation. Google's structured data policies page states that a structured data manual action makes a page lose eligibility for rich results. It also states that rankings are not affected.

Therefore, if traffic holds steady but stars vanished across the whole site at once, a manual action is a strong candidate. If the report shows an entry, read it closely. It usually names the issue type and gives sample URLs.

On the other hand, if the report shows no issues, do not treat the loss as a penalty. The cause is then more likely eligibility, a technical error, or an algorithmic display choice. In other words, the Manual Actions report is your first and clearest filter. If it is empty, move on.

If there is a manual action, you fix the issue and then request a review. Describe concretely what you changed. There is no fixed timeline and no guarantee that the request succeeds.

What does the rich result report in Search Console show?

According to Search Central, the rich result status report shows valid and invalid items on indexed pages. For review snippets, look for the related report in the enhancements area, or a similar section. Menu names change over time, so do not rely on exact button labels.

Look at three things in this report. First, check whether invalid items jumped on a specific date. Second, check the error types, such as a missing required field or an invalid value. Third, check whether valid items dropped suddenly.

For example, if valid items stay flat while stars disappear, Google still sees the markup as valid. The problem then lies in eligibility or display. In contrast, if invalid items rose on the same day as a theme update, something broke. Also keep in mind that the report takes time to reflect changes. So a flat chart right after a fix is normal.

If you see parsing errors across the site, our article on the unparsable structured data error handles that issue step by step.

How do you use the Rich Results Test and URL Inspection?

Google recommends two tools. The Rich Results Test validates markup and previews features. The URL Inspection tool shows how Google sees a live page. They answer different questions, so run both.

1. Enter the page URL in the Rich Results Test and check whether it detects a review snippet item.
2. Note errors and warnings separately. Errors block eligibility, while warnings usually do not.
3. Run a live test in URL Inspection and confirm that the rendered HTML contains the structured data.
4. If JavaScript adds your markup, make sure the data appears in the rendered version.

However, a "valid" result does not mean the stars will appear. Google's policy page says clearly that valid markup only makes a rich result possible. Display is never guaranteed. So if the test is clean but there are no stars, continue with the eligibility and visibility checks below.

If you need to rebuild the markup, our schema generator tool gives you a clean starting draft.

Do the rating and review text need to be visible on the page?

Yes. The Search Central documentation says users should be able to see the review text and the associated rating. If you use an aggregate rating, users must also see that aggregate on the page. The general policy page also asks you not to mark up content that is hidden from readers.

In practice, tabs, sliders, and widgets that load reviews in a separate frame break this rule most often. For example, reviews may load from an external source only after a click. In that case, the rating in your markup may not exist on the page in readable form. As a result, the markup and the visible content no longer match.

• Show the rating as plain text near the title.
• Make sure the review count in your markup matches the count on the page.
• Mark up all the reviews you display, since the policy asks you to represent every visible item.

That way, what Google reads and what users see are the same. That match is the foundation of eligibility.

Can you mark up ratings collected from other websites?

No. The review snippet documentation asks you not to aggregate reviews or ratings from other websites. Comparison sites and review aggregators break this rule often.

Example scenario: a product page averages ratings from several marketplaces and marks that number up as its own aggregate rating. Users did not leave those ratings on your site, so the markup does not reflect reality. This kind of setup can lead to lost stars or even a manual action.

Instead, mark up only reviews that real users left on your own site. Also, for local businesses and organizations, ratings must come directly from users, not from human editors. Fake reviews and undisclosed incentivized reviews must stay out completely. For better ways to collect reviews, see our article on how product reviews affect sales.

How do you read the review stars decision table?

The table below links the symptom you see to the most likely cause and the first action. Read it from top to bottom and stop at the first row that matches.

However, two causes can apply at the same time. For example, you may fall under the self-serving restriction and also have duplicated markup after a theme update. In that case, clean up the technical error first. Then make the eligibility decision.

How can a theme or plugin change break your markup?

In content management systems, structured data often comes from the theme, an SEO plugin, and a review plugin at the same time. As a result, one update can add two product items or two different rating blocks to the same page.

Example scenario: a theme update turns on its own product markup. Meanwhile, the SEO plugin already outputs product markup. Now the page carries two items with different rating values. Google cannot tell which one to trust. The item may become invalid or simply drop out of display.

• Count how many items of the same type appear in the page source.
• Check the review plugin's markup setting and keep only one source active.
• Make sure a caching plugin is not serving an outdated version.

In addition, if you add markup through Google Tag Manager, confirm that the tag fires correctly on every page. We cover that method in our article on adding schema with Google Tag Manager.

Do missing required fields remove review stars?

Yes, they can. Google's structured data policies ask you to include all required properties and, ideally, the recommended ones. A missing required field makes the item invalid and blocks eligibility directly.

For review snippets, the fields that most often go missing are these. The item being reviewed, the rating value, the review or rating count for aggregates, and the author for single reviews. According to the documentation, author names must be valid and stay under a character limit. Avoid generic labels like "Customer" or "Anonymous." Use a real name or a real nickname instead.

Also keep your rating scale consistent. For example, if the page shows a rating out of five but the markup says out of ten, what users see and what the markup says conflict. In short, reviewing the field list once per template is much faster than fixing pages one by one.

Why are review stars still missing when the markup is valid?

Because Google does not commit to showing rich results. The policy page says that even when markup passes the test, the algorithm may prefer a plain text result. So with everything correct, stars may show for some queries and not for others.

The policy also says outdated, time-sensitive content will not earn rich results. It asks for original content that stays relevant to the page focus. Therefore, expecting stars on old, thin, or low-value pages is not realistic.

What you can do here is strengthen the page itself. For example, adding real usage details, clear photos, and recent reviews to a product page matters more than editing the markup again. Also, do not judge from a single search on your own device. Results vary by person, device, and location. If you are tracking broader visibility changes, our article on diagnosing SERP losses in Search Console helps you read the data.

Should you remove your organization rating markup?

In most cases, yes, but the decision depends on your content. An organization rating that falls under the self-serving restriction will not earn stars. So keeping it in the markup brings no search benefit. Moreover, if the rating is hidden or collected from elsewhere, it adds policy risk.

That said, you do not need to delete the reviews from the page. Customer feedback is valuable for visitors and supports conversions. You simply stop marking it up as an organization rating to chase stars.

1. List the rating markup on organization and local business pages.
2. Keep the markup on supported types such as products, courses, or events.
3. Test the change on one template first, then roll it out.

This approach keeps the trust signal for visitors while removing markup that cannot help you in search. As a result, your structured data becomes simpler to maintain.

Do reviews loaded with JavaScript affect review stars?

They can, but JavaScript alone is not the blocker. Google can process content you render with JavaScript. The problem usually starts when the markup or the rating never appears in the rendered version at all. So do not trust the raw source alone. The real test is the rendered HTML in URL Inspection.

We see three problem patterns in the field. First, a review widget loads the rating only after the user scrolls. Second, the markup comes late from an external server and times out. Third, the widget injects its own markup that collides with yours.

• Run a live test in URL Inspection and search the rendered HTML for the rating value.
• Show the rating on first load, without waiting for user interaction.
• If the widget outputs markup, turn off either your markup or the widget's.

Also read the widget provider's documentation, since many providers let you switch markup on or off. In short, aim for one consistent rating block per page that Google can read.

What should you watch for on product pages?

Product pages are the most natural candidates for review stars. Products are a supported type, and product reviews do not fall under the self-serving restriction. Still, online stores lose stars often. The cause is usually a small inconsistency at template level.

Example scenario: a store prints an empty aggregate rating block on products that have no reviews yet. Google may find these items meaningless, which can weaken trust in the template overall. Similarly, on products with variants, every variant page may present all reviews of the parent product as its own.

1. Do not print a rating block on products with no reviews.
2. Match the review count in the aggregate with the reviews listed on the page.
3. On variant pages, make clear which product the rating belongs to.
4. Keep pages for discontinued or out-of-stock products up to date.

Moreover, product markup carries price and availability too, not only stars. So after any rating fix, confirm with the Rich Results Test that you did not break other fields.

Which mistakes should you avoid with review stars?

After losing stars, the biggest risk is making things worse while hunting for a quick fix. Therefore, rule out the following on purpose.

• Changing the content type so an unsupported page looks like a product.
• Writing a rating into the markup that the page does not show.
• Copying ratings from other platforms as if they were your own.
• Asking employees or friends for reviews, or hiding incentives.
• Changing the markup every day instead of waiting for results.

All of these conflict with Google's structured data and spam policies. A manual action can put much more than stars at risk, namely rich result eligibility across your site. Instead, choose a slow but clean path. Diagnose, change one template, measure, then roll out. That way you also prove what worked.

How do you track whether review stars come back?

After your fix, Google has to recrawl and reprocess the page. There is no official fixed timeline for this. So set up a weekly routine instead of checking every day.

• Check whether invalid items drop in the rich result report.
• If the report offers a validation option for a fixed issue, use it.
• Recheck a few important pages in URL Inspection.
• If the Performance report offers a search appearance filter, compare rich result impressions over time.

Tracking click-through rate also helps. When stars return, the same ranking may bring more clicks, although that is not guaranteed. Meanwhile, changing the markup again and again only muddies the diagnosis. In short, waiting between fix and result is unavoidable.

What belongs on a review stars checklist?

Apply this list once per template. That way, you fix the problem at its source instead of page by page.

1. Is the marked-up content a supported type?
2. Does the page mark up reviews about your own business or organization?
3. Can users clearly see the rating and review text?
4. Do the rating and review count in the markup match the page?
5. Are any ratings collected from other websites?
6. Are required fields complete and author names real?
7. Is there duplicated markup on the same page?
8. Is the Manual Actions report clean?
9. Do the Rich Results Test and URL Inspection agree?

If you can answer yes to all nine, you have done most of what you can on the technical and policy side. The rest is Google's display decision.

How do review stars fit with other search features?

Review stars are only one of many search appearance features. So instead of treating a loss as a disaster, look at the page's overall search appearance.

For example, the same page can appear in the related questions box with question-style headings and short, direct answers. We cover that separately in our guide on how to appear in People Also Ask. It offers a visibility path that does not depend on stars.

On the other hand, if you hoped FAQ markup would make up for lost stars, note that according to Search Central the FAQ rich result no longer shows in Google Search. Our article on removed FAQ rich results explains what that means. In short, the lasting fix is a genuinely useful page with accurate markup, not markup tricks.

When should you get help with missing review stars?

Suppose you ran the checklist, there is no manual action, and the test is valid. Yet you still cannot tell which template is affected across hundreds of pages, or why. At that point the problem is no longer a single page fix. It is site architecture, and the theme, plugins, and review setup need a joint review.

Also, decisions like removing organization ratings or switching review providers affect your other markup too. A careless bulk change can break rich results that have nothing to do with stars. Therefore, on large sites, test changes on a small group of pages first and measure the effect.

With our seo consulting services, we run this diagnosis at template level, document every change, and track its effect in Search Console. We do not promise the stars will return, because Google makes that call. However, we can make your eligibility clean and sustainable.

Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.