Nothing is more frustrating than a full shop whose products don't show up in Google Shopping. In Google Merchant Center the items sit at “disapproved” or “under review”, and every disapproved product means visible revenue lost. The good news: the reasons are almost always the same, and nearly all are a data problem, not a product problem.
Our position on this is clear: we don't build you another feed. We zero out your disapprovals. That distinction matters, because most feed apps simply generate a new file and hope Google accepts it. We look at why Google is rejecting the products you already have, and fix exactly that.
First, understand this: crawl data vs. feed data
The key aha moment: Google knows your product from two sources, and they often contradict each other. One is the feed (the structured file your shop or an app sends to Merchant Center) and one is the crawl (Google visits your actual product page and reads it). If a value lives in the shop but not in the place the feed source reads, it's missing in Merchant Center, even though it “exists” in the backend. This exact gap between crawl and feed explains most warnings.
1. “Landing page not accessible” / “Product page not accessible”
The most common and most expensive error. A product is in the Google sales channel but not published to the Online Store: draft, hidden, or only enabled for other channels. The result: the landing page Google has in the feed returns a 404. Google can't reach the promised page and disapproves it.
The fix: either publish the product to the “Online Store” sales channel so the page exists, or remove the product from the feed if it's deliberately not for sale. A product should never be in the Google feed without a reachable page on the Online Store. Pay special attention to old drafts and sold-out items that got stuck in the channel by accident.
2. Missing “shipping_weight”
A classic crawl-vs-feed problem: the weight is set in the shop (on the variant), but the source feeding the feed doesn't read it; it crawls the storefront, and the weight isn't visible there. Google needs it to calculate shipping and flags the missing attribute.
The fix: map the catalog weight cleanly to the `shipping_weight` feed attribute, or configure flat shipping settings in Merchant Center so Google no longer needs a per-product weight. Both routes are valid; what matters is that Google gets reliable shipping information.
3. Missing availability
Without the `availability` attribute, Google doesn't know whether the item is in stock, and won't advertise it when in doubt. Some feeds hard-code it to “in stock”, which triggers warnings the moment a product actually sells out.
The fix: derive availability from your real inventory: `instock`, `outof_stock` (or `preorder`) dynamically from the stock level, not as a fixed value. That keeps the feed honest and Google trusting your listings.
4. Missing or invalid GTIN
For many branded products Google expects a valid GTIN (the barcode / EAN). If it's missing or invalid, visibility drops or the product is disapproved.
The fix: fill the GTIN from the product's real barcode. One point is non-negotiable here: never invent a GTIN. A made-up number violates Google's policies and can get your account suspended. If a product genuinely has no GTIN (e.g. handmade), you correctly set `identifier_exists = no` instead. That's the clean, policy-compliant path.
5. The EU legal layer foreign apps skip
The reason internationally built feed apps fail in Germany, Austria and Switzerland by the dozen: they don't know the local legal situation. Google mirrors these requirements in Merchant Center.
- Unit price (PAngV): for products sold by quantity (ml, g, pieces), German price-indication law requires a unit price, and missing it means warnings and legal risk.
- Electronics / WEEE labels: for electronic items, both the channel and the law expect correct declarations.
- Legal texts (imprint, returns, privacy): if they're missing or not cleanly linked, Google rates the landing page as untrustworthy. Providers like the Händlerbund feed these texts automatically into the right shop pages.
A feed app that ignores this layer produces a technically “green” feed that still gets disapproved. This is exactly where craft parts ways with automation.
Almost every Merchant Center disapproval is a data problem, not a product problem. Understand the difference between crawl and feed data and you fix it at the root, instead of stacking yet another feed on top.
How we work
- Diagnose: every warning in Merchant Center is mapped to its real cause: page accessibility, weight, availability, GTIN, category/title, legal.
- Fix at the source: publish products, map attributes correctly, tie availability to stock, fill GTINs from real barcodes.
- Secure EU law: check and feed in unit price, electronics labelling and legal texts.
- Re-check: verify again until disapprovals are at zero.
Feed Doctor: diagnosis and repair in one place
For exactly this work we built Feed Doctor, our tool that diagnoses GMC disapprovals and auto-fixes many of them: category, title, GTIN, weight, availability and page accessibility. It works with deterministic rules (traceable, no black box) and optional AI assistance for the tricky cases. You can try it live at feeddoctor.gbdesign.art.
Whether with Feed Doctor or by hand with us: the goal is always the same: not another feed, but your disapprovals at zero and your products back in Google Shopping.
Running a Shopify store? Install Feed Doctor straight from the Shopify App Store, at apps.shopify.com/feed-doctor-1. The diagnosis is free for good, so you see what's wrong first and decide afterwards.