Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

Why might valid structured data fail to produce an eligible rich result?

Because validity and eligibility are different tests, and eligibility is not a guarantee of display. Markup can be perfectly formed according to schema.org and still lack a property Google requires for a specific feature, describe a type Google has no feature for, sit on a page that breaks Google’s content guidelines, or simply not be chosen. Google states the last point without qualification: 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”, and “Using structured data enables a feature to be present, it does not guarantee that it will be present” (Google’s structured data general guidelines).

Syntax versus feature eligibility

Three separate questions are being asked, by three different checks.

Question Tool What a pass means
Is the markup valid schema.org? Schema Markup Validator The vocabulary and syntax are correct
Does it meet Google's requirements for a specific feature? Rich Results Test The page is eligible for that feature
Is the feature being shown? Search results, and Search Console's performance and enhancement reports Google chose to display it

The first check knows nothing about Google’s features. The schema.org vocabulary is far larger than the set of features Google supports, and Google publishes required and recommended properties for each feature it does support. Markup can pass the validator and fail the Rich Results Test in two ways.

  • The type is valid and Google has no feature for it.
  • The type is supported and a property Google requires for that feature is missing. Google’s documentation says “You must include all the required properties for an object to be eligible” for a rich result (Google’s introduction to structured data).

A contrast for one page, with hypothetical results:

Check Result (hypothetical) Reading
Schema Markup Validator No errors, no warnings Syntactically valid
Rich Results Test "No items detected" No Google feature recognized for this markup
After adding a required property "Valid item detected", with warnings for recommended properties Eligible
Search results two weeks later Plain result Not displayed, for now

Each line is a correct result from its own test. They do not contradict each other.

Page and policy criteria

An eligible item can still be ruled out by the guidelines. Google’s general guidelines list reasons, including that the structured data “is not representative of the main content of the page, or is potentially misleading”.

Conditions that remove eligibility:

  • Content in the markup that visitors cannot see. The guidelines say “Don’t mark up content that is not visible to readers of the page”.
  • Markup for something that is not the page’s main subject.
  • Out-of-date information. The guidelines ask for up-to-date information in markup.
  • Markup that is incorrect in a way the Rich Results Test was not able to catch, which the guidelines list as a reason of its own.
  • A feature-specific rule. Review stars, for example, are not available to LocalBusiness or Organization pages whose reviews the business itself controls.
  • Blocked access. The guidelines say not to block structured data pages to Googlebot “using robots.txt, noindex, or any other access control methods”.
  • A manual action. The guidelines note that a structured data manual action means a page loses eligibility for rich results. The Manual Actions report in Search Console shows whether one applies.

Features can also be withdrawn. The FAQ rich result is an example: the changelog for Google’s Search documentation records a deprecation notice stating that the feature “will no longer appear in Google Search starting May 7, 2026” (Google Search documentation updates). Markup written for a retired feature stays valid and produces nothing.

Search presentation discretion

Past eligibility, the decision is Google’s. The guidelines explain that the algorithm tailors results to what it thinks is the best search experience for a user, “depending on many variables, including search history, location, and device type”, and that in some cases it may determine that one feature is more appropriate than another, “or even that a text result is best”.

What follows from that wording, for anyone reporting on rich results:

  • The same eligible page can be shown with the feature to one searcher and as a plain result to another.
  • Device type is among the named variables, so a check on one device does not settle the other.
  • A plain text result for an eligible page is an outcome the guidelines describe, not a fault.
  • New or changed markup is read only when Google next crawls the page.

None of these is an error to fix. The markup makes the display possible. It does not command it.

Inspection and testing

Work through the checks in order, and stop at the first failure.

  1. Syntax. Run the Schema Markup Validator. Fix errors.
  2. Feature eligibility. Run the Rich Results Test on the live URL. Confirm the intended feature is detected, with no errors. Read the warnings for recommended properties.
  3. Rendered output. In the Rich Results Test or URL Inspection, confirm the markup is present in what Google renders, especially if a script inserts it.
  4. Indexing. Use URL Inspection to confirm the page is indexed and the enhancements section lists the item.
  5. Guidelines. Compare the markup with the visible page, field by field. Check the feature’s own content rules.
  6. Manual actions. Check the report.
  7. Site-wide state. Open the relevant enhancement report in Search Console for counts of valid and invalid items and their trend.
  8. Display. In the performance report, use the search appearance filter, where the feature has one, to see whether rich results are being served for any queries.
  9. Live check. Search several queries for the page, on more than one device, and record what appears, with the date.

Reading the outcome:

Finding Conclusion
Fails step 1 or 2 Fix the markup
Passes 1 and 2, fails 3 or 4 A rendering or indexing problem
Passes 1 to 4, fails 5 or 6 A guideline problem
Passes 1 to 7, never displayed Eligible and not selected; not a markup fault
Displayed for some queries Working as designed

When everything passes and nothing is displayed, the remaining levers are the page itself, its content and how well it serves the queries involved, and patience. Adding more markup does not raise the chance.

The requirements differ by feature. Two that publishers ask about, with their own property rules, are covered in the guides to when to add Article structured data and when an author profile page should use ProfilePage structured data.

The summary: valid means well formed, eligible means it meets Google’s rules for a feature, and displayed means Google chose to show it. Each has to be checked separately.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *