By Hridoy Ahmed | Last updated: November 2026 | 11 min read
Short answer: A structured data error in Search Console means Google found your markup, but a required part is missing, wrong or unreadable, so that item cannot qualify for its rich result. Fix errors before warnings. Start with the cause that repeats across many pages. On WordPress, that is often a template or two plugins outputting the same schema. Then validate the fix in the report.
In this guide
- What the report shows
- The 5 kinds of structured data problems
- A 6-step triage
- WordPress: where duplicate schema comes from
- Fixing common messages
- When the feature itself is gone
- Validate the fix
- Mistakes to avoid
- FAQ
What the report shows
Under Enhancements in Search Console, Google lists a separate report for each rich result type it found on your site, such as breadcrumbs, products, articles or videos. You see a report only when Google found markup of that type. Each report sorts items into three groups.
| Group | Meaning | What to do |
|---|---|---|
| Error | A required property is missing or invalid. The item is not eligible for the rich result. | Fix first |
| Warning | A recommended property is missing. The item can still appear, sometimes with a reduced result. | Fix if it is cheap and useful |
| Valid | Google found nothing wrong | Leave it |
Two details save confusion. First, the reports count items, not pages. One page can hold several items. Second, structured data on pages that are not indexed, including duplicate or alternate pages, does not show up in these reports. If your count is lower than you expect, check indexing first. See why a page is not indexed and duplicate pages without a declared canonical.
An error does not mean a ranking penalty. It means that item will not earn the rich result. Your normal blue-link ranking is a separate matter.
The 5 kinds of structured data problems
When you read the list of messages, sort each one into a family. The family tells you who should fix it and where.
| Family | What it looks like | Usual cause | Where the report shows it |
|---|---|---|---|
| 1. Unparsable | Missing comma, brace or quote. Google cannot read the code. | Hand-edited JSON-LD, a broken plugin field | The Unparsable structured data report |
| 2. Missing required field | “Missing field” messages | Empty template field, no image, no price | The rich result report for that type |
| 3. Invalid value | Wrong type or format, such as text where a number belongs | Currency symbol in a price, bad date format, relative URL | The rich result report for that type |
| 4. Missing recommended field | A warning | Optional details left out | The warnings table |
| 5. Not matching the page | Markup says one thing, the visible page says another | Hidden content, copied markup, stale prices | Often not shown by any tool |
Family 5 is the dangerous one. Google’s guidelines expect markup to describe content that visitors can actually see. A test can pass while the markup still breaks the rules. Marking up hidden content, fake or self-written reviews, or prices that do not match the page can lead to a manual action for structured data. No tool warns you in advance, so you must check the page by eye.
A 6-step triage
- Open the report and filter out warnings and valid items. Work on errors only for now.
- Read the issue name and the affected count. One issue on 400 items is almost always a template problem. Fix the template once, not 400 pages.
- Click an example URL and open its details. You can see the markup that Google read and the exact line it complains about.
- Test the live page, not a pasted snippet. Run the URL through Google’s Rich Results Test. Google advises testing the live page, because the rendered page may differ from the code in your template. Use the Code tab to see what the page really outputs.
- Use the Schema Markup Validator for syntax and non-Google types. It checks markup against the full schema.org vocabulary. The Rich Results Test only knows types that Google supports.
- Compare the markup to the visible page. Do the name, price, rating and dates match what a visitor sees? If not, fix the content or the markup before anything else.
Many items, many types, and no time to untangle them? My technical SEO service includes a structured data review with a clear fix list per template.
WordPress: where duplicate schema comes from
On WordPress, the most common structured data problem is not a typo. It is more than one source outputting schema for the same page. The result can be two Article items, two Organization items, or conflicting breadcrumbs. Sources to check:
- Your SEO plugin. Rank Math adds schema by default, based on your Schema settings and the Schema tab of each post.
- Your theme. Some themes add Article, Breadcrumb or Organization markup on their own.
- Page builders and add-ons. Widgets for FAQs, reviews, products or events often output their own JSON-LD.
- WooCommerce and shop plugins. They output Product markup, and an SEO plugin may add another.
- Review and rating plugins. They may add aggregate ratings that your page does not show.
- Hand-pasted code. A snippet added in a header or footer long ago, then forgotten.
How to find the source
- Open the page, right-click and choose View page source.
- Search for
application/ld+json. Count the blocks, and note the@typein each. - If the same type appears twice, find who outputs each. Disable one plugin or one theme feature at a time, clear the cache and view the source again.
- Keep one source per type. Rank Math can produce most of what a normal site needs. Turn the extras off.
Set the default schema type for each post type in your SEO plugin once, rather than editing single pages. My Rank Math setup guide shows where those settings live, and how to add schema markup to a WordPress page covers manual cases.
Fixing common messages
Exact wording changes by type, but these patterns repeat.
| You see | Likely meaning | Fix |
|---|---|---|
| Unparsable structured data, missing comma or brace | The JSON is broken | Fix the syntax. Start from an empty object and add parts back one by one. |
| Missing field for a required property such as name or image | The template left it empty | Fill the source field, such as the featured image or product name. |
| Invalid value type or invalid number | Text given where a number is expected | Use a plain number for price and put the currency in its own field. |
| Invalid URL | Relative or broken link in a URL field | Use full URLs that start with https. |
| A product needs an offer, a review or a rating | A required group is missing | Add at least one of the required parts that is real and visible on the page. |
| Warnings for recommended fields | Optional details missing | Add only if the data is real. Skip invented values. |
A tiny syntax example makes the first row clear.
Broken: {"@type": "Article" "headline": "Hello"}
Fixed: {"@type": "Article", "headline": "Hello"}
The broken line has no comma between the two properties. Google cannot read it, so it cannot even tell the type. After you repair a parsing error, new errors may appear, because items that were unreadable are now visible to Google. That is normal progress.
When the feature itself is gone
Sometimes the markup is fine, but the rich result no longer exists. Google ended FAQ rich results for most sites on 7 May 2026, and HowTo rich results are deprecated. Warnings or errors for these types are no longer worth your time if your only goal was the rich result. Valid FAQ markup is still valid schema.org, and the FAQ text still helps readers. Decide whether to keep or remove the markup using my guide on FAQ schema after Google’s update.
Also remember that a report can shrink or vanish when a type is retired, when pages drop out of the index, or when Google stops finding that type on your site. Check indexing before you assume your markup broke. For AI search and schema, see what actually helps.
Validate the fix
- Fix every known instance of one issue on your site. If Google finds even one left, validation stops.
- Open that issue and click Validate fix. Do not click it again until the first run ends.
- Wait. Validation usually takes up to about two weeks, and sometimes longer. Search Console emails you the result.
- If it fails, open the validation details, fix the failing page and start a new validation.
A faster way for big sites: submit a sitemap with only the affected pages, filter the report by it and validate that smaller set. Google says a smaller request can finish sooner.
Mistakes to avoid
- Fixing page by page when a template is the cause. One change in the template fixes hundreds of items.
- Running several schema plugins at once. Duplicates and conflicts follow.
- Adding invented values to clear a warning. A fake rating or price breaks the rules and your trust.
- Marking up content visitors cannot see. Keep markup and page in step.
- Testing only pasted code. Test the live URL and check the rendered output.
- Chasing warnings before errors. Errors block eligibility. Warnings only polish it.
- Expecting instant results. The report updates only after Google recrawls the pages.
FAQ
Do structured data errors hurt my rankings?
Not directly. An error stops that item from qualifying for a rich result. Your normal ranking depends on other things.
What is the difference between an error and a warning?
An error means a required property is missing or invalid, so the item is not eligible. A warning means a recommended property is missing, and the item can still be eligible.
Why did my structured data report disappear?
Google shows a report only when it finds that type on indexed pages. The report may vanish if the type was retired, if the pages left the index or if the markup was removed.
Which tool should I use to test?
Use the Rich Results Test on the live URL for Google rich results. Use the Schema Markup Validator to check syntax and types outside Google’s supported list.
Structured data errors on many pages? I trace each one to its source, whether a template, a plugin or hand-pasted code, then fix it cleanly. See my SEO and technical SEO service.
About the author: Hridoy Ahmed is an SEO specialist and WordPress security expert based in Dhaka, Bangladesh. He has 8+ years of experience and works with clients worldwide.
