---
title: "Schema Validator Compared: Schema.org vs Rich Results Test"
url: https://hostmy.blog/schema-validators-compared/
date: 2026-10-29
modified: 2026-10-29
lang: en
author: "Aditya Sharma"
description: "Schema Markup Validator or Rich Results Test? What each tool answers, why Google split them, what Search Console adds, and which to use for which job."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2631-1024x538.jpg
word_count: 1374
---

# Schema Validator Compared: Schema.org vs Rich Results Test

There are two free validators for structured data, a third place that reports on your live pages, and they answer different questions. Using the wrong one is how people end up with a clean result and a page that still does not qualify for anything, or a warning they cannot explain.

This post compares Schema.org's Schema Markup Validator and Google's Rich Results Test. It adds the report in Search Console that watches your pages after launch, and says which to use for which job. It does not repeat the manual curl method for checking markup, which is in [check your schema without Google's Rich Results Test, using curl and Python](/check-schema-without-google/).

## Two tools from one

The two tools exist because Google split one in two. Google's page on its [schema markup testing tool](https://developers.google.com/search/docs/appearance/structured-data) explains it. Google removed the Google-specific validation from its old Structured Data Testing Tool. It then moved that tool to a new domain, as the Schema Markup Validator. What was left on Google's side is the Rich Results Test.

That history explains the difference. One tool answers whether your markup is valid schema.org. The other answers whether Google can use it to build a rich result.

| Tool | What it answers | Run by |
| ---- | --------------- | ------ |
| Schema Markup Validator | Is this structured data valid, as schema.org describes it? | The schema.org community |
| Rich Results Test | Can Google generate a rich result from this page, and what might it look like? | Google |
| Search Console rich result reports | Is it still working on my live pages? | Google, from your site's own data |

## What the Rich Results Test tells you

Google recommends starting with the Rich Results Test to see which Google rich results can be generated for a page, and to preview how they might look in Search. Its introduction to structured data calls it a useful tool for validating your structured data, and in some cases for previewing a feature, and advises checking your markup with it during development.

The limit is built into what it does. It checks against the rich result types Google supports. Markup can be perfectly valid schema.org and still produce no result in this tool, because Google has no feature for that type. A message that nothing was detected therefore does not mean the markup is broken. It may only mean that no supported rich result applies.

## What the Schema Markup Validator tells you

Google describes the Schema Markup Validator as validating all schema.org-based structured data embedded in web pages, without Google-specific warnings. That is its strength and its limit. It is the right tool for questions about the markup itself: is the syntax right, are the properties spelled correctly, does the type exist. It is silent on whether Google will do anything with it.

The [Schema Markup Validator](https://validator.schema.org/) is where you go to debug a type that Google has no feature for, such as the Speakable or Person markup in [structured data in WordPress](/structured-data-wordpress/). The Rich Results Test may have nothing to say about those.

## What Search Console adds

Both tools test a page on demand, once. Neither tells you what happens after you publish. Google's introduction to structured data points to the rich result status reports in Search Console for that, because pages might break after deployment due to templating or serving issues. A plugin update, a theme change or a template edit can alter your markup site-wide, and the reports are how you find out without testing every page.

## Which to use when

| Your question | Use |
| ------------- | --- |
| Is my markup valid schema.org? | Schema Markup Validator |
| Will Google show a rich result for this page? | Rich Results Test |
| I am building or editing a template | Both, on one page of each template |
| Did something break after an update? | Search Console reports, then a test of one page |
| Is there duplicate markup on the page? | The curl method, because neither tool is built to count it |

The last row is worth a note. A page can carry two Article nodes and still pass both tools, because each node is valid on its own. Counting nodes is a separate check, covered in [adding schema in WordPress without duplicating what Yoast already writes](/schema-plugin-wordpress/).

## What a pass does not mean

A pass is not a guarantee. Google's introduction says that adding structured data can enable enhanced results and might encourage more interaction, and that markup which does not follow its guidelines might be ineligible for rich result display. It does not promise a result. A pass also says nothing about whether the markup is true. Google recommends that structured data match the visible text on the page, and no validator reads the page to check. A FAQ block in the markup that is not on the page, or a date that differs from the one shown, will validate and still be wrong.

## A routine for a WordPress site

`1. After any theme or plugin change, test one post and one page in the Rich Results Test.
2. For types Google has no feature for, test the same pages in the Schema Markup Validator.
3. Check that the markup matches the text on the page.
4. Count Article nodes and canonicals with curl.
5. Check the Search Console rich result reports monthly.`

Test one page of each template, not every page. A post, a page, an archive and a front page cover most of what a site generates, and a fault in a template shows up on the first one you test.

## A worked example: one post, three results

Take a post with Article and FAQPage markup, and run it through all three. The Schema Markup Validator reads the markup and reports whether it is valid schema.org. The Rich Results Test reports which Google rich result features it can detect for the page, which may be fewer than the types you wrote, or none. Search Console, some days later, reports the status of any rich result feature Google has recognised on your pages.

The three can disagree, and the disagreement is informative. Valid in the first tool and nothing detected in the second usually means the markup is correct and Google has no feature for it. Detected in the second and flagged in Search Console later usually means something changed after you tested, such as a template edit or a plugin update. Work from left to right: syntax first, eligibility second, live status third.

## Reading errors and warnings

For many rich result features, Google's documentation lists required properties, and a missing one can stop a page being eligible for that feature. It also lists recommended properties, which can improve how a result displays. For some types there are none that are required: Google's [Article documentation](https://developers.google.com/search/docs/appearance/structured-data/article) says there are no required properties. It also says to consider fixing non-critical issues the tool flags, though fixing them is not necessary to be eligible. So when a tool flags a problem, check which kind it is before you spend time on it. A page can show several warnings and still be eligible, and a missing required property can rule it out.

## Why live pages drift from what you tested

Google's introduction to structured data warns that pages might break after deployment due to templating or serving issues, and that is the pattern to expect on WordPress. A theme update can change a template. A plugin update can start writing its own markup. A caching layer can serve an old copy of a page. None of these shows in the tool you used last month, which is why the Search Console reports and a regular spot check matter more than a one-off pass.

Last checked in October 2026 against Google's structured data documentation. Tool behaviour and supported features change, so test with the current tools.

## Where RankReady fits

RankReady writes Article, FAQPage, Speakable and Person schema, and checks for another schema-writing plugin first, so it adds to the existing graph instead of writing a second copy. Its schema page invites you to verify this with Google's Rich Results Test before and after, and the Schema Markup Validator is the better tool for the types Google does not display. It runs alongside Yoast, Rank Math, AIOSEO and SEOPress, and it is free. The free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) runs 41 checks on your live site.

If your best post passed both validators today, would the markup still match what a reader sees on the page?