What does the Schema Debugger check?

The Schema Debugger validates your JSON-LD against schema.org type definitions — checking that required properties are present, that property values are in the correct format, that @type values are valid schema.org types, and that nested entities are correctly structured. It also checks against Google's specific rich results requirements for types like Product, FAQPage and HowTo.

What is the difference between a schema error and a warning?

Schema errors are problems that prevent a page from being eligible for rich results — missing required properties, invalid property values, or malformed JSON. Schema warnings are issues that reduce the quality or completeness of the schema but do not prevent it from working — missing recommended properties, suboptimal values, or best practice violations. Fix all errors before addressing warnings.

My schema validates but I still do not get rich results. Why?

Valid schema is necessary but not sufficient for rich results. Google also requires that the page content matches the schema claims, that the page has sufficient quality signals, and that the site has not been penalised for schema abuse. Rich results are not guaranteed even with perfect schema — Google selects which pages to enhance based on additional quality signals.

How to Validate Your Schema Structured Data Markup

The most common schema errors and how to fix them

Missing required properties

Every schema type has required properties that must be present for the schema to be valid. Product requires name and at least one of offers, review or aggregateRating. FAQPage requires at least one Question with an acceptedAnswer. The debugger shows exactly which required properties are missing.

Invalid property values

Some properties require specific value formats. Price must be a decimal number — "29.99" not "£29.99". Date must be ISO 8601 format — "2026-05-15" not "15 May 2026". URL properties must be absolute URLs with the https:// prefix.

Wrong @type values

@type values must exactly match schema.org type names. "FAQ" is wrong — it must be "FAQPage". "Local Business" is wrong — it must be "LocalBusiness" (no space, capital B). The debugger flags invalid type names.

Malformed JSON

A missing comma, unclosed bracket or unescaped quote character will break the entire JSON-LD block. The debugger shows the exact line and character where the JSON syntax error occurs.

🔬 Debug Schema Now

Run the Schema Debugger and get results in minutes. Pay as you go.

Debug Schema →

Schema Debugger: JSON-LD Validation and Rich Results