Paper Boat Media / Search field notes

Review Stars in Google: Which Reviews, Whose Website, What Eligibility?

The stars look familiar. The rules behind them are not interchangeable.

A business owner sees stars beside another result and reasonably asks how to get them. The tempting answer is a plugin. The useful answer begins with a few less glamorous questions.

What exactly is being reviewed? Where did the reviews come from? Who controls the page? And are we looking at a local listing, a product result or another rating treatment?

The icon conceals those distinctions. The implementation cannot.

Start with the reviewed thing

Context What to inspect What not to assume
Business Profile reviews The actual business location and reviews on that platform Website review markup controls the map listing’s rating.
A product review snippet The specific product, visible reviews and applicable product requirements A company-wide testimonial is a review of every product.
A business reviewing itself on its own website Who controls the reviews and the entity being rated A third-party widget removes the self-serving restriction.

Google’s review-snippet guidance makes LocalBusiness and Organization pages ineligible for the star-review feature when the reviewed entity controls its reviews on its own site. Embedding a third-party widget does not remove that restriction.

This does not make genuine testimonials worthless. A prospective client may find a detailed account useful. It means their reader value and their eligibility for a particular search treatment are separate questions.

Do not move a rating to a different subject

Imagine a fictional outdoor retailer with reviews praising helpful staff and fast delivery. It also sells a camping stove. Assigning the store’s service rating to the stove would make the number describe a different thing.

A buyer trying to understand the stove’s performance needs reviews about the stove. Service feedback can still be shown in an appropriate place, clearly labeled. Combining the two may produce a larger review count while making the information less meaningful.

A useful review record

Reviewed entity: the exact item or organization.
Reviewer and source: where the feedback originated.
Rating scale: what the number means.
Published context: where readers can see the review.
Aggregation: which eligible reviews contribute to the displayed value.

Keep those relationships explicit before considering markup. If the team cannot explain how the average was calculated or which items it covers, the problem exists in the data already.

Validate the content before validating the syntax

Google requires marked-up review information to be available to readers on the page. An invisible rating inserted only for search is not a sound implementation. Check the reviewed entity, review text, authorship, count and scale against what the page actually shows.

Then inspect the structured data generated by the theme, commerce plugin and review tool. A single page can accumulate several competing descriptions. Choose a coherent implementation that reflects the content instead of adding another block whenever a test report looks incomplete.

Use the Rich Results Test for technical validation and review the applicable policies separately. A test can parse a rating without establishing whether it was collected honestly or assigned to the right entity.

Missing stars do not diagnose the cause

If stars do not appear, investigate eligibility and actual implementation before changing the review collection process. Check whether the page is accessible and indexed, whether the supported type fits, whether the review information is visible, and whether the markup is accurate.

Even an eligible, technically valid page is not guaranteed the presentation. A comparison with another business is incomplete unless you know the result type and publishing context are comparable.

Do not respond by inventing ratings, relabeling the business as a product or copying third-party aggregates into an unrelated page. Those shortcuts undermine the information the rating is supposed to convey.

Read the review, not just the average

I am interested in what a review helps the next customer understand. A specific account of delivery, fit, durability or support gives a buyer something to evaluate. A high average without context can leave the consequential question unanswered.

Organize genuine feedback so people can find the parts relevant to their decision. Keep the source and subject clear. If a recurring concern points to an operational issue, assign it to someone who can investigate the service or product rather than asking marketing to decorate around it.

The SERP guide’s review entry helps identify the format. For a purchasable item, use my product-search audit alongside the product-specific requirements and the actual offer the customer will encounter.

Questions worth clearing up

Will a Google reviews widget get my company page stars?

Not automatically. Google’s self-serving review restriction for LocalBusiness and Organization also covers embedded third-party widgets on the reviewed entity’s own site.

Can I use the store rating on every product?

A rating should describe the item actually reviewed. Do not assign company service reviews to an unrelated product.

Why are stars missing when the test passes?

Passing a syntax test does not establish every policy requirement or guarantee display. Review eligibility, visible content and the actual result type before drawing a conclusion.

Scroll to Top