Structured data errors: what to fix first and what to ignore.

Structured data errors arrive by email: "New issue detected" in a client's Search Console. Some break rich results on hundreds of pages; others are warnings about optional fields, or reports for features Google no longer shows. The job is knowing which is which.

Key takeaways

  • Structured data errors that matter are critical issues on pages and types Google still supports.
  • Use the Rich Results Test for Google features and the Schema Markup Validator for general schema.
  • Check deprecations first: FAQ rich results stopped appearing on May 7, 2026.
  • Fix by template, test the live URL, then click Validate fix once.

Fixing structured data errors is routine work on client sites, but it gets messy quickly. On the dealership fleets and the 18 online stores we support, markup comes from themes, plugins, apps and custom code at the same time, and one bad template can produce the same error on thousands of URLs. This guide gives agencies a triage order and the tools for each step, as part of the technical work we deliver through white label SEO. For writing LocalBusiness markup from scratch, see the LocalBusiness schema guide.

Which tools show structured data errors?

Three tools cover most cases. The Rich Results Test checks one URL or code snippet against Google's supported rich result types. The Schema Markup Validator checks any schema.org markup, including types Google does not use. Search Console's rich result reports show errors across the whole site, grouped by issue, with example pages and validation status.

ToolBest forLimits
Rich Results TestOne page or snippet, Google featuresOnly Google-supported types; page must be crawlable
Schema Markup ValidatorGeneral schema.org syntax and typesDoes not say if Google will show a rich result
Search Console rich result reportsSite-wide patterns and validationExample table limited to 1,000 rows
URL Inspection (live test)Checking a fix on the live pageOne URL at a time

Search Console Help describes the Rich Results Test: it shows which rich result types were found, uses the smartphone user agent by default and reads the rendered code. The Schema Markup Validator at validator.schema.org replaced Google's old Structured Data Testing Tool for general-purpose checks.

What is the difference between errors and warnings?

A critical issue makes an item invalid, so it cannot appear as a rich result. A non-critical issue, often a missing recommended property, leaves the item valid but may limit how it looks. Search Console lists non-critical issues as ways to improve item appearance. Fix critical issues first, on the page types that matter most.

The definitions come from the rich result report overview: a valid item has no critical issues and can appear as a rich result; an invalid item has at least one. Reports only appear for supported types where Google found markup, so a missing report is not an error by itself.

Which rich results has Google deprecated recently?

Several. In June 2025 Google announced it would phase out seven features, including Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. FAQ rich results, already limited since 2023, stopped appearing in Google Search on May 7, 2026. Errors on deprecated types no longer affect what users see.

Search Engine Roundtable reported the June 2025 announcement, which also listed Book Actions and said leaving the markup in place will not hurt. Book Actions was later kept, and Search Console stopped reporting the other six types on September 9, 2025. In 2023 Google limited FAQ results to well-known government and health sites and removed HowTo results from mobile, as covered at the time. Google's FAQPage documentation now states that the feature no longer appears in Search. Check that page and the Search Central updates log before spending budget on any error.

In what order should you fix structured data errors?

Start with critical issues on supported types that bring business: products, merchant listings, local business, reviews where allowed, events, articles. Then fix markup that does not match the visible page, because that is a policy risk. Then warnings on important templates. Leave deprecated types for a cleanup sprint, and document anything you decide not to fix.

  • Confirm the type is still supported and the error is on pages that matter.
  • Group example URLs by template; fix the template, not single pages.
  • Check that marked-up values match what users see on the page.
  • Fix critical issues first, then warnings on high-value templates.
  • Test the fix with the Rich Results Test and the live test in the URL Inspection tool.
  • Click Validate fix once and note the date in the change log.

Search Console Help's guide to fixing structured data issues recommends the same pattern: fix one issue across all affected URLs, fix templates at the source and expect validation to take two weeks or more depending on crawl frequency.

Why does markup that validates still cause problems?

Because validation only checks syntax and required fields. Google's quality guidelines also require that structured data truly represents the visible page and does not mark up hidden content. Fake review stars, prices that differ from the page or marked-up content users cannot see can lead to a manual action that removes rich result eligibility.

Google's general structured data guidelines say a structured data manual action removes eligibility for rich results but does not change ranking, and that quality rules are not easy to test automatically. That is why a person should review a sample of pages, not just the tool output. Product variants are a frequent source of mismatches; see product variant structured data.

What should the agency tell the client?

Tell them which rich results the site can still earn, which errors affect them, what was fixed and when validation will finish. Explain that warnings and deprecated types are not emergencies. A short table with issue, pages affected, cause, fix and status is clearer than forwarding the Search Console email, and it builds trust over time.

Add structured data checks to every release with our SEO QA checklist. If you need schema audits and fixes under your brand, our white label technical SEO covers them. Or book a 30-minute call.

Frequently asked questions

Do structured data errors hurt rankings?

Not directly. Invalid items lose rich result eligibility; Google says a structured data manual action does not change ranking. Fix errors in order of impact, starting with the templates that cover the most important pages. Warnings for optional fields can usually wait until the main errors are fixed.

Should we remove FAQ markup now that the rich result is gone?

It is not required. Remove it in a cleanup if it adds weight, but it is not an emergency. Google still reads valid markup to understand the page, and removing it brings no ranking benefit. Plan any cleanup for a normal release, test the templates and avoid breaking other schema in the process.

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

Search Console reflects the last crawl of many pages; one test checks one page now. Check the date of the report, the specific URLs listed and whether the page version Google crawled matches the live one. Then fix the template and use Validate Fix so Google recrawls the affected pages.

Can a plugin cause duplicate schema?

Yes. Themes, SEO plugins and apps often output overlapping markup; pick one source. Turn off schema output in the tools you do not need, then test key templates again. Duplicate or conflicting markup can confuse search engines and make errors harder to trace.

How often should we check structured data reports?

Monthly in the regular report, and after every release that touches templates. Check sooner if a new plugin or theme update is installed. Catching errors early prevents them from spreading across many pages before the next report. Keep a short log of what changed, and when, for each client.

Juan José Giraldo, senior white label SEO specialist

About the author

Juan José Giraldo is a senior SEO specialist with 5+ years of experience. He works on technical and local SEO for 600+ US car dealerships and supervises the SEO of 18 US e-commerce stores. He runs White Label SEO LATAM from Medellín, Colombia, and delivers white label SEO for agencies in the US, UK, Canada and Australia. Read more · LinkedIn.

Want these agency guides first? Choose White Label SEO LATAM as a preferred source on Google, and my articles are more likely to show up for you in Top Stories.

Follow on GoogleAdd as a preferred source

Sources

  1. Search Console Help, Rich Results Test
  2. Search Engine Land, Schema.org launches its schema markup validator tool
  3. Search Console Help, Rich result report overview
  4. Search Console Help, Fix structured data issues in Search Console
  5. Google Search Central, FAQ (FAQPage) structured data
  6. Search Engine Roundtable, Google drops support for seven existing structured data markups (June 13, 2025)
  7. Search Engine Roundtable, Google Search Console drops support for 6 deprecated structured data types (September 9, 2025)
  8. Search Engine Roundtable, Google to show fewer FAQ and HowTo rich results (August 9, 2023)
  9. Google Search Central, General structured data guidelines
  10. Search Console Help, URL Inspection tool

Ready to test a pilot client?

Book a 30-minute call. You get an honest read on fit, scope and price, with no obligation.