Schema Validator vs Rich Results Test: what’s the difference?

Validator catches syntax and structural issues. Rich Results Test evaluates eligibility for Google rich results. Use both before shipping.

Do I need to eliminate every warning?

Fix all errors first. Warnings depend on the schema type and your rich-result goals. Keep markup consistent with visible page content.

Why don’t I see rich results after validating?

Validation is necessary but not sufficient. Google may choose not to show rich results based on quality, authority, and policy constraints.

Schema Validator Guide

Most schema issues are not “missing schema” but “broken schema”. This workflow helps you ship correct JSON-LD that search engines can parse.

1) Common error categories

Invalid JSON syntax (trailing commas, quotes, missing braces)
Missing required properties
Markup doesn’t match visible content

2) Example: BreadcrumbList

json

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Tools", "item": "https://example.com/tools" }
  ]
}

3) Workflow: validate → fix → re-test

Open Schema Validator and paste your JSON-LD.
Fix all errors, then evaluate warnings based on your goals.
Confirm eligibility using Google Rich Results Test.

Need to generate markup quickly? Use Schema Generator.

Schema / JSON-LD Schema Generator Guide Schema markup

FAQ

Validation vs eligibility and common misconceptions.