How to validate JSON-LD for AI Overviews

Work through it in seven steps.

1. 01

   Check JSON syntax before anything else

   Parse the exact application/ld+json served on the page. {“@context”:”https://schema.org”,”@type”:”Article”,”headline”:”Example”} is valid JSON. The same object with a trailing comma before the closing brace is invalid JSON. Fix parsing errors before interpreting types or properties.

2. 02

   Validate Schema.org meaning separately

   Use the Schema.org validator to check whether types, properties, and value shapes fit the vocabulary. A made-up property such as {“aiOverviewEligible”:true} does not create a supported AI Overview control, even though the surrounding JSON can parse.

3. 03

   Test Google rich-result eligibility only where relevant

   Use Google’s Rich Results Test for markup types and pages that Google supports as rich results. Required and recommended properties come from the documentation for that specific Google feature. A pass means the page can be eligible for that feature; it does not guarantee display, ranking, or AI Overview inclusion.

4. 04

   Match markup to the visible page

   Google’s structured data policies require markup to represent the page it describes. A Product price of $99 in JSON-LD is misleading if visitors see $129. Check titles, authors, dates, ratings, availability, images, and URLs against the rendered page, including mobile output.

5. 05

   Verify indexing and snippet eligibility

   Google’s AI feature documentation says a page must be indexed and eligible to appear with a snippet. Check the canonical URL, crawl response, robots rules, noindex controls, and snippet controls. Structured data cannot rescue a page that Google cannot index or show with a snippet.

6. 06

   Inspect the page as Google sees it

   Compare source HTML, rendered HTML, and Google’s inspected page when markup is injected dynamically. Confirm that structured data and the visible facts are present in the version Google can process. Avoid serving materially different claims by device or user agent.

7. 07

   Measure AI Overview visibility as a separate outcome

   After fixing a material issue, annotate the date and monitor the affected queries and pages. Search Console groups AI feature traffic within the Web search type, so use its available filters and page-query data without claiming that a markup change caused every movement. Controlled spot checks can confirm what appeared for a particular search at a particular time.