Skip to content

How do I check structured data in Google Search Console?

Technical SEO

Search Console checks structured data in three places. The rich result reports under Enhancements (and Shopping) show site-wide results for each type Google supports, the URL Inspection tool shows what Google detected on one page, indexed or live, and the Performance report's Search appearance tab shows the clicks rich results earn. Before publishing, test your code with the Rich Results Test.

Which tool answers which question

QuestionTool
Is markup broken anywhere on the site?Rich result reports in Search Console
What did Google find on this page?URL Inspection, indexed result and live test
Will this code qualify before I ship it?Rich Results Test, with a URL or pasted code
Is my schema.org markup valid in general?Schema Markup Validator, run by schema.org
Did the rich result change clicks?Performance report, Search appearance tab or a page filter

The Rich Results Test also accepts pages outside your property, which is handy for comparing your markup with a competitor's.

A routine for new or changed markup

Google's introduction to structured data suggests roughly this order:

  1. Write the markup. Google recommends JSON-LD where your setup allows it; Microdata and RDFa are also accepted.
  2. Test it with the Rich Results Test while you build.
  3. Deploy, then inspect a few affected URLs to confirm Google has found the markup.
  4. Keep an eye on the rich result reports, because template or serving changes can break markup long after launch.
  5. Compare the pages with similar unmarked pages in the Performance report over a few months.

What the reports won't tell you

  • Types without a report. Search Console reports only the types on its list. Article, Organization or Local business markup gets no report, so check those with URL Inspection or the Rich Results Test.
  • Retired features. FAQ rich results ended on 7 May 2026 and How-to results in 2023, so neither has a report whatever an older guide says. Rich results in Search Console lists what remains.
  • Whether a result will show. Including every required property makes an item eligible, not guaranteed. Google prefers fewer recommended properties filled in completely and accurately over many half-filled ones.

Problems worth checking first

  • The markup describes something users can't see. Google's guidelines rule out structured data about information that isn't visible on the page, even if it's accurate.
  • Only some templates carry it. Inspect one URL from each template (article, product, category) rather than assuming one good page means all of them are.
  • Mobile and desktop differ. Google indexes the mobile version, so the markup must be on the mobile page as well.
  • A required property comes from an empty field. One product without a price or one event without a date shows up as an invalid item; fix the data source, not just the page.

How AutoPSEO helps

AutoPSEO's bulk URL inspection runs up to 500 URLs from a list or sitemap through the URL Inspection API and shows the rich results Google detected on each, a quick way to confirm that every template carries its markup. To see whether the markup pays off, its reports can be broken down by search appearance and compared with the previous period, month or year (filters and dates).

Put your SEO content on autopilot

Connect Search Console and your site. AutoPSEO scans it and plans the first topics right away. No credit card needed.