Five Google Merchant Center Causes Outside Your Shopify Dashboard

On r/shopify last month, a merchant wrote that since publishing a new theme in April, Google Merchant Center has been disapproving their products in waves. They request a recrawl, the numbers improve for twelve hours, then the wave returns. They checked their products, their policy pages, Google's documentation. Nothing in their store explains the rejections. The cause sits somewhere Shopify does not surface in the admin.

I have seen this same pattern in four audits this year. Most Google Merchant Center disapprovals I run into on Shopify trace back to causes that do not appear anywhere in the merchant's admin. Here are the five I keep finding, in the order I check them.

What I look at before I open a single product

The first thing I open on a GMC disapproval audit is not Shopify and not Merchant Center. It is status.shopify.com.

When Shopify has a platform incident, even one that is short and reported as recovered, it cascades into Merchant Center as "product page unavailable" errors. A May 2026 outage knocked roughly 250 products at once into a GMC error state for merchants in Australia and the UK. Recovery took 10 to 12 hours after Shopify's own infrastructure came back, because Google's re-verification queue processes slowly. If a merchant comes to me with a sudden wave of disapprovals and there was an outage in the last 48 hours, I tell them to wait. Filing a re-review during that window can burn one of three review credits per suspension period, and those credits matter later.

The second thing I check is whether they recently published a new theme. Shopify rate-limits Googlebot in ways the merchant has no visibility into. The community post that taught me this was from a Plus merchant who pulled their Cloudflare logs and watched Googlebot get through 100% of the time, only to receive 429 responses from Shopify's own layer. Google reads those 429s as 5xx errors. The result is a "Not Approved" status on a random subset of products that cycles in and out after every manual recrawl. That merchant cycled 30 to 40 of 93 products in and out of Not Approved for weeks. No product change would have fixed it.

I now ask about theme launches before I look at the product feed. If there was one in the last 14 days, I will ask Shopify support to investigate rate-limit behavior before I touch anything else.

The cause that comes back every time: feed ownership

The Google & YouTube channel app owns the product feed. Anything a merchant fixes manually inside Google Merchant Center, a corrected title, an overridden price, a shipping attribute, gets overwritten on the next Shopify sync.

I learned this the slow way. The first two times I saw a merchant's manual GMC fix get reset within 24 hours, I assumed the merchant had reverted it in Shopify by accident. The third time, I watched the sync happen in front of me on a screen share. Whatever I had typed into GMC was gone. The feed had pushed its native value back.

There is no toggle for this in the Shopify Google & YouTube app. The only path to persistent overrides is to switch to a feed app that uses Google's Content API for submission. Three names come up consistently in the threads I trust: Feedonomics, DataFeedWatch, and Simprosys. One agency operator who shows up regularly on r/shopify has said on the record that they use Feedonomics for most of their clients and do not see this class of problem. EmmanuelFlossie at FeedArmy mostly recommends Simprosys for smaller catalogues. Cost is $15 to $50 per month depending on the app and your catalogue size.

I do not push the switch on every merchant. The native app is genuinely fine for a clean catalogue. But if a merchant has spent a weekend fixing data in Google Merchant Center and watched it reset by Monday, I tell them to stop. The native app is doing what its documentation says it does: pushing Shopify's own values back on every sync. If you want a second pair of eyes on whether to keep wrestling with it or move, that is exactly what help1's first 15 minutes free is built for. Show us the disapproval history, and we will tell you whether the switch earns its monthly fee.

Why "Misrepresentation" is the worst flag to chase

If a merchant tells me Google Merchant Center has flagged their account for Misrepresentation, my first move is no longer to look at the store. I check whether they have completed Google's identity verification.

In January 2026, Google expanded identity verification to all merchants in the EU, UK, US, Canada, and Australia. The request appears inside GMC under Account Settings, and it asks for government-issued photo ID, proof of business address, and company registration documents. Merchants have 30 days to respond. Many merchants stuck in a Misrepresentation re-review loop have a pending verification request sitting there that is silently blocking the re-review from doing anything useful. Completing verification first has become a regular fix in 2026, more regular than any of the things you can change inside the store.

The other thing about Misrepresentation: each failed review request extends the cooldown before the next one. Google has warned merchants directly that submitting too many review requests can lead to permanent account suspension. So the appeal mechanism itself has a price. One merchant on Shopify Community spent over a month locked out, missed the entire holiday season, and ended every review attempt with the same generic rejection. They had completed every checklist item they could see.

