Hydrogen SEO
Log inStart free

Validate Your Rich Results

Test your structured data with Google’s Rich Results Test and Schema Markup Validator, read what each one is actually telling you, and fix what fails.

4 min read
On this page
  1. Google Rich Results Test
  2. Schema.org validator
  3. Errors vs warnings
  4. Re-testing after fixes
  5. Monitoring in Search Console
  6. FAQ
  7. The validator shows no structured data at all. What's wrong?
  8. Do warnings hurt my rankings?
  9. I passed the Rich Results Test. Why don't I see a rich result in search?
  10. How often should I validate?
  11. Related reading

Validating rich results means running your live page through Google's Rich Results Test and the Schema.org validator to confirm the structured data Hydrogen SEO outputs is complete, correctly formatted, and eligible for enhanced display in search. It takes about two minutes per page, and it is the step that separates "we added schema" from "our schema works." Do it after every schema change, whether the fields were filled by hand, with smart tags, or by AI-assisted schema.

Because Hydrogen SEO renders all JSON-LD server-side with zero front-end JavaScript, what the validators fetch is exactly what every crawler sees. There is no rendering gap to worry about.

Google Rich Results Test

The Rich Results Test answers one question: is this page eligible for Google rich results, and if not, why not?

  1. Go to Google's Rich Results Test at search.google.com/test/rich-results.
  2. Enter the full URL of the live page (test the real URL, not a preview or a pasted snippet, so you validate what Google will actually fetch).
  3. Click Test URL and wait for the crawl to finish.
  4. Read the results. The tool lists each rich-result type it detected (Product, Breadcrumbs, Recipe, and so on) with a status per item.
  5. Expand any item with issues to see exactly which field is affected and whether it is an error or a warning.

If a page is not yet public, the tool also accepts pasted code, but URL testing should be your default because it validates the whole delivered page.

Schema.org validator

The Schema.org validator at validator.schema.org checks something subtly different: whether your markup is syntactically valid, well-formed structured data, regardless of Google's rich-result programs. Google's tool only reports on types Google shows rich results for; the Schema.org validator sees everything.

  1. Go to validator.schema.org.
  2. Enter the page URL and run the check.
  3. Review the parsed tree: every schema object on the page is shown with its properties, so you can literally read back what machines will read.

Run both tools. Google's tells you about rich-result eligibility; Schema.org's confirms the markup itself is sound, which matters for every other consumer of your structured data, including AI answer engines (see answer engine optimization).

Errors vs warnings

The distinction matters, so don't treat the two alike:

  • Errors mean a required field is missing or malformed. The item is ineligible for rich results until fixed. Fix errors always.
  • Warnings mean a recommended (optional) field is absent. The item is still eligible, but adding the field could enrich the result. Fix warnings when the data genuinely exists; never invent values just to silence a warning.

Common causes of errors with typical fixes: a price field left empty on Product schema (fill it in the SEO Settings sheet), a date in the wrong format (use the typed fields; as of v0.0.14 date-time, telephone, and email fields render correctly formatted values), or duplicate markup because two SEO plugins are both printing schema (see duplicate meta output).

Re-testing after fixes

  1. Make the fix in the Schema screen or the post's SEO Settings sheet and save.
  2. If you use a caching plugin or CDN, purge the cache for that URL so the validators fetch the updated HTML.
  3. Re-run the Rich Results Test on the same URL.
  4. Repeat until errors are gone and remaining warnings are ones you have consciously accepted.

Keep the loop tight: one fix, one re-test. Changing five things between tests makes it hard to know what worked.

Monitoring in Search Console

Validators check one page on demand; Google Search Console monitors your whole site continuously. In Search Console, the Enhancements section (and related structured-data reports) shows, per rich-result type, how many pages are valid, how many have warnings, and how many have errors, as Google discovers them during normal crawling.

Check it monthly, and after any large schema rollout. When you fix an issue at scale, use the report's Validate Fix button so Google re-crawls the affected pages and tracks the fix's progress. Pair this with your site health score, which includes schema markup as one of its seven audit areas, so regressions surface even between manual checks.

FAQ

The validator shows no structured data at all. What's wrong?

First, view the page source and search for application/ld+json to confirm the markup is present. If it's missing, check that a schema type is actually configured for that page in the Schema screen or its SEO Settings sheet. If it's present but the validator can't see it, a cache or a robots rule blocking the tool is the usual culprit; see sitemap troubleshooting for general crawler-access debugging and the robots.txt editor for access rules.

Do warnings hurt my rankings?

No. Warnings flag missing optional fields. Add the field if you have real data for it; otherwise a warning can be a permanent, harmless resident of your report.

Eligibility is not a guarantee. Google decides per query whether to show a rich result, and some types no longer have a rich result at all. HowTo went in 2023, Course info in 2025 and FAQ in May 2026, and valid markup won't bring them back, so check those types with the Schema Markup Validator instead. See FAQ & HowTo schema for the honest picture. Valid markup is the part you control.

How often should I validate?

After every schema change on the affected pages, and via Search Console's Enhancements reports on an ongoing basis for the site as a whole.

Common questions

What is a rich snippet validator?
It is a tool that reads the structured data on a page and reports whether Google can parse it and which rich result it qualifies for. Google runs two: the Rich Results Test, which answers "will this earn a rich result", and the Schema Markup Validator, which answers "is this valid schema.org". They disagree often, because valid schema and eligible-for-rich-results are different questions.
Why does my schema validate but show no rich result?
Validation only proves the markup parses and carries the required properties. Google decides separately whether to show a rich result, and it declines when the markup describes something not visible on the page, when the page is not indexed, or simply when it judges the result unhelpful for the query. Valid markup makes a rich result possible, never guaranteed.
Do I need to validate every page?
No. Validate one page per template. Schema is generated from the template, so the blog post you test stands in for every blog post. Re-test a template after you change the theme, the plugin, or anything that writes markup.
Was this page helpful?
Still stuck? Contact support