How to Fix Schema Markup Errors That Block Rich Results

You've added schema markup, submitted your sitemap, and waited. But Google Search Console still shows errors, or your pages simply aren't earning the rich results you expected. Schema errors are one of the most frustrating technical SEO issues because they're often invisible on the page itself. The good news: most are caused by a handful of fixable mistakes.

This guide walks you through the most common schema markup errors, how to diagnose them with the right tools, and how to fix them so search engines can properly understand your content. (And a quick reality check: even perfectly valid schema doesn't guarantee a visual rich result—more on that below.)

First, understand what schema errors actually mean

Schema markup (structured data) is code that describes your page content to search engines. When you add it, you're speaking a standardized vocabulary—usually Schema.org, expressed in JSON-LD, Microdata, or RDFa.

Errors occur when:

• Required properties are missing. For example, a Product schema without name or offers.
• Values are the wrong type. A price entered as text instead of a number, or a date in the wrong format.
• The markup doesn't match the visible content. Marking up a rating that isn't on the page.
• Syntax is broken. A missing comma, bracket, or quote in JSON-LD.
• The schema type doesn't apply to the page. Using Article on a product page, for instance.

Google uses structured data to understand entities and relationships, and in some cases to generate rich results. But eligibility is narrow and shrinking—FAQ rich results now appear only for authoritative government and health sites, and HowTo rich results have been discontinued entirely. So treat schema as a comprehension aid first, not a guaranteed visual upgrade.

Step 1: Find the errors with the right tools

Start by identifying what's actually broken. Use these current, supported tools:

• Google Search Console → Enhancements reports. These show errors and warnings for schema types Google actively supports (e.g., Product, Article, Breadcrumb, Event). This is your primary source of truth.
• Rich Results Test (search.google.com/test/rich-results). Paste a URL or code snippet to see which rich result types your page is eligible for and what's missing.
• Schema Markup Validator (validator.schema.org). Checks your markup against the full Schema.org vocabulary—useful for catching issues beyond Google's rich result requirements.

Avoid retired tools like Google's Structured Data Testing Tool and Structured Data Markup Helper—they no longer work.

Step 2: Fix the most common schema errors

Missing required properties

Every schema type has required and recommended properties. For a Product, name and offers (with price and priceCurrency) are essential. For an Article, you need headline, image, and datePublished.

Fix: Check the type's documentation on Schema.org and Google's structured data docs. Add all required properties, and include recommended ones where truthful.

Invalid value types

JSON-LD is strict. "price": "19.99" is a string; "price": 19.99 is a number. Dates must follow ISO 8601 (e.g., 2025-01-15).

Fix: Match the expected type exactly. Use a JSON validator to catch syntax errors before deploying.

Markup that doesn't match visible content

Google requires structured data to reflect what users see. Marking up a 5-star rating that isn't displayed, or a price that differs from the page, can trigger a manual action or simply be ignored.

Fix: Audit each property against the rendered page. If a value isn't visible to users, remove it from the markup.

Wrong schema type for the page

Using Article on a category page or Organization on a product page confuses search engines.

Fix: Choose the most specific type that accurately describes the page. A product page should use Product; a blog post should use Article or BlogPosting.

Broken JSON-LD syntax

A single missing comma breaks the entire block. Browsers may render the page fine, but search engines can't parse the markup.

Fix: Validate your JSON-LD with a linter or the Rich Results Test. Keep markup in a single <script type="application/ld+json"> block per entity where possible.

Step 3: Re-test and monitor

After fixing, re-run the Rich Results Test and Schema Markup Validator. Then request validation in Search Console's Enhancements report. Validation can take days to weeks—don't panic if errors persist temporarily.

Set a reminder to check the Enhancements reports monthly. New template changes or CMS updates can silently break markup.

A note on expectations

Even error-free schema may not produce a rich result. Google decides eligibility based on query, device, and content type. FAQ rich results are now limited to authoritative government and health sites, and HowTo rich results are gone. Focus on accurate, complete markup that helps search engines understand your content—not on chasing visual snippets that may never appear.

Quick pre-flight checklist

Before you publish any page with schema:

• [ ] Required properties present for the chosen type
• [ ] Values use correct types (numbers, ISO dates)
• [ ] Markup matches visible page content
• [ ] Schema type fits the page's purpose
• [ ] JSON-LD passes the Rich Results Test
• [ ] No deprecated schema types or properties

Bottom line

Schema errors are usually caused by missing properties, type mismatches, or markup that diverges from visible content. Fix those, validate with current tools, and monitor Search Console. If you want a fast way to spot structured data issues alongside other technical problems, run a free audit of your site. For more step-by-step fixes, browse the guides library.

More guides · Compare audit tools · Run a free website audit