This is the part where I have to be honest with merchants: I do not have a reliable way to predict which Misrepresentation trigger fired for a specific store. The triggers Google does not document publicly include duplicate contact pages (your store might have both /policies/contact-information and /pages/contact), shipping time language that says "4 to 8 Tage" on product pages but "business days" on the shipping policy, a custom domain that redirects to your myshopify subdomain instead of being set as primary, and right-click blocking code installed by some conversion apps. Any of those can be the one. If a merchant has burned a review credit without checking each, the next credit is likely wasted too.

The four invisible triggers I keep finding

Outside the Misrepresentation cooldown loop, the same handful of triggers show up in most of my GMC audits. None of them surface in the Shopify admin in a way a merchant would catch on their own.

1. The Shopify CDN strips IPTC metadata from every uploaded image. If a merchant uses AI-generated product photography, Google's policy requires a specific IPTC tag (DigitalSourceType = TrainedAlgorithmicMedia) embedded in the image file. Shopify's image pipeline drops that tag on upload. A Shopify staff member acknowledged the bug in May 2026 and said they were investigating with no fix timeline. As of this writing, there is no fix. The workaround I know of is to host AI images on an external CDN that preserves IPTC metadata and reference them in a supplemental feed. Merchants who built their photography pipeline around Shopify's native upload have no clean path.

2. Dynamic checkout buttons stay visible on out-of-stock variants. Google's March 2026 enforcement update treats an active buy button on a zero-inventory page as Misrepresentation at the account level. Shopify's default themes do not hide Apple Pay, Shop Pay, or Google Pay when inventory drops to zero on the selected variant. Hiding them takes theme code or a variant availability app that swaps the buy area into a sold-out state. The Shopify admin does not surface this as a toggle.

3. Custom shipping profiles silently break the Google feed. Merchants who use a third-party shipping rate app, or a Shopify custom shipping profile, often find their Google feed stops syncing. Shopify support has confirmed that only flat rates or native Shopify shipping rates sync reliably with the channel app. The workaround that has held up for me is to keep calculated rates at checkout but expose flat rates only to the Google feed. Most third-party feed apps support this kind of per-channel override.

4. A billing freeze creates a robots.txt block that does not clear on its own. When a Shopify store goes offline for a billing payment failure or a maintenance window, even for a few hours, Google's crawler hits a robots.txt-blocked response and disapproves the affected products. Recovery requires explicit Allow directives for Googlebot, Googlebot-image, and Storebot-Google in robots.txt, plus three to seven days of patience. Manual recrawl requests help but do not shortcut the wait.

There is a fifth small one worth a footnote. If a merchant keeps seeing a Local Feed Partnership reappear in GMC after deleting it twice, the source is a setting in the Shopify Google & YouTube app's settings tab, not GMC. Disable Local Listings there and the partnership stops coming back. This one is documented in a years-old Shopify Community thread and merchants still hit it.

When I tell a merchant to switch feed apps

Most merchants who come to me with Google Merchant Center problems do not need to switch off the native app. The free Google & YouTube channel app works fine for stores with clean catalogues, native Shopify shipping, no AI imagery, and no Misrepresentation history. I do not put a $30 a month subscription on a merchant who can live with the defaults.

The switch becomes worth recommending when one of these is true:

1. They have spent more than two hours fixing product data inside GMC and watched it get reset by the next sync.
2. They run custom shipping profiles they cannot move off, and their feed has stopped syncing.
3. They got hit with a Local Feed Partnership they cannot remove from GMC's interface.
4. They tried the "reinstall the Google & YouTube app" advice the community gives, and ended up with country targeting and shipping settings rewritten in ways they did not request. (One merchant on Shopify Community wound up with 175,000 products flooded into GMC after that reinstall, with no documented removal path. Don't.)

For those merchants, my default recommendation is Simprosys for smaller catalogues and Feedonomics or DataFeedWatch for larger ones. None of those apps fix Shopify's Googlebot rate limiting, the IPTC metadata bug, or the OOS buy button problem. They do solve the feed-ownership reset, the shipping profile incompatibility, and the Local Feed Partnership recurrence. That is enough to clear most of the audits I run.

The store-level diagnostic in the help1 app flags the OOS buy-button risk and recent theme launches on install. Those are the items hardest for a merchant to spot by eye, and they map directly to two of the five causes here.

If your Google Merchant Center disapprovals came back the same week you fixed them in the dashboard, ask yourself who actually owns your product feed. The answer points to whether your next move is in Google's interface, in Shopify's admin, or somewhere else entirely.