How to Fix Structured Data Errors on Your Website
Structured data errors occur when a page's schema markup (usually JSON-LD) can't be parsed or is missing properties that Google requires for that type. By the end of this guide you will have found every affected page, fixed the syntax and required fields at the template level, removed duplicate markup, and confirmed the fixes in Google's tools.

Why it matters
Search engines ignore markup they can't parse, and Google drops pages from rich result eligibility (product prices, ratings, breadcrumbs, event dates) when required properties are missing. That means plainer search snippets and lower click-through. AI search features and assistants also read schema to pull facts such as prices, addresses and authors, so broken markup lets them guess or skip your page.
Because schema is usually generated by a template, one error often repeats across hundreds of URLs, and the audit counts every one of them.
What you need
Step-by-step fix
Group the failing pages by template
Export the affected URLs from your audit and sort them by page type, such as product, blog post, category or location. Structured data almost always comes from a shared template, plugin or app, so fixing one template usually clears dozens of URLs. Pick one representative URL per group to test.
- In Search Console, also open Enhancements (and Shopping for products) in the left menu to see Google's own error counts per type.
Check that the JSON-LD parses
Open the page, view source (Ctrl+U or Cmd+Option+U), search for application/ld+json, and paste each block into the Code tab of the Schema Markup Validator. Parse errors stop search engines from reading the entire block. Common causes:
- Trailing commas after the last property or array item
- Curly "smart" quotes pasted from a word processor
- Unescaped double quotes or line breaks inside text values, such as product descriptions
- HTML comments or JavaScript left inside the script tag
<!-- Broken: trailing comma and unescaped quote -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Co 12" Skillet",
}
</script>Run the Rich Results Test on each template
com/test/rich-results and choose the smartphone crawler. Separate errors (red, which block eligibility) from warnings (orange, recommended properties that are missing). Fix every error first.
Warnings are worth fixing if the data exists, but they don't count as invalid markup.
Add the missing required properties
Fill in what Google requires for each type. The most frequent gaps:
- Product:
nameplus at least one ofoffers,revieworaggregateRating. Each Offer needsprice(orpriceSpecification) andpriceCurrency. - AggregateRating:
ratingValueplusratingCountorreviewCount. It must refer to the item it is nested in. - BreadcrumbList: each
ListItemneedspositionandname, plusitemon every entry except the last. - Event:
name,startDate(ISO 8601) andlocation. - LocalBusiness:
nameandaddress(PostalAddress). - Recipe:
nameandimage. - Article: no strict required fields, but add
headline,image,datePublishedandauthorwithname.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Example Co Cast Iron Skillet 12in",
"image": "https://example.com/images/skillet-12.jpg",
"sku": "EC-SK12",
"brand": { "@type": "Brand", "name": "Example Co" },
"offers": {
"@type": "Offer",
"url": "https://example.com/products/skillet-12",
"price": "49.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.6",
"reviewCount": "87"
}
}
</script>Remove duplicate and conflicting markup
Themes, SEO plugins and review apps often each output their own Product or Organization block. You end up with two Products on one page, one of which lacks offers. Keep a single source per type, disable the others, and delete leftover Microdata (itemscope/itemprop) if JSON-LD now covers the same entity.
Make the markup match the visible page
Every value in the schema must appear on the page: the same price, rating, author and dates. Google treats markup describing hidden or different content as a policy violation, and it can issue a manual action that removes rich results site-wide. Also check that the markup is in the server-rendered HTML or reliably rendered by JavaScript, and is not injected only after user interaction.
Deploy, retest and validate in Search Console
Clear any page or CDN cache, then rerun the Rich Results Test on each representative URL and on a few random URLs from every group. In Search Console, open each affected report under Enhancements or Shopping, click the error and press Validate fix. Finally, rerun your site audit to confirm the count of pages with structured data errors has dropped to zero.
Platform-specific notes
WordPress
Most schema comes from Yoast SEO (Yoast SEO > Settings > Content types / Site representation) or Rank Math (Rank Math > Titles & Meta and the Schema tab in the post editor). WooCommerce adds its own Product markup. If your theme also outputs schema, turn it off in the theme options or with the plugin's documented filter so only one source remains.
Shopify
Product JSON-LD lives in the theme. In Online Store > Themes > Edit code, look in sections/main-product.liquid or snippets for application/ld+json. Current themes use {{ product | structured_data }}. Older or custom themes hand-build it. Review apps often inject a second Product block, so turn off rich snippets in one of them.
Wix
Wix adds default markup per page type. Edit it in Marketing & SEO > SEO Settings > select the page type > Edit > Structured data markup. For a single page, use the page's SEO Basics > Advanced SEO > Structured Data Markup. The editor rejects invalid JSON, but it won't check Google's required properties.
Webflow
Add JSON-LD in Page Settings > Custom Code (Inside <head> tag). On CMS template pages, insert CMS fields into the script. Rich-text or quote-containing fields can break the JSON, so use plain-text fields for schema values.
Next.js
Render a <script type="application/ld+json"> in the page or layout using dangerouslySetInnerHTML={{ __html: JSON.stringify(data).replace(/</g, '\\u003c') }}. This keeps it valid and safe from script injection. Build it from the same data that renders the page so values never drift.
Check that it worked
✅ How to verify
- Rich Results Test shows each detected item as valid, with zero errors, for a sample of URLs from every template.
- Schema Markup Validator parses every application/ld+json block on the page without syntax errors.
- Search Console Enhancements/Shopping reports show the validation status as Passed after recrawl.
- A fresh run of your site audit reports no pages with structured data errors.
⚠️ Common mistakes
- Fixing the one URL from the report in the page editor instead of the template, so the error persists on every other page of that type.
- Treating Rich Results Test warnings as the problem while red errors remain, or adding fake values just to clear warnings.
- Leaving both a plugin and the theme (or a review app) outputting Product or Organization schema, which creates duplicate, partially empty items.
- Outputting raw CMS text into JSON-LD without encoding, so a single quote mark or line break in one product description breaks that page's markup.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Do structured data errors hurt my rankings?
Not directly. Schema isn't a ranking factor, but invalid markup makes pages ineligible for rich results such as prices, ratings and breadcrumbs. That usually lowers click-through. It also removes reliable facts that search and AI features use to understand the page.
What is the difference between an error and a warning in the Rich Results Test?
Errors mean a required property is missing or invalid, and the item can't appear as a rich result. Warnings mean a recommended property is missing. The item is still valid, but adding the property can make the result richer.
Should I use JSON-LD or Microdata?
Google supports both, but recommends JSON-LD because it sits in one script block and is easier to maintain without touching visible HTML. Pick one format per entity to avoid duplicates.
Why does Search Console still show errors after I fixed them?
Search Console only updates after Google recrawls the pages, which can take days to weeks. Click Validate fix in the report and request indexing for key URLs. Meanwhile, rely on the live Rich Results Test to confirm the current state.
How to Fix Missing Organization Schema (JSON-LD Guide)
How to Fix Index Coverage Gaps in Google Search Console
How to Fix Missing WebSite Schema (JSON-LD Guide)
How to Fix Conflicting Canonical and Noindex Tags
How to Fix Missing Product and Article Schema (JSON-LD)
How to Fix Canonical Tags Pointing to Non-200 URLs