Rich Results Not Showing in Google: Causes and Fixes
Rich results — star ratings, FAQs, recipes, breadcrumbs, and more — can dramatically improve click-through rates in Google Search. But valid structured data does not guarantee rich results will appear. Google applies strict eligibility criteria, content policies, and quality thresholds before showing enhanced snippets. Understanding why your rich results are not showing is the first step to earning them consistently.
Structured Data Is Valid But Rich Results Are Still Missing
The most common — and most confusing — scenario is passing the Rich Results Test with zero errors, yet the rich result never appears in Google Search. Valid markup is necessary but not sufficient. Google must also: have indexed the page, determine the page is eligible based on content policy, believe the enhanced snippet provides genuine value to searchers for that specific query, and decide to show a rich result rather than a standard snippet at the time of search. All of these conditions must be met simultaneously.
Common Structured Data Errors That Block Rich Results
Even small markup errors can prevent rich result eligibility. Common issues include: missing required properties (every schema type has required fields — omitting them disqualifies the page), incorrect property types (using a string where a URL is expected), mismatched content (structured data describing content not present on the visible page), and nesting errors in JSON-LD. Use Google's Rich Results Test and the Schema Markup Validator to identify specific errors. Fix required property violations first — they are the most common disqualifier.
Google's Content Policies for Rich Results
Google maintains content policies that restrict which pages qualify for rich results. Review schema is not eligible on pages with harmful, deceptive, or manipulative content. FAQ schema has been significantly restricted — as of 2023, it only shows for well-known, authoritative government and health sites. Aggregate ratings must reflect genuine user reviews, not editorial scores. Medical and health-related content has additional scrutiny. Violating these policies results in manual actions in Google Search Console or silent non-display of rich results.
Page Indexing and Rich Result Display
Rich results can only appear for pages that Google has indexed. If a page is new, recently migrated, or blocked from crawling, its structured data cannot be processed. Check Google Search Console's URL Inspection tool to confirm the page is indexed and that Google has processed any recent structured data changes. After fixing markup errors, request re-indexing via the URL Inspection tool to accelerate re-processing — rich result changes typically take days to weeks to reflect in search results.
JavaScript Rendering Issues
If your structured data is injected via JavaScript rather than included in the server-side HTML, Googlebot must render the page to access it. Google does render JavaScript, but there is typically a delay of days or weeks between crawl and render. During this window, structured data is invisible to Google's rich result processor. The solution is to output JSON-LD in the server-rendered HTML rather than injecting it client-side. Next.js, Nuxt, and other SSR frameworks make this straightforward to implement.
Rich Results Test vs. Actual SERP Appearance
Passing the Rich Results Test confirms your markup is technically valid — it does not guarantee display in search results. Google uses the test to validate structure only; eligibility, policy compliance, and the decision to show a rich result are separate processes. A useful debugging step is to search Google for your exact page URL (using site: operator) or the query you're targeting and check whether competitors are receiving rich results for the same query. If they are and you are not, the issue is likely eligibility or markup completeness rather than a Google-wide restriction.
Monitoring Rich Results in Search Console
Google Search Console's "Enhancements" section shows a dedicated report for each rich result type detected on your site. Each report shows: valid pages (eligible for rich results), pages with warnings (valid but with non-critical issues), and pages with errors (invalid markup that disqualifies the page). Monitor these reports after any structured data changes. A sudden drop in "valid" pages indicates a markup regression — typically caused by a CMS update, plugin change, or template modification that broke the schema output.
When to Expect Rich Results After Fixing Markup
After fixing structured data errors and re-indexing pages, expect one to four weeks before rich results appear consistently in search results. Google must re-crawl the page, process the structured data, determine eligibility, and update the SERP rendering — each step adds latency. For high-traffic pages crawled frequently, the cycle is faster. Use Google Search Console's URL Inspection "Live Test" to verify that the current live version of your page passes validation, then monitor the Enhancements report weekly for status changes.