How to Test and Fix Schema Markup Errors

Schema markup errors are easy to create and easy to miss: a stray comma, a missing required property or a plugin update can quietly switch off a page’s eligibility for rich results. The good news is that almost every error falls into a handful of patterns. This guide shows you which tools to test with, how to read their messages, and a repeatable workflow for fixing schema markup errors and keeping them fixed.

This guide is part of our complete website SEO audit guide, which walks through every step of auditing a small site.

Schema markup errors vs warnings: what the messages mean

Testing tools sort problems into two main levels, plus outright parsing failures, and they deserve very different amounts of attention. Knowing the difference stops you wasting an afternoon on cosmetic warnings while real schema markup errors sit unfixed.

Do not chase every warning by inventing data. If a Product warning asks for reviews and you have none, leaving the property out is the correct answer. Adding fake or hidden values to clear a warning is a guideline violation, which is a far bigger problem than the warning itself.

The tools for testing schema markup errors

Each tool answers a slightly different question, so it helps to know which one to reach for:

• Google’s Rich Results Test checks a URL or code snippet against Google’s rich result requirements. Use it to answer “Is this page eligible for the enhancement I want?” It renders JavaScript, so it also sees markup injected by scripts.
• Schema Markup Validator (validator.schema.org) checks against the full schema.org vocabulary. Use it for types Google does not support as rich results, and for spotting misspelt property names that the Rich Results Test may simply ignore.
• Search Console enhancement reports show errors across your whole site, grouped by issue, with example URLs. Use them to find patterns and to confirm fixes with “Validate fix”.
• URL Inspection in Search Console shows what Google found in its last crawl of a specific page, which helps when the live test and the report disagree.

For day-to-day spot checks, the free LiteScroll SEO Inspector Chrome extension lets you review the schema markup on whatever page is open in your browser. It is a quick way to confirm that a block exists, has the right type and carries the values you expect before running a formal test.

A step-by-step workflow for fixing schema markup errors

1. Start with Search Console. Open the relevant enhancement report and note each issue type and how many URLs it affects. One issue repeated across 200 pages almost always points to a template, not 200 separate schema markup errors.
2. Test one example URL live. Run it through the Rich Results Test. If the error has already disappeared, the problem may have been fixed since Google last crawled.
3. Find where the markup comes from. View the page source and search for application/ld+json. Identify whether each block comes from your SEO plugin, theme, another plugin or hand-written code.
4. Fix at the source. Change the plugin setting, template or code block rather than patching individual pages.
5. Clear caches and retest. Page caches and CDNs often serve the old markup for hours. Purge them, then run the Rich Results Test again.
6. Validate in Search Console. Click “Validate fix” on the issue so Google rechecks the affected URLs.
7. Log what you changed. A one-line note (“Removed duplicate Article schema from theme, 23 Sept”) saves hours the next time something breaks.

The most common schema markup errors and their fixes

Parsing errors: broken JSON

The block cannot be read at all. Usual causes:

• A trailing comma after the last property in an object or list.
• Curly “smart” quotes pasted from a word processor instead of straight quotes.
• Unescaped double quotes inside a text value, such as a headline containing a quotation.
• Missing closing braces or brackets.

Here is a broken snippet and its corrected version:

// Broken: trailing comma and unescaped quotes
{
  "@type": "Article",
  "headline": "The "best" way to test schema",
}

// Fixed
{
  "@type": "Article",
  "headline": "The \"best\" way to test schema"
}

Missing required field

Messages like Missing field “name” or Missing field “itemListElement” mean a property Google needs for that rich result is absent. Check Google’s documentation for the type, find the required list, and make sure your plugin or template fills each one from real page data.

Invalid value type or format

The property exists but holds the wrong kind of value. Common examples are dates written as “4th Sept 2026” instead of ISO 8601 (2026-09-04), prices with currency symbols in the price field, or relative image paths where a full URL is needed.

Unknown type or property

schema.org names are case-sensitive and exact. "@type": "Localbusiness" or "datepublished" will not be recognised. The Schema Markup Validator flags these clearly, while the Rich Results Test may simply not detect the item.

Duplicate or conflicting items

Two blocks describing the same page with different values, typically when a theme and an SEO plugin both output Article or Organization markup. Disable one source so that each entity is described once.

Content mismatch

Markup that describes things users cannot see, such as reviews that are not on the page or an FAQ hidden in the code. Testing tools cannot always detect this, but it breaks Google’s structured data guidelines and can lead to a manual action. Remove the markup or show the content.

Errors that live in your templates and plugins

On most sites, schema markup errors are systemic rather than one-off typos. A useful habit is to test one URL from every template, not every URL:

If the blog post template is clean, every blog post is probably clean. If it is broken, fixing the template fixes them all. Remember to retest after every plugin or theme update; these are the moments when duplicate or malformed blocks most often appear.

When the tools disagree

Sometimes the Rich Results Test shows a clean result while Search Console still reports schema markup errors for the same URL. This is usually a timing issue rather than a contradiction. Search Console reflects the version Google crawled days or weeks ago; the live test reflects the page right now. If the live test is clean, use “Validate fix” and give Google time to recrawl.

The reverse also happens. A page can look fine in your browser’s page source but fail the live test because the markup is injected by JavaScript that loads late, or is blocked for Googlebot by a consent banner or a security plugin. Compare the rendered HTML in the Rich Results Test with your page source. If the block appears in one but not the other, the delivery method is the problem, not the markup itself.

How to stop schema markup errors coming back

• Keep one source of truth for each schema type, ideally your SEO plugin or your templates, not both.
• Store hand-written blocks in version control or a shared document so you can see what changed.
• Retest after updates. Add “test one URL per template” to your plugin update routine.
• Watch Search Console emails. New enhancement issues trigger notifications; act on them within the week.
• Audit structured data alongside the basics. Schema problems often appear on pages that also have weak titles, missing H1s or canonical issues.

That last point is where a crawl helps. The LiteScroll SEO Crawler scans up to 25 pages free and flags titles, meta descriptions, H1s, alt tags, canonicals and indexability, so you can fix the foundations at the same time as your markup. Our guide on how to read an SEO crawl report explains how to prioritise what it finds.

Key takeaways

• Fix parsing errors and invalid items first; treat warnings as optional improvements, never as a reason to invent data.
• Use the Rich Results Test for eligibility, the Schema Markup Validator for vocabulary, and Search Console for site-wide patterns.
• Most schema markup errors live in templates and plugins, so fix them at the source and test one URL per template.
• Purge caches before retesting, then use “Validate fix” in Search Console.
• New to structured data? Start with our beginner’s schema markup guide and the copy-ready JSON-LD examples.

Find more practical SEO walkthroughs on LiteScroll.com.