The common belief is that valid structured data equals rich result eligibility. That assumption is wrong and leads to wasted diagnostic effort. Structured data validation confirms syntax compliance and required property presence. Rich result display is a separate decision that factors in page quality, site trust, competitive density, SERP layout constraints, and Google’s own testing of rich result formats. Google’s documentation explicitly states that correctly marked-up pages are not guaranteed to show rich results. A page can have perfect schema and never earn enhanced SERP treatment, and diagnosing why requires evaluating factors far beyond markup validity.
The Gap Between Validation Pass and Rich Result Eligibility
The Rich Results Test and Search Console’s enhancement reports validate two things: the structured data is syntactically correct JSON-LD (or Microdata/RDFa), and the required properties for the target rich result type are present. These tools do not evaluate whether Google considers the page eligible for rich result display.
Eligibility operates on a separate layer. Google’s own documentation acknowledges that structured data may be correct “in a way that the Rich Results Test was not able to catch” while still failing eligibility requirements. The validation tool tests the markup. The eligibility system evaluates the page.
The gap between validation and eligibility varies by schema type. Product schema with all required properties passes validation, but rich result display requires that the product has verifiable pricing, genuine availability data, and is offered by a site with sufficient commercial trust signals. Review schema passes validation with the required reviewRating and author properties, but Google restricts self-serving review rich results and suppressed LocalBusiness review snippets for entities that control their own reviews. FAQ schema passes validation on any site, but since August 2023, FAQ rich results are limited to well-known government and health authority websites.
The diagnostic starting point is identifying which eligibility layer is blocking display. Validation pass eliminates syntax errors from the diagnosis. The remaining candidates are page quality, domain trust, schema-specific restrictions, and SERP-level competition.
Position confidence: Confirmed. Google’s documentation explicitly states that passing validation does not guarantee rich result display.
Diagnosing Page-Level Quality and Trust Barriers to Rich Result Display
Google applies quality thresholds to rich result eligibility that are independent of structured data accuracy. Pages on domains with manual actions, thin content patterns, or low E-E-A-T signals may have all structured data ignored for rich result purposes, even when the markup itself is flawless.
The first diagnostic check is Search Console’s Manual Actions report. An active spammy structured markup manual action suppresses all rich results across the affected URL scope (site-wide or section-specific). This is the only explicitly confirmed quality barrier because Google reports it directly.
The second check evaluates domain-level structured data trust. Sites that have historically implemented accurate, content-consistent schema build implicit trust that increases rich result display rates. Sites with patterns of inaccurate or over-optimized schema accumulate negative trust signals that suppress rich results even on pages with legitimate markup. This trust signal is not reported in any Google tool but can be inferred by comparing your rich result display rate against competitors with similar structured data implementations.
The third check assesses page-level content quality. Thin content pages, pages dominated by ads, pages with user experience issues flagged in Core Web Vitals reports, or pages that lack demonstrable expertise on the marked-up topic may be excluded from rich result display. Google has stated that rich results are designed to enhance the search experience for users, and pages that would not serve that purpose are excluded regardless of markup quality.
A practical diagnostic test: publish identical structured data on a high-quality, comprehensive page and on a thin, low-value page within the same domain. If the high-quality page earns rich results and the thin page does not, quality filtering is the blocking factor.
Schema-Specific Eligibility Requirements Beyond Required Properties
Each rich result type has eligibility nuances that extend beyond the documented required properties. These undocumented or partially documented requirements are the most common cause of “valid but no rich result” situations.
Product rich results require the product to be a physical or clearly defined item available for purchase. Service pages marked with Product schema rarely generate rich results because Google’s product rich result system is designed for purchasable items with concrete attributes (price, availability, condition). The offers property must contain a real, current price, not a “starting from” range or a “contact for pricing” placeholder.
Review and AggregateRating rich results are restricted by Google’s self-serving review policy. If the entity being reviewed controls the reviews displayed on the page, rich result eligibility is denied. This restriction affects LocalBusiness and Organization reviews on the business’s own website. Third-party review platforms that aggregate independent reviews are not affected.
FAQ rich results eligibility was dramatically narrowed in 2023. Only well-known, authoritative government and health sites now receive FAQ rich result treatment. All other sites can implement FAQ schema without generating visible SERP enhancements, though the markup may still contribute to entity understanding and AI Overview citations.
HowTo rich results were similarly restricted on mobile SERPs, where the vast majority of searches occur. Desktop may still display HowTo rich results in limited cases, but the mobile restriction effectively eliminates the traffic impact for most sites.
Diagnosing schema-specific restrictions requires checking the current status of each rich result type against Google’s documentation, which is updated as features are added or deprecated. In 2025 alone, Google deprecated rich results for Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, and Vehicle Listing schema types.
SERP Layout Competition That Suppresses Individual Rich Results
Even when page quality and schema eligibility are satisfied, SERP layout constraints can suppress rich result display. Google limits the visual real estate allocated to rich results on any given SERP, and multiple competing signals determine which results receive enhanced treatment.
SERP feature competition is the primary suppression mechanism. When a query triggers an AI Overview, Knowledge Panel, featured snippet, and a local pack, the remaining organic results have reduced visual space. Google may suppress product rich results, FAQ rich results, or review stars on organic listings when other SERP features already provide the information those rich results would display.
Competitive density affects display on a per-query basis. If 8 of the top 10 results have valid Product schema, Google does not display rich results for all 8. Typically, 3-5 results receive rich result treatment, with selection influenced by the overall ranking position, structured data completeness (including recommended properties, not just required ones), and domain trust signals.
The diagnostic approach for SERP-level suppression is direct observation. Search the target query in an incognito browser and examine which results, if any, display rich results. If competitors show rich results and your page does not, the issue is page-level or domain-level. If no results show rich results for that query, the issue is SERP layout suppression, and no amount of structured data optimization will produce a rich result for that query at this time.
The Diagnostic Action Sequence From Validation Pass to Root Cause
A systematic diagnostic protocol for rich result failure follows a priority-ordered sequence that eliminates causes from most impactful to least.
Step 1: Confirm Googlebot access to rendered structured data. Fetch the page using Google’s URL Inspection tool and verify that the rendered HTML contains the expected JSON-LD. JavaScript-rendered structured data that fails to execute within Googlebot’s rendering timeout will not be parsed, regardless of what the Rich Results Test shows (which uses its own rendering environment).
Step 2: Check for manual actions. Review Search Console’s Manual Actions report for structured data spam flags. This is the only guaranteed blocking factor that Google explicitly reports.
Step 3: Verify schema type eligibility. Confirm that the target rich result type is still actively supported and that your site category qualifies. FAQ and HowTo restrictions, review self-serving policies, and recently deprecated schema types eliminate many valid-but-ineligible scenarios.
Step 4: Assess page and domain quality. Compare your page’s rich result display rate against competitors with similar structured data. If competitors show rich results and you do not, investigate domain trust, page quality, and content depth differences.
Step 5: Evaluate SERP-level competition. Search the target query and assess whether any organic results display the target rich result type. If none do, the query’s SERP layout does not currently allocate space for that rich result type.
Step 6: Audit recommended properties. Pages that include only required properties may lose competitive rich result selection to pages that include recommended properties as well. Adding aggregateRating, brand, image, and other recommended properties can shift the competitive balance in your favor.
Document findings at each step. The root cause often involves multiple factors acting simultaneously, and addressing only one while ignoring others produces no visible improvement.
Can adding recommended schema properties to an already-valid implementation unlock rich results that required properties alone did not trigger?
Yes. In competitive SERPs where multiple pages have valid structured data, Google uses recommended properties as a tiebreaker for rich result selection. Adding properties like aggregateRating, brand, image, and review to a Product schema that already includes all required properties can shift the competitive balance. Pages with 80-100% property completeness consistently outperform pages with only required properties in rich result display rates.
Does Core Web Vitals performance directly affect rich result eligibility for pages with valid schema?
Core Web Vitals contribute to page quality assessment, which influences rich result display decisions. Pages with poor LCP, CLS, or INP scores may be excluded from rich results not because of a direct technical gate but because poor performance signals lower page quality. Fixing Core Web Vitals alone will not guarantee rich results, but persistent performance issues can contribute to the quality threshold that blocks display.
Why might a page lose rich results it previously displayed without any changes to its structured data?
Rich result display depends on SERP-level factors that change independently of your markup. A new competitor entering the top 10 with more complete schema, an AI Overview deploying for the query and consuming visual space, or Google restricting a schema type (as with FAQ in 2023) can all remove previously displayed rich results. The structured data remains valid, but the external conditions governing display have shifted.
