Why star ratings in search results are not something you can mark up yourself

Stars beside a search result are not a switch you flip with markup. Google Search Central’s review snippet documentation puts one eligibility rule ahead of every technical detail: if the entity being reviewed controls the reviews, the page does not qualify. AggregateRating about your own business, on your own site, has not earned a star rating in Google Search since 2019.

Where Google puts that restriction

The review snippet page lists the features that can carry ratings, and two entries carry a restriction inside the entry itself. Local business is offered “only for sites that capture reviews about other local businesses”. Organization is offered “only for sites that capture reviews about other organizations”. Both phrases link to an anchor on the same page named self-serving.

The sentence at that anchor is the rule:

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.

Google’s example follows: “For example, a review about entity A is 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).” An embedded widget is not a way around the rule: it is named in it.

Two further bullets sit under the same heading, and both are about where the numbers came from rather than whether they are accurate: “Ratings must be sourced directly from users”, and “Don’t rely on human editors to create, curate, or compile ratings information for local businesses”.

What Google means by self-serving

The documentation uses the phrase and does not define it. The definition is in the post the documentation links to for that purpose, Making Review Rich Results more helpful:

We call reviews “self-serving” when a review about entity A is placed on the website of entity A - either directly in their markup or via an embedded third-party widget.

An update added to that post two days later restates the test as one of authorship rather than accuracy:

We consider this “self-serving” because the entity itself has chosen to add the markup to its own pages, about its own business or organization.

Notice what is absent from both sentences. Nothing turns on whether the reviews are real, whether the average is arithmetically right, or whether the widget is honest. The disqualifying facts are who put the markup there and who it is about, so a truthful average of genuine customer reviews, embedded from a genuine review platform, is still self-serving. The post closes the obvious next question too: “It applies to Review and AggregateRating”.

Which content is still eligible

Ratings stay eligible on plenty of pages, as long as the subject is not the site publishing them. “When Google finds valid reviews or ratings markup, we may show a rich snippet that includes stars and other summary info from reviews or ratings”, and the page lists what can supply them: book, course list, event, local business, movie, product, recipe and software app, plus schema.org types including episode, game and music recording. A site that reviews other businesses keeps the feature: “Sites that gather reviews can show up with review snippets (for their reviews of other organizations) in search results.”

Two conditions apply wherever it is eligible. The reviews have to be on the page a reader lands on, because “It must be immediately obvious to users that the page has review content”, and “If you use AggregateRating, users should be able to see that aggregate rating on the page”. And the ratings have to be yours to publish: “Don’t aggregate reviews or ratings from other websites”, and “Don’t include fake or undisclosed incentivized reviews on your page or in your structured data markup”. The general guidelines compress that into “Provide original content that you or your users have generated.”

What Google does with markup that is not eligible

Two different outcomes. Ineligibility by itself is not a penalty: the markup stays on the page, gets parsed, and earns nothing, which is what Google’s FAQ says in the table below.

Breaking the guidelines is the other outcome. The review snippet page carries a warning above its guidelines: “If your site violates one or more of these guidelines, then Google may take manual action against it.” The general structured data guidelines say what that costs, and what it does not: “A structured data manual action means that a page loses eligibility for appearance as a rich result; it doesn’t affect how the page ranks in Google web search.” The same page describes a softer failure, that “Violating a quality guideline can prevent syntactically correct structured data from being displayed as a rich result in Google Search, or possibly cause it to be marked as spam”. Invented reviews are named: “Don’t mark up irrelevant or misleading content, such as fake reviews or content unrelated to the focus of a page”, next to the flat instruction “Don’t use structured data to deceive or mislead users”.

Four questions from Google’s FAQ:

The question, as Google’s FAQ puts it	Google’s answer
What if I’m using a third-party widget to display reviews about my business?	“Embedding a third-party widget is seen as controlling the process of linking reviews.”
Do I need to remove self-serving reviews from LocalBusiness or Organization?	“No, you don’t need to remove them.”
Will I get a manual action for having self-serving reviews on my site?	“You won’t get a manual action just for this.”
Does this update apply to AggregateRating too?	“It applies to Review and AggregateRating”

This is Search, not Maps

The rating on your Google Business Profile is a separate system under a separate policy, and the same FAQ says so: “No, your Business Profile is not affected as this update only relates to organic Search.” Nothing on these structured data pages governs the reviews customers leave on Maps. That is the Maps User Generated Content Policy, which covers reporting a fake review, what removal gets you, why a reply gets rejected and answering unhappy customers. A Maps rule does not decide a Search outcome, and a Search rule does not decide what stays on Maps.

Valid and eligible are not the same test

Schema.org defines AggregateRating as “The average rating based on multiple ratings or reviews.” Nothing in that vocabulary definition says who may publish one, so a self-serving rating validates cleanly: a validator checks shape. Eligibility is decided elsewhere, and the general guidelines put the limit plainly: “Using structured data enables a feature to be present, it does not guarantee that it will be present.”

Our own build refuses to emit this markup at all

The content gate on this site fails any emitted page containing an @type of aggregateRating or review, matched without regard to case, for us and for everyone else. Google’s rule is why it is absolute rather than conditional. We have no customers and therefore no ratings, so a rating we marked up about ourselves would be a fabricated fact before it was ever an ineligible one. A competitor’s published rating is not ours to mark up either: we did not collect it from users, we read it off their page, which is what “Don’t aggregate reviews or ratings from other websites” forbids. Our separate rating rule does let a competitor’s real number appear as text, inside an element that must name the subject, the source and the date we read it, and it rejects any rating whose subject is this product. Structured data gets no such exception, because eligibility is Google’s to grant and not ours to assert. A comparison of review management tools can quote a published rating honestly. It cannot ask Google for stars on the strength of it.