wprichsnippets
Guide · Schema types · Errors and fixesCERT No. ST R001

How to Fix Structured Data Errors: Search Console Messages Mapped to Fixes

Schema type
Article BreadcrumbList
Checked against
Search Console Help and Google Search Central documentation, read November 2026
Author
The wprichsnippets.com editors
Published
Updated
Direct answerField 01

To fix a structured data error, read the exact message in Search Console, find the property it names, correct the template that prints it, test the page in the Rich Results Test, then click Validate fix. Critical issues make an item invalid for rich results; non-critical issues only limit how it can appear.

53 wordsUpdated November 16, 2026
FeatureFig. 01
A grid of index cards, each pinned beside a matching corrected card, in a specimen tray
Each message names one property. Fix the template that prints it, not the single page.

01How to fix structured data errors: the message map

A structured data error is a message from Google's parser saying that markup on a page is missing something, holds the wrong kind of value, or cannot be read at all. This page answers how to fix structured data errors by mapping each message to its cause and its fix, using the wording Search Console shows.

The table below combines two lists that Google publishes: the rich result error messages and solutions page and the error types in the Unparsable structured data report. Google says plainly that the first list is not comprehensive, so treat the table as the common cases, not every message that exists.

Search Console structured data messages and their fixes (checked 9 November 2026)
MessageWhat it meansFixWhere it appears
Missing field "property name"A property the feature uses is absent, or present as an empty string.Add the property with a real value from the page. If it is only recommended and the page has no such value, leave it out.Rich result reports
Invalid object type for field "property name"The property holds the wrong kind of object, for example a Text value where an Organization is expected.Change the nested @type to the type the feature guide lists for that property.Rich result reports
Either "property 1" or "property 2" should be specifiedThe feature needs at least one of a group of properties and found none.Add the property from the group that the page can honestly support.Rich result reports
Datetime property "property name" is missing a timezoneA date and time has no offset, so it cannot be placed on a clock.Write it as ISO 8601 with an offset, for example 2026-11-16T09:00:00+00:00.Rich result reports
Invalid datetime value for "property name"The value is missing a component, most often the time.Give a fully specified date and time.Rich result reports
Date/time not in ISO 8601 format in field "property name"A date is written for people, not machines.Use ISO 8601 in the markup; keep the friendly date in the visible text.Rich result reports
Invalid URL in field "property name"A URL is relative, malformed or not a URL.Use an absolute URL that resolves.Rich result reports
Invalid enum value in property "property name"The value is not one of the allowed enumerated values.Use a listed value, such as a full schema.org availability URL.Rich result reports
Invalid ISO 4217 currency codeThe currency is a symbol or a name instead of a code.Use the three-letter code, for example USD.Rich result reports
Rating is missing required best and/or worst valuesThe rating sits outside the default 1 to 5 scale and the scale is not declared.Add bestRating and worstRating.Rich result reports
Rating value is out of rangeratingValue falls outside the declared best and worst values.Correct the value or the declared scale so they agree.Rich result reports
Multiple reviews without aggregateRating objectThe item carries several reviews but no summary rating.Add an aggregateRating built from the visible reviews.Rich result reports
Item does not support reviewReviews are attached to a type Google does not show review snippets for.Move the review under a supported item type, or accept that no stars will show.Rich result reports
No global identifier provided (e.g., gtin, mpn, isbn)A product has no identifier.Add gtin, mpn or isbn where the product has one.Rich result reports
Duplicate field "property name"A single-value property is defined twice in one object.Keep one value. Two plugins writing the same object is the usual cause.Rich result reports
Invalid or unsupported @context valueThe @context is misspelled or a custom remote context.Use https://schema.org.Rich result reports
Data-vocabulary.org schema deprecatedMarkup uses the retired data-vocabulary.org vocabulary.Rewrite it in schema.org vocabulary.Rich result reports
Parsing error: Missing ',' or '}'The JSON is broken: a comma or closing brace is missing.Repair the JSON syntax, then retest.Unparsable structured data
Parsing error: Missing '}' or object member nameUsually a trailing comma before a closing brace.Delete the trailing comma.Unparsable structured data
Bad escape sequence in stringA backslash starts an escape JSON does not allow.Escape the backslash, or remove it.Unparsable structured data
Duplicate unique propertyA unique property, such as @context, is defined twice.Keep one definition.Unparsable structured data
Invalid JSON documentThe block has a top-level syntax error, so nothing inside it can be read.Paste the block into the Rich Results Test code tab and rebuild it piece by piece.Unparsable structured data

The map is a living reference. It is rechecked against Google's help pages every month, and rows are added when a message changes or a new one appears. The date in the caption is the date of the last check.

02What does an error mean, compared with a warning?

Search Console sorts every issue into one of two groups. The rich result report overview calls them critical and non-critical issues. A critical issue makes the item invalid, which means it cannot appear as a rich result at all. A non-critical issue leaves the item valid but limits how it can appear.

Critical and non-critical issues
Critical issueNon-critical issue
Report tableWhy items are invalidImprove item appearance
Item statusInvalidValid
Can show as a rich resultNoYes, if Google chooses to
Typical causeA required property is missing or unreadableA recommended property is missing or imperfect
What to doFix it firstFix it when the page has the data

The same message text can appear in either table. Missing field "aggregateRating" is a good example: whether it blocks anything depends on whether the feature guide lists that property as required or recommended. Read the feature guide before you treat a message as urgent.

Counts in the report are items, not pages. One page with three broken review blocks adds three to the invalid total, and the report only shows a sample of items, so a missing URL does not mean the page is clean.

03Which structured data errors stop rich results?

Only critical issues stop an item outright. Google's general structured data guidelines state that items missing required properties are not eligible for rich results, and that any rich result also depends on the page following the content policies.

A clean report is still not a promise. The same guidelines list reasons a valid item may not show: the feature is not judged the best result for that search, the markup does not represent the main content, it describes content hidden from readers, it is wrong in a way the test could not catch, or the page breaks a guideline. Our checklist of reasons rich snippets stop showing works through each of these in order.

A structured data manual action is a separate case. Google's guidelines say it removes eligibility for rich results but does not change how the page ranks in web search. It appears in the Manual actions report, not in the rich result reports.

04What are unparsable structured data errors?

Parsing errors sit in their own report. Google describes the Unparsable structured data report as a list of markup that could not be parsed because of a serious syntax error, so Google could not even tell which type it was meant to be. Every row in that report is critical; there are no warnings.

The help page adds two points worth acting on. The most common reason one error hits many pages is a template error. And after a parsing error is fixed, new warnings or errors can appear, because the parser can finally read the item and check its properties.

05What does missing field mean in Search Console?

Missing field means the item Google read does not contain a property that the feature uses. Google's message page adds that the same message appears when the property is present but holds an empty string, which is common when a template prints a field the editor left blank.

  • If the property is required for the feature, the item is invalid until you add it.
  • If the property is recommended, the item stays valid. Add it only when the page shows that information.
  • If the property is empty, fix the template so it omits the key when there is no value, rather than printing "".

Never fill a missing field with a value the page does not show. Google's guidelines say not to mark up content that is not visible to readers, and a made-up rating or price is a bigger problem than a warning.

06How to fix an error and confirm the fix

  1. Open the report and click the issue row. Note the property name and two or three example URLs.
  2. Find the source. On WordPress this is usually a theme template, an SEO plugin setting or a block, not the individual post.
  3. Fix the template, then test one example page in the Rich Results Test, or with Test live URL in the URL Inspection tool.
  4. When every instance is fixed, click Validate fix on the issue details page. Google checks a sample first and stops early if the issue is still there.
  5. Wait. The report help says validation typically takes up to about two weeks and sometimes longer.

Two details save confusion. An issue stays in the table for 90 days after its last instance is fixed, and if it recurs within those 90 days it keeps its original first detected date.

07A broken and a corrected rating block

The first block below is valid JSON but produces Rating is missing required best and/or worst values, because a score of 8 is read on the default five-point scale. The second declares the scale. All values are examples.

Example 1 · rating on an undeclared scaleJSON-LDDisplay only
1{2  "@context": "https://schema.org",3  "@type": "Review",4  "itemReviewed": {5    "@type": "Book",6    "name": "Example Book Title"7  },8  "reviewRating": {9    "@type": "Rating",10    "ratingValue": 8111  },12  "author": {13    "@type": "Person",14    "name": "Example Author"15  }16}
  1. 1Line 108 is read on a 1 to 5 scale, so it is out of range
Example 2 · the same review with its scale declaredJSON-LDDisplay only
1{2  "@context": "https://schema.org",3  "@type": "Review",4  "itemReviewed": {5    "@type": "Book",6    "name": "Example Book Title"7  },8  "reviewRating": {9    "@type": "Rating",10    "ratingValue": 8,11    "bestRating": 10,112    "worstRating": 113  },14  "author": {15    "@type": "Person",16    "name": "Example Author"17  }18}
  1. 1Line 11bestRating and worstRating declare a ten-point scale

The rules behind each review property are in the review schema guide, and the AggregateRating schema guide covers which rating values must match what the page shows. For the wider picture of what markup is for, see the structured data handbook, and for every feature-level guide, the schema types section.

08Questions

Q1Do structured data warnings hurt rankings?

Search Console calls warnings non-critical issues, and its help pages describe them as limits on how an item can appear. Nothing in those pages presents them as a ranking factor. The item stays valid and can still show as a rich result, so fix them when the page has the missing information.

Q2Why does Search Console show an error the Rich Results Test does not?

The report reflects the version Google last crawled, while the test fetches the page now. If you fixed the template since the last crawl, the report lags until the page is recrawled. Use Validate fix to ask Google to recheck the affected URLs.

Q3How long does it take for fixed errors to clear?

Google's help pages say validation typically takes up to about two weeks and can take longer. Fixed issues also stay listed with a count of zero for 90 days before they drop out of the table.

Q4Should I delete markup that keeps producing errors?

Only if it describes nothing useful on the page. Removing a broken item clears the error but also removes eligibility for the feature. If the page genuinely has the content, fixing the template is usually less work than it looks, because one fix covers every page.

09Sources

  1. Rich result report overviewSearch Console Help