Rich Results Report (Google Search Console)

TL;DR — Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s rich-result status reports tell you whether structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. for a supported feature is eligible for a rich result — those enhanced listings like star ratings, recipe images, and breadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results.. It gives each type of rich result its own report showing how many items are Valid (good to go), Valid with warnings (fine, but missing some recommended details), or Invalid (has an error that blocks it). It tells you what’s wrong; it can’t fix anything for you.

What this report is

If you’ve added structured data (schema markupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.) to your site — for products, recipes, articles, breadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., reviews, and so on — the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report is where you check whether Google can actually use it. Open Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., look under Enhancements in the left menu, and you’ll see a report for each rich result type Google foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. on your site. (Product and Merchant listings sit under Shopping instead.)

Each report does one job: it takes the structured data items Google found, sorts them into Valid or Invalid, tracks that over time on a chart, and lists the issues holding back the invalid ones.

Report vs. Test — don’t mix them up

This is the single most common confusion, so let’s kill it up front. There are two Google tools with almost the same name:

• The Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test is a one-off checker. You paste in one URL, hit test, and it tells you what rich results that page is eligible for right now. You use it before you publish, or when debugging a single page.
• The Rich Results ReportThe Rich Results Report is Google Search Console's site-wide, over-time health check on structured data: a separate per-type report (under Enhancements, or Shopping for Product/Merchant listings) showing how many items are Valid, Valid with warnings, or Invalid, and why. It only tracks markup that's eligible for a supported rich result, and it can't fix anything for you. (this page) is an ongoing dashboard. It watches your whole site over time and flags problems after you’ve deployed — the kind that creep in when a template changes or a plugin updates.

Test = spot-check one page before publishing. Report = monitor the whole site after publishing. Google itself pairs them exactly this way.

What the states mean

• Valid — the item has no critical issues and is eligible to appear as a rich result.
• Valid with warnings — it’s still eligible, but you’re missing some recommended fields that could make the result richer.
• Invalid — it has at least one critical issue, so it can’t appear as a rich result until you fix it.

The one thing everyone gets wrong

Valid does not mean the rich result will show. Valid just means you’re eligible. Google still decides whether to actually display the enhanced listing based on things like page quality and the search itself. So a page can be perfectly Valid in this report and still show a plain blue link in search — that’s normal, not a bug.

Also worth knowing: the report shows a sample, and it counts items, not pages — so the numbers rarely add up neatly. Want the full picture, including why the totals never tie out, how to fix and validate issues, and what happened to the FAQ report? Switch to the Advanced tab.

TL;DR — Rich-result status reports are Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s post-deployment, site-wide monitors for structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. — one report per supported rich result type, under Enhancements (or Shopping for Product/Merchant listings). It only appears once Google finds valid markup of a type it supports. Read it knowing three things: it’s the Report, not the single-URL Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test; it counts items from a sample, not pages, so totals rarely tie out; and Valid means eligible, not displayed. Most Invalid items come from a missing required property — fix at the template level, confirm live, then click Validate fix and wait ~two weeks. Not every schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. type earns a report (only Google’s supported feature types do), and FAQ stopped appearing in Search on May 7, 2026 — Google’s changelog states a plan to drop the dedicated report and Rich Results Test support too.

Where it lives and when it appears

Google is blunt about what the reports are: “Rich result reports in Google Search Console show structured data (and its validity) foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. on your site.” You get a separate report per type — Google says it “provides a separate report for each type of rich result found on your property.” To find them, “Locate the reports under Enhancements in the navigation bar.” Product snippets and Merchant listings are the exception — those live under Shopping.

A crucial gotcha: a report doesn’t exist for a type just because you added that markup. “A rich result report for a type will appear only if: Google finds valid markup in your property, and The markup is a supported rich result type.” Both conditions. If you never see a “Recipe” report, it can mean Google never found valid Recipe markupRecipe schema (schema.org/Recipe) marks up a cooking recipe's image, name, ratings, times, ingredients, and nutrition so the page can earn Google's recipe rich result — a visual card with star ratings and cook time, plus carousel and recipe-filter eligibility. — or that your markup has a syntax error serious enough that it lands in the separate Unparsable structured data report instead (more on that below).

Report vs. Rich Results Test — the distinction Google itself draws

