Rich Result Is Invalid: How to Fix Schema Validation Errors

What this check flags

This check fires when a page has structured data on it, but that markup is malformed or missing required properties — so it fails validation and the page can't earn the rich result it was built for. The stakes: you did the work to add schema, but a broken value or an absent required field means Google won't render the star ratings, FAQ dropdowns, recipe cards, or price snippets in search — you get the plain blue link while a competitor with valid markup gets the eye-catching one.

A real example, and the fix

A recipe site added Recipe schema to every post and expected the rich cards with cook time and ratings. The Rich Results Test threw an error on all of them: "Missing field 'recipeIngredient'" plus a warning that prepTime wasn't a valid ISO 8601 duration. The markup had this:

"prepTime": "15 minutes",
"cookTime": "PT30M"

cookTime was correct; prepTime was a human string Google can't parse. And recipeIngredient — a required property — had been left out entirely because the CMS template didn't map it. Two fixes: format the duration correctly and add the required field.

"prepTime": "PT15M",
"cookTime": "PT30M",
"recipeIngredient": [
  "2 cups flour",
  "1 tsp salt",
  "3 large eggs"
]

PT15M is ISO 8601 for "15 minutes." Once the duration was valid and the required ingredient array was present, the Rich Results Test went green and the recipe cards started appearing. The pattern here is the usual one: a required field missing, plus a value in the wrong format.

Errors vs. warnings — and which block the rich result

The Rich Results Test distinguishes errors from warnings, and confusing the two wastes hours. Here's the split.

Errors are hard blocks — clear every one. Warnings weaken eligibility or richness but won't stop the rich result; treat them as a second pass.

How to detect it on your own site

1. Run the Rich Results Test. Paste the URL or the raw markup into Google's Rich Results Test. It tells you which rich-result types the page qualifies for and lists every error and warning with the exact property at fault.
2. Use the Schema Markup Validator. For general schema.org correctness beyond Google's rich-result types, validator.schema.org catches syntax and vocabulary problems the Rich Results Test skips.
3. Check GSC's enhancement reports. Search Console has per-type reports (Products, FAQs, Recipes, Breadcrumbs) that flag invalid items at scale across your whole site, not just one URL. Cross-reference with the Page Indexing report.
4. Inspect the rendered markup, not the source. If schema is injected by JavaScript or a tag manager, validate the rendered DOM — use URL Inspection's rendered HTML in GSC, because the source view won't show it.

How to fix it

1. Read the exact error. The Rich Results Test names the property and the problem. "Missing field X" means add it; "Invalid value in field Y" means fix the format.
2. Add every required field. Check the schema.org type's Google requirements and make sure all required properties are present and populated with real values — not empty strings.
3. Fix value formats. Durations as ISO 8601 (PT30M), dates as ISO 8601, prices as numbers, URLs as absolute. Wrong-format values fail as hard as missing ones.
4. Match markup to visible content. Schema must describe what's actually on the page. Marking up a rating the user can't see is a policy violation that can cost you the rich result and more.
5. Re-test until green. Fix, re-run the Rich Results Test, repeat until zero errors, then request re-indexing so Google re-evaluates. For a deeper walkthrough see validating and debugging structured data.

Common mistakes

• Fixing warnings while ignoring the errors that actually block the rich result.
• Using human-readable strings ("30 minutes," "Jan 5") where ISO 8601 is required.
• Validating the page source when the schema is injected by JavaScript and only exists in the rendered DOM.
• Marking up ratings, prices, or content that isn't visible on the page — a guideline violation, not just an error.

FAQ

What's the difference between an error and a warning?

An error — a missing required field or an invalid value — blocks the rich result entirely. A warning flags a recommended-but-optional field; the rich result can still show, just less richly. Clear errors first.

I fixed the markup but the rich result still isn't showing. Why?

Valid markup makes you eligible; it doesn't guarantee display. Google decides per-query whether to show a rich result, and it needs to re-crawl the fixed page first. Confirm zero errors, request re-indexing, and give it time.

Do I need both the Rich Results Test and the Schema Validator?

They serve different jobs. The Rich Results Test checks eligibility for Google's specific rich-result types. The Schema Markup Validator checks general schema.org correctness. Use the Rich Results Test for "will I get the rich result," the validator for "is my schema syntactically sound."

My schema is added by a plugin or tag manager — does that matter?

Only in how you validate it. JavaScript-injected schema won't appear in the page source, so validate the rendered HTML instead. The markup itself is judged the same way.

Can invalid structured data hurt me beyond losing the rich result?

Marking up content that doesn't match what's visible — fake reviews, hidden prices — can trigger a manual action against structured data. A plain validation error just costs you the rich result; a guideline violation can cost more.