Structured data errors: how to find and fix them

Structured data can be correct at launch and broken six months later. A template changes, a required field goes empty, a migration drops a property, and nobody notices until rich results quietly disappear from the results page. Search Console tells you something is wrong, but its reports are built for triage, not explanation. Here is how to read them, fix what actually matters, and stop the same errors from coming back.

Where structured data errors actually show up

Three tools cover almost every case, and they overlap less than you'd think.

• Search Console's Enhancements reports (under each rich result type, like Product or FAQ) show errors and warnings across your whole site, but only refresh every few days and often lag a fix by a week or more.
• The Rich Results Test checks a single URL right now, against the live page, so it's the fastest way to confirm a fix actually worked.
• The Schema.org Validator checks the markup itself against the vocabulary, independent of whether Google supports that type for a rich result at all. Use it when you're not sure if the problem is your markup or Google's coverage.

If you generate schema from a template, don't just check the URL you happen to remember. Pull a handful of pages from that template, including an edge case like a product with no reviews or an article with no author, and test each one separately. A template bug usually hits every page it touches, not just one.

Errors and warnings are not the same problem

Search Console's language is easy to misread under pressure. An error means the page is not eligible for that rich result at all: a required property is missing, malformed, or the wrong type. A warning means the page is still eligible, but you're leaving a recommended property out, so Google may render a plainer version of the result or skip a feature like a star rating.

Triage errors first, always. A page with a warning still shows up with some enhancement. A page with an error shows up as a plain blue link, no different from a page with no schema at all. If you have limited time, fix every error on your highest-traffic templates before touching a single warning anywhere.

The errors that show up most often

1. Missing required property: every schema type has a short list of fields Google treats as mandatory, like 'price' and 'availability' for Product. Check the type's documentation, not just intuition, since required fields differ by type.
2. Invalid value format: a date that isn't ISO 8601, a price with a currency symbol baked into the string instead of a separate currency field, or a rating above the stated scale. These pass a basic JSON syntax check but fail validation.
3. Type mismatch in nested objects: a Review needs an 'author' that is itself a Person or Organization object, not a plain string. This is the most common copy-paste error when someone adapts an example from documentation without adjusting the nesting.
4. Duplicate or conflicting schema on one page: two JSON-LD blocks describing the same entity with different data, often left behind when a CMS plugin adds schema and a developer also hand-codes it. Google picks one and you don't fully control which.
5. Schema describing content that isn't visible on the page: marking up a rating or FAQ that isn't shown to a visitor. This isn't just an error, it risks a manual action for spam, so treat it as higher priority than any validator warning.

What broken schema means for AI engines

Google's Rich Results reports only tell you about Google. AI answer engines that crawl your site don't publish an equivalent error report, so you're mostly inferring behavior. The reasonable assumption is that most of them fall back to the visible page text when structured data is malformed or missing, rather than failing to process the page entirely. That's a reasonable assumption, not a confirmed one. What is clear is that consistent, valid schema removes ambiguity for any system reading the page, human-built or automated, so the same fixes that help a Google rich result are unlikely to hurt anywhere else.

Build validation into your workflow, not just your backlog

Checking Search Console once a quarter means errors sit live for months before anyone notices. A better pattern is cheap and doesn't need new tooling.

• Run the Rich Results Test on a staging URL before any template change ships, the same way you'd check a page for a broken layout.
• Pick one day a month to scan the Enhancements reports for new errors, not just the total count, since a slow rise in one error type usually points to a single template or content source.
• When a migration or CMS change touches page templates, add 'check schema on affected pages' to the release checklist next to redirects and canonical tags.

None of this requires new software. It requires treating structured data as a piece of the page that can break, the same way you already treat broken links or a missing title tag, and checking it on the same schedule.