A validated block that yields no visible feature is not wasted, but it is also not doing what the ticket promised. Structured data buys two things: an unambiguous machine reading of the page, and eligibility if a feature is on offer. The display decision belongs to Google and is made per query.
Does structured data with no rich result do anything at all?
It still gives Google a stated reading of the page instead of an inferred one, and it keeps the page eligible if the feature appears later. What it does not do is move rankings by itself.
Google's own documentation frames schema markup as a way to help it understand a page and to make that page eligible for rich results. Eligibility is stated as eligibility, never as a guarantee. That framing is the whole answer to the question: you are buying a clearer reading and a lottery ticket, and the reading is the part you can count on.
The clearer reading matters most where a page is genuinely ambiguous to a parser. A price that lives inside a JavaScript-rendered widget, an author name that only appears in a byline image, a publication date that sits in a sidebar next to three other dates: markup states each of those as a fact rather than leaving it to pattern matching. Anything that parses the page can read it, which is a different argument from the rich-result one and does not depend on Google showing anything.
Why would Google read your markup and show nothing?
Four reasons, in rough order of how often they turn out to be the explanation: the type no longer has a visible treatment, the query did not call for it, the site is not trusted enough for a feature that implies endorsement, or the markup is valid but thin.
The last one is the most fixable and the most missed. Validation checks that required properties are present and well formed. A result often needs the recommended properties too: a product schema block with a name and an image passes validation, while the merchant treatment people actually want generally needs price, currency and availability as well. Green does not mean complete.
Query dependence is the one that wastes the most debugging time. The same URL can show a breadcrumb trail on one query and a plain blue link on another, because Google decides the result layout per search, not per page. Testing your markup by searching your own brand name tells you very little about what a buyer sees.
Validation answers "can Google read this". Only the Search Appearance breakdown in Search Console answers "did Google show it". Teams that stop at the green checkmark never find out which half of their markup is decorative.
Which types still earn a visible result, and which stopped?
The honest list is shorter than it was three years ago. Google retired or restricted several popular treatments, and markup for a retired feature still validates, which is why so many sites carry it.
| Type | Visible treatment | Current state |
|---|---|---|
| Product | Price, availability, merchant listing | Still widely shown; needs the commerce properties, not just name and image |
| Review and AggregateRating | Star rating | Limited to specific types, and ignored when the reviews are about the site itself |
| FAQPage | Expandable question list | Restricted in 2023 to a small set of authoritative government and health sites |
| HowTo | Step list in the result | Retired from Search; the markup validates and shows nothing |
| BreadcrumbList | Breadcrumb trail replacing the URL line | Still shown, and cheap to implement |
| Organization | None of its own | Feeds entity understanding; judge it on that, not on snippets |
| Article | None of its own | States headline, author and dates for Google's reading of the page |
Read that table as a budget. Breadcrumbs and Organization are worth shipping because they are nearly free. A hand-maintained FAQPage block on 400 pages is a liability: the cost is ongoing and the payoff was withdrawn.
How do you tell eligibility from a display decision?
Use two different tools, because they answer two different questions. The Rich Results Test tells you whether a page is eligible. The Performance report's Search Appearance filter in Google Search Console tells you whether a result actually appeared.
The enhancement reports sit between the two and are the ones most often misread. They count valid items detected, which is a crawling fact rather than a display fact. A report that says 1,200 valid Product items and a Search Appearance filter that reports almost no merchant impressions is not a contradiction; it is the answer. Google read all 1,200 and chose to show something else.
Adding an AggregateRating you collected about your own business to get stars. Google ignores self-serving reviews for this treatment, and manufactured ratings fall under its structured data policies, where the downside is a manual action rather than no stars.
What should you ship when no rich result is on offer?
Ship the markup that states facts a parser would otherwise have to guess, and stop there. That is usually Organization, BreadcrumbList, Article on editorial pages, and the full commerce properties on anything transactional.
Then make the call the data supports. If the Search Appearance filter shows no feature impressions for a type after a full crawl cycle, the remaining argument for that markup is the machine reading, which is real but does not justify a maintenance burden on hundreds of templates. Keep the generated markup, retire the hand-written blocks for withdrawn features, and spend the freed time on the thing a snippet cannot fix: whether the page deserves the click once organic search sends it.