Google reports rich result errors

SeverityMedium

ScopeWhole site

EffortMedium

Verified byManually

Rule keyrich_result_errors

Short answer

Google’s URL Inspection says these pages contain structured data items with errors (rich result verdict “FAIL”). An item with an error is not eligible for its rich result, so the enhanced listing — review stars, price, breadcrumbs, event dates and so on — does not appear. The evidence lists Google’s own error messages.

Why it matters

This is Google’s verdict, not an estimate: it comes from the same inspection that powers Search Console. Errors usually mean a required property is missing or has an invalid value (a price without a currency, a rating outside its range, a date in the wrong format). Warnings are not reported here, because they do not block the rich result.

How Glimana detects it

Glimana asks the URL Inspection API about your most important pages every day (within Google’s quota of 2,000 per property). Since 1 November 2026 it also stores the rich result verdict and up to five error-level issues from each answer. The rule lists pages whose latest verdict, at most 45 days old, is FAIL. Pages are not re-inspected just for this rule.

How to fix it

Find the affected pages in Glimana. Open Issues › Google reports rich result errors. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
Apply the fix on your platform.

For each page, read the errors in the evidence and fix the property Google names, using values that are visible on the page. Then test one page per template in Google’s Rich Results Test; a template fix usually fixes every page that uses it.

WordPressShopifyCustom code

Structured data usually comes from the SEO plugin (Yoast, Rank Math), a schema plugin and the theme at the same time. Find which one outputs the failing item, fill in the missing fields in its settings (for products, WooCommerce product data), and turn off duplicate outputs.

Product and offer markup comes from the theme’s structured-data snippet and from apps (reviews, bundles). Check that the price, currency and availability come from the product object and that review apps output ratings in the required range.

Generate JSON-LD from the same data that renders the page, validate it in CI with a schema validator, and match Google’s required properties for the type (see the type’s documentation under Search Central’s structured data gallery).
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with curl -s https://your-domain/page | grep -i '<title\|canonical\|robots' that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached.
Verify in Glimana. In Search Console, open the matching rich result report and click Validate fix; Google re-crawls the affected pages. Glimana picks up the new verdict at the next inspection of each page, and the issue closes when no page has a FAIL verdict.

How the fix is verified

Verification is manual: the issue closes when Google’s next inspection of each page no longer returns a FAIL verdict.