Disapproved in Google Merchant Center? The WooCommerce fields behind it
Two symptoms, one cause. Fewer products in the feed than your store holds, and items disapproved after upload, both usually come down to a field in the product. You can find every one of them from the command line, without installing a plugin.
Google Merchant Center is where a store sends its product feed—the list that Google Shopping listings and Shopping ads are built from. Two different things go wrong on the way, and from the outside they look alike.
A product can be missing from the feed—never exported at all, because the store gave the feed plugin nothing to export. Or it can reach the channel and be disapproved there. Either way the feed plugin is usually just the messenger: the requirement that failed is a field in the product, not a line in the feed.
Knowing which of the two you have saves a day. If the feed simply holds fewer products than your catalog, start with price, availability and visibility—an item with no price, with nothing in stock, or hidden from the catalog is dropped before the export ever happens, and no feed setting will bring it back. If the products are in the feed and the channel rejects them, start with images and identifiers.
This page goes through those requirements one at a time: what each one is, what breaks it in
a WooCommerce catalog, and how to find it yourself. Every check below is a WP-CLI command you
can run on your own store, with no plugin and no account. Replace wp_ with your own table prefix.
The percentages come from our study Clean catalogs are rare: 237 WooCommerce stores. The main figure in each section is from the September 2026 scan of the public catalogs of 72 Polish stores (per-store data under CC BY 4.0); the UK and US figures are from the October scan, counted the same way.
Price—no price, no listing
Google requires price for every product. WooCommerce will publish a product with the price field
empty without a word of warning; on the storefront it simply cannot be bought.
38% of the stores had products with no price or no way to buy them—1,138 items. In the UK and the US: 40% and 46%. Of the three figures quoted on this page, the report marks this one as the least reliable, and says why. When we checked 40 of these items by hand, only 4 looked like a mistake; most were free gifts, vouchers and similar items with no price on purpose.
wp db query "SELECT p.ID, p.post_title FROM wp_posts p LEFT JOIN wp_postmeta m ON m.post_id = p.ID AND m.meta_key = '_price' WHERE p.post_type = 'product' AND p.post_status = 'publish' AND (m.meta_value IS NULL OR m.meta_value = '' OR m.meta_value = '0')"
Availability—the feed says in stock, the store says no
availability has to match what a customer actually finds. Two states break it, and they need two
different queries.
The first is the simple one—everything currently out of stock:
wp db query "SELECT p.ID, p.post_title FROM wp_posts p JOIN wp_postmeta m ON m.post_id = p.ID AND m.meta_key = '_stock_status' WHERE p.post_type = 'product' AND p.post_status = 'publish' AND m.meta_value = 'outofstock'"
The second is the one that hides: a variable product whose every variation is sold out. The parent still reports itself as in stock, so it looks fine in a listing and in the query above, and a customer who clicks it finds nothing they can add to the cart.
wp db query "SELECT par.ID, par.post_title FROM wp_posts par \
JOIN wp_posts v ON v.post_parent = par.ID AND v.post_type = 'product_variation' AND v.post_status = 'publish' \
JOIN wp_postmeta s ON s.post_id = v.ID AND s.meta_key = '_stock_status' \
WHERE par.post_type = 'product' AND par.post_status = 'publish' \
GROUP BY par.ID, par.post_title HAVING SUM(s.meta_value = 'instock') = 0"
Neither query knows whether the item ever sold—that needs the order tables, and it is the difference between a list of 400 out-of-stock products and the four that were earning money until they ran out.
Image—no picture, no listing
image_link is required, and three different states end the same way: the product has no image at
all, the database row points at a file no longer on disk, or the file is there but can’t be
displayed.
29% of the stores had products with no image of their own—421 items. In the UK and the US: 35% and 33%.
wp db query "SELECT p.ID, p.post_title FROM wp_posts p LEFT JOIN wp_postmeta t ON t.post_id = p.ID AND t.meta_key = '_thumbnail_id' WHERE p.post_type = 'product' AND p.post_status = 'publish' AND (t.meta_value IS NULL OR t.meta_value = '' OR t.meta_value = '0')"
For the other two, this lists every image in the Media Library whose file is missing, or is there but can’t be read as an image (empty or broken). It changes nothing, and it skips SVG files:
wp eval 'foreach (get_posts(["post_type" => "attachment", "post_mime_type" => "image", "post_status" => "inherit", "numberposts" => -1, "fields" => "ids"]) as $id) { $f = get_attached_file($id); if (!$f || !file_exists($f)) echo $id, "\tmissing\t", $f, "\n"; elseif ("image/svg+xml" !== get_post_mime_type($id) && !@getimagesize($f)) echo $id, "\tunreadable\t", $f, "\n"; }'
An image that opens but is only a few pixels across is a size problem; the command on Google Merchant Center image size finds those.
Description—too short to help
description is required. A one-line description meets the requirement, but little else: this is
the text that decides whether a shopper who clicked through finds an answer or leaves.
wp db query "SELECT ID, post_title, CHAR_LENGTH(post_content) AS znakow FROM wp_posts WHERE post_type = 'product' AND post_status = 'publish' AND CHAR_LENGTH(post_content) < 200 ORDER BY znakow"
Link—the product page has to be reachable
link must lead to a page a customer can see. A product set back to draft or private gives anyone
who follows its old link a 404 “page not found” error. A product hidden from the catalog keeps its
page, but shoppers can no longer find it in your store, and it is worth knowing which ones those are
before you compare the feed with the store. This query lists published products hidden from the
catalog:
wp db query "SELECT p.ID, p.post_title FROM wp_posts p JOIN wp_term_relationships tr ON tr.object_id = p.ID JOIN wp_term_taxonomy tt ON tt.term_taxonomy_id = tr.term_taxonomy_id JOIN wp_terms t ON t.term_id = tt.term_id WHERE p.post_type = 'product' AND p.post_status = 'publish' AND tt.taxonomy = 'product_visibility' AND t.slug = 'exclude-from-catalog'"
A unique id—two products, one identity
Google wants id unique for each product. If your feed plugin builds the id from the SKU, two
products sharing an SKU means one of them loses.
10% of the stores had a duplicate SKU—134 items. In the UK and the US: 2% and 1%.
wp db query "SELECT meta_value AS sku, COUNT(*) AS n FROM wp_postmeta pm JOIN wp_posts p ON p.ID = pm.post_id WHERE pm.meta_key = '_sku' AND pm.meta_value <> '' AND p.post_type IN ('product','product_variation') AND p.post_status = 'publish' GROUP BY meta_value HAVING n > 1"
Variations are included on purpose: a feed exports each variation as its own item, so a variation sharing an SKU with a product is a real collision there. Before you compare numbers with any tool, note that Merchlint’s own duplicate checks (SKU and GTIN alike) compare published products only, so they can report fewer pairs than the two duplicate queries on this page.
If your store is multilingual, translations of one product legitimately share an SKU. Those are one product, not a duplicate—count the translation groups, not the posts.
GTIN—the number that matches your product to the same product elsewhere
gtin is strongly recommended if available, and mpn becomes required when a product has none.
Google’s GTIN help page says products with a
missing or incorrect GTIN “may have limited visibility”.
WooCommerce has had the field since 9.2—Product data → Inventory → GTIN, UPC, EAN, or ISBN. Nothing in the admin points at it, and nothing tells you when two products carry the same number.
wp db query "SELECT p.ID, p.post_title FROM wp_posts p LEFT JOIN wp_postmeta g ON g.post_id = p.ID AND g.meta_key = '_global_unique_id' WHERE p.post_type IN ('product','product_variation') AND p.post_status = 'publish' AND (g.meta_value IS NULL OR TRIM(g.meta_value) = '')"
wp db query "SELECT TRIM(meta_value) AS gtin, COUNT(*) AS n FROM wp_postmeta pm JOIN wp_posts p ON p.ID = pm.post_id WHERE pm.meta_key = '_global_unique_id' AND TRIM(pm.meta_value) <> '' AND p.post_type IN ('product','product_variation') AND p.post_status = 'publish' GROUP BY TRIM(meta_value) HAVING n > 1"
On a variable product the identifier belongs on each variation—each size and color is a separate trade item with its own number, and a variation does not inherit the parent’s. A parent with a number and six variations without one exports as six items with no identifier.
If your products have no identifiers at all (handmade goods, products you make yourself), don’t invent one. Google’s advice is plain: “don’t guess or make up a value”. A made-up number can belong to a real product somewhere else, and that is a worse mistake than leaving the field empty.
There is one thing to set in that case, and it belongs to the feed rather than to the product.
Google expects identifier_exists to be no when an item has neither a GTIN nor a combination of
MPN and brand, and many feed plugins can set it—as a fixed value or per product. The reverse is
a trap as well: sending no for a product that does carry an identifier can get it disapproved.
What this page does not check
Here is what this page can’t check, and why. These are real requirements that nothing above will find for you:
| Requirement | Why it is not here |
|---|---|
brand | Required for most new products, but WooCommerce has no single native field for it—it lives in a taxonomy or in a plugin, so there is no honest one-line check. |
mpn | Required when a product has no GTIN. Same reason: no native field. |
| A GTIN kept outside WooCommerce’s own field | The query above reads _global_unique_id, the field WooCommerce added in 9.2. A store that keeps the number somewhere else—a dedicated EAN plugin, Yoast’s WooCommerce fields, a product attribute such as pa_ean — will look entirely empty to it. Check where your feed maps gtin from before you trust the count. And the reverse trap: if your feed plugin lists WooCommerce’s field only under a generic “custom attributes” group, that list may be cached—and saving a product does not refresh it—or built from a single product, the most recently published one. A filled field can then stay invisible in the mapping until you clear the plugin’s attribute cache; do that first, before concluding the field is empty. |
| Price matching the landing page | Needs the feed and the rendered page compared side by side. A database query cannot see what the page shows after tax, currency and dynamic pricing. |
| Title matching the landing page | The same. Length can be measured; agreement cannot. |
Image resolution deserves a note as well: Merchant Center begins enforcing a 500 × 500 px minimum on January 31, 2027, and undersized images are a common quiet rejection. The store check lists the main images below that size with nothing to install—it reads their dimensions from the public catalog. In WordPress, the free Merchlint lists main and variation photos under that size, each with its dimensions: Photo too small for Google. Google Merchant Center image size has the dates and a WP-CLI command for the whole catalog, and Image too small for upcoming enforcement explains the two warnings Merchant Center already shows.
Everything above is a query you run yourself, on your own database. If you would rather have these
checks run over the whole catalog at once, with counts, the list of affected products and what
each one costs, Merchlint does that. It is free, it only reads, and it changes
nothing in your store. The one thing the free version leaves to you is the third image state
above, a file that exists but can’t be displayed; the wp eval command in the image section finds it.