Structured Data Errors and How to Fix Them

Structured data errors are faults in the code that describes a page to search engines. Each one stops the affected item from appearing as a rich result, such as a product listing with its price or a breadcrumb trail in place of a plain URL. The markup is invisible to visitors, so errors tend to build up unnoticed until Search Console reports them or a familiar listing loses its extra detail. Finding and clearing them is a routine part of technical SEO for organisations using structured data.

Most errors are small and mechanical, such as a missing property, a date in the wrong format or a stray comma that breaks the code. The sections below cover what the errors mean, where Search Console reports them, the faults that appear most often and how to fix and validate them so they stay fixed.

What Structured Data Errors Mean

A structured data error means Google has read the markup on a page and found something that breaks its rules for a rich result. Structured data restates the content of a page in a shared vocabulary from schema.org, telling search engines that the page describes a product, an event, an article or an organisation. Google compares that code with the requirements for each rich result type and flags anything missing, malformed or contradictory.

Google supports three formats for writing structured data. All three are equally valid when the markup follows the documentation, although Google’s introduction to structured data recommends JSON-LD in most cases because it is usually the easiest format to implement and maintain.

• JSON-LD sits in its own script block, separate from the visible text, which makes nested information easier to express and test.
• Microdata uses HTML attributes to label content inside the page, so the markup is woven through the visible text.
• RDFa is an HTML5 extension that also adds attributes to the visible content, with a focus on linked data.

Popular WordPress SEO plugins output JSON-LD, which is why it is the format most often seen in Search Console reports. Older themes can still carry Microdata in their templates, so a single page may contain two formats describing the same thing.

Where Search Console Reports Structured Data Errors

Search Console reports structured data errors in the rich result reports listed under Enhancements, with a separate report for each rich result type Google finds on the website. Each report charts valid and invalid items over time and lists the issues behind them, as the rich result report overview explains. The reports count items rather than pages, so a single page listing several products can contribute several errors.

Two other places matter when a report looks incomplete. The Unparsable structured data report lists markup Google could not read at all because of a serious syntax error, which means it cannot even tell which rich result the code was meant to describe.

The rich result reports also show a sample of items and only cover indexed pages. Google’s guidance on missing structured data points to the URL Inspection tool for checking whether a page is indexed before assuming its markup has failed. If the page turns out not to be indexed, our guide to pages crawled but not indexed covers why Google leaves pages out.

Errors and Warnings Need Different Responses

Errors and warnings need different responses because only errors remove eligibility for a rich result. Search Console separates critical issues, which make an item invalid, from issues that only affect how the item could appear. An item with a single critical issue cannot show as a rich result, while an item with warnings alone remains valid and eligible.

Warnings usually flag recommended properties that are missing, such as a review count or a product brand. Google’s general structured data guidelines say that items missing required properties are not eligible for rich results, while extra recommended properties improve the quality of the result for users.

A report with no errors and a handful of warnings is a healthy state for most websites. Chasing every warning tends to produce filler values, which swaps a cosmetic issue for a real one.

The order of work matters as well, since several errors often share one cause. Fixing a single issue type across every affected URL before moving to the next makes it easier to see which change cleared which error.

The Structured Data Errors That Appear Most Often

The errors that appear most often are missing required properties, values in the wrong format and broken code that Google cannot parse. Google publishes a list of rich result error messages and solutions that names the property involved in each case, so the message usually points straight at the fix.

The table below covers messages that come up regularly, what each one means and the usual correction. The property named in the message is the place to start, because it shows exactly which part of the markup needs attention.

Parsing errors deserve separate attention because they hide everything else. Google’s documentation for the Unparsable structured data report warns that fixing a parsing error can reveal further errors that stayed hidden while the code could not be read, so a clean first result is not always the end of the job.

How to Fix Structured Data Errors

Fixing structured data errors follows a short loop of finding the faulty property, correcting it where the markup is generated, retesting and asking Google to validate the change. The Rich Results Test shows which rich result types Google detects on a URL or a code snippet and opens each error in a code explorer at the point where it occurs. The same help page warns that the test ignores comments inside JSON-LD blocks even though comments are not part of the standard, so they should be removed before the page goes live.

For checks against the schema.org vocabulary itself, Google handed its old testing tool to the schema.org community as the Schema Markup Validator. Its update on the Structured Data Testing Tool explains that the Rich Results Test remains the tool for Google rich results, while the validator checks syntax and compliance with schema.org.

Validation does not finish the moment the button is clicked. Google’s guide to fixing structured data issues in Search Console says it can take two weeks or more depending on how often the affected pages are crawled. If validation fails, the issue details page lists the URLs that still carry the error so they can be corrected before the next attempt.

Why the Same Errors Keep Returning on WordPress Websites

Errors keep returning on WordPress websites when more than one plugin or theme outputs markup for the same thing, or when a template generates faulty code for every page built from it. An SEO plugin, a reviews plugin and WooCommerce can each describe the same product with slightly different values, which leaves Google with duplicate or conflicting data. The fix is to choose one source for each schema type and switch off the others.

Template errors work the same way in reverse. Google notes that the most common cause of one error affecting many pages is an underlying template error, so a single correction to the template can clear every affected URL at once.

Updates are the other common trigger, because a plugin or theme update can change the markup it produces without any visible change to the page. A crawl that extracts structured data from every template, using tools of the kind covered in technical SEO auditing tools, can catch these changes before Search Console reports them. WordPress support for business websites that includes testing after updates closes the same gap.

Why Valid Markup Can Still Show No Rich Result

Valid markup can still show no rich result because eligibility is not a guarantee. The general guidelines state that structured data allows a feature to appear without guaranteeing it will. Google decides for each search whether a rich result, another feature or a plain text result suits the person searching, based on factors such as location and device.

Some rich result types have also been withdrawn. The Search Central documentation updates record that the FAQ rich result is no longer shown in Google Search, so FAQ markup can be valid and still produce nothing visible. The background to that change is covered in Google ending FAQ rich results in Search.

Markup that misrepresents the page is the other cause. The same guidelines say content that is hidden from readers, irrelevant or misleading should not be marked up. A structured data manual action removes rich result eligibility for the affected pages without changing how they rank. The Manual Actions report in Search Console shows whether one applies to a website.

Structured Data and AI Search

Structured data plays a supporting role in AI search rather than a decisive one. Google’s guide to optimising for generative AI features says structured data is not required for those features and that no special schema.org markup is needed. It still advises continued use as part of overall SEO, because the markup supports rich result eligibility.

Other systems read the same markup, which is why consistency matters as much as validity. Helen Pollitt’s Search Engine Journal piece on structured data mistakes recommends defining an entity such as an organisation once with an @id and referring back to it, so every page describes the business with the same details. The wider case for markup aimed at AI systems is set out in structured data for AI.

Clearing errors and keeping one consistent source for each schema type gives search engines and other systems a single accurate description of the business. Priority Pixels runs technical SEO as its own discipline, with structured data covered alongside Core Web Vitals, indexation control, canonicalisation and crawl budget.