To troubleshoot structured data issues, start by identifying problems in Search Console error reports. Then use the Rich Results Test to check the markup and the URL Inspection tool to check the live page. After making fixes, request validation. Check structured data after the initial deployment and after template or code updates, and analyze traffic regularly. Note that passing the test does not guarantee that rich results will appear. You still need to check compliance with content guidelines and allow time for recrawling and indexing.
Find the right report, then distinguish errors from suggested improvements
Once a page is indexed, check the relevant rich result status report. If the data cannot be parsed, also check the Unparsable Structured Data report. Use the appropriate report for each page type: check the Merchant Listings report for pages where products can be purchased, and the Product Snippets report for other product-related pages, such as product reviews. The checks performed by these two reports are not identical.
Use the Rich Results Test to validate the code and fix all critical errors. Addressing non-critical issues is also recommended to improve data quality, but fixing non-critical issues is not required for eligibility to appear in rich results. If a CMS provider or someone else maintains the website, pass along the relevant Search Console messages to them.
Confirm that the fixes are reflected on the live page
- After fixing invalid items, check the live URL to see whether the issues persist.
- Use the URL Inspection tool to see how Google renders the page, confirm that Google can access it, and check whether robots.txt, noindex, or login requirements are preventing crawling or indexing.
- Request validation through the status report. Once you have confirmed that the page is correct, you can also request recrawling and submit a sitemap to help Google discover the changes.
After publication, Google may take a few days to find and crawl the page. Both recrawling and indexing take time, so the absence of rich results immediately after deployment should not be treated as proof that the fix failed.
Check content guidelines even if the test reports no errors
Spam or improper use of markup can cause problems unrelated to syntax. The Rich Results Test may not identify their causes, so also check the markup and content against the structured data guidelines. If you receive a manual action for structured data, review the Manual Actions report and address the issues. This type of action causes the structured data on the page to be ignored, but the page may still appear in regular search results.
Track changes in both valid and invalid items after updates
- Invalid items increase after major website changes: there may be a problem with the new template itself or with how it works on the website.
- Valid items decrease without an increase in errors: pages may no longer contain embedded structured data. Use the URL Inspection tool to investigate.
These changes are troubleshooting clues; they do not establish the cause. For routine monitoring, use the Performance report to track rich result impressions, clicks, and average position. If you need to retrieve data automatically, you can use the Search Console API.
Troubleshooting and monitoring structured data issues: perspectives from across the web
How should you troubleshoot a missing or incorrect work location in a job posting?
First, confirm that the work location in the markup is where the employee will actually report for work, rather than the recruitment location. If Google cannot match the data to a physical location, check and add the applicable jobLocation, addressLocality, or addressRegion properties based on the location; not every property applies to every location. Provide as much location detail as possible, then use the preview in the Rich Results Test to confirm that the correct location is displayed.
References
- 瞭解徵人啟事結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: How should you troubleshoot a missing or incorrect work location in a job posting?
- 教育問與答結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 如何新增商家資訊結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 食譜結構定義標記 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.


