Skip to content

Rich results not showing: why valid markup gets no result

Rich results not showing even though the markup passes the Rich Results Test? Valid markup only makes a page eligible. Here are Google's documented causes and fixes.

By Crawlito · 9 min read

In short

  • Google says structured data enables a feature to be present but does not guarantee that it will be present, so a passing Rich Results Test means eligibility, not display.
  • Google lists hidden content, markup that is not representative of the main content, and errors the Rich Results Test cannot catch as reasons a rich result may not show.
  • In Search Console rich result reports, an item with a critical issue cannot appear as a rich result, while non-critical issues only limit how it can look.
  • Some rich results appear on one device type only: Google's breadcrumb documentation says that feature is available on desktop.
  • A structured data manual action removes rich result eligibility for the affected pages but, according to Google, does not affect how they rank in web search.
On this page

Rich results are not showing for most valid pages because valid markup only makes a page eligible. Google's structured data guidelines say that using structured data "enables a feature to be present, it does not guarantee that it will be present." Once the syntax is right, the remaining causes are an unindexed page, a feature Google does not show for that query, place or device, markup that breaks a policy rule no validator checks, or a manual action. Work through them in that order.

This post is the troubleshooting sequence for markup that already passes. If the Rich Results Test still shows errors, fix those first with common JSON-LD errors. If you are unsure whether the type you use still has a Google feature at all, check deprecated rich results before going further.

Why passing the Rich Results Test is not enough

The Rich Results Test answers one question: does this markup, on the live URL, meet the technical requirements for a feature? It does not tell you whether Google has indexed the page, whether the feature exists for your searchers, or whether the markup follows the content rules. Google's guidelines say plainly that their quality rules "are not easily testable using an automated tool."

Google's help page on missing features in search results and its structured data guidelines together list these documented causes:

CauseWhere Google says itHow to check
Page not crawled or indexed yetMissing features help pageURL Inspection, indexed version
Google cannot access the page, or it is blocked by robots.txt or noindexMissing features help page, guidelinesURL Inspection, response headers
Markup has a critical issueRich result report helpSearch Console rich result report
Feature not supported in your location, or only on one deviceMissing features help pageThe feature's own documentation
Google decided another result type suits the query betterMissing features help pageNothing to fix
Markup not representative of the main content, or misleadingGuidelinesCompare markup with the visible page
Marked-up content hidden from the userGuidelinesLook at the page as a visitor
Self-serving or fake reviewsReview snippet docs, guidelinesWho controls the reviews
Structured data manual actionManual actions reportSearch Console

Step 1: confirm the page is indexed with its markup

A rich result can only appear for a page that is in Google's index, and Search Console's reports only count indexed pages. Google's page on debugging missing structured data says "Only indexed pages appear in Search Console reports" and names "a login requirement, robots.txt restrictions, or a noindex directive" as reasons the data is not seen.

  1. Open URL Inspection for the exact URL, including the right host and protocol.
  2. Check the indexed version first, not the live test. If the page is not indexed, that is your problem, and the rich result question waits until it is solved.
  3. In the indexed result, look at the detected structured data. If the live test finds your markup but the indexed version does not, Google has probably not recrawled since you added it. The missing features help page warns that "a crawl request can take a week to fulfill."
  4. Make sure the image URLs in your markup can be fetched. The guidelines say "All image URLs specified in structured data must be crawlable and indexable."
  5. If the markup is injected by JavaScript, confirm it is in the rendered HTML. Google says it can process structured data "available in the DOM when it renders the page", but for Product markup it warns that "dynamically-generated markup can make Shopping crawls less frequent and less reliable."

The Rich Results Test fetches the live page as Google-InspectionTool, so it can pass on a page that Googlebot has never indexed. URL Inspection and rendered HTML explains how to compare the indexed and live versions.

A quick check from the command line shows what your server returns right now, outside either Google tool:

bash
URL="https://www.example.com/products/oak-table"

# Status code and any X-Robots-Tag header
curl -sI "$URL" | grep -iE '^(HTTP|x-robots-tag)'

# A robots meta tag in the HTML
curl -s "$URL" | grep -ioE '<meta[^>]+name="(robots|googlebot)"[^>]*>'

# The image named in the markup must also return 200
curl -sI "https://www.example.com/images/oak-table.jpg" | head -1

A noindex in either place, a 4xx or 5xx status on the page, or an image URL that cannot be fetched explains a missing result on its own. Your server may answer Googlebot differently from curl, so treat URL Inspection as the final word.

Step 2: read Search Console's critical and non-critical issues

The rich result report overview splits issues into two kinds, and the difference decides whether the item can show at all:

Report termWhat Google saysWhat it means for you
Valid itemHas no critical issues and "can appear on Google as a rich result"Eligible, not guaranteed
Critical issue"These issues prevent your structured data from being used by Google"Item cannot appear as a rich result
Non-critical issueListed under "Improve item appearance"Item is eligible, but missing optional detail
Invalid itemHas "at least one critical issue"Fix before expecting anything