Competitor content conflates these two constantly, sometimes titling a page for one and explaining the other. Google draws the line cleanly in its own structured-data intro: “Be sure to check your structured data using the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test during development, and the Rich result status reports after deployment, to monitor the validity of your pages, which might break after deployment due to templating or serving issues.”

That one sentence is the whole distinction:

• Rich Results Test (search.google.com/test/rich-results) — single URL, on-demand, during development. It supports JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., Microdata, and RDFa and lets you preview the desktop/mobile layout. This is your pre-publish spot check.
• Rich Results ReportThe Rich Results Report is Google Search Console's site-wide, over-time health check on structured data: a separate per-type report (under Enhancements, or Shopping for Product/Merchant listings) showing how many items are Valid, Valid with warnings, or Invalid, and why. It only tracks markup that's eligible for a supported rich result, and it can't fix anything for you. (this report) — whole property, tracked over time, after deployment. This is your ongoing monitor. It’s where you catch the breakage the Test can’t — a template edit or serving change that quietly invalidates a thousand pages at once.

Which types get their own report

Only Google’s supported types. As of now, Google says it “supports reports for the following rich result types: BreadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., Datasets, Discussion forum, Education Q&As, Events, Hotels, Image metadata, Job postings, Math solvers, Merchant listings, Practice problems, Product snippets, Profile pages, Q&As, Recipes, Review snippets, Subscribed content, Vacation rentals, Videos.” That list grows and shrinks over time — Discussion forum, Subscribed content, and Practice problems are relatively recent additions; FAQ was on it until its Search appearance stopped in 2026 (see “What just changed” below).

This is the accuracy point most explainers miss: schema.org defines 800+ types, but Google only builds reports for the finite set of features it supports. A generic WebPage, a Person outside a profile-page context, or an unsupported CreativeWork subtype can be perfectly valid schema.org and still never generate a report here — because it was never eligible for a Google rich result to begin with. Google says as much in its intro doc: “There are more attributes and objects on schema.org that aren’t required by Google Search; they may be useful for other search engines, services, tools, and platforms.” If you’re staring at a type that has no report, the first question isn’t “what’s broken” — it’s “is this type even one Google shows a rich result for?”

Reading the chart and the two issue tables

The landing page for each report has a chart and two tables:

• The chart plots Valid vs. Invalid items over time. Google: “The chart shows how many valid and invalid structured data items Google found on your site over time.” A Valid item has no critical issues and can appear as a rich result; an Invalid item has at least one critical issue preventing it.
• “Why items are invalid” lists the critical issues — the ones that block eligibility entirely. This is your priority table.
• “Improve item appearance” lists the non-critical issues — warnings. These items are Valid (still eligible), but you’re missing recommended properties that could unlock a richer display or more layouts.

So the three states map like this: Invalid = has a critical issue → not eligible. Valid with warnings = only non-critical issues → eligible, but not maximized. Valid = clean → eligible.

Why the numbers never quite add up

This is the most-asked question about the report, and it has two separate answers, both from Google.

Issue totals can exceed valid + invalid totals. That’s because “One item may have multiple issues (critical and non-critical), causing it to appear multiple times in issue tables” — but it’s counted once in the Invalid tab. One broken product item with three problems shows up three times across the issue tables and once in the total.

Item totals can be lower than the number you expect. Because the report is a sample, not a census: “The reports aren’t a comprehensive list of all detected items.” It shows a representative sample to help you judge quality — Google explicitly tells you to “Use the URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. to see if URLs not listed in the report have detected the structured data.”

And the mental unlock behind all of it: the report counts items, not pages. One page can carry several structured data items — a product page often has both a Product item and a BreadcrumbList item — so the item count and your page count were never going to match.

Common causes of Invalid items

