Google Rich Results Test vs Schema Markup Validator (2026): which should you pick?

Pick Google Rich Results Test if

• Fits if you're checking structured data before a page goes live
• Works for finding out why a rich result stopped showing for a page

Look elsewhere if

• Skip it if you need general schema.org checks, as it only knows Google's rich result types
• Not for you if the page is behind a login, firewall or robots.txt block, unless you paste the code or use a tunnel
• Watch out: passing the test doesn't mean Google will show the rich result, as it picks layouts per search
• Watch out: shared links and saved history last about 90 days, and anyone with the link can open them

Pick Schema Markup Validator if

• Fits if you're a developer checking that schema.org markup is well formed
• Works for sites using structured data for engines and apps other than Google

Look elsewhere if

• Skip it if you want to know about Google rich results, which need Google's Rich Results Test
• Too light for a whole site, as it checks one URL or snippet per run
• Not for you if you want saved history or scheduled checks, as the page offers neither
• Watch out: it's hosted by the schema.org community project, not a company selling support

Google Rich Results Test

• Checks only the rich result types Google Search supports; Google points to the Schema Markup Validator for general schema.org checks.
• Pages behind a firewall or login, or blocked by robots.txt, cannot be tested by URL; you need a tunnel or a code snippet.
• A passing test does not guarantee a rich result: Google says it chooses result layouts per search.
• Shared results links and saved test history last only about 90 days, and anyone with a bookmark can open it.

Schema Markup Validator

• Does not tell you whether a page qualifies for Google rich results; Google's Rich Results Test does that.
• Tests one URL or one snippet per run; the page offers no site crawl, scheduling or saved history.
• Hosted by the schema.org project, a community effort founded by Google, Microsoft, Yahoo and Yandex, not a company selling support.

Google Rich Results Test

Test a URL or a code snippet

Enter a public URL, or paste code and edit and rerun it as often as needed; JSON-LD, RDFa and Microdata are supported.

Rich result detection

Lists the rich result types found, such as Article, Breadcrumb, Event, Job posting, Product snippet, Recipe and Review snippet, with each item's errors and warnings.

Crawl checks

Reports whether Google could crawl and fetch the page, whether robots.txt allows it, and which page resources failed to load.

Search result preview

For some rich result types, shows how the result might look in Google Search on desktop and mobile.

Code explorer

Clicking an error opens the rendered source at the line in question.

Shareable results and history

Share a results link that anyone can open, and bookmark runs to keep a test history, each kept for about 90 days.

Schema Markup Validator

Fetch a URL

Enter a page address and the validator fetches the page and checks the structured data embedded in it.

Test a code snippet

Paste markup into the editor to check it before it is published, and rerun the test after each change.

Any schema.org type

Checks syntax and compliance with schema.org standards for every type in the vocabulary, not only the ones Google uses for rich results.

No Google-specific warnings

Google describes it as validating schema.org data without Google feature-specific warnings, which its Rich Results Test covers instead.

Interface in many languages

The validator's interface can be switched between dozens of languages, including Japanese, German, Hindi, Arabic and Spanish.

Google Rich Results Test

• Free$0

  URL and code tests for JSON-LD, RDFa and Microdata, smartphone or desktop crawler, previews and shareable results.

Schema Markup Validator

• Free$0

  Validates schema.org markup from a fetched URL or a pasted code snippet, with the interface in several languages.