Schema Validator Google: The Current Tools Explained

The Short Answer: Google's Schema Validator Is Now Two Tools

If you're searching for a "schema validator google," the tool you probably remember — the Google Structured Data Testing Tool — is dead. It's been replaced by two separate official tools that split its old job in half:

• The Rich Results Test — checks whether your markup qualifies for specific Google rich results (FAQ, Product, Review, Breadcrumb, Event, and more).
• The Schema Markup Validator (validator.schema.org) — checks any schema.org markup for syntax correctness, regardless of whether Google supports that type as a rich result.

Use the Rich Results Test when you care about how a page appears in Google Search, and use the Schema Markup Validator when you need broader schema.org compliance checking, including types Google doesn't display as rich results. Most site owners will spend 90% of their time in the Rich Results Test — but it's worth knowing both exist, since plenty of outdated tutorials still point to a single "structured data testing tool" that no longer functions.

What Happened to the Structured Data Testing Tool

The old Structured Data Testing Tool wasn't quietly updated — it was formally retired. Google announced in a 2020 Search Central blog post that it was refocusing its structured data tooling around actual Search features rather than general schema.org syntax checking. The generic validation function — checking any schema type against schema.org's vocabulary — moved to the schema.org project itself, becoming the Schema Markup Validator available today.

Google, meanwhile, built out the Rich Results Test as its primary in-house tool, scoped specifically to the structured data types that actually affect how pages look in Google Search results. The old tool is deprecated in every practical sense: the URL still redirects for some users, but it no longer reflects how Google evaluates your markup. If you bookmarked it years ago, or you're following a guide written before 2021, you're testing against a tool that's been gone for years — which explains a lot of the confusion around "why doesn't this match what I'm seeing."

Rich Results Test vs Schema Markup Validator: Which to Use

The split comes down to scope. The Rich Results Test only evaluates schema types Google currently supports for rich results in Search — think FAQ, HowTo (limited use now), Product, Review, Recipe, Event, Breadcrumb, and a handful of others. Run a URL or code snippet through it, and you'll see exactly which eligible rich results were detected, plus any errors or warnings blocking eligibility, along with a rendered preview of how the result could appear — useful for catching mismatches early.

The Schema Markup Validator doesn't care whether Google displays a rich result for your schema type. It validates any JSON-LD, Microdata, or RDFa block against the full schema.org vocabulary — useful for marking up something Google doesn't reward with a rich snippet (Organization, JobPosting variants, SoftwareApplication, or custom extensions) while still confirming the syntax is correct and nothing is malformed.

In practice: if your goal is visibility in Google Search results, start and usually finish with the Rich Results Test. If you're auditing a broader implementation, checking a schema type Google doesn't support, or want a second opinion on syntax the Rich Results Test doesn't flag, run it through the schema.org validator as well. Google's own structured data documentation confirms this exact order: Rich Results Test first, Schema Markup Validator for generic checks.

How to Validate Your Schema Step by Step

A practical workflow to check schema markup for Google Search looks like this:

1. Test the live URL first. Paste the published page URL into the Rich Results Test. This checks the schema as Googlebot actually sees it, including anything injected by JavaScript.
2. Test unpublished or staging pages via code snippet mode. Both tools accept a raw HTML/code snippet, not just a URL — this is how you validate structured data before a page is live, or on login-gated and staging environments Googlebot can't crawl. Paste the relevant block or full page source directly.
3. Read the results by severity. Red errors mean the markup is invalid or missing required properties — these will block rich result eligibility outright. Amber warnings mean optional-but-recommended properties are missing; your schema may still qualify, but you're leaving potential enhancements (like ratings or images) unused.
4. Cross-check in Search Console. The Enhancements reports in Google Search Console show how Google is actually interpreting your structured data across the whole site over time — not just on the one URL you tested manually. This is where you catch markup that validated fine on one page but is throwing errors site-wide after a template change.

This four-step loop — live check, pre-publish check, severity triage, Search Console confirmation — covers the core of how to validate structured data for Google without guesswork.

Passing Validation Isn't the Same as Getting Rich Results

A clean pass in the Rich Results Test confirms your syntax is correct — it does not confirm you'll get the rich result. Eligibility also depends on content quality guidelines, whether the marked-up content actually matches what's visibly on the page, and Google's own discretion about when to display enhanced results at all. Errors versus warnings tell you about the code; they say nothing about whether Google trusts the content enough to feature it.

This gap is where a lot of teams get stuck. Schema validates clean, Search Console shows no errors, and rich results still don't appear — often because the structured data and the visible page content have drifted apart after a redesign, a CMS update, or a content edit nobody re-checked against the schema. Google's tools validate a snapshot; they don't monitor for that drift over time, and they don't check the dozens of other technical and UX signals that affect whether a page converts once it ranks. Schema validation is really one piece of a larger technical picture — the kind covered in a full technical SEO audit.

That's the gap ongoing, automated auditing is built to close: catching content-schema mismatches, markup that silently breaks after a template update, and the broader UX, accessibility, and performance issues that manual spot-checks miss between audits.

Frequently Asked Questions

Is there still a Google schema validator, or was it removed?

Yes — the original Google Structured Data Testing Tool was removed, but it was replaced by two current tools: the Rich Results Test and the Schema Markup Validator (validator.schema.org). Between them, they cover everything the old tool did, split by whether you're checking Google-specific rich results or general schema.org syntax.

What's the difference between the Rich Results Test and the Schema Markup Validator?

The Rich Results Test only checks schema types Google currently supports as rich results in Search, like FAQ, Product, and Review, and shows a preview of eligibility. The Schema Markup Validator checks any schema.org-vocabulary markup for syntax correctness, regardless of whether Google displays a rich result for that type.

Why did Google get rid of the Structured Data Testing Tool?

Google refocused its tooling around actual Search features rather than generic schema.org syntax checking, announced in a 2020 Search Central blog post. The general validation functionality moved to the schema.org project as the Schema Markup Validator, while Google kept rich-result-specific checking in-house as the Rich Results Test.

Can I validate schema markup without a live URL?

Yes — both the Rich Results Test and the Schema Markup Validator accept a pasted code snippet instead of a URL. This lets you test markup on staging environments, login-gated pages, or pages that aren't published yet.

Does passing Google's schema validator mean my page will get rich results?

No — passing validation only confirms your syntax is correct, not that Google will display a rich result. Eligibility also depends on content quality, whether the visible page content matches the marked-up data, and Google's own discretion about when to show enhanced results.

Which schema validator should I use for custom or niche schema types Google doesn't support?

Use the Schema Markup Validator (validator.schema.org), since it checks any schema.org type regardless of whether Google supports it as a rich result. The Rich Results Test will simply ignore or flag as unsupported anything outside its limited list of Google-recognized types.

Once your schema passes both checks, the harder problem is keeping it that way — catching mismatches after a redesign, markup that breaks silently after a CMS update, and the UX or conversion issues neither Google tool was built to check. See what's actually happening on your site with Optimevra's live demo, or head to Optimevra to run a fuller audit.