Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

Eight Merchant Center Disapprovals and What Is Actually Wrong

The message Google gives you is rarely the real cause. Eight common product feed disapprovals, what sits behind each one, and how to fix them at the source.

Merchant Center disapprovals are rarely mysterious. Google tells you the reason, but the wording is terse and the actual cause is usually one layer back in your product data. These are the eight we see most often, with what the message says and what is actually wrong.

1. “Missing value [availability]”

What it means: the feed has no availability field, or the field is empty for some items.

What is usually wrong: the feed was generated by a plugin that maps stock status only when a product has stock management enabled. Products with “manage stock” turned off export no value at all.

Fix: export availability explicitly — in_stock, out_of_stock, preorder — derived from both stock status and backorders setting. Do not rely on the plugin default.

2. “Invalid value [price]”

What it means: the price field does not match the required format, or is missing a currency.

What is usually wrong: a multi-currency store exporting prices with a currency symbol, a thousands separator, or a comma decimal. Google expects 49.99 USD, not $49.99 and not 49,99.

Fix: format prices as a plain decimal with a dot and append the ISO currency code with a space. Check tax-inclusive versus tax-exclusive consistency at the same time; mismatched tax handling across products triggers the same error class.

3. “Price mismatch”

What it means: the price in the feed differs from the price on the landing page.

What is usually wrong: cache. The feed was generated before a price update, or the landing page serves a cached version with a different price. Discount plugins that apply at cart level make it worse: the feed shows the regular price, the page shows a struck-through price, and Google’s crawler sees whichever version it happens to get.

Fix: regenerate the feed after any price change, and make sure the discounted price shown to an anonymous visitor matches the feed exactly.

4. “Image too small” or “Image not accessible”

What it means: the primary image is under the size requirement or returns something other than an image.

What is usually wrong: the feed uses the original upload rather than a sized version, or your image CDN blocks Google’s crawler. Hotlink protection and bot filtering are frequent causes.

Fix: export a URL that returns a JPEG or PNG over 500×500 (larger is better), publicly accessible, no redirects. Test three URLs in an incognito window.

5. “Insufficient product identifiers”

What it means: a product in a category that requires GTIN/MPN/brand has none of them.

What is usually wrong: handmade, private-label or custom items without barcodes. Sellers then leave the field empty, which is not allowed for most categories.

Fix: if the product genuinely has no GTIN, set identifier_exists to no and provide brand and MPN. This is a supported value, not a workaround — but it must be set deliberately.

6. “Mismatched value [link]”

What it means: the link goes somewhere that does not show that product — a category page, a homepage, a 404, or a redirect.

What is usually wrong: variant products all pointing at the parent URL, or a migration that left redirects in place.

Fix: every feed row needs its own canonical landing URL. For variants, link to the variation where possible or to a page that preselects it.

7. “Unavailable mobile landing page”

What it means: the landing page fails on a mobile user agent.

What is usually wrong: a broken mobile layout, or a cookie or age gate that blocks the crawler before content loads.

Fix: test the product URL with a mobile user agent. If a popup intercepts before the product renders, that is the cause.

8. “Adult or restricted content”

What it means: the classifier thinks the product falls into a restricted category.

What is usually wrong: not the product, but the feed. A store selling cosmetics, swimwear or medical-adjacent items can trip the classifier because of keywords in the title or description.

Fix: reword titles and descriptions to describe the product rather than its effect. “Post-surgery support bra” reads differently to a classifier than “recovery bra with compression”.

The pattern behind all eight

Seven of the eight come down to the same thing: the feed is generated from a different source of truth than the landing page. Price from the database, availability from a plugin setting, images from a CDN, links from a permalink structure — each can drift independently.

The reliable fix is not chasing individual errors. It is generating the feed from the same data the storefront renders, then diffing a sample of rows against the live pages before submitting. Ten products, compared field by field, catch almost everything.

If you are running a feed for a multi-language store, remember that Merchant Center treats each country feed separately — a product can be approved in one market and disapproved in another for different reasons. That is normal, and it is why the error count never quite reaches zero.

Most of this work sits at the boundary between product data and technical SEO, which is where these problems usually get created in the first place.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote