To qualify for Google rich results, choose a structured data type that matches the page content, supply the required properties, and follow the content and technical guidelines. Then validate the code and confirm that Google can access the live page. Passing a test is only part of becoming eligible and does not guarantee that rich results will appear; Google still chooses how to display results based on the search context.
Check content eligibility before adding markup
Structured data should describe the page’s main content. It must not be misleading or mark up only information that users cannot see. Start by checking what content is eligible for the target feature and reading its specific guidelines, rather than copying markup simply because another site displays stars or images.
For example, Recipe markup is intended for content about preparing a particular dish; “facial scrub” or “party ideas” do not fit that purpose. Even with correct syntax, a mismatch in content type can make a page ineligible for recipe rich results.
Distinguish required properties from recommended properties
Requirements vary by feature, so use the relevant documentation to check each property rather than applying one type’s field list to every page. For recipes, for example, required properties include an image of the finished dish. The image must match the marked-up content, and its URL must be crawlable and indexable.
- Required properties: Supply these as specified for the target feature to meet its basic eligibility requirements.
- Recommended properties: Adding applicable information can enrich the content and improve the user experience, but these properties should not all be treated as mandatory.
- Content guidelines: Having every field filled in does not mean the markup complies with the rules. You must still follow the general structured data guidelines and the feature-specific requirements.
Test the code and inspect the live page
First, validate the code with the Rich Results Test and fix all critical errors. Addressing non-critical issues flagged by the tool is also recommended to improve data quality, but fixing them is not required for eligibility.
Next, deploy a small number of pages and use the URL Inspection tool to check the content as rendered by Google. Key checks include whether robots.txt blocks access, whether noindex is set, and whether a login is required to read the page. If there are no problems, you can request recrawling. After publication, you still need to allow time for Google to crawl and index the pages.
Track valid and invalid items after indexing
After Google indexes the pages, check the relevant rich result status reports in Search Console. If there are invalid items, fix them, inspect the live URLs, and then request validation through the report. After updating templates or code, also watch for an increase in invalid items.
If a page passes testing but does not appear as a rich result, do not just keep revising the syntax. The testing tool may not detect issues such as spam, inappropriate markup, or hidden content, so also check the Manual Actions report. Even without these issues, Google may choose to show a standard text result based on factors such as the user’s location or device.
Rich results: perspectives from across the web
What information do software applications need to provide?
Required properties for software applications include the name, offer price, and either an aggregate rating or an individual review. Set the price to 0 for free applications; when the price is greater than 0, including a currency is recommended. If an application uses only the VideoGame type, Google will not display a software application rich result. Add another applicable type, such as MobileApplication. Complete markup still does not guarantee display.
Which lists can use a host carousel?
Google’s host carousel documentation lists supported content such as course lists, movies, recipes, and restaurants, and requires ItemList to be paired with an applicable type. There is also a carousel beta with different supported types and eligible regions, and its requirements may change. For example, its documentation requires a summary page linking to multiple detail pages and does not support all-in-one pages that use same-page anchors for details. The two sets of requirements must not be mixed.
Can sexually explicit content qualify for rich results?
Google states that sexually explicit pages are ineligible for certain features, including rich results, featured snippets, and video previews, regardless of whether the user has enabled SafeSearch filtering. This is a content eligibility restriction; adding structured data or fixing test errors alone cannot make these features available. Other pages must still be assessed against each feature’s guidelines.
How can you track rich result performance?
Regularly check Search Console’s Performance report to see how often pages appear as rich results and receive clicks, and monitor their average position. Use the Search Console API if you need automated data retrieval. If impressions stay the same but clicks decline, a less relevant title or snippet, or more appealing results from other sites, are only possible explanations. Compare queries, URLs, and time periods before drawing conclusions; do not assume rich results caused the decline.
Does a structured data manual action affect regular search rankings?
Google’s general structured data guidelines state that if a page receives a manual action for a structured data issue, it will not be eligible to appear as a rich result, but that action does not affect its ranking in Google web search. You can confirm and address the issue in Search Console’s Manual Actions report. This statement applies only to manual actions involving structured data; it does not mean that actions taken for other violations also have no effect on rankings.
References
- 我的網站在 Google 搜尋中遭錯誤標示為情色露骨內容 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Can sexually explicit content qualify for rich results?
- 產品子類結構化資料 (ProductGroup、Product) | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 軟體應用程式 (SoftwareApplication) 結構定義 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: What information do software applications need to provide?
- 輪轉介面 (Beta 版) 結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Which lists can use a host carousel?
- 輪轉介面 (ItemList) 結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Which lists can use a host carousel?
- 針對 Google 搜尋流量下滑情形進行偵錯 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can you track rich result performance?
- 結構化資料通用指南 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Does a structured data manual action affect regular search rankings?
- 如何新增商家資訊結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can you track rich result performance?
- 食譜結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.


