Rich-Results Errors, Google Search Console

Structured-data errors that strip your pages of enhanced SERP features such as price, rating and availability snippets. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Rich Results

Structured-data errors blocking enhanced SERP features (price, rating, availability snippets). Each lost rich result is lost CTR.

At a glance

A near-real-time count of invalid structured-data items across your property, as reported by Google Search Console’s Rich Results and Enhancement reports. When a Product, Review, Breadcrumb, FAQ or Article item has an error, Google drops the enhanced result (star ratings, price, in-stock badge, FAQ accordion) and falls back to a plain blue link. Plain links earn materially lower organic CTR than rich results, so every error here is a direct, measurable bleed on organic clicks. This is a fire-alarm card, not a trend chart: any non-zero error count on revenue-critical schema (Product, Article) should be triaged the same day.

What it tracks	The number of items with structured-data errors that block eligibility for rich results, taken from Search Console’s per-enhancement reports (Products, Merchant listings, Review snippets, Breadcrumbs, FAQs, How-to, Articles, Sitelinks search box, Videos and similar). An “error” is a required-property failure or invalid value that makes the item ineligible, distinct from a “warning” (recommended property missing) which keeps the item eligible.
Data source	detail: Structured-data errors blocking enhanced SERP features (price, rating, availability snippets). Each lost rich result is lost CTR. Pulled from the Search Console Enhancement and Rich Results status reports for the connected property.
Time window	RT (real-time): refreshed on the standard pulse cycle and compared against the most recent Search Console validation state, not a rolling historical window. Search Console itself revalidates on its own crawl cadence, so the underlying state can lag the live page (see Reconciling below).
Alert trigger	>0 on Product or Article schema. Any error item on Product or Article structured data trips the alert, because these two types drive the highest-CTR enhanced results (price/rating/availability for Product, headline/date/author for Article). Errors on lower-impact types raise an amber note rather than a hard alert.
Sentiment	Lower is better. Zero errors is the only healthy state; the card does not reward “fewer errors than last week” if any revenue-critical type is still failing.
Roles	owner, marketing

Calculation

The card sums item-level errors across every structured-data enhancement type Search Console reports for the property. It does not count valid items, and it does not count warning-only items (those remain eligible for rich results). The headline number is therefore:

Rich-Results Errors = Σ (error items) across all enhancement reports

Two refinements matter for how the alert behaves:

1. Type weighting for the alert. The hard alert is gated on Product or Article errors (>0 on Product or Article schema) because these are the highest-value enhanced results for an ecommerce or content property. Errors on Breadcrumb, FAQ, Sitelinks search box and similar are still counted in the headline total but surface as amber rather than red.
2. Error vs warning. Search Console separates “invalid” (error: required property missing or wrong type, item ineligible) from “valid with warnings” (recommended property missing, item still eligible). This card counts only the error tier. A page with a missing aggregateRating warning still shows its price snippet, so it is not bleeding CTR the way an error item is.

Because the source is a validation state rather than a clicks metric, the value steps rather than trends: it holds flat until Google revalidates after a crawl, then jumps as a batch of items is reclassified.

Worked example

A UK homeware retailer runs a Shopify storefront with Product structured data injected by a theme app. Search Console is connected to Vortex IQ. On 14 Apr 26 a developer ships a theme update that changes the price formatting from "49.99" to "£49.99" inside the price field of the Product schema. Google requires price to be a number without a currency symbol, with currency carried separately in priceCurrency.

Within two crawl cycles, Search Console reclassifies the affected product pages. The card moves as follows:

Date	Product error items	Article error items	Card state	Note
13 Apr 26	0	0	Green	Healthy baseline
15 Apr 26	1,840	0	Red alert	Theme update broke price formatting on every product
16 Apr 26	1,840	0	Red alert	Errors confirmed in Products enhancement report
22 Apr 26 (fix shipped 20 Apr)	60	0	Amber	Revalidation in progress, most items passing
26 Apr 26	0	0	Green	Validation complete, price snippets restored

Three observations for triage:

1. The card fired before any clicks card did. Organic CTR for those product queries fell over the following days as the price snippet vanished and listings reverted to plain links, but the clicks dip is a lagging, noisy signal spread across thousands of queries. The structured-data error count is a single, unambiguous number that fired on 15 Apr, days before the CTR damage was visible in aggregate.
2. The fix is shipped once, but recovery is gated by Google’s crawl. After the developer corrected the price field on 20 Apr, the merchant used Validate Fix in the Search Console Products report to request priority revalidation. Even so, full recovery to zero took until 26 Apr because Google revalidates in batches across the affected URL set.
3. Estimate the cost in clicks, not just items. With ~1,840 product pages losing their price/rating snippet and an assumed 0.8 percentage-point CTR drop on the affected impressions, the merchant lost a meaningful slice of organic product clicks for roughly ten days. Pair this card with CTR by Page to quantify the actual CTR delta on the affected URLs.

Rule of thumb. Any non-zero count on Product or Article: treat as a same-day incident, ship the schema fix, then click Validate Fix in Search Console to shorten the recovery tail.

Sibling cards merchants should reference together