• Missing required properties — the #1 cause. Google’s own framing: “You must include all the required properties for an object to be eligible for appearance in Google Search.” Miss one required field and the item is Invalid, full stop. This is where most errors come from.
• Wrong value types and syntax errors. A price as text instead of a number, a malformed date, a broken bracket. If the JSON is broken badly enough that Google can’t even tell what type you meant, it doesn’t land in the type’s report at all — it goes to the separate Unparsable structured data report, which “lists structured data found on your site that could not be parsed because of a serious syntax error.” Every item there is critical: “All items in this report are critical structured data errorsStructured data errors are problems in a page's schema.org markup that either break parsing entirely (malformed JSON-LD — trailing commas, unescaped quotes, a missing colon or brace) or parse fine but fail a search engine's eligibility rules for a rich result: missing required properties, wrong value types, a colliding/duplicate @id, or markup describing content that isn't visible on the page. Google surfaces them in the Rich Results Test and Search Console's Rich result report; schema.org's Schema Markup Validator checks general syntax/vocabulary. Fixing them restores rich-result eligibility — structured data isn't a ranking factor.; there are no warnings or valid items.” This is the report to check first when a type-specific report is unexpectedly empty.
• Markup describing content that isn’t visible on the page. Marking up a rating or price a user can’t actually see on the page violates Google’s structured data policies and risks a manual action — a separate problem from a simple validation error.

TIP Catch a broken star-rating block before it becomes a report-wide issue

This example is deliberately about rating data: the average needs a supporting count and must fit inside its declared scale.

Build and validate the rating block with my free Schema Markup Generator Free

1. Choose the real parent type and enter the rating users can see on the page.
2. Add ratingCount or reviewCount and keep ratingValue inside the declared scale.
3. Deploy the corrected template, test a live URL, and then use Validate fix on the matching Search Console issue.

Tap to enlarge

The generator reports two issues: the AggregateRating needs ratingCount or reviewCount, and ratingValue 6 cannot exceed bestRating 5. The code preview shows the incomplete aggregateRating nested in a Product.

Fixing and validating issues

Google’s workflow, and the reason there’s no magic button:

There’s no “fix it for me,” by design. “The structured data resides on your website, not Google’s servers.” Google can only report; the fix has to happen in your source code.

Fix at the template level, not page by page. Open the report, click an issue to see affected pages, and fix the root cause. Because most structured data is generated by a template or plugin, one template fix typically clears every affected URL at once — which is exactly why chasing individual pages is a waste of time here.

Then click Validate fix. Google “will initially check a sample of pages. If they pass, it will proceed to validate other affected pages.” Two things to know: it’s not required (Google updates counts through normal crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. anyway — Validate fix mainly gives you a trackable log and a notification), and it’s slow — “Validation can take two weeks or more, depending on crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial..” Don’t re-click mid-cycle, and never click it before you’ve actually fixed and deployed the cause, or you just burn two weeks ending in “Failed.”

The 90-day issue-lifetime rule matters for anyone tracking dates in an audit trail: “An issue remains active until 90 days pass without new instances. If a new instance appears after 90 days, it is treated as a new issue. The First detected date reflects the original detection date and does not reset.”

Valid doesn’t mean it will show

Reinforce the eligibility-not-guarantee principle from the rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. glossary rather than restating it: “Using structured data enables a feature to be present, it does not guarantee that it will be present.” When an item is Valid but no rich result appears, John Mueller’s framing (relayed via Search Engine Journal) is the cleanest way to reason about it — Google checks, in order, whether the markup is technically valid, whether it complies with policy, and then a broader site-wide quality signal. This report only measures the first gate.

That’s why two other Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. surfaces belong in your mental checklist here:

• Manual Actions report. “A structured data manual action means that a page loses eligibility for appearance as a rich result; it doesn’t affect how the page ranks in Google web search.” If items are Valid but nothing shows, check for a penalty — it’s a separate report from this one.
• Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason.. Only indexed pages appear in structured data reports — Google lists “Pages not indexed” among the reasons items go missing, and “A drop in indexed pages leads to fewer structured data items in reports.” If items vanished, an indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. drop (the sibling index-coverage report is where you’d see it) is a prime suspect, not necessarily a markup regression.

Don’t panic at a sudden spike — the report has been wrong before

A jump in Invalid counts doesn’t always mean you broke something. Google has, at least once, mislabeled its own report. In October 2022, per Search Engine Roundtable’s coverage, a bug moved many warnings into the critical-error table purely as a display issue — Google said it was “strictly a reporting issue” that didn’t affect whether rich results could actually display. Google also periodically changes what it counts as an error vs. a warning within a type (the Product report got exactly this kind of accuracy overhaul in December 2021). So before assuming a regression on a sudden move, check whether it’s a known reporting change first — your issue-detail page and current SEO news will usually tell you.

What just changed — FAQ rich results being wound down (2026)

