First, confirm what Google actually sees
Run the page through Google's Rich Results Test, which reports which rich result types it detects and any errors or missing properties. Use the live URL rather than pasted code, since the deployed page is what Google crawls. Then compare with the enhancement reports in Search Console (GSCGoogle's search performance and indexing tool.): each supported type has its own report listing valid items, items with warnings and items with errors across the site. If the type has no report at all, Google has not detected it on any crawled page.
Next, inspect the URL itself. URL inspection shows whether the page is indexed, when it was last crawled and which enhancements were found on the crawled version. A page that is not indexed cannot show any rich result, however perfect its markup. Finally, check the manual actions and security issues reports, and search the query yourself, ideally from the target country, to see what the SERPThe page of results a search engine shows. currently shows for the page and its competitors. With those four views you can place the problem in one row of the table.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| The test or the enhancement report lists errors for the item | Error details: the property at fault and the affected URLs | Markup invalid or missing required properties | Correct the values or supply the required properties from real data |
| The type is detected but no rich result is offered for it | Google's search gallery of supported features; deprecation notices | Type not eligible for a rich result, or deprecated | Keep valid markup only where useful; drop work aimed at a retired feature |
| Ratings, prices or FAQs in the markup do not appear on the page | Compare the JSON-LD values with the visible content | Marked-up content not visible on the page | Show the content to users or remove the markup that describes it |
| Rich results stopped site-wide, often after a notice | Manual actions report; messages in Search Console | Structured data manual action or policy issue | Fix the policy problem everywhere and request reconsideration |
| The markup is valid but the URL has no crawl since it was added | URL inspection: index status and last crawl date | Page not indexed or not yet recrawled | Resolve indexing first, then request indexing and wait for a recrawl |
| Valid, eligible and indexed, yet results show a plain listing | Search the query; compare competitors; observe across days | Valid and eligible, but Google chose not to show it | Improve page quality and relevance; accept that display is not guaranteed |
Fix, verify and prevent each cause
Errors in the markup
Google's search gallery lists required and recommended properties for each feature. An error means the item is ineligible, often because a template field is empty, a value is in the wrong format, or a nested object is missing.
Fix: trace each error back to its data source, fill the field from real data or omit the item, and use the correct formats for dates, prices and durations.
Verify: the Rich Results Test passes on a sample, and using "validate fix" in the enhancement report starts Google's recheck of the affected URLs.
Prevent: generate Schema MarkupStructured data vocabulary. from structured fields rather than free text, the approach recommended in structured data and schema. For product pages, the product structured data tutorial maps each property to a catalogue field so the markup cannot drift from the page.
A type that does not produce a rich result
Plenty of schema.org types are valid but have no rich result in Google, and Google has retired or narrowed some features over time. Markup for these is harmless and may help understanding, but no amount of correction will create a visual enhancement.
Fix: check the type against Google's current gallery, and redirect effort to a type that is supported for your page if one genuinely fits.
Verify: the Rich Results Test names the feature you expect.
Prevent: before implementing a type, record which feature it targets and recheck the gallery when planning work, as part of deciding what to implement in the structured data guide.
Markup describing invisible content
Google's general structured data guidelines require the marked-up content to represent the main content of the page and to be visible to users. Review stars drawn from reviews that appear nowhere on the page, or answers held only in the code, break that rule.
Fix: either display the content to visitors in full, or remove the markup for it.
Verify: every value in the JSON-LD can be found on the rendered page.
Prevent: keep markup and visible content generated from the same data, so they cannot drift apart; the structured data guide covers keeping markup correct over time.
A manual action or policy issue
When markup misleads, for example self-serving reviews or hidden content at scale, Google can apply a manual action that removes rich results for the whole site or a section. Search Console reports these, with the affected pattern.
Fix: correct every instance of the problem, not just the examples, then file a reconsideration request that explains what changed.
Verify: the manual actions report clears after review, and enhancements begin to appear again over subsequent crawls.
Prevent: check the manual actions and messages reports as part of the routine described in the Search Console guide.
The page is not indexed or not yet recrawled
Rich results are an enhancement of an indexed result, so a page outside the index or crawled before the markup shipped cannot have one.
Fix: resolve any indexing exclusion first, then request indexing for a few key pages and let the rest be recrawled naturally.
Verify: URL inspection shows the page indexed and lists the detected enhancement on the crawled version.
Prevent: add markup to pages at launch rather than afterwards, and check index status with the sequence in crawling and indexing.
Google's discretion
Google's introduction to structured data states that correct markup makes a page eligible but does not guarantee that a rich result is shown. Display can depend on the query, the device, the location and Google's view of the site's quality.
Fix: there is no switch; improve the page's usefulness, make sure the markup reflects it accurately, and compare with competitors who do receive the feature.
Verify: monitor the search appearance filter in the performance report over weeks rather than checking single queries.
Prevent: set expectations with stakeholders that eligibility is the goal you control, as the structured data guide frames it.
Prevention: markup in the release checklist
Rich results most often disappear because a template change quietly broke the markup. Put structured data into the release checklist: run the Rich Results Test on one example of every changed template before release, and watch the enhancement reports in the days after. Keep a register of which types each template emits and which feature each one targets. Review Google's gallery when planning, because features change. Remember that a result's title link is a separate system: if the issue is that Google shows different title text, read the sibling page on Google rewriting title tags instead. Markup drafted by an AI tool needs this release check and a few of its own, which the tutorial on checking AI-generated structured data sets out: documented properties only, nothing the page does not show and values read from the template's fields.
A cookery school whose event listings vanished
A cookery school has event rich results for 85 class pages until a redesign in May. Three weeks later the event report shows 85 items with errors: "missing field startDate". The new template takes the date from a field that only 20 classes have filled; the others store it in free text. The team adds a structured date field, backfills it, and validates the fix. Within two weeks the report shows 80 valid items. The remaining five are classes with no scheduled date, which are correctly left without event markup.
Common mistakes
Treating the Rich Results Test as a promise of display. Adding markup for content that is not on the page. Chasing a feature Google has retired. Fixing the example URLs in a report while the template keeps producing the error.
