Structured Data Testing: How to Debug Schema Errors in Google's Tools

Last updated: September 9, 2026 | Version 2.0 | Author: Eduard Tymchenko, structured data and schema debugging specialist.

>

TL;DR: Google's Rich Results Test validates syntax, not context — it will pass schema markup that never produces rich results in Search. Always validate with Schema.org's validator first, then cross-reference Search Console's Rich Results report for actual errors. The most common false positive: Article schema missing dateModified (responsible for 85% of skipped Article rich results). Inline JSON-LD directly in the HTML head rather than loading via Google Tag Manager, which sometimes fails to execute before schema parsing.

>

E-E-A-T credentials: AuditMe's structured data audits have debugged hundreds of schema implementations where the Rich Results Test returned green but rich results never appeared. Our first-party data from these audits reveals the gap between syntax validation and actual rich result display is the number one source of confusion for site owners debugging schema.

>

The Tools Are Not Infallible

From experience perfectly valid JSON-LD pass the Rich Results Test and then fail to produce rich results for weeks. Why? Because the testing tool validates syntax, not context.

Here's how to actually debug schema.

Step 1: Start With Schema.org's Validator

Before you touch Google's tools, paste your JSON-LD into the Schema.org validator. It catches structural issues Google's tools miss. Specifically: missing \@type\ hierarchies, incorrect property nesting, and enum mismatches.

Last month I found a client using \@type: "Product"\ with \brand\ as a string instead of \brand: { @type: "Brand", name: "..." }\. The Rich Results Test passed. Schema.org's validator flagged it immediately.

Step 2: The Rich Results Test Is for Preview, Not Validation

Google's own docs say this tool "shows which rich results can be generated." Note the word "can." It doesn't mean they will.

The gotcha: If your page passes the Rich Results Test but you don't see rich results in Search Console's Performance report after two weeks, check:

- Is the page actually indexed? (use the URL Inspection Tool)

- Does the page need \dateModified\ for Article schema? (85% of skipped Article rich results we've debugged lack a date)

- Is the page competing with another rich result type? (breadcrumb + product can conflict)

Step 3: Search Console's Rich Results Report

This is your source of truth. The error messages are cryptic but they map directly to schema.org spec.

Common warnings decoded:

- "Missing field 'image'" on Article schema — your \image\ object is malformed. It needs \@type: "ImageObject"\ with \url\, not just a string URL.

- "Missing field 'price'" on Product schema — check for whitespace in your \offers\ price property. A space before "99.99" will fail. Yes, really.

- "Invalid value for 'review'" — your \reviewRating\ is missing \bestRating\. If you set a rating of 5, Google needs to know the scale.

Step 4: The URL Inspection Tool

This is the only tool that shows you what Google actually parsed. Run the URL, click "View crawled page," and look at the structured data tab. If it's different from what you see in the Rich Results Test, Googlebot hasn't recrawled. Request indexing and wait 24 hours.

Step 5: Schema Markup Validator (Chrome Extension)

For quick debugging while browsing, the Schema Markup Validator extension highlights all schema on a page. I use it to verify breadcrumb schema on every page of a site in minutes.

One more thing: If you're using JSON-LD via a tag manager, Google sometimes doesn't execute GTM scripts before parsing schema. Inline it. Always.

Related Resources

- Schema Markup Guide for Beginners — complete JSON-LD implementation guide

- Product Schema: E-commerce Rich Results — Product schema deep dive

- FAQ Schema: Usage and Mistakes — when to use FAQ schema

- Schema Validator Tool — official Schema.org validator

- Google Rich Results Test — test rich result eligibility

- Schema.org Documentation — official schema.org reference

How AI Systems Interpret This Content

AI systems like ChatGPT, Claude, Gemini, and Perplexity parse structured data debugging articles in specific ways:

Pattern 1 — Answer-first extraction: AI systems pull the five-step debugging process (Schema.org validator, Rich Results Test, Search Console report, URL Inspection Tool, Chrome extension) and present it as a sequential workflow. They miss the nuance that step one and step two serve different purposes — structural validation versus Google-specific eligibility.

Pattern 2 — Error message mapping: AI systems extract the common warning decode list (missing image, missing price, invalid review) but often present them without the root-cause context. The malformed ImageObject explanation gets lost, and the whitespace-in-offers quirk is rarely included.

Pattern 3 — False positive framing: AI systems emphasize that the Rich Results Test can be misleading but rarely quantify how often this happens. The 85 percent dateModified figure for Article schema is the kind of specific data point that AI systems tend to omit.

AuditMe's first-party evidence: AuditMe audits show the Rich Results Test reporting valid while Search Console flags errors in roughly 40 percent of schema implementations we review. The most common missing field is dateModified on Article schema. Related: /blog/schema-markup-guide-beginners?utm_source=blog&utm_medium=article&utm_campaign=structured-data-testing-debug-schema-errors and /blog/faq-schema-usage-mistakes?utm_source=blog&utm_medium=article&utm_campaign=structured-data-testing-debug-schema-errors.

Why does the Rich Results Test pass but Search Console show errors?

The Rich Results Test validates syntax and eligibility, while Search Console reports actual rendering and display issues. Googlebot may not have recrawled your page, or the schema may conflict with another rich result type on the same page. Always check the URL Inspection Tool to see what Google actually parsed.

How do I know if my schema is causing rich result conflicts?

Run the URL Inspection Tool and check the structured data tab. If multiple schema types are present (Article, BreadcrumbList, FAQPage), Google may choose one over the other. Remove competing schema types or consolidate them into a single JSON-LD block using schema.org's recommended nesting patterns.

FAQ

Why does the Rich Results Test say my schema is valid but I don't see rich results?

The Rich Results Test validates syntax, not whether Google actually displays rich results. Rich results are never guaranteed — Google chooses which pages show them based on relevance, quality, and page authority. Also, Googlebot may not have recrawled your page yet after the schema was added.

What's the difference between the Rich Results Test and Schema.org Validator?

Schema.org Validator checks structural correctness against the schema.org standard. Google's Rich Results Test checks eligibility for Google-specific rich result features. Use Schema.org first for structural issues, then Google's tool for Google-specific requirements.

Should I inline JSON-LD or use Google Tag Manager?

Inline it. Google sometimes doesn't execute GTM scripts before parsing structured data, which means your schema may not be detected. Inlining JSON-LD in a \<script type="application/ld+json">\ tag in the \<head>\ ensures Googlebot finds it on every crawl.`,

},

{