Three details trip people up:

  • The numbers count items, not pages. Google says the "numbers in the reports reflect items not pages", so one product page with Product and BreadcrumbList markup can count once in each of two reports. One item with several issues appears in several issue tables but once in the invalid total.
  • The report is a sample. Google says the reports "aren't a comprehensive list of all detected items", and example tables stop at 1,000 rows. A URL missing from the report is not proof that Google found no markup there; check it with URL Inspection.
  • Validation is slow. After a fix, Validate fix has Google "initially check a sample of pages", and Google says the process "can take two weeks or more, depending on crawl frequency." If it fails, Search Console validation failed covers why.

Step 3: check the feature exists for that query, place and device

Even a valid, indexed item is shown only when Google decides the feature suits the search. The missing features page says "Google doesn't guarantee display of rich results for any given page" and that Google "sometimes decide[s] that a specific rich result isn't the best result for that query." There is no setting for this, so test with queries where the feature would be useful, not only your brand name.

Then rule out the two availability limits Google names:

  1. Location and language. "Your rich result might not be supported for your location yet." Each feature page states its own availability. For example, Google's product snippet documentation says pros and cons from editorial reviews are available in ten languages, including English, French and German, and not in others.
  2. Device. "Test on both desktop and mobile. Many rich results can appear on only one device type." Google's breadcrumb documentation says that feature "is available on desktop", so checking breadcrumbs on a phone will never show them.

Also check that the feature still exists. Google has retired a number of rich results, including seven types it announced it would phase out in June 2025, and markup for a retired type can still look valid in a general schema validator while no result ever appears.

Step 4: run the policy checks no validator can do

These are the causes no tool reports for you. Google's guidelines list reasons a rich result may not show even when the test passes, including these, quoted directly:

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

Turn each one into a manual check on a real page:

CheckWhat fails itFix
Is the marked-up item the main subject of the page?Product markup on a category page, Recipe markup on a blog post that only links to a recipePut markup on the page it describes; Google's product docs say product rich results only support pages that focus on a single product
Can a visitor see every marked-up fact without tools?Ratings, prices or Q&A that exist only in JSON-LDShow the content, or remove it from the markup
Is the most specific type used?Thing or CreativeWork where Recipe or Product appliesUse the most specific schema.org type, as the guidelines advise
Who controls the reviews?A business marking up reviews of itself on its own siteRemove the star markup from those pages
Are the reviews real and from users?Testimonials written or picked by the siteMark up only genuine reviews, or none

Two rules on reviews deserve a closer look. Google's review snippet documentation says that when the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization type "are ineligible for star review feature", even if the reviews come through a third-party widget. It also says "It must be immediately obvious to users that the page has review content." The Review and AggregateRating guide covers what remains eligible.

A pattern to look for in templates: markup filled from data that is no longer on the page. In this example, the theme stopped displaying reviews, but the JSON-LD still carries the rating:

html
<!-- Visible page: no reviews section, no stars -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Oak dining table",
  "aggregateRating": { "@type": "AggregateRating", "ratingValue": 4.8, "reviewCount": 37 }
}
</script>

The Rich Results Test can report this Product as valid. Google's rule is "Don't mark up content that is not visible to readers of the page", so the fix is to show the reviews again or drop aggregateRating.

Step 5: rule out a structured data manual action

If a human reviewer at Google finds markup that breaks the guidelines, Google can apply a manual action. The guidelines say "A structured data manual action means that a page loses eligibility" for rich results and that "it doesn't affect how the page ranks in Google web search." So affected pages can keep their positions and still lose their rich results.

Open the Manual actions report in Search Console. Google also sends a message to the Search Console message center. Structured data issues listed there include:

  • Structured data found on hidden content
  • Review written by the site or person providing the service
  • Structured data does not match content
  • Company marked as product, or non-product labeled as product
  • Event structured data is actually a promotion
  • Structured data policy violation

Fix every affected page, not only the examples shown: Google says fixing just some pages "will not earn you a partial return to search results." Then select Request Review. Google says most reconsideration reviews can take several days or weeks and asks you not to resubmit before you get a decision.

Frequently asked questions

How long after adding markup should a rich result appear?

Google gives no timeline for display. It says a crawl request can take a week to fulfill, and the rich result can only appear after Google has indexed the page with the markup, so check URL Inspection before waiting longer.

Do warnings stop a rich result from showing?

No. Search Console calls them non-critical issues: the item stays eligible but may look less complete. Only critical issues make an item invalid.

My rich result showed before and then disappeared. Why?

Check for a manual action, a drop in indexed pages, markup that stopped parsing after a template change, and whether Google retired the feature. Search Console's debugging page names fewer indexed pages and newly invalid markup as causes of drops.

Does a structured data manual action hurt rankings?

Google's structured data guidelines say it removes rich result eligibility but does not affect how the page ranks in web search.

Do rich results affect AI search answers?

Google does not document a link between rich result eligibility and AI answers. Its AI features documentation says no special schema.org markup is needed for AI Overviews or AI Mode; see structured data for AI search.

Check what crawlers receive on the page

Before chasing a policy cause, confirm the basics on the server side: the page returns 200, carries no noindex, and has its JSON-LD in the HTML. The free check tests one page with no account. For a site where the problem spans many templates, an audit covers up to 500 pages with human review and a PDF of evidence and prioritized fixes.

Filed under Structure and schema. Topics: structured-data, google, search-console, troubleshooting