Rich Results status troubleshooting

How the Rich Results status report works

In Google Search Console, the Rich results report (under Enhancements) lists the *Page types* you have implemented: Recipe, Article, Product, Breadcrumb, and so on. (FAQ rich results were retired by Google in 2026 and no longer appear in Search.) For each type it shows a status per URL. Because the UI moved away from detailed "item" numbering, the two lines you actually track are:

The structured data article covers the markup side; here the focus is the report itself and its decisions.

A status history line shows changes over time: a page flips from Eligible to Enhancement required (a template edit removed a field), or from Enhancement required to Eligible (a fix landed and Google re-parsed). The report does not tell you why a specific URL dropped: that is the job of the URL inspection tool, which shows the live rendered page and its detected structure.

The Status report is a mirror, not a diagnosis

This is the most important mental model: the Rich results report mirrors what Google successfully parsed. It does not test your data. When you fix a field and resubmit, the report updates only after Google re-crawls and re-parses. So:

1. Use URL Inspection for the per-URL truth. "View Crawled Page" shows exactly what Google rendered and the rich-extraction checklist for that URL.
2. The status aggregate lags the test. A freshly deployed schema may still show the old status for hours while URL Inspection already sees the new markup.
3. A page can be Eligible and still not show. Eligibility is necessary, not sufficient. Competition and CTR affect whether Google displays the rich result; a Recipe with low relevance stays plain even when status says Eligible.

Symptom: a page drops from Eligible to a status you don't want

Work through in order:

1. Pin the exact URL from the drop column, then open it in URL Inspection. Look at the page's source as fetched, not the live DOM.
2. Read the specific item error. The report names the property and value, for example a Schema validation issue such as "name" must be a string. Search that exact line for the fastest known fix.
3. Compare the failing property prefix against the type's requirements: Recipe requires name and image (plus ingredient and step fields as applicable), a Product requires a conforming price, and Article requires headline plus author or publisher. Use the structured data types doc for the exact property lists.
4. Fix in the raw data (the CMS or template) so regenerated pages carry the change; then retest two URLs minimum, one with the error and one not.
5. Allow the next crawl to re-fetch (the crawl-stats guide tells you how the crawl frequency behaves), then re-check status after it reports a re-test.

Rich Results Test vs the report

The Rich Results Test (richresults.google.com) is the tool you want for "did my markup parse". Give it a URL and it returns "Not eligible" plus warnings, or a deep tree of detected items and enhancements. The report and the test can disagree for a page that is live but not yet re-parsed; trust the test on markup, the report on history.

The fix cadence

Because "eligible" is a status, stack the normal SEO loop: fix the underlying markup, retest, then resubmit indexing for the changed URL (request indexing covers that). The enhancements report article is the broader view of all Structured Data features in the account, and the structured data types doc lists which item errors are worth fixing at all.