SEO
Validating schema with Google Rich Results Test — the actual workflow
The Rich Results Test is the only validator that matches what Google sees in production. The workflow, the common warnings, and the fixes that actually work.
26 April 2026 · 2 min read
Quick frame: Google's Rich Results Test (search.google.com/test/rich-results) is the only validator that reflects what Google's production parser sees. Schema.org's own validator is permissive — pass it, then run Rich Results Test for the real check.
Why Rich Results Test specifically
Schema.org validators check syntax (is the JSON well-formed, are the required fields present?). Rich Results Test goes further: it tests whether your markup actually qualifies for any of Google's rich result types. A page can pass schema.org and fail Rich Results, because qualifying requires more than syntactic validity.
The validation workflow
- Generate the schema with a schema generator.
- Paste into your page's
<head>. - Run the live URL (or pasted code) through Rich Results Test.
- Resolve any errors (blocking) — page won't qualify until fixed.
- Resolve any warnings (non-blocking) — page qualifies but with reduced visibility.
- Re-test after each fix.
Errors vs warnings
Errors (red) — blocking. Page does not qualify for rich result.
Common errors:
- Missing required field (e.g., Article without headline).
- Wrong data type (string where URL expected).
- Invalid date format.
Warnings (yellow) — non-blocking. Page qualifies but Google flags suboptimal patterns.
Common warnings:
- Missing recommended field (e.g., Article without author).
- Logo too small.
- Description over 5000 characters.
The most common fixes
| Error | Fix |
|---|---|
| "Missing field 'author'" on Article | Add author: { @type: Person, name: ... } |
| "Image URL is not crawlable" | Replace with absolute https URL on a public host |
| "Date is invalid" | Use ISO 8601 (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS+05:30) |
| "Schema does not match visible content" | Hidden FAQ / hidden breadcrumb — make them visible |
Re-testing after deployment
Run Search Console → Enhancements → look at the structured-data report. Errors there appear 1–4 weeks after Google re-crawls. Investigate and fix in the source, then trigger a fresh crawl via URL Inspection.
Beyond schema: the bigger picture
Schema is one signal of many. Combine with article schema, breadcrumb schema, FAQ schema, Organization schema and LocalBusiness schema for a full bundle. The microdata-vs-JSON-LD discussion is in JSON-LD vs Microdata vs RDFa.
FAQ
Q. Why does my schema validate but no rich result shows? A. Validation only confirms eligibility. Google decides whether to actually show the rich result based on site quality, user intent and SERP layout.
Q. Does Rich Results Test work for unpublished pages? A. Yes — paste raw HTML or JSON-LD code directly. No need to publish first.
Q. How often should I re-validate? A. After every schema change, after every CMS upgrade, and quarterly as a baseline check.
Try the free tool
Article Schema Generator
JSON-LD Article / BlogPosting / NewsArticle — paste, copy, done.
Open Article Schema Generator →