Research Guides
Check Who Controls the Page Before Expecting Review Stars
A review widget can help visitors evaluate a business without making that business eligible for review stars in Google Search. Check whose business is being reviewed and who controls the page before treating valid review markup as a search feature.
Identify the page publisher and the reviewed entity
Suppose a fictional café embeds a third-party review widget on its own homepage. The widget displays a 4.7 rating from 83 reviews of that café. Write down the two roles: the café publishes the page, and the café is the entity being rated. The company that supplies the widget is not the publisher of the homepage.
Check the rule before debugging the markup
Google Search Central’s review snippet guidance says pages controlled by the business or organization being reviewed are ineligible for the star review feature for the LocalBusiness and Organization types. Google includes third-party widgets in its examples. For the café homepage, the useful conclusion is “ineligible for this feature under the self-serving review rule,” not “the widget needs a different rating property.” This does not mean the business must remove the visible reviews.
Keep eligibility, syntax, and actual display separate
If an independent site collects ratings of the café directly from its own users, examine that page separately. Check that the rating is visible to readers, refers to the specific café, and satisfies the other feature requirements; importing a rating from another site is not a shortcut. Syntax validation tells you whether markup is understood, not whether the feature will appear. Even an eligible page is not guaranteed stars. For that layer of testing, use the structured data QA worksheet.
Copy this decision row
Page and publisher | reviewed entity and type | who controls the page | where the rating came from | visible rating and count | eligibility finding | next step
Write down what failed first. A policy mismatch calls for a different expectation; a syntax problem calls for a markup fix. Treating them as the same issue can turn a useful on-page widget into an unnecessary engineering project.