Guide Structured data · 8 of 8
Structured Data Errors in Search Console: How to Fix Them
Fix structured data errors in Search Console: inspect live URLs, repair syntax and missing fields, validate fixes, and follow up on failed checks.
Key takeaways
- Record the exact issue, affected item, and URL before changing code.
- Separate syntax errors, missing fields, and quality concerns.
- Fix the shared source and verify affected live pages before validation.
- Follow validation status without treating a pass as a rich result guarantee.
Structured data errors in Search Console need a focused repair, not another block of schema pasted onto the page. Open the exact issue, inspect a live example, find the source, and fix all pages that share the cause. Then ask Google to validate the change.
This guide follows that task from the first report to the follow-up check. It separates syntax problems, missing fields, and quality concerns. For the broader terms and setup choices, see our structured data for SEO guide.
Which structured data issue are you seeing?
Start with the exact report and issue name. A product report, a breadcrumb report, and the Unparsable structured data report answer different questions. Copy the label into your task notes instead of reducing every case to “schema broken.”
Google’s Unparsable structured data report covers serious syntax errors that prevent Google from reading the item and identifying its intended type. It appears only when Google finds such data. All items in that report are critical errors, not warnings.
A feature report may instead show an item that Google can read but that lacks a required field. A warning about an optional field is a different task again. Open the linked feature guidance to see what the field means before deciding how to fix it.
Write down the affected item as well as the URL. One page can contain an article, a breadcrumb, and a product. An error in one item does not tell you that every item on that page is wrong.
How to inspect an affected URL
Choose one example URL from the issue details. Save the issue name, affected item, last crawl date, and current page template. Open the page as a reader and check whether it shows the facts that the markup claims. For a wrong author reference, connect author profiles to their articles and compare the two public pages.
Use the Rich Results Test to review the current output. Compare the indexed and live views in URL Inspection where relevant. A report based on an earlier crawl can differ from the page now on your site.
Check the public URL, not just a CMS preview. Record what the tool reads and where the wrong value comes from. Your notes should help a developer reproduce the problem without guessing which draft or version you saw.
Keep access problems separate from code problems. If the intended public page requires a login or cannot be fetched, investigate that cause. Use our crawling and indexing guide when discovery or access is the main issue.
How to fix syntax errors and missing fields
A syntax error means the code cannot be read as intended. Google’s report includes missing commas, missing braces, and bad escape sequences among the possible causes. Fix the reported break first. Once the item can be read, other field errors may become visible. For an article field issue, check Article and BlogPosting fields before changing the post template.
A missing-field issue needs a different check: does the information apply, does it exist, and does the template output it? Do not make up a price, review, or author just to turn a status green.
Use a small case sheet like this fictional example:
| Page | Finding | Source to review |
|---|---|---|
| Door repair guide | Breadcrumb JSON has a missing comma | Shared navigation template |
| Desk lamp product | Offer lacks its current price | Catalog-to-page field mapping |
| Author profile | Profile points to another writer | Author setting and profile link |
These are separate tasks with different owners. A fix for the comma does not repair the product price. A code test may also miss the wrong writer because the URL itself is valid.
How to correct the source across affected pages
Group examples by the template or source they share. If the same issue appears on many posts, check the common code or field mapping before editing each post. If it appears on one page, review that page’s values too. If the affected entity is the publisher, keep the business and publisher identity consistent at its shared source.
Save the old setup and test a controlled change on a safe copy of the site. Check a few affected pages plus one page that was working before. This helps catch a broad fix that removes useful data or breaks a second template.
After release, confirm the public output. Cached pages can still show the old version. If two plugins disagree, trace the source with our WordPress schema conflict guide. Adding a third version makes diagnosis harder.
For field-specific rules, use the relevant guide. Our Product schema guide covers product and offer checks. The BreadcrumbList guide covers navigation paths and list fields.
When to click Validate fix
Google’s fix and validate guidance says to correct the issue across the relevant URLs, verify the live output, and then use Validate fix on the issue details page. Google checks a sample before continuing through affected pages.
Do not use that button as a test of an unfinished patch. First confirm the same cause is fixed across the intended scope. Keep a short release note with the changed source, test URLs, and the person who approved it.
Validation can take two weeks or more, depending on crawling. Wait for the cycle to finish rather than restarting it repeatedly. A live test pass and a completed Search Console validation are separate milestones.
What validation statuses mean
Use the status to choose the next action. Google’s issue guidance gives these broad meanings:
| Status | What to do |
|---|---|
| Not started | Inspect examples and fix the issue before requesting validation. |
| Started | Follow the active validation attempt. |
| Looking good | Checks have passed so far; wait for completion. |
| Passed | Known instances are resolved; keep your test record. |
| Failed | Inspect the remaining examples and repair the cause. |
| N/A | Google detected the fix without a validation attempt. |
Keep the issue and page context beside the status. One page can have a resolved issue and another that still needs work. Read the details instead of treating one Passed label as a clean bill for the whole site.
What to do if validation fails
Open the failed examples and compare them with your original test set. Look for a second template, a missed field, or an old cached response. Fix the remaining cause, check the live pages, and restart validation after the current cycle ends.
Do not hide a useful public page or remove all markup just to reduce an issue count. Decide whether the page and feature still belong on the site. Record that decision if you deliberately retire them.
Also review the structured data quality guidelines. Correct syntax cannot make misleading or irrelevant claims acceptable. Valid markup does not guarantee a rich result.
DEX Health can help you review broader page quality and SEO, including on the free plan. Pair it with Search Console and dedicated schema tests. Its score does not replace Google’s validation. Explore DEX for page checks alongside your content work, while keeping a named owner and clear follow-up for each reported issue.
FAQ
Should I change every page by hand?
+
First check whether the pages share a template or source setting. A shared cause is usually better fixed at that source. Retest a few affected pages and a working page after the change.
Does an old report mean my fix failed?
+
Compare the report's crawl information with the current live output. Keep the dates of your release and tests so you can tell an older observation from a problem that is still present.
What should I send the developer?
+
Provide the exact issue name, public example URL, affected item, test findings, and expected value. Add the suspected template or field source if you have traced it, without guessing at a cause you have not checked.
Sources
Dex SEO is an AI SEO agent for small businesses. Every article here is planned from search data, drafted by Dex, fact-checked against the sources it cites, and reviewed by the team before it is published.
How this article was made: planned and drafted by Dex from search data, fact-checked by Dex (7 claims checked), then approved by the Dex SEO team.