Google Merchant Center suspensions: the product feed errors that silently delist your best sellers

Your best seller can vanish from Google Shopping on a Tuesday and your storefront will look completely fine. No error banner, no broken checkout, no customer complaints. The product page loads, the price is right, the inventory count is accurate. The only thing missing is the thing you can't easily see: the listing itself, disapproved in Google Merchant Center for a feed attribute error that has nothing to do with how your site looks or functions.

Why suspensions are invisible until the sales report tells you

Google Merchant Center governs a separate layer from your storefront: the product feed. This is the structured data (title, price, availability, GTIN, MPN, brand, condition) that Google reads to decide whether to show your product in Shopping ads and free listings. Your website and your feed can disagree, and when they do, Google trusts the feed.

That disagreement is the trap. A store owner checks the site, sees a product listed correctly, in stock, priced right, and assumes everything is fine. Meanwhile Merchant Center has flagged the same product for a missing or mismatched identifier and quietly stopped showing it. The first symptom most owners notice is a slow bleed in Shopping traffic, which often gets misread as a seasonal dip or a algorithm shift rather than a feed problem.

This is the same blind spot that shows up when traffic drops and owners can't tell if it's the store or Google. Feed disapprovals are one of the quieter causes on that list, because they don't touch your site at all.

The GTIN and MPN errors that trip up otherwise healthy feeds

Global Trade Item Numbers (GTINs, the UPC/EAN/ISBN family) and Manufacturer Part Numbers (MPNs) are how Google matches your product to its own catalog of known items. Google requires a GTIN for most new products in most categories, per its own product data specification (support.google.com/merchants). Get this wrong and the listing doesn't rank poorly, it gets disapproved outright.

The common mistakes: reusing a GTIN across variants that actually have different codes (a shirt in three colors each has its own UPC, but a rushed catalog import assigns one to all three), entering a GTIN with the wrong number of digits after a spreadsheet auto-formats it and drops a leading zero, or leaving the field blank for a private-label product and not setting the "identifier exists: no" flag that tells Google there genuinely isn't one.

MPN errors are subtler. Google cross-checks MPN against brand and GTIN to confirm they describe the same product. If a bulk import assigns a generic "N/A" or copies the SKU into the MPN field, Google may flag it as a mismatch rather than a missing value, which reads differently in the diagnostics report and gets missed by owners scanning for the word "missing."

Any of these can trigger a full account-level review if enough products are affected, not just an item-level suppression. That's the scenario Shopify merchants describe as "Shopify Google Shopping suspended" in support forums: not one bad listing, but the whole feed getting pulled for pattern violations.

Availability mismatches: the silent inventory lie

Availability is where feed problems and inventory problems overlap. Google wants your feed's "in stock," "out of stock," or "preorder" status to match reality within a reasonable window, and it actively checks your live product page against what the feed claims (support.google.com/merchants, landing page requirements).

A few ways this drifts out of sync: your store marks a product out of stock instantly when the last unit sells, but the feed only refreshes every 24 hours, so for a day Google is sending traffic to a page that says "sold out." Or the reverse, more damaging one: a restock updates the storefront immediately but the feed still says out of stock, so Google keeps suppressing a listing you actually want live, right when you finally have inventory to sell.

This is closely related to the broader problem covered in inventory counts that drift across channels: your store's own admin, your feed, and Google's cached view of your feed can all say something slightly different at the same moment, and nothing forces them to reconcile except a scheduled or triggered feed refresh.

Repeated availability mismatches don't just get one item suppressed. Google treats a pattern of inaccurate availability data as a feed quality signal, and enough of it can lower trust across your whole account, according to Google's own merchant quality guidance.

Price, image, and landing page mismatches worth checking too

GTIN and availability get most of the attention, but three other mismatches quietly disapprove listings just as often.

Price mismatch: if the price in your feed doesn't match the price a shopper actually sees on the landing page, even briefly during a sale sync delay, Google disapproves the item. This overlaps with currency and tax bugs described in wrong prices in the wrong currency, where a conversion error changes the displayed price without anyone touching the feed.

Image requirements: Google rejects placeholder images, watermarked stock photos, and images below its minimum resolution. A theme change or CDN migration that swaps in a generic "image coming soon" graphic for products still being photographed can trigger this at scale.

Landing page errors: if the product URL in your feed 404s, redirects through a chain, or lands on a different product than advertised, Google disapproves it as a landing page mismatch. This is exactly the failure mode covered in redirect chains and 301 loops after a URL migration, and it's a common side effect of replatforming or bulk-editing URL slugs without updating the feed source.

Monitoring feed health before the sales drop tells you

The standard workflow for most stores is reactive: notice Shopping revenue is down, log into Merchant Center, find a wall of disapproved items, fix them one by one, wait for reprocessing. That cycle can easily take a week, during which your best sellers are invisible to the channel that likely drives a meaningful share of your traffic.

A better workflow checks feed health on a schedule, independent of whether sales look off yet. That means periodically verifying that a sample of high-revenue SKUs are still approved, that GTIN and MPN fields match your source catalog, and that availability status in the feed agrees with your live inventory count, not once after a problem surfaces but continuously.

This is part of why Cassian™ includes product feed checks alongside uptime, pricing, and stock monitoring: feed disapprovals behave like the other silent failures in this category (a broken sitemap, a stalled webhook, an expired certificate) in that the storefront looks fine while the actual problem sits in a system layer most owners never open unless something already went wrong. Catching a GTIN mismatch the day it happens costs you one afternoon of fixing. Catching it three weeks later, after Google's algorithm has already downweighted your account for a pattern of errors, costs considerably more to recover from.

Keeping your best sellers visible

Feed disapprovals are unglamorous compared to a site outage, but they hit the same revenue line just as hard, and with less warning. The fix isn't complicated: keep GTIN, MPN, price, and availability data accurate at the source, and check feed status on a schedule rather than waiting for a sales dip to prompt the search. Store owners who treat their product feed as infrastructure worth monitoring, the same way they'd monitor uptime or checkout, tend to catch these errors in hours instead of weeks.