If you land on older “how to read your FAQ report” content, it’s describing a feature Google has been actively retiring. The timeline, from Google’s own changelog (relayed via Search Engine Journal and Search Engine Land) — treat the 2026 dates after May as Google’s stated plan, not something re-verified live inside a Search Console property for this update:

• May 7, 2026 — FAQ rich results stopped appearing in Google Search results. This one has already happened and is the most load-bearing date here.
• June 2026 — per Google’s changelog, the FAQ search-appearance filter, the dedicated FAQ rich result report in Search Console, and FAQ support in the Rich Results Test were slated for removal.
• August 2026 — Google says FAQ data will be removed from the Search Console API. As of this update, that date hasn’t arrived yet, so don’t assume the API change is already in effect.

One more caution worth stating plainly: Google’s FAQPage documentation page has now been removed — the old URL returns a 301 to the “removing FAQ rich result” entry in Google’s Search changelog, which records the documentation removal on June 15, 2026. Watch the redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. status rather than the rendered content when you check a doc like this: a fetch that quietly follows the redirect will show you the changelog page and look like the original is still live. If your own property still shows an FAQ row in Enhancements, don’t assume that’s a bug; confirm what your account currently shows rather than taking any single date here as gospel.

Don’t confuse this with the 2023 change. Back in August 2023 Google restricted FAQ display to well-known, authoritative government and health sites (and narrowed How-To) — which is why most sites already stopped seeing FAQ rich results years ago. The subtle, under-reported detail: that 2023 change hit the Performance reportThe Google Search Console report that shows how your site actually performed in Google Search, built from real impressions and clicks. It reports four metrics — clicks, impressions, average CTR, and average position — and keeps the most recent 16 months of data.’s impression counts for the FAQ/How-To search appearances, not the Rich Results Report’s item counts. Item validity stayed the same; only the display volume (and its Performance-report tracking) dropped. The 2026 change is different in kind — per Google’s own plan, it removes the report itself, not just the display volume.

What to do with existing FAQPage markup: nothing urgent. It’s still a valid schema.org type, causes no errors, triggers no manual action, and does no ranking harm — it just won’t produce a rich result or a report anymore. Google’s long- standing line has been that unused structured data doesn’t cause problems and there’s no need to proactively strip it out.

Rich Results Report vs. Bing’s markup validation

Bing has no direct 1:1 equivalent — no site-wide, over-time, per-type dashboard tracking Valid/Invalid items automatically. Its closest surface is the Markup Validator inside Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility.’ URL Inspection (also standalone at bing.com/toolbox/markup-validator), which checks whether the structured data on a single URL is readable by BingbotBingbot is Microsoft Bing's primary web crawler — the bot that discovers, fetches, and renders pages to build the Bing index. That index also powers Yahoo, DuckDuckGo, Ecosia, and Microsoft Copilot, so Bingbot's reach is far wider than Bing's own search-market share., across JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., Microdata, Microformats, Open Graph, and RDFa. In other words, Bing’s tool behaves like Google’s Rich Results Test, not its Report. “Rich Results Report” is Google’s product name, and the whole ongoing-monitoring concept is Google-specific.

AI summary

A condensed take on the Advanced version:

• What it is: Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s site-wide, over-time monitor for structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. — one report per supported rich result type, under Enhancements (or Shopping for Product/Merchant listings). A report appears only once Google finds valid markup of a supported type.
• Report ≠ Test. The Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test is a single-URL, on-demand check for during development; the Report is the whole-property monitor for after deployment. Google pairs them exactly this way in its own docs.
• States: Invalid = at least one critical issue (blocks eligibility); Valid with warnings = eligible but missing recommended fields; Valid = clean. The two tables are “Why items are invalid” (critical) and “Improve item appearance” (non-critical).
• The numbers never tie out because the report counts items, not pages, from a sample not a census, and one item with multiple issues appears multiple times in issue tables but once in the total.
• Most Invalid items = a missing required property. Fix at the template level, confirm live, then Validate fix (samples pages, ~2 weeks; not required, no auto-fix — the markup is on your server).
• Valid ≠ displayed. Eligibility isn’t a guarantee (Mueller’s three gates: markup validity → policy → site-wide quality). Also check Manual Actions and Page IndexingThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. when Valid items don’t show or go missing.
• Not every schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. type gets a report — only Google’s supported feature types. Badly broken JSON lands in the separate Unparsable structured data report.
• FAQ stopped appearing in Search on May 7, 2026, and Google’s changelog states a plan to drop the dedicated report and Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test support too (distinct from the 2023 display restriction, which hit Performance-report impressions, not item counts). Existing FAQPage markup is harmless to leave in place.

