Shopify Rich Results Drop? Fix Structured Data, GMC & Crawl Issues

Hey everyone! I recently saw a really insightful discussion in the Shopify community that I just had to share. It's a situation many of you might find yourselves in: you've done all the hard work, cleaned up your structured data, and the Rich Results Test says everything is perfect, yet your rich results in Google Search keep declining. Frustrating, right?

Our fellow store owner, @negativescu, was in this exact boat after migrating their analog photography store from OpenCart to Shopify. They saw great growth initially, then a sharp drop in Product rich snippets, Merchant listings, and even their favicon disappeared in SERPs. The kicker? No errors in Google Search Console (GSC), and their structured data was now passing the Rich Results Test with zero errors.

This is a classic head-scratcher, and the community really rallied to offer some fantastic, nuanced advice. It turns out, a "clean" Rich Results Test is just the first step. Google has a lot more going on behind the scenes.

Why Your Rich Results Might Still Be Hiding (Even With Perfect Schema)

The consensus from the experts in the thread was clear: a clean schema is necessary for eligibility, but it doesn't guarantee display. Google considers several other factors, especially after a big platform migration like OpenCart to Shopify.

1. The Google Merchant Center (GMC) Connection: A Common Culprit

This was highlighted by several members, including Maxime_StoreCanary and Ecom_swift_LLC. It's often the biggest blind spot. Your Merchant listings (those detailed product results with prices and availability) rely heavily on your Google Merchant Center feed, not just your on-page structured data.

Consistency is Key: If the price, availability, or condition in your GMC feed doesn't exactly match what Google reads on your landing page, it will likely drop your merchant snippet. These aren't always flagged as warnings in GSC, which makes them tricky to spot.
How to Check: Go to Products > All Products in Merchant Center. Filter by "Limited" or "Disapproved" status. Open individual items and look for errors like "Price on landing page doesn't match" or "Availability on landing page doesn't match."
Sync Health: As websensepro pointed out, ensure your Google & YouTube app (or whatever you use for GMC sync) is actively syncing your feed without item-level disapprovals.

2. The "Google Dance" & Re-evaluation Period

After significant changes, like migrating platforms or fixing major schema conflicts (like negativescu's Rise theme vs. Judge.me clash), Google needs time to re-evaluate your site's trust and re-process all the new signals. PieLab and websensepro both emphasized this, suggesting a recovery period of 4 to 8 weeks, sometimes even up to 12+ weeks. It's a "waiting room" scenario.

3. Dynamic Data & Product Variants

This is a subtle but critical point raised by PieLab. If you've built custom JSON-LD, it might not dynamically update when a user (or Google's crawler) switches a product variant (e.g., a different size, color, or film format). If Google's live crawler catches mismatched price or stock data on a variant, it can hold back your rich snippets.

Check Your Liquid: Ensure your custom schema in sections/main-product.liquid (or wherever it lives) is correctly pulling dynamic values for all variants.
priceValidUntil: Maxime_StoreCanary mentioned this specific field. If you hardcoded a static date that's already passed, Google will drop price eligibility. Make sure it's dynamic (via Liquid) or set far into the future.

4. Your Best Friend: The URL Inspection Tool in GSC

Multiple experts (Maxime_StoreCanary, GencerKarakaya, Steve_TopNewYork, cuongnm_trooix) stressed the importance of this tool. It's your window into what Google actually sees.

Last Crawled Date: Check this on affected product URLs. If it predates your schema fix, Google is still indexing old data.
Live Test & Rendered HTML: Use "URL Inspection > Live Test" to compare what Googlebot sees in real-time with your manually tested JSON-LD. Check the "View crawled page" to ensure the rendered HTML actually contains your clean application/ld+json block.
Google-Selected Canonical: Confirm this is correct and consistent.
Request Indexing: For a handful of your most important product URLs (10-15, don't bulk submit hundreds), manually request indexing to push Google to re-crawl them faster.

5. Structured Data Nuances Beyond "Clean"

@id Reconciliation: As websensepro suggested, if you're using a custom JSON-LD block, make sure your Product and Offer nodes share a consistent @id anchored to the canonical URL. This helps Google understand that variant URLs still refer to the same main product.
Empty Conditional Metafields: If you're conditionally adding aggregateRating from Judge.me metafields (reviews.rating / reviews.rating_count), ensure that if a product has zero reviews, the Liquid code completely omits the aggregateRating node, rather than rendering it with empty or 0 values. Empty nodes can quietly strip eligibility.

6. The Favicon Fix: A Separate Battle

The favicon disappearing (which negativescu also experienced) is usually a separate issue. GencerKarakaya, websensepro, and cuongnm_trooix all advised treating it distinctly. Check your in theme.liquid. Ensure it uses a fixed size (multiples of 48x48px, like 48x48 or 96x96) and is easily crawlable. Request reindexing of your homepage once fixed.

7. GSC Reports vs. Real-World Display

Ilanadavis, Steve_TopNewYork, and cuongnm_trooix all made a crucial clarification: the Enhancements reports in GSC only show a sampling of your URLs and whether structured data is detected and valid. They are not a direct measure of how many rich results you're actually earning or displaying. A valid report means eligibility, not a guarantee. Don't get too hung up on fluctuations in these reports; focus on the underlying validity and consistency checks.

8. Broader Google Updates

Cuongnm_trooix wisely pointed out that Google's own updates (like the May 2026 core update or June spam update mentioned in the thread) can also influence visibility. It's important to consider these broader shifts as a potential factor, rather than assuming everything is solely due to your migration.

What to Do Now: A Systematic Approach

After all these checks, what's the best course of action? The community experts offered some great, actionable advice:

Prioritize GMC: Start by thoroughly checking your Google Merchant Center for any product disapprovals or consistency errors. This is often the quickest win.
Inspect Key URLs: Use the GSC URL Inspection tool on 10-15 of your most important product pages. Check the "Last crawled" date, run a "Live Test," and examine the "View crawled page" HTML to ensure Google sees your clean, dynamic structured data. Request indexing for these pages.
Stop Tweaking Schema (for now): As mikelweller3, GencerKarakaya, and websensepro advised, avoid making further changes to your JSON-LD. Constant edits can reset Google's re-crawling queue and prolong the re-evaluation period.
Monitor & Be Patient: Establish a controlled sample of products and monitor their indexing, Merchant listings eligibility, and impressions separately in GSC. Then, give it time. The recovery window can be weeks, sometimes months.
Address Favicon Separately: If your favicon is still missing, treat it as a distinct issue. Verify your setup and request reindexing for your homepage.

It's tough when you've done everything "right" and still see declines, but as this discussion shows, the world of rich results is complex. It's rarely just one thing, and often involves a combination of feed consistency, crawl lag, and Google's trust signals. Keep a systematic approach, lean on these community insights, and you'll likely see those rich results return. Hang in there!

The Shopify Rich Results Mystery: Why Clean Schema Doesn't Always Mean Instant Visibility