Passing the Rich Results Test means Google can parse supported markup and may consider the page eligible. It does not guarantee indexing, selection, or display of a rich result for any particular search.
- A successful syntax test establishes eligibility conditions rather than a promised search appearance.
- Structured data must accurately represent visible, current page content and remain accessible to crawlers.
- Use live URL testing, indexing evidence, enhancement reports and performance data instead of judging one manual query.
- Schema.org validity and Google rich-result eligibility answer different questions.
01
Definition
A page can pass the Rich Results Test and still appear as an ordinary blue-link result. That outcome is not a contradiction.
A successful test means Google can parse the submitted markup and recognize a supported structured-data type. It does not mean the page has earned, reserved, or permanently unlocked a particular search appearance. Google’s current general guidelines state that structured data enables eligibility for a feature rather than guaranteeing that the feature will appear. Search systems can decide that another presentation, including a normal text result, better fits the query, user, device, location, or available result set. General structured data guidelines[1]
Separate these states:
- Parseable: The syntax can be read.
- Recognized: Google identifies a supported item or feature.
- Eligible: Required technical and content rules appear satisfied.
- Indexed: Google has processed the page into its search systems.
- Selected: Google chooses the page and feature for a particular search.
- Displayed: The rich result actually appears for that impression.
The Rich Results Test mainly helps with the first three states. It cannot promise the last three.
Structured data also serves a broader descriptive purpose. Google explains that structured data supplies explicit clues about the meaning of a page and the entities described on it. Rich results are one possible use, not the only reason the data exists. Introduction to structured data markup[2]
02
Mechanism
The markup must describe the visible page
A technically valid object can remain ineligible when it exaggerates, misstates, or describes material that users cannot see.
Examples include:
- Marking up reviews that are not shown on the page
- Describing an event that has expired
- Publishing a recipe object on an article that is not actually a recipe
- Supplying an offer price that differs from the visible price
- Marking a category page as one specific product
- Using an organization logo that is blocked or unrelated
- Creating breadcrumb positions that do not match a meaningful path
Google’s quality guidelines require structured data to represent the page’s main content, remain current, and avoid hidden or misleading claims. These requirements are not completely testable with syntax tools. A green test result can therefore coexist with a quality failure. General structured data guidelines[1]
The page must be accessible and indexable
A rich result cannot be shown for a page that Google cannot properly access or use.
Check:
- Successful public response
- No login requirement
- No blocking robots rule
- No
noindex - Crawlable structured-data images
- Correct canonical URL
- Rendered markup present when JavaScript is required
- Content visible in the rendered page
- No manual action affecting structured data
The Rich Results Test can evaluate a code sample that is not deployed. It can also test a live page at one moment while the indexed version remains older. Use URL Inspection to compare the live page with the indexed state and allow time for recrawling and reprocessing. Google recommends deploying a small sample, inspecting the live URL, then monitoring the relevant rich-result report after indexing. Structured data testing tools[3]
Eligibility depends on the exact feature
Schema.org vocabulary and Google rich-result support are overlapping but different systems.
A property can be valid schema.org without being used by a Google rich-result feature. Likewise, a supported type can require a particular set of properties or content rules beyond generic schema validity.
Use two tests for different questions:
| Question | Appropriate check |
|---|---|
| Is the syntax and schema vocabulary valid? | Schema Markup Validator |
| Is the page eligible for a supported Google rich-result type? | Rich Results Test |
| What did Google fetch and select? | URL Inspection |
| Are many pages valid or invalid over time? | Search Console enhancement report |
| Did the feature actually receive impressions? | Search performance data |
A Schema Markup Validator success does not establish Google feature eligibility. A Rich Results Test success does not establish future display.
Search appearance is query dependent
One indexed page can appear differently across searches.
The system may show:
- A standard text result
- A rich result
- An image result
- A product presentation
- A local or knowledge feature
- No result from the page
This means spot-checking one query is weak evidence. The absence of a rich result for one search does not prove that the markup has never been used.
03
Examples
Valid recipe markup, ordinary result
The page passes required-property checks, remains indexed, and has no manual action. Google still shows a standard result for a particular query. That is a permitted outcome, not a technical error.
Investigation:
- Confirm that the visible page is genuinely a recipe.
- Confirm that required and recommended fields match the page.
- Inspect the live and indexed page.
- Check the recipe enhancement report.
- Review performance over a meaningful period.
- Avoid repeatedly changing valid markup solely because one search looked ordinary.
Product data differs from the page
The markup says the product costs 39.99 and is in stock. The visible page says 49.99 and unavailable.
The object may parse perfectly. The mismatch violates the core requirement that structured data represent current visible content. Fix the source-of-truth problem rather than adding more properties.
JavaScript inserts markup late
A browser eventually displays a JSON-LD object, but rendering fails for Google or the object is generated only after an interaction.
Test the URL, inspect rendered HTML, and confirm through logs or rendering tools that the markup exists without requiring a click. Passing a copied code sample does not prove the deployed page reliably delivers it.
Valid Organization data without a knowledge panel change
Organization markup can help Google understand administrative details and disambiguate an entity. It does not provide direct control over every knowledge-panel field or guarantee that a panel appears. Treat it as a consistency layer, not a form that instantly edits search.
04
Boundaries
Do not respond to a missing rich result by adding unrelated types, fabricated reviews, invisible text, or increasingly elaborate graphs. More markup is not automatically better markup.
Use this diagnostic order:
- Confirm that the desired feature still exists and applies to the page type.
- Test the live URL, not only copied code.
- Verify required properties.
- Compare markup with visible content.
- Check crawl, indexability, canonical, and rendering state.
- Check enhancement reports and manual actions.
- Allow time for recrawling.
- Evaluate search-performance evidence rather than one manual query.
- Record the remaining uncertainty.
Continue with JSON-LD vs. Microdata vs. RDFa when the problem concerns implementation format. Use Breadcrumb Structured Data for breadcrumb-specific validation. Use Product Structured Data when product snippets and merchant listings are being confused.
The defensible conclusion is narrow: valid markup establishes that the submitted structure is readable and may be eligible. Search appearance remains selected per result, not owed to the site.
References
Sources behind this record
- General structured data guidelines — Google (accessed August 1, 2026)
- Introduction to structured data markup in Google Search — Google (accessed August 1, 2026)
- Explore the search gallery and test your structured data — Google (accessed August 1, 2026)
Corrections
Correction history
No corrections recorded.
To report an error, use the public corrections path.
Search appearance is selected dynamically by Google and can vary by query, user, device, location and processing state even when the underlying markup remains valid.