Official documentation

Primary-source documentation from Google.

Google — the report itself

• Rich result report overview — the canonical Help doc: where it lives, the supported-type list, the chart, the two issue tables, the counting quirks, and the “no fix button” explanation.
• Fix structured data issues in Search Console — the find → fix → Validate fix workflow, validation states, timing, and the 90-day issue-lifetime rule.
• Debug missing structured data or drops in structured data items — why items go missing or drop (sampling, unparsable markup, unindexed pages, access issues, indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. drops).
• Unparsable structured data report — the separate report for markup too broken to classify by type.

Google — the structured-data concepts behind it

• Intro to how structured data markup works — the Test-during-development / Report-after-deployment pairing and the “required properties” rule.
• Structured data markup that Google Search supports (feature gallery) — the finite list of Google-supported feature types (the reason not every schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. type gets a report).
• General structured data guidelines — eligibility-not-guarantee, and the structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. manual action.
• Rich Results Test — the companion single-URL validator (not the same tool as this report).
• Changes to HowTo and FAQ rich results (Aug 2023) — the earlier restriction that hit Performance-report impressions, not this report’s item counts.

Quotes from the source

On-the-record statements from Google. Each Google link is a deep link that jumps to the quoted passage on the source page.

Google — what the report is and where it lives

• “Rich result reports in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. show structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. (and its validity) foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. on your site.” — Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. Help. Jump to quote
• “Locate the reports under Enhancements in the navigation bar.” Jump to quote
• “A rich result report for a type will appear only if: Google finds valid markup in your property, and The markup is a supported rich result type.” Jump to quote

Google — the chart, the sample, and the counting quirks

• “The chart shows how many valid and invalid structured data items Google found on your site over time.” Jump to quote
• “The reports aren’t a comprehensive list of all detected items.” Jump to quote
• “One item may have multiple issues (critical and non-critical), causing it to appear multiple times in issue tables.” Jump to quote

Google — no auto-fix, by design

• “The structured data resides on your website, not Google’s servers.” Jump to quote

Google — the fix and validate workflow

• “Google will initially check a sample of pages. If they pass, it will proceed to validate other affected pages.” — Google Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. Help. Jump to quote
• “Validation can take two weeks or more, depending on crawl frequencyCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial..” Jump to quote
• “An issue remains active until 90 days pass without new instances. If a new instance appears after 90 days, it is treated as a new issue. The First detected date reflects the original detection date and does not reset.” Jump to quote

Google — the separate Unparsable report

• “This report lists structured data found on your site that could not be parsed because of a serious syntax error.” — Google Search Console Help. Jump to quote
• “All items in this report are critical structured data errorsStructured data errors are problems in a page's schema.org markup that either break parsing entirely (malformed JSON-LD — trailing commas, unescaped quotes, a missing colon or brace) or parse fine but fail a search engine's eligibility rules for a rich result: missing required properties, wrong value types, a colliding/duplicate @id, or markup describing content that isn't visible on the page. Google surfaces them in the Rich Results Test and Search Console's Rich result report; schema.org's Schema Markup Validator checks general syntax/vocabulary. Fixing them restores rich-result eligibility — structured data isn't a ranking factor.; there are no warnings or valid items.” Jump to quote

Google — Test vs. Report, required properties, and schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. scope

• “Be sure to check your structured data using the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test during development, and the Rich result status reports after deployment, to monitor the validity of your pages, which might break after deployment due to templating or serving issues.” — Google Search Central docs. Jump to quote
• “You must include all the required properties for an object to be eligible for appearance in Google Search.” Jump to quote
• “There are more attributes and objects on schema.org that aren’t required by Google Search; they may be useful for other search engines, services, tools, and platforms.” Jump to quote

Google — eligibility is not a guarantee, and manual actions

• “Using structured data enables a feature to be present, it does not guarantee that it will be present.” — Google Search Central docs. Jump to quote
• “A structured data manual action means that a page loses eligibility for appearance as a rich result; it doesn’t affect how the page ranks in Google web search.” Jump to quote