Card	Why pair it with Rich-Results Errors
Rich Results CTR	The upside this card protects. When errors clear, watch rich-result CTR recover here.
Rich Results Impressions	Impressions of enhanced results collapse as items go invalid; the quickest corroboration of an error spike.
Rich Results Performance	The per-type breakdown. Use it to see which appearance type is bleeding clicks while this card flags the error.
Search Appearance Types	Confirms which enhanced appearances you currently win, so you know which errors actually cost you SERP features.
CTR by Page	Quantifies the CTR loss on the exact URLs whose structured data broke.
Mobile Usability Errors	The sibling validation-state alarm. Both are crawl-gated, page-level eligibility errors.
Indexed Pages	A page must be indexed to be eligible for rich results; an error spike alongside a deindex is a deeper template fault.

Reconciling against the source

Where to look in Google Search Console:

Search Console left nav, under the property: the Enhancement reports (Products, Merchant listings, Review snippets, Breadcrumbs, FAQs, How-to, Articles, Videos, Sitelinks search box). Each report has a status chart and an Invalid / Valid with warnings / Valid breakdown. The card’s headline number is the sum of the Invalid counts across these reports.

The Rich Results Test (single URL) and URL Inspection confirm the live, on-page structured data for one URL, which is the fastest way to see whether your fix is correct before you ask Google to revalidate the whole set.

For programmatic checks, the URL Inspection API returns per-URL rich-result verdicts, and the Search Analytics API (searchType plus the SEARCH_APPEARANCE dimension) shows clicks and impressions for enhanced appearances, which is the click-side counterpart to this eligibility count.

Why our number may legitimately differ from a manual check:

Reason	Direction of divergence
Crawl lag. Search Console revalidates on its own crawl cadence. A fix shipped today may keep showing errors for days until Google re-crawls; equally, a freshly broken template may not show errors until the next crawl.	Card can lead or lag the live page by 2 to several days
Error vs warning tiering. We count only the Invalid (error) tier; Search Console also surfaces “Valid with warnings”. If you compare our number to the report’s total flagged items, ours will be lower.	Our count lower than “all flagged”
Type weighting in the alert. The hard alert keys on Product and Article only; the headline total still includes all types. A green-ish headline with a red alert is possible if non-critical types are clean but Product has one error.	Alert stricter than headline
Validation-in-progress states. While Google revalidates after a Validate Fix request, items can sit in a transitional state; counts wobble until validation completes.	Temporary over- or under-count
Data delay. Search Console data is typically 2 to 3 days delayed, rare-query data is anonymised, and report tables cap at 1,000 rows, so a very large error set may need the API or export to enumerate fully.	Card aligned to delayed source, not the live HTML

Cross-connector reconciliation: if errors spike here and organic clicks fall on the same URLs in Top Pages by Clicks, the rich-result loss is the likely cause. For root-cause tracing across the deploy that broke the schema, use Vortex Mind.

Known limitations / FAQs

The card shows zero errors but my product listings still have no star ratings. Why? Zero errors means nothing is invalid; it does not mean every page is eligible. Three common causes: (a) the page is valid but Google chooses not to show the enhancement for that query (rich results are never guaranteed), (b) the rating data is present but the item carries a warning, not an error, that suppresses the snippet in practice, or (c) the page is not indexed. Check Indexed Pages and run the Rich Results Test on a sample URL.

I fixed the structured data days ago but the error count has not dropped. Is the card broken? Almost certainly not. Recovery is gated by Google’s crawl and revalidation, not by your deploy. Confirm the fix is live with the Rich Results Test on a sample URL, then use Validate Fix in the relevant Enhancement report to request priority revalidation. Counts then drain over subsequent crawl cycles.

What is the difference between an error and a warning here? An error (Invalid) means a required property is missing or has an invalid value, so the item is ineligible for the rich result. A warning (Valid with warnings) means a recommended property is missing, but the item stays eligible. This card counts errors only, because warnings do not strip the SERP feature.

Why does the alert only fire on Product and Article and not on FAQ or Breadcrumb? Product (price, rating, availability) and Article (headline, date, author) drive the highest-CTR enhanced results for ecommerce and content sites, so they are revenue-critical. FAQ, Breadcrumb and similar types still count toward the headline total and raise an amber note, but they do not trip the hard alert by default. You can adjust this in the Alert Rules tab per profile.

Can a single broken template create thousands of errors overnight? Yes. Structured data is usually templated, so one bad field in a theme or component breaks every page that renders it. That is why this card is built as a fire-alarm: a single deploy can move it from zero to thousands in one crawl cycle, as in the worked example.

Does the 1,000-row cap affect this card? The headline error count is a sum, not a row listing, so it is not capped. The cap bites when you try to enumerate every affected URL in the Search Console UI table; for the full URL list on a large error set, export from Search Console or pull the URL Inspection API.

Will deindexed or noindex pages show up as errors? No. A page that is not indexed is not eligible for rich results and is reported under indexing, not as a structured-data error. If errors and a deindex happen together, suspect a deeper template or deployment fault and check indexing first.

---

Tracked live in Vortex IQ Nerve Centre

Rich-Results Errors is one of hundreds of KPI pulses Vortex IQ tracks across Google Search Console and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.