Your Schema Validates but No Rich Result Appears: What to Check

Valid structured data can make a page eligible for a rich result; it does not earn one. When a page passes the Rich Results Test and still shows a plain listing, work through four checks in order: Google currently supports the feature, the page meets that feature’s own rules, the markup matches what readers see, and Google has indexed the version with the markup. If all four hold, the remaining decision is Google’s, and the useful thing to do is record your evidence and stop changing the markup.

Google is explicit about this. Its structured data general guidelines, checked September 27, 2026, say: “Google 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.” The same page says using structured data “enables a feature to be present, it does not guarantee that it will be present.”

Confirm the feature is supported today

Open Google’s search gallery, checked September 27, 2026. It lists the structured data features Google Search currently documents, including Article, Breadcrumb, Event, Local business, Organization, Product, Profile page, Recipe, Review snippet and Video. If your markup targets a type that is not listed, Google documents no rich result for it, and fixing the markup will not change that. FAQ and HowTo, for example, are not in the gallery. Google’s retired rich results covers the features that have been removed and what to do with the markup.

Two related mix-ups are common:

• The Schema Markup Validator passed. The Schema Markup Validator checks markup against schema.org. Google’s structured data testing page, checked September 27, 2026, says it tests schema.org markup “without Google-specific validation.” Schema.org defines far more types than Google uses for search features (its vocabulary page, checked September 27, 2026, counts 826 types), so a clean result there does not test Google eligibility.
• An SEO plugin prints the type. A plugin generating markup is an implementation aid. WP Visibility, for example, prints Organization or Person, WebSite, WebPage, BreadcrumbList, and a BlogPosting node (a subtype of Article) on posts, and deliberately generates no FAQPage or HowTo. It cannot make Google show a rich result, and it cannot check your page against every content policy.

Check the page against the feature’s own rules

Each feature in the gallery has its own page with required properties, recommended properties and guidelines. Google’s introduction to structured data, checked September 27, 2026, says you must include all required properties for an object to be eligible for enhanced display. Read the specific page, not a general checklist. Two examples of details that are easy to miss:

• Google’s breadcrumb documentation, checked the same day, says: “This feature is available on desktop in all regions and languages where Google Search is available.” If you are checking on a phone, you are checking the wrong place.
• Google’s Article documentation, checked the same day, lists no required properties and says images must be crawlable and indexable. An image blocked by robots.txt, or hosted on a domain that blocks crawlers, fails that rule even though the markup itself is well formed.

Read the feature’s guidelines for content rules too. Many feature pages add content guidelines beyond the required properties, and the general guidelines note that markup can be wrong in ways the Rich Results Test does not catch.

Check that the markup describes the visible page

The general guidelines list reasons a correctly marked-up page may not get a rich result. Three of them are about content:

• “The structured data is not representative of the main content of the page, or is potentially misleading.”
• “The structured data is incorrect in a way that the Rich Results Test was not able to catch.”
• “The content referred to by the structured data is hidden from the user.”

Open the page signed out and compare. Is the marked-up headline the visible headline? Are the dates the ones in the byline? Is the review, price or event date in the markup also visible on the page? The same guidelines say “Don’t mark up content that is not visible to readers of the page,” and to put structured data “on the page that it describes, unless specified otherwise by the documentation.”

Check what Google has indexed

The Rich Results Test checks the page as it is now. Search results reflect the version Google last indexed.

1. URL Inspection. In Search Console, inspect the URL. The indexed view shows the rich result types Google detected the last time it indexed the page; the live test shows what it finds now. Google’s URL Inspection help, checked September 27, 2026, is clear that a valid live test does not mean the page will be indexed. It also says not every rich result type is supported by the tool: a type it does not list, such as Article, can be present and valid on the page but will not appear there.
2. Rich result reports. Google’s rich result status reports help, checked the same day, says a report appears only for a supported rich result type where Google found valid markup (Article is not on its list of report types), and each issue shows the date Google last crawled the affected page. A fix you made yesterday may not show until Google crawls the page again.
3. Access. The general guidelines say not to block structured data pages from Googlebot with robots.txt, noindex or other access controls. Check the page is not set to noindex and that the markup is not served only to signed-in visitors.
4. Manual actions. Look at the Manual actions report in Search Console. The general guidelines say violations can lead to a manual action that makes a page ineligible for rich results.

Record what remains outside your control

If the feature is supported, the page meets its rules, the markup matches the page, and the indexed version has valid markup, there is nothing left to fix in the markup. The general guidelines explain why: “The Google algorithm tailors search results to create what it thinks is the best search experience for a user, depending on many variables, including search history, location, and device type.” Write down what you checked so the next person does not redo it:

Resist rotating through new markup types in the hope of triggering a feature. Each change resets the evidence you were collecting and can introduce errors. If your markup came from a plugin and you are unsure whether the plugin or the page is at fault, the structured data audit shows how to separate them.

Rich result checklist

• The feature is in Google’s search gallery today.
• Every required property on the feature’s page is present and true.
• The markup matches visible content on the same page.
• URL Inspection shows the markup in the indexed version, where the tool supports the type.
• The page is not noindexed or blocked, and there is no manual action.
• Your checks are recorded with dates.