The pattern in one line
Your structured data has errors, so pages that could earn rich results appear as plain blue links.
Rich results need structured data that is valid and matches the visible page. Missing required fields, mismatched content, and broken syntax stop eligibility, and even valid markup does not guarantee a rich result. Run the markup through Google's testing tools, fix errors before warnings, and keep it in line with what the page shows.
What this looks like
A set of pages once showed review stars or product details in results. Now they show a plain title and description. Search Console lists errors in the structured data report, and the number grows with each new page.
Structured data tells search engines what a page contains: a product, a recipe, a local business, a set of questions. For some types, valid markup makes a page eligible for an enhanced listing, and errors can remove that eligibility. The common ones are missing required properties, wrong formats for prices and dates, and markup describing content a visitor cannot see.
Most large error counts come from a single source. A plugin outputs the same broken field on every product, or a theme template leaves a required property empty. Fixing the template clears hundreds of pages at once.
Check again after every theme or plugin update. Markup often breaks when a template changes, and the first sign is a growing error count in Search Console. A short check after each update catches the problem before rich results disappear.
Valid markup is still not a promise. Search engines choose whether to show a rich result.
Common traits
- Google Search Console reports errors in a structured data or rich results report
- Pages that used to show stars or product details now show plain listings
- The schema was added by a plugin or theme and never reviewed
- The markup describes content that is not visible on the page
- Errors appear on many pages at once, often from 1 template
Why it happens
-
A template outputs invalid fields
1 broken template repeats the same error on every page that uses it.
-
Required properties are missing
Types such as products and reviews need specific fields to qualify.
-
Markup does not match the page
Marking up content that is not visible, or values that differ from the page, breaks the rules for rich results.
-
Several plugins add overlapping markup
Duplicate or conflicting schema from more than 1 source can confuse the result.
How to confirm it in Doily
- Run a site audit and review the ranked fixes, noting which affect whole templates.
- Open rank tracking and check SERP features for the keywords where rich results disappeared.
- Compare against the structured data reports in Google Search Console and Google's Rich Results Test, which validate the markup itself.
- Re-run the audit after fixes and compare the issue list.
Fixes to try
| Fix | Impact | Effort |
|---|---|---|
| Fix errors in the template or plugin that produces the markup | High | Medium |
| Add required properties before recommended ones | High | Low |
| Make the markup match the visible content on the page | High | Low |
| Remove duplicate schema output from extra plugins | Medium | Low |
| Validate each fix in Google's testing tools before rolling it out | Medium | Low |
| Mark up only the types that suit the page | Low | Low |
What to watch after
- Error and warning counts in Search Console
- Pages with valid markup
- Rich result appearances in rank tracking SERP features
- New errors after theme or plugin updates
Questions
Does valid schema guarantee a rich result?
No. Valid markup makes a page eligible. Search engines decide whether to show an enhanced result. Google stopped showing FAQ rich results in Search on May 7, 2026, whatever the markup.
Should I fix warnings or errors first?
Errors first. They block eligibility. Warnings point to optional improvements.
Does schema help AI engines?
It can make the content of a page easier to interpret, but nothing guarantees it changes what an engine says. Google says no special markup is needed for its AI features, so the visible content has to be clear on its own.
