If aggregate review markup passes Schema Validator but no stars or review count appear in search results, that alone does not mean the industry is ineligible. Nor does passing Schema Validator establish that the code meets Google’s display requirements. Check, in order, whether the item being reviewed is supported, whether the page and markup comply with the guidelines, and whether Google can access the page. Even if the markup passes the Rich Results Test, Google does not guarantee display; being eligible and actually appearing are two different things.
Check what is being reviewed, not just the industry or type name
Google’s review snippet documentation lists supported items such as products, books, movies, and recipes. Start with what the page actually reviews, then check the applicable feature guidelines rather than making assumptions based solely on the industry name.
- LocalBusiness: Only applicable to sites that collect reviews about other local businesses.
- Organization: Only applicable to sites that collect reviews about other organizations.
- Aggregate ratings: The official documentation describes how to nest an aggregate rating using the aggregateRating property. When aggregating reviews, you must provide the average rating to be displayed.
For example, a business publishing ratings of itself on its official website cannot assume it meets these conditions simply by switching to Organization. First check the item being reviewed and the website’s role, then examine the required properties; changing the type name is no substitute for an eligibility assessment.
Test the code and check the content users can see
Use Google’s Rich Results Test to validate the markup, prioritizing fixes for all critical errors. Addressing non-critical issues is also recommended to improve data quality, but the official documentation explicitly states that fixing these issues is not required for eligibility.
In addition to reviewing the test results, check the page itself:
- Does the markup represent the page’s main content, rather than unrelated or misleading information?
- Are the reviews and ratings referenced by the markup visible to users?
- Does the page comply with the content policies, general structured data guidelines, and review snippet-specific guidelines?
For example, if ratings exist only in the markup and users cannot see the related content on the page, passing the test is not proof of compliance. Google notes that some errors cannot be detected by testing tools.
Check access and manual actions—eligibility is no guarantee of display
After deployment, use Search Console’s URL Inspection tool to see how Google renders the page. Confirm that robots.txt, noindex, or login requirements are not preventing Google from accessing or indexing it. You can request recrawling after making fixes, but recrawling and indexing take time; it may take a few days after publication for the page to be discovered and crawled.
Also check the Manual Actions report. A manual action related to structured data makes the page ineligible for rich results, but that action does not affect its ranking in regular web search. Even if all the checks above reveal no issues, Google may still choose to show a standard text result based on factors such as search history, location, or device. Not seeing stars in a single search is not enough to conclude that the markup must be wrong.
Assessing rich result eligibility when review ratings are missing: perspectives from across the web
What did the test show when AggregateRating was used on its own in the forum example?
After testing the original poster's code, a forum respondent said the example was not eligible for rich results and attributed this to using AggregateRating on its own. This was an assessment of the supplied code, not a conclusion that can be applied directly to all pages. Another respondent suggested trying Organization, but the original poster encountered another error when modifying the example. Changing the type therefore cannot be treated as a verified solution.
Why did a competitor's ratings appear in search results but not in the test preview?
The available information does not establish why the preview differed from the actual search results. The forum's original poster entered another company's source code into the Rich Results Test and found that the preview showed no ratings, even though ratings appeared in search results. This was an individual observation. Google also explains that the tool can preview most features, but actual search results may look different. A single preview therefore does not justify concluding that the other company's ratings will definitely not appear.
References
- 評論摘錄 (Review、AggregateRating) 結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Why did a competitor's ratings appear in search results but not in the test preview?
- 結構化資料通用指南 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- Do I need to disable Yoast to use my schema?localsearchforum.com — Discusses: What did the test show when AggregateRating was used on its own in the forum example?
- Do I need to disable Yoast to use my schema?localsearchforum.com — Discusses: What did the test show when AggregateRating was used on its own in the forum example?
- Do I need to disable Yoast to use my schema?localsearchforum.com — Discusses: What did the test show when AggregateRating was used on its own in the forum example?; Why did a competitor's ratings appear in search results but not in the test preview?



