GSC Rich Results Report: Debug Structured Data at Scale

Most Structured Data Problems Are Silent

You add schema markup to your pages. Google crawls them. And then nothing happens - no rich results, no warnings, no feedback. You assume it's working.

It often isn't.

Google Search Console's Rich Results report is the closest thing to real-time feedback you'll get on your structured data. It tells you which pages are eligible for rich results, which ones have errors blocking them, and which have warnings that are quietly degrading your appearance in search.

Most site owners never open it. That's a mistake. Rich results - including review stars, FAQ dropdowns, recipe cards, product pricing, and event listings - can lift click-through rates by 20-30% for the same ranking position. Broken markup means leaving that advantage on the table.

Where to Find the Rich Results Report

Open Google Search Console and look at the left sidebar. Under the “Enhancements” section, you'll see a list of structured data types Google has detected on your site. Each one is a separate report.

The types shown depend entirely on what markup you've deployed. A news publisher might see “Articles” and “Breadcrumbs.” An e-commerce site will likely see “Products” and “Reviews.” A restaurant or event site might see “Events,” “Recipes,” or “Local Business.”

If you don't see any Enhancement reports, one of two things is happening: either you haven't implemented structured data yet, or Google hasn't crawled enough of your pages to detect it. In the second case, using the URL Inspection Tool on a page that has markup is the fastest way to confirm whether Google can see it. The URL Inspection Tool guide covers that process in detail.

The Three Status Categories That Matter

Every Rich Results report breaks your pages into three groups. Understanding the difference between them is where the real diagnostic work starts.

Errors

These are pages where Google found structured data but won't show rich results because of a critical problem. Errors are blocking - they actively prevent the enhancement from appearing in search.

Common error types include missing required properties (like leaving out a product's “name” or a review's “ratingValue”), using the wrong data type for a field, or having markup that references URLs Google can't access.

Fix errors first. A page with errors earns zero benefit from its structured data investment.

Valid with Warnings

Warnings are more nuanced. Google can still show rich results for these pages, but the markup is incomplete or uses deprecated properties. You're getting partial credit.

A product page missing optional but recommended properties like “brand” or “sku” might still show a star rating, but won't qualify for enhanced Shopping features. A recipe page without “totalTime” can still appear in recipe cards but misses certain filter eligibility in search.

Warnings are worth fixing systematically, especially if you have many pages in this state. The ROI on fixing warnings is lower than fixing errors, but it's real.

Valid

Valid pages have structured data Google considers complete and correct. They're eligible for rich results - though “eligible” doesn't guarantee Google will show them. Google still decides whether to display rich results based on query context, result page composition, and other signals.

Don't confuse “valid” in GSC with “showing rich results in search.” Use the Search Appearance filters in GSC to see which valid pages are actually generating impressions with rich results applied.

How to Diagnose Errors Efficiently

When you click into an error group inside the Rich Results report, GSC shows you the specific error type and the affected URLs. This is where most people stop - they read the error description, fix one page manually, and move on.

That approach works when you have five pages with errors. It doesn't scale to five hundred.

Start by grouping errors by type, not by URL. If “Missing field 'offers'” affects 300 product pages, that's a template problem. Fixing the template fixes all 300 at once. If “Invalid value for field 'ratingValue'” affects only a handful of pages, those probably have data quality issues in your CMS or review feed that need individual attention.

Click on any specific URL in the error list and use the URL Inspection Tool to view a live rendering. GSC will show you the actual structured data Google parsed from that page, highlighted with the specific property causing the error. This live test is far more reliable than re-reading your code - what you wrote and what Google parsed aren't always the same, especially with JavaScript-rendered markup.

The Most Common Errors by Markup Type

Product markup errors almost always come down to missing “offers” properties. Google requires price and availability data for product rich results. If your product pages pull pricing dynamically from a JavaScript-rendered component, there's a real chance Googlebot isn't seeing it. Test with the URL Inspection Tool's “Test Live URL” option, which renders JavaScript before parsing.

Review and aggregate rating errors typically involve “ratingValue” or “reviewCount” being absent or formatted incorrectly. A common mistake is passing “4.5 out of 5” as a string instead of just “4.5” as a number.

FAQ markup errors often stem from pages where FAQ items exist in the markup but the actual visible content doesn't match - Google's guidelines require that FAQ structured data reflect questions and answers genuinely visible on the page. Hiding FAQ content from users but including it in schema is a policy violation, not just a technical error.

For more on FAQ implementation, the FAQ schema guide covers the exact property requirements Google enforces.

Fixing Warnings: Which Ones Are Worth Your Time

Not all warnings have equal impact. Prioritize based on which properties, if added, would unlock additional rich result features.

For product pages, adding “brand,” “gtin,” and “sku” properties can qualify products for merchant-focused rich results in Google Shopping. The e-commerce structured data guide breaks down which properties matter most for Shopping eligibility.

