To monitor rich results, use Search Console to track valid and invalid items, as well as search impressions, clicks, and average position. When something looks wrong, use the Rich Results Test and URL Inspection tool to check markup, access, and rendering. After making fixes, inspect the live URL and request validation, but passing a test does not guarantee rich results: Google does not guarantee that features powered by structured data will appear in search results.
Which reports should you check after deployment and routinely?
After deploying structured data for the first time, wait for Google to index the pages, then check the relevant rich result status report. Ideally, the number of valid items should increase without an increase in invalid items. If you find invalid items, fix the issues, inspect the live URLs, and then request validation through the status report.
For routine monitoring, use the Performance report to track rich result impressions, clicks, and average position. You can also use the Search Console API to retrieve data automatically. Status reports help identify markup issues, while the Performance report shows search performance. Checking only one type of report is not enough to conclude that troubleshooting is complete.
Watch for two changes in item counts after site updates
After publishing a new template or updating code, pay particular attention to these signals:
- An increase in invalid items: The new template may not be working correctly, or problems may arise when it interacts with existing site features. Check the relevant changes.
- A decrease in valid items without an increase in errors: Some pages may no longer contain embedded structured data. Use the URL Inspection tool to investigate the cause.
For example, if valid items decrease after a redesign, the absence of new errors does not necessarily mean the markup is working correctly. Start by checking whether the live pages still contain the original structured data, but do not assume that markup is missing based on changes in item counts alone.
Fix critical errors first, then check rendering
Use the Rich Results Test to validate your code, add any missing required properties, and fix critical errors. Fixing non-critical issues is also recommended to improve data quality, but it is not required for rich result eligibility.
After deployment, also check robots.txt, noindex, and login restrictions to confirm that Google can access the pages. If you suspect JavaScript is affecting the content, use the Rich Results Test or URL Inspection tool to examine loaded resources, console exceptions, and the rendered DOM. You can also collect JavaScript errors encountered by users and Googlebot. However, a general error handler cannot capture every error; some parsing errors, for example, may go unrecorded.
Even without syntax errors, check guidelines and crawling progress
Spam or inappropriate markup does not necessarily cause syntax errors, so testing tools may not detect these problems. If the markup appears correct but rich results are not showing, review the guidelines and check the Unparsable structured data report and Manual Actions report.
After making fixes, allow time for Google to recrawl and index the pages. Google may take a few days to discover and crawl a page after publication, but this does not mean rich results are guaranteed to appear within a few days.
Rich results: perspectives from across the web
Which report should you check for product pages?
For pages where consumers can purchase products, check the Merchant listings report in Search Console. For other product-related pages, such as product reviews or aggregator sites, check the Product snippets report. Both reports provide warnings and errors for Product structured data, but they run different checks based on the requirements of the relevant search experience. Choose the report according to the page’s purpose first.
How can you troubleshoot a dataset that is not appearing in search results?
First, use the Rich Results Test to check the page describing the dataset for missing or incorrect Dataset markup. Even if markup is present, the page may not have been crawled yet. Use Search Console to check its crawl status. The test does not support the RDFa example that uses the DCAT vocabulary, so do not treat this limitation as evidence that the dataset markup is incorrect.
Why are there no rich results for a software application marked up only as VideoGame?
If a software application uses only the VideoGame type, Google will not display software app rich results for it. Include other applicable types that accurately reflect the content; for example, a mobile app can use MobileApplication. However, adding an applicable type does not guarantee that Google will display the feature.
Will a page still appear in search results after a structured data manual action?
According to Google’s troubleshooting guidance, when a page receives a structured data manual action, its structured data is ignored, but the page will still appear in Google Search results. This is separate from whether rich results are displayed. Check the Manual Actions report and use the information there to fix the structured data issues.
References
- 修正會影響搜尋體驗的 JavaScript 問題 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 產品子類結構化資料 (ProductGroup、Product) | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 度假民宿結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Will a page still appear in search results after a structured data manual action?
- 資料集結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How can you troubleshoot a dataset that is not appearing in search results?
- 軟體應用程式 (SoftwareApplication) 結構定義 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Why are there no rich results for a software application marked up only as VideoGame?
- 如何新增商家資訊結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Which report should you check for product pages?