Google — why items go missing

• “A drop in indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. pages leads to fewer structured data items in reports.” — Google Search Console Help. Jump to quote

John Mueller / Google incidents — relayed via industry coverage

• On the Oct 2022 mislabeling bug, Google described it as “strictly a reporting issue” that didn’t affect whether a rich result could display — a reminder to check for a known bug before panicking at an error spike.
• Mueller’s framing for why Valid markup still might not show breaks down into three gates: markup validity, policy compliance, and a site-wide quality signal.

Which path should I take?

“My Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report shows an Invalid item.”

1. Click into the “Why items are invalid” table and read the specific issue.
2. Is it a missing required property? → Add it in the template that generates the markup, not on one page. → Deploy → confirm with the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test on a live URL → Validate fix → wait ~2 weeks.
3. Is it a wrong value type / syntax issue? → Fix the type/format in the template → same deploy-confirm-validate loop.
4. Is the whole type-report empty or missing when you expected items? → Jump to the next tree.

“The report shows 0 items (or the type has no report at all).”

1. Is the type even supported by Google for a rich result? If it’s not in Google’s feature list, there will never be a report — stop here.
2. Check the Unparsable structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. report — a serious syntax error routes items there instead of the type report.
3. Are the pages indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.? Only indexed pages surface here — check the Page IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. report.
4. Could it just be the sample? Use URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. on a specific URL to confirm Google detected the markup there.

“The item is Valid but no rich result shows in search.”

1. Remember: Valid = eligible, not guaranteed. This is often normal.
2. Check the Manual Actions report for a structured data manual action.
3. Do a rough site: search — if the rich result shows there but not for normal queries, that points to a site-wide quality gate, not a markup problem.
4. If none of the above, it may simply be Google’s display choice for that query — nothing to “fix.”

“My numbers jumped/dropped suddenly.”

1. Did you deploy a template or plugin change recently? → Likely a real cause; work the Invalid table.
2. No change on your end? → Check for a known reporting change/bug (issue-detail page + SEO news) before assuming a regression.
3. Items dropped? → Check the Page IndexingThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason. report — an indexing drop reduces item counts here.

“Should I remove my FAQPage markup now that FAQ rich results are being wound down?” No urgent need. It’s a valid schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. type, causes no errors and no penalty, and won’t produce a rich result (or, per Google’s stated plan, a report) anymore. Remove it only if you’re cleaning up for maintenance reasons.

Rich Results Report — cheat sheet

Report vs. Test

The three states

The two issue tables

Why the numbers don’t tie out

• Counts items, not pages (one page can hold several items).
• Shows a sample, not every item — use URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. to check specific URLs.
• Issue totals can exceed valid + invalid — one item with multiple issues appears multiple times in issue tables, once in the total.

Fast facts

• No auto-fix — markup lives on your server, not Google’s.
• Validate fix samples pages; ~2 weeks or more; not required (crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. updates counts anyway); don’t click before deploying the real fix.
• 90-day rule — an issue stays active until 90 days with no new instances; First-detected date doesn’t reset.
• Not every schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. type gets a report — only Google’s supported feature types.
• Broken JSON → lands in the separate Unparsable structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. report.
• FAQ stopped appearing 2026 — report/Test support being wound down per Google’s plan (schema type still valid; harmless to keep).

Working the Rich Results Report — checklist

• Open Enhancements in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. (Product/Merchant listings are under Shopping).
• Confirm the type you care about is one Google actually supports a report for — if not, no report will ever appear.
• Read the chart as a trend, not a scorecard; don’t expect item counts to match your page counts (it counts items, sampled).
• Work the “Why items are invalid” (critical) table before the “Improve item appearance” (warnings) table.
• For each critical issue, identify whether it’s a missing required property (the usual culprit) or a value-type/syntax problem.
• Fix at the template/plugin level, not URL by URL.
• Confirm the fix on a live URL with the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test before validating.
• Click Validate fix only after the fix is deployed; expect ~2 weeks; don’t re-click mid-cycle.
• If a type-report is unexpectedly empty, check the Unparsable structured data report and whether the pages are indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..
• If items are Valid but nothing shows, check the Manual Actions report and remember eligibility isn’t a guarantee.
• On a sudden spike/drop with no deploy on your side, check for a known reporting change/bug before assuming you broke something.
• Treat any lingering FAQ row as historical — Google stopped showing FAQ rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. May 7, 2026, and has stated a plan to drop the report and Test support too.