For event markup, “eventStatus” and “eventAttendanceMode” became recommended properties after Google added virtual and hybrid event support. Pages without these are still valid but miss filters Google uses to surface events by attendance type.

For article markup, “author.url” pointing to a credible author profile page is now a recommended property tied to Google's E-E-A-T signals. Articles missing this property won't lose rich result eligibility, but they may lose ground on trust signals that influence ranking.

Tracking Fixes: Using the Trend Line

After fixing structured data errors, GSC doesn't update instantly. Google needs to recrawl and reprocess the affected pages before the error count drops. For high-traffic pages, this can happen within days. For lower-priority pages, it might take weeks.

Use the trend line in each Rich Results report to track progress over time. You should see the error count declining and the “Valid” count rising as Google recrawls fixed pages. If the error count stays flat after two to three weeks, either the fix didn't deploy correctly or Google isn't recrawling those pages at the expected rate.

To force faster recrawling after significant fixes, submit the affected URLs for reconsideration using the “Validate Fix” button in GSC. This signals Google to prioritize recrawling those URLs. It's not guaranteed to speed things up, but it helps for critical pages like homepage schema or high-value product templates.

Comparing trend lines across date ranges is much easier if you've built a regular reporting cadence. The date range comparison approach covered in the GA4 context applies equally to tracking GSC metric changes over time.

Scaling Structured Data Audits Across Large Sites

If your site has thousands of pages, manually reviewing individual URLs in the Rich Results report isn't practical. You need a systematic approach.

Export the affected URLs from GSC using the “Export” button in any error or warning group. This gives you a CSV you can cross-reference against your CMS or template structure. Group URLs by template type - product detail pages, category pages, blog posts - and identify which templates are generating which errors.

For sites running structured data through Google Tag Manager, template-level fixes are typically GTM configuration changes rather than code deployments. That means faster iteration cycles and the ability to test fixes on a subset of URLs before rolling out site-wide. The GTM setup guide covers structured data deployment through Tag Manager specifically.

Another approach for large sites: run periodic crawls with a tool like Screaming Frog configured to extract structured data. This gives you a snapshot of what markup exists across your entire site, independent of what GSC has processed. Comparing your crawl output against GSC's Rich Results report surfaces discrepancies - pages GSC hasn't seen yet, pages where markup was recently added but not yet recrawled, and pages where markup exists in code but isn't rendering for crawlers.

Structured Data and AI Search Visibility

There's an increasingly important reason beyond click-through rates to keep your structured data clean. AI search tools - including Google's own AI Overviews and third-party tools like Perplexity - rely heavily on machine-readable signals to understand page content and decide what to cite.

Valid, complete structured data makes your content significantly easier for AI models to parse accurately. Broken or absent markup forces AI crawlers to interpret your content from raw HTML and natural language alone, which is less reliable. The connection between schema quality and AI citation rates is covered in depth in the schema markup and AI search guide.

Keeping your Rich Results report clean isn't just a traditional SEO task anymore. It's part of maintaining AI search visibility as well.

What the Rich Results Report Can't Tell You

The Rich Results report is a powerful diagnostic tool, but it has blind spots worth knowing about.

It doesn't tell you whether your valid markup is actually generating rich result impressions in search. For that, you need the Search Appearance filters in the Performance report. Filter by “Rich Results” as a search type to see impressions, clicks, and CTR for pages where Google is rendering your markup as a rich result.

It also doesn't catch policy violations that would prevent rich results even from technically valid markup. If your review markup aggregates ratings from your own employees, or your FAQ content is deceptive, Google may suppress rich results algorithmically without flagging an error in GSC. Policy-level suppression is harder to detect and usually requires comparing expected vs. actual appearance in search results for specific queries.

Finally, the Rich Results report only shows markup types Google actively monitors for rich results. General schema types like “Organization,” “WebPage,” or “BreadcrumbList” may not generate a dedicated Enhancement report in GSC, even if they're influencing how Google understands your site's structure.

A Practical Audit Cadence

For most sites, a monthly check of the Rich Results report is sufficient. Set a recurring calendar reminder. Open each Enhancement report, note the error count, and compare it to the prior month.

Any new error spike that correlates with a site deployment is a strong signal that a template change broke something. Catch it within days rather than weeks and the fix is straightforward. Let it sit for months and you've lost rich result visibility across an entire content type for that entire period.

For sites actively publishing new structured data types - adding product markup for the first time, rolling out FAQ schema across a content section, or implementing event markup - check weekly during the rollout period. The first few weeks after deploying new markup are when errors surface, and fast iteration is much easier than backfilling fixes across thousands of already-indexed pages.

Structured data is one of the most reliable ways to improve click-through rates without changing your rankings. The Rich Results report makes auditing it systematic. Most of the work is just showing up and reading what Google is already telling you.