Why Your Star Ratings Don't Show in Google Search

You paid someone to add review schema. The Rich Results Test says it's valid. Search Console shows zero errors. And there are still no stars next to your listing in Google — while the guy across town has a shiny 4.8 with 212 reviews under his name.

Nothing is broken. Google is doing exactly what it says it does. The stars are missing because of a policy, not a bug, and no amount of re-validating your JSON-LD will change it.

Why doesn't Google show your star ratings even though your markup validates?

Because valid is not the same as eligible. Google supplies review-snippet stars for eight content types — Book, Course list, Event, Local business, Movie, Product, Recipe, and Software App — and its review snippet documentation marks Local business as available 'only for sites that capture reviews about other local businesses.' Your site captures reviews about you. That's the whole problem.

The Rich Results Test only checks syntax. It answers 'is this parseable and complete?' — not 'will Google use it?' Google's structured data policies state it outright: 'Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test.'

So a green checkmark in the tester is not a promise. It's a spell-check. Plenty of agencies stop there, screenshot the green tick, and put it in the monthly report.

What is the self-serving review policy, and why does it kill your stars?

A self-serving review is a review about you, published on a site you control — and one sentence in Google's review snippet guidelines ends the argument: '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.'

Read the next line, because it closes the loophole everyone tries. Google's example of a self-serving review is 'a review about entity A placed on the website of entity A, either directly in their structured data or through an embedded third-party widget (for example, Google Business reviews or Facebook reviews widget).'

That means the plugin that pulls your Google reviews onto your homepage and marks them up does not get you around the rule. Same reviews, same entity, same ineligibility. The widget is a conversion asset. It is not a SERP asset.

Two more rules from the same page kill the usual workarounds: 'Don't aggregate reviews or ratings from other websites,' and 'Don't rely on human editors to create, curate, or compile ratings information for local businesses.' Scraping your Yelp average into your own schema is explicitly out.

Are LocalBusiness pages even eligible for review snippets?

Almost never, for the business itself. Google's LocalBusiness documentation lists both aggregateRating and review as recommended properties with a bolded qualifier: 'This property is only recommended for sites that capture reviews about other local businesses.'

Sites that capture reviews about other local businesses means Yelp, Angi, Trustpilot, a city guide, a directory. Not your plumbing company. The property exists in the spec for the platform, not the practice.

This is where the 'my SEO guy said' myth comes from. He wasn't lying — LocalBusiness really does support aggregateRating. He just never read the qualifier next to it.

Where do the stars next to your competitors actually come from?

Three sources, and none of them is schema on a competitor's own site. Here's what's really generating each set of stars you're jealous of:

Look closely at the SERP next time. The 4.8 next to a competitor's name is almost always their Business Profile in the local pack, or a Yelp/Angi page outranking them in organic. It is not their homepage schema.

Google Business Profile reviews surface next to the Business Profile itself — in Maps and in Search. Not next to your website. Next to your profile.

Should you remove your AggregateRating markup?

Yes — remove it from any LocalBusiness or Organization page describing your own company, and keep it only where you're marking up something that isn't the business itself. Use this as your decision table:

Removing it costs you nothing you currently have. It was producing zero stars. What it was producing was risk, plus a false sense that a box was ticked. Fold the cleanup into a technical SEO pass rather than treating it as its own project.

Keep the rest of your LocalBusiness object — name, address, geo, telephone, openingHoursSpecification, url. Those are the properties Google actually wants from you, and they still matter for how AI engines and Google parse your entity.

Can fake or self-collected review markup get you a manual action?

Self-serving markup that reflects real, visible reviews is normally ignored rather than punished — but invented ratings are a different category, and the penalty is concrete. Google's structured data policies ban marking up 'irrelevant or misleading content, such as fake reviews,' and state that a structured data issue 'can result in a manual action,' meaning 'a page loses eligibility for appearance as a rich result.'

There is a second, quieter trap: marking up content that isn't on the page. Google's rule is 'don't mark up content that is not visible to readers of the page.' If your schema claims 212 reviews at 4.9 stars and the page shows a static badge with no review text, that's markup without visible content.

And if you ever get tempted to buy reviews: Google's review content policy prohibits offering incentives — money, free or discounted goods or services — in exchange for reviews. Discount-for-a-review cards in the invoice envelope are a policy violation, not a growth hack.

How do you actually get stars next to your business in Google?

You earn them on your Google Business Profile, and you keep them fresh. BrightLocal's 2026 Local Consumer Review Survey of 1,002 US consumers found 47% won't use a business with fewer than 20 reviews, and 74% only care about reviews written in the last three months — so review velocity, not lifetime count, is the number to manage.

The same survey found 31% of consumers will only use a business rated 4.5 stars or higher, up from 17% the previous year. The bar is rising while most trades businesses still ask for reviews once a quarter, badly.

Ranking-wise, this is not a soft signal either. In Whitespark's 2026 Local Search Ranking Factors survey — 47 local-search experts scoring 187 factors — 'high numerical Google ratings (e.g. 4–5)' ranked 6th and 'quantity of native Google reviews (with text)' ranked 9th among all local pack signals.

So the real work is operational, not technical: a request sent within 24 hours of the job, a direct review link, and a reply to every review. That's a process problem, and we'd fix it inside Google Business Profile optimization before touching a line of schema. If you want tooling, compare the review-request platforms first.

What should a service business do with its on-site review widget?

Keep it, and stop expecting it to do SEO. BrightLocal's 2026 survey found 97% of consumers read reviews for local businesses, so the testimonial block on your homepage is doing real conversion work — it just does none of it in the SERP.

Practically, that means three changes. Move the widget above the fold on your service pages where it can influence a call. Strip the AggregateRating JSON-LD it injects. And stop counting 'star rating in Google' as a deliverable anyone can promise you with markup.

If someone sold you review schema as the route to stars in organic search, that's the tell. They read the schema.org spec and skipped Google's guidelines. It's the same instinct that produces a 12-month contract and a PDF full of validated-green screenshots.

Want to know what's actually eligible on your site and what's dead weight? We'll audit your structured data and the rest of your technical SEO setup and tell you which rich results you can realistically win. Get my free audit.