The mental models

1. Test then Report. The Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test is the pre-publish spot check on one URL; the Report is the post-deployment monitor on the whole site. Google literally pairs them this way. Use the Test to ship clean; use the Report to catch what breaks later.

2. Items, sampled — not pages, counted. The report counts structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. items from a sample, and one item can appear in several issue rows. Internalize this and the “my numbers don’t add up” panic disappears — the totals were never designed to tie out to your page count.

3. Two tables, two severities. Why items are invalid = critical = blocks eligibility → fix first. Improve item appearance = non-critical = eligible but not maximized → fix to enrich. Map every issue to one of these before deciding urgency.

4. Eligible ≠ displayed (Mueller’s three gates). Valid markup passes only the first gate: (1) markup validity — what this report measures, (2) policy compliance — check Manual Actions, (3) site-wide quality — outside this report entirely. A Valid item that doesn’t show usually failed gate 2 or 3, not gate 1.

5. Supported list, not the whole vocabulary. Google builds reports only for its finite feature-gallery types, not schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.’s 800+. If a type has no report, first ask whether Google even shows a rich result for it — before hunting for a “bug.”

6. Fix the template, then validate. Structured data is template-generated, so fix the source once and it clears every affected URL. Validate fix is a tracking convenience with a ~2-week clock, not a speed-up and not a requirement — and never a substitute for actually deploying the fix.

Tools for working the report

• Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. — Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report — Enhancements (or Shopping); the site-wide, over-time monitor this article is about.
• Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test (search.google.com/test/rich-results) — the single-URL, pre-publish validator; supports JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., Microdata, and RDFa and previews desktop/mobile layout. The Report’s companion, not a substitute.
• URL Inspection toolA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. (GSC) — confirm whether Google detected structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. on one specific URL that isn’t showing in the sampled report.
• Unparsable structured data report (GSC) — the separate report that catches JSON too broken to classify by type; check it when a type report is unexpectedly empty.
• Manual Actions report (GSC) — where a structured data spam action shows up when Valid items still don’t display.
• Schema MarkupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. Validator (validator.schema.org) — validates against the full schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. vocabulary (broader than Google’s rich-result feature set), useful for markup Google doesn’t build a report for.
• Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. — Markup Validator (bing.com/toolbox/markup-validator) — Bing’s single-URL structured-data check (there’s no Bing equivalent of Google’s site-wide Report).
• Site crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. — Ahrefs Site Audit and Screaming Frog SEO Spider surface structured-data issues across a crawl so you can find affected templates faster.

Prove a structured-data fix reached Google

Test the corrected template before release

• Test to run: Run a representative URL or code sample through Google’s Rich Results Test after changing the structured-data template.
• Expected result: The intended rich-result type is detected with no critical errors; any remaining warnings are understood and accepted.
• Failure interpretation: The generated markup is still missing a required property, has invalid syntax, or does not match a rich-result type Google supports.
• Monitoring window: Immediate for the tested code or live URL.
• Rollback trigger: Stop the release if the change creates a new critical error or removes a previously detected supported item.

Test the live page Google can fetch

• Test to run: After deployment, test the live URL and inspect it with URL Inspection rather than relying only on a development code sample.
• Expected result: The live response contains the corrected markup and Google can detect the same item and properties seen before release.
• Failure interpretation: A cache, renderer, template branch, or deployment mismatch is serving different markup in production.
• Monitoring window: Immediately after caches and the deployment have settled.
• Rollback trigger: Roll back when the production template drops required properties across a page type or exposes invalid markup at scale.

Test the report-level fix

• Test to run: Open the issue in the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report and start Validate fix only after representative live URLs pass.
• Expected result: Validation progresses to Passed and the Invalid item count falls as Google recrawlsCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial. affected pages.
• Failure interpretation: A sampled URL still has the issue, another template variant was missed, or Google has not yet recrawled the corrected pages.
• Monitoring window: Allow about two weeks for validation, and longer when Search Console reports that rechecking is still in progress.
• Rollback trigger: Revert or hotfix if Invalid items increase after deployment or a previously valid template begins failing; do not roll back merely because report counts lag.

Resources worth your time

My related writing

• Schema Markup: What It Is & How to Implement It — the Ahrefs guide to implementing structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.; it makes the point that to check the status of all your rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. you need Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results., and flags the shared blind spot that both GSC and the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test only check the markup that powers rich results — not schema’s other uses.
• The Beginner’s Guide to Technical SEO — where structured data and Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. fit in the bigger technical picture.

My speaking

• How Search Works (SlideShare) — my walkthrough of crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and serving, the pipeline every structured-data item has to pass through before it can show up in a report. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• Rich result report overview (Google) — the primary Help doc; keep it open while you read your own report.
• Fix structured data issues in Search Console (Google) — the official find → fix → Validate fix workflow and the 90-day rule.
• Intro to how structured data markup works (Google) — the cleanest sourcing for the Test-during-development / Report-after-deployment distinction.
• We Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved. (Ahrefs, Louise Linehan, May 2026) — a useful reality check: validity in this report is about SERP-display eligibility, not an AI-visibility or ranking lever; adding schema to already-cited pages barely moved AI citationsAn AI citation is the visible source link an AI answer engine shows next to its generated text — the clickable reference that credits the web page it used. A citation's presence is a separate thing from whether the cited page actually supports the statement, and from being retrieved (read behind the scenes) or merely mentioned (named without a link); citation is driven more by brand mentions and being retrievable than by traditional ranking..
• Google’s John Mueller on Troubleshooting Rich Results (Search Engine Journal, Matt G. Southern, Feb 2021) — the three-gates framing for why Valid markup still might not display.
• Google Search Console Bug Mislabeled Many Rich Results Issues As Errors When They Were Warnings (Search Engine Roundtable, Barry Schwartz, Oct 2022) — the “check for a known bug before panicking” data point.
• Google Drops FAQ Rich Results From Search (Search Engine Journal, Matt G. Southern, May 2026) — coverage of the 2026 FAQ retirement timeline.
• Google to no longer support FAQ rich results (Search Engine Land, May 2026) — corroborating coverage of the same change.
• r/TechSEO — the community for structured-data and Search Console debugging.

Videos

• Google Search Central (YouTube) — the structured-data and Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. explainers from the Search Relations team, including Martin Splitt’s rich-results and structured-data troubleshooting videos. Channel

Test yourself: the Rich Results Report

Five quick questions on reading and using Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results.’s Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report. Pick an answer for each, then check.

Rich Results Report

The Rich Results Report is Google Search Console's site-wide, over-time health check on structured data: a separate per-type report (under Enhancements, or Shopping for Product/Merchant listings) showing how many items are Valid, Valid with warnings, or Invalid, and why. It only tracks markup that's eligible for a supported rich result, and it can't fix anything for you.

Related: Rich Results, Structured Data, Google Search Console

Rich Results Report

The Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Report is the set of per-type diagnostic reports inside Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. that show whether the structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. on your site is valid enough to be eligible for a given rich resultRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show.. Google provides a separate report for each supported rich result type it finds on your property — BreadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., Products, Recipes, Reviews, Events, Job postings, Q&As, and more. Each report lives under Enhancements in the left navigation (Product snippets and Merchant listings live under Shopping), and a report only appears at all once Google finds valid markup of a type it actually supports.

Each report has a chart of Valid vs. Invalid items over time plus two issue tables: “Why items are invalid” (critical issues that block eligibility) and “Improve item appearance” (non-critical warnings). An item is Valid when it has no critical issues, Invalid when it has at least one, and Valid-with-warnings when it’s eligible but missing recommended properties.

It is not the same thing as three neighbors it’s easy to confuse it with: the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test (a one-off, single-URL validator you run before publishing — the Report is the ongoing, site-wide monitor after deployment); structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. the underlying markup concept; and rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. the SERP featureSERP features are any element on a search results page beyond the classic ten blue links — featured snippets, People Also Ask, knowledge panels, sitelinks, image and video packs, AI Overviews, and structured-data-driven rich results. Google documents that losing rich-result eligibility doesn't affect ranking; their SEO relevance is CTR (they redistribute clicks). Some are unlocked by markup; most are purely algorithmic. itself. The Report has no “fix it for me” button by design — the markup lives on your server, not Google’s — and most errors trace back to missing required properties.

Related: Rich Results, Structured Data, Google Search Console

Changelog