When structured data is not displaying properly, first confirm the markup type and what you expect to see in search results. Then identify the problem: is the testing tool unable to parse the markup, has the page not yet been crawled, or is the expected search feature missing? Start by checking whether the markup type matches the content. Next, check the code, whether Google can access the page, and the page’s indexing status. Finally, review the applicable guidelines and check for manual actions. Even if you have added markup and it passes testing, Google does not guarantee that rich results will appear.
First, confirm the markup type and expected appearance
Rather than simply asking why schema is not showing up, identify the page, the type used, and the result you want to see. Harris’s overview recommends first understanding what the markup means and how it is displayed, then choosing it based on the page’s actual content, rather than applying markup solely to obtain a desired search appearance.
- Does the markup match the content? For example, a sneaker product page should not use unrelated Recipe markup just to change how it appears in search results.
- Are the display conditions met? The supplied Google movie documentation describes a Movie list carousel limited to mobile devices. When troubleshooting this type of case, check the device being used as well.
When a tool reports errors, address the problems it identifies first
Use the Rich Results Test to validate the code, fixing critical errors before addressing the non-critical issues flagged by the tool. Google’s documentation recommends addressing non-critical issues to improve data quality, but not every recommendation is a requirement for display.
If Search Console shows relevant error messages, use them alongside the list of structured data errors and the Unparsable structured data report to locate the problems. If the website uses a CMS or is managed by someone else, pass the specific error messages to the relevant administrator so they can address them. Do not simply say that something is not appearing in search.
After publishing or making changes, confirm that Google can read the page
In addition to testing the code, use the URL Inspection tool to check the page content as Google renders it. According to the supplied Google documentation, check the following:
- Whether robots.txt restricts Google’s crawling.
- Whether the page has a noindex directive or requires a login to access.
- Whether Google has recrawled and indexed the page after deployment.
Once you have confirmed that the page has no issues, you can request that the URL be recrawled. Google may need several days after publication to find and crawl the page. This does not mean that a search feature will necessarily appear within a few days.
If testing passes but nothing appears, check guidelines and manual actions
The Rich Results Test cannot rule out every problem. Spam or inappropriate markup does not necessarily contain syntax errors, so you still need to check the applicable guidelines. If a structured data manual action has been issued, Google will ignore the page’s structured data, but the page can still appear in search results. In that case, make corrections based on the Manual Actions report. Even without a manual action, however, a search feature is not guaranteed to appear.
Troubleshooting structured data display issues: perspectives from across the web
If an AMP page is not appearing, where should you start?
First, confirm that you expect an AMP page to appear, rather than a particular type of rich result. The supplied Google documentation recommends checking the amphtml links on canonical and other non-AMP pages, the AMP page's canonical link, and whether Googlebot can access the relevant content. You should also check the applicable structured data guidelines. The documentation also notes that indexing takes time and that certain search features may not be available in some regions.
If a page has multiple schema types, must you remove all but one?
You cannot conclude that removal is necessary simply because something is not appearing. A forum respondent speculated that Google might be prioritizing other schema on the same page and therefore recommended using only one type per page. However, they also acknowledged that details were missing and asked to see the code or page before making a further assessment. This was speculation and advice about an individual case; the supplied material is insufficient to establish “only one type per page” as a general rule.
References
- 使用結構化資料標記電影 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 驗證 AMP 網頁 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: If an AMP page is not appearing, where should you start?
- 商家運送政策結構化資料 (ShippingService) | 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: If a page has multiple schema types, must you remove all but one?
- Do I need to disable Yoast to use my schema?localsearchforum.com — Discusses: If a page has multiple schema types, must you remove all but one?
- SEO必學:Google結構化資料標記(Schema)是什麼?www.yesharris.com — Source used in the article above.



