Shopify Google Shopping Feed Gone Silent? Troubleshooting 0 Products in Merchant Center for Multi-Market Stores

The Silent Killer: When Your Shopify Google Shopping Feed Disappears

As a Shopify store owner, you’re probably used to the occasional hiccup with your Google Shopping feed. Disapprovals, product data errors, shipping issues — these are all part of the game. But what about when your feed just… disappears? No warnings, no disapprovals, just a big fat zero where your products should be. That’s what one store owner, stffndtz, recently ran into, and it sparked a really insightful discussion in the Shopify Community that I want to unpack for you.

This isn’t just about a broken feed; it’s about a “silent killer” — a problem that can go unnoticed for weeks or months, quietly eroding your traffic and sales without a single alert. Let’s dive into what happened and, more importantly, what you can do if you find yourself in a similar spot.

The Mystery of the Missing France Feed

Stffndtz’s setup was pretty common for a growing international store: a single Shopify store with seven markets, all served as subfolders on one claimed domain. They were using the Google & YouTube app, with automatic product, country/language, and shipping sync all enabled. Six of their markets were syncing perfectly fine — Germany, EU, Switzerland, UK, Norway, USA — but their France market? Crickets. Since around August 1st, its two data sources (for French and English content) showed 0 products in Merchant Center, down from ~1,400.

The really unsettling part? There were no disapprovals, no “limited” statuses, no errors. The products simply stopped arriving. Stffndtz had already ruled out a ton of common culprits:

• The France market was active, currency set correctly.
• Market default language was French, with a valid subfolder domain.
• The product catalog was active, with “automatically include new products” enabled (and other markets using the same setup were fine).
• Shipping rates to France existed in Shopify and Merchant Center.
• Test products were active, in stock, published to the Google & YouTube sales channel, and in the France catalog.
• A controlled resync of 10 products changed nothing.

The only structural difference they could find? France was their only “nested” market — its parent was their EU market, rather than sitting directly under the store default. This felt like a big clue.

The Content API Migration & The Plot Twist

One of the first, and very good, hypotheses came from HamidEjaz, who pointed out that the timing — around August 1st, leading up to the August 18th Content API sunset — lined up suspiciously well. Hamid suggested that perhaps France hadn’t properly migrated to the new Merchant API, while other markets had. If it was stuck on the “dying pipe,” that would explain the silent failure.

It was a solid theory, but stffndtz had a plot twist: they confirmed that both France sources had indeed flipped to the Merchant API. The new pipe was built, but it was just never carrying anything. “Which is arguably stranger,” stffndtz noted, and I’d have to agree!

Beyond Product Data: It’s a Routing Game

This is where the community really started to zero in on the core issue. Both JaumeG and kekke1016 independently suggested that this wasn’t a product-attribute issue at all, but an “offer-routing failure.” Meaning, the problem wasn’t with the product data itself, but whether the data was actually being sent from Shopify to Google, and if so, whether Google was correctly placing it under the France feed label.

Stffndtz had already confirmed Google’s own specialists stated “the feed country and language are currently not syncing to the Merchant Center” for their test products, which strongly supported this routing-failure interpretation. It wasn’t about what was in the products, but whether they were getting to the right place.

Actionable Steps: How to Trace a Silent Feed Failure

If you’re facing a similar “0 products” scenario, here’s a consolidated approach based on the community’s best advice:

1. Stop Tweaking Product Data: Resist the urge to keep changing product attributes or resyncing everything. The problem likely isn't there.
2. Gather Specific Details for a Test Variant: Pick one exact product variant that should be syncing to the problematic market and gather as much info as possible for both the working markets and the broken one. This includes:
   • Shopify variant ID
   • Merchant Center offer ID (if one exists for a working market)
   • API data source ID
   • Feed label and content language
   • Target country and final landing URL
   • UTC timestamp of the most recent insert or update attempt
3. Engage Support with Targeted Questions: Armed with your specific variant data, reach out to both Shopify Support and Google Support. The key question for them is: “Did the Google & YouTube app send an offer for [your specific variant] using the [problematic market’s] feed label? If so, which data source received it?” This helps pinpoint if the failure is on Shopify’s outbound side or Google’s inbound routing.
4. Avoid Reinstalling the App: JaumeG wisely advised against this, as it might remove crucial evidence needed for diagnosis.
5. Push Back on Generic Advice: Stffndtz experienced Google support trying to push them towards fixing a “market domain that is already correct,” suggesting they drop subfolders. Remember, if other subfolder markets are syncing fine, it’s unlikely to be the issue for one specific market. Don't restructure your markets based on bad advice!

The Nested Market Hypothesis – A Key Clue?

The “nested market” angle remained a leading hypothesis. Stffndtz’s France market was a child of their EU market, and it had its own feed label, “FR,” which was simply never filled. JaumeG’s question — “whether nested markets support independent feed labels after the Merchant API migration” — was the one nobody could definitively answer.

One ask from the community: If you run a NESTED market (a market whose parent is another market rather than the store default), could you check whether its feed label actually populates in Merchant Center? Even a single confirmation either way would be incredibly helpful for everyone!

The True Danger: The Silent Failure

Perhaps the biggest takeaway from this whole discussion came from vedasuite’s question about how stffndtz even noticed the problem. The answer? Manually checking Merchant Center for an unrelated reason. There were no alerts, no warnings, no disapprovals. France was a small share of their traffic, so the revenue dip was well within normal variance. “Realistically this could have run for months unnoticed,” stffndtz reflected.

This is the “real lesson” here: a feed that silently stops being populated produces no signal anywhere. A disapproval at least gets flagged. This highlights a critical operational risk for multi-market stores. If you’re not actively monitoring your feed health for each market, you could be losing sales without even knowing it.

This whole situation really underscores how complex multi-market setups can be, especially with ongoing platform migrations and API changes. It’s a powerful reminder to be proactive, monitor your Google Shopping feeds diligently across all markets, and don’t be afraid to push for detailed investigations with support if something feels off. The community’s collaborative spirit in dissecting this problem is a testament to how we can all learn and protect our businesses together!