Structured Data for Rich Results in GSC — Monitor and Fix Snippet Issues

Why are your rich snippets missing from Google?

You've implemented structured data on your site, but rich results aren't showing. Or Google shows them inconsistently, and you don't know why. This is one of the most common problems we see when clients come to us: the schema markup exists, but it's not validated, not monitored, not maintained. The result? Wasted hours and lost potential clicks.

We, at Meteora Web, always start from the practical side: if structured data doesn't generate a rich result, it doesn't exist. And the Rich results report inside Google Search Console (GSC) is the tool that tells you exactly what's wrong. In this guide, we'll show you how to use it, what to look for, and how to fix errors — no unnecessary theory.

What are rich results and why monitor them in GSC?

A rich result is a search result enhanced with extra visual elements: review stars, price, availability, breadcrumbs, FAQ drop-downs, recipes, events, videos. It's not a prize: it's the result of well-crafted structured data that Google recognizes.

Monitoring them in Google Search Console is critical for two reasons:

• Continuous validation: Google may stop showing a rich result overnight if the markup becomes invalid or the algorithm changes.
• Error diagnostics: GSC lists every failure with URL, schema type, and error details. Saves hours of manual debugging.

We see it every day: an e-commerce client had implemented Product schema, but after a theme update the price was no longer passed in a valid format. The Rich results report showed it immediately. Without it, months could pass unnoticed.

How to find failed rich results in Google Search Console?

1. Open the Rich results report

After logging into GSC for your property, click on Rich results in the left menu. You'll see an overview with two charts: one for trend over time, one for item types (Product, FAQ, Recipe, etc.).

2. Filter by errors and warnings

Below the chart you find the list of detected structured data types. For each, GSC shows three indicators:

• Errors: markup that Google can't interpret or violates guidelines.
• Warnings: valid markup but with recommendations (e.g., optional field missing).
• Valid items: pages that produce a correct rich result.

Click on a type with errors. A table appears with the affected URLs and error description.

3. Inspect a specific URL

Click on a URL. GSC shows the structured data as it parsed it and highlights the problematic field. You can also use the Rich Results Test Tool (hammer icon in GSC) to validate a live page.

// Example error: missing 'price' in Product schema
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Running shoe",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "EUR",
    // price missing! This generates an error.
  }
}

Which structured data errors to check first in GSC?

Not all errors are equal. We recommend starting with these three, as they are the most frequent and impactful:

Missing required field

Every schema has required fields. For Product you need name and offer with price. For FAQPage you need question and answer. GSC tells you exactly which field is missing.

Invalid field value

For example, price must be a decimal number with a dot (e.g. 29.99), not a comma (29,99). Or availability must be a URL from schema.org vocabulary (e.g. https://schema.org/InStock), not a string like "available".

Wrong JSON-LD nesting

Often developers nest objects incorrectly. For instance, placing offers inside @graph without linking to Product. Always use Google's official validator to cross-check.

How to fix structured data to get rich results in GSC?

1. Read the full error

Don't just read the title: expand the error in GSC and read the incriminated code line. Google gives context. If unclear, use the test tool with the URL or code.

2. Edit the markup on your site

If you use a WordPress plugin like Yoast SEO or Rank Math, verify the version is updated and field mapping is correct. We prefer to handle structured data via theme or custom code with Laravel or plain PHP, because we have full control and no dependency on external updates.

3. Request re-validation in GSC

After fixing the error, go back to the Rich results report and click Validate for the URL or the entire group. Google re-checks the pages and updates the status. It can take from minutes to a few days.

// Example of fixed Product schema
{
  "@context": "https://schema.org/",
  "@type": "Product",
  "name": "Running shoe",
  "offers": {
    "@type": "Offer",
    "price": 79.99,
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/running-shoe"
  }
}

What tools to use besides GSC to check rich results?

Google Search Console is not the only ally. We use it as a first filter, then we add:

• Rich Results Test Tool: test URL or code snippet. Essential for quick debugging.
• Schema Markup Validator: an open tool from schema.org that gives extra details.
• Chrome DevTools: in the Network panel, filter for requests to search.google.com/structured-data/testing-tool to see responses.

For those managing many URLs, we recommend writing a Python script that queries the GSC API and generates an automated error report. We've done it for clients with thousands of products — the time saving is huge.

What to do now

1. Log into Google Search Console and open the Rich results report for every property of your site.
2. Identify the three schema types with the most errors and click to see the URLs.
3. Fix one error (e.g., add the missing price) and request validation.
4. Set a weekly reminder to check the report: even one error can make rich results disappear.
5. Incorporate automated testing into your deployment (e.g., a GitHub workflow that runs the validator on every new page).

If you need help cleaning up your site's structured data, contact us. We're used to working on inherited projects with messy markup. We start from the Rich results report and fix it together.

For more in-depth knowledge, read our Pillar Guide to Advanced Google Search Console (Italian version).