Why does valid schema sometimes never show a rich result?

Because valid only means the markup is built correctly. Whether a rich result appears is a separate decision Google makes for each page and search, and passing a test does not oblige it to show anything. Google’s structured data policies say so directly: it “does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test.” Between valid and shown sit several checks that a validator does not run.

The gates between valid and shown

1. The feature still exists for that type. Some markup validates long after its feature is gone. The FAQ rich result stopped appearing in May 2026 and HowTo results ended in 2023, so markup of those types can be flawless and still show nothing.
2. The page is eligible for that feature. Eligibility rules differ by feature. For merchant listings, Google’s merchant listing documentation says only pages where a shopper can buy the product qualify, not pages that link to other sites that sell it.
3. Required properties are present. Google’s policies state that “Items that are missing required properties are not eligible for rich results.” Recommended properties are optional; required ones are not.
4. The markup matches what the page shows. Marking up a rating visitors cannot see, or a price that differs from the visible one, conflicts with the rule that structured data must represent the page’s content.
5. Google has crawled the version with the markup. If the markup is added by JavaScript, check the rendered HTML in URL Inspection to confirm it is there.
6. The policy for that feature is met. Review snippets, for instance, cannot use ratings aggregated from other websites, and a business that controls reviews about itself is ineligible for the star feature on its LocalBusiness or Organization pages.

Checks 4 and 6 rest on Google’s structured data policies, and how Google treats markup that breaks them is read in why Google ignores schema it considers spammy. For Product markup in particular, read whether Product schema affects ranking or only the rich result; for markup that validates but nests wrongly, see what breaks when schema is nested incorrectly.

Where to look

Run the live page through the Rich Results Test to confirm the markup Google can read today, then inspect the URL in Search Console, which reports on Google’s indexed version of the page. If the two disagree, the indexed version is older than your fix and needs a recrawl. A clean result in both places means the page is eligible, which is still not the same as being shown for every search.

When everything checks out

If the type has a live feature, required properties are present, the markup matches the page, the feature’s own eligibility and policy rules are met, and Google has indexed it, the remaining factor is Google’s choice for each search; valid markup is necessary, not sufficient. Google’s policies also note that it will not show a rich result for time-sensitive content that is no longer relevant, such as an event that has passed. Keep the markup accurate, then judge it by whether the feature appears for the searches that matter to you over the following weeks, not by a single test.