Your Google Merchant Center product feed: how to set one up, find it again, and fix the products Google disapproves

Everything your products do on Google starts with one file. Shopping ads, free listings, Performance Max and Google’s AI shopping answers all read the product feed in Merchant Center. Get that feed right and everything your products do on Google improves at once. Leave it broken and the best campaign in the world runs on half a catalog.

Here is what the feed needs, how to get it into Merchant Center, where to find its address again when another channel asks for it, and why Google keeps disapproving the same products.

What Google needs in the feed

Seven attributes on every product: id, title, description, link, image_link, availability and price. A product missing any of them is rejected before it can run.

Then the ones that depend on what you sell.

• Identifiers. A gtin wherever the product has a barcode. Where it does not, brand plus mpn. A brand on every new product that has one.
• Apparel. color, size, age_group and gender for clothing sold in Brazil, France, Germany, Japan, the UK and the US, and for all apparel in free listings.
• Variants. One row per size or colour, each with its own ID, sharing one item_group_id. Google requires it for variants in free listings and for Shopping ads in those same six countries.
• Used goods. A condition on anything refurbished or second-hand.

Everything else is recommended. Recommended does not mean optional in practice. gtin is the clearest case: Google says a product sent without its barcode may have limited visibility.

Getting a feed into Merchant Center

Merchant Center takes products as a data source. The two that matter for a store are a file Google fetches from a URL on a schedule, and a file you upload. Pick the URL. An uploaded file is frozen the moment you upload it, and prices and stock move every day.

The URL comes from your store. Shopify, WooCommerce, Magento and BigCommerce each export a Google-style feed through a third-party plugin or a built-in export. Paste that URL into the data source, set the fetch schedule, and Google re-reads it on its own. How to export a product feed from Shopify, WooCommerce, Magento and BigCommerce

Where to find your feed URL again

You will need it. Perplexity reads Google’s feed format. Meta, TikTok and Microsoft take the same products. The fastest way to launch on a second channel is to hand it the feed Google already fetches.

1. In Merchant Center, open Settings and choose Data sources. The same list is reachable from Products, under manage product sources.
2. Open the source Google fetches on a schedule. Only a source fetched from a file URL has one.
3. Copy the file URL from its settings. That is the address your store publishes.

If you cannot find it, the store is probably connected to Merchant Center through its own Google app instead of a URL. Then the feed address lives in the store, not in Google.

Why does Google keep disapproving my products?

Google shows the reason on the product itself, under Needs attention in Products. Almost every reason is one of six, and each has a fix in the feed, not in the campaign.

1. Missing or invalid GTIN. A barcode whose check digit does not add up, or one that belongs to a different product. Fix: fill the real barcode from a column you have, a rule, or a supplier feed.
2. A required attribute is missing. No brand, no condition on a used item, no size on apparel. Fix: map the column or set the value with a rule.
3. Promotional wording in the title. SALE, free shipping, ALL CAPS for emphasis. Google treats the title as product data, not ad copy. Fix: one rule that strips the words from every title and keeps new products clean.
4. Price or availability does not match your page. Google crawls the product page and compares. A stale feed fails that check, and a mismatch can disapprove products Google thinks are likely to be affected too. Fix: a feed that refreshes as often as your prices change, mapped to the price you actually charge.
5. The image is rejected. A promo overlay or watermark on the photo, a placeholder, a broken link, or an image too small. Google has set a 500 by 500 pixel minimum for all products from January 31, 2027. Fix: point the image field at a clean product shot, or generate one.
6. A policy issue. Some products cannot be advertised, and account-level reviews are settled in Merchant Center, not the feed. Fix: exclude the product from the feed so it stops tripping the account.

After any fix, Google re-reviews on its own schedule once it has fetched the updated feed. No feed tool clears a disapproval. It makes the next review pass.

Fix it once for the whole catalog

Renable sits between your store and Google. It imports the feed your store exports, or connects to your Merchant Center account directly, re-reads it every hour, and publishes a clean Google feed at a fixed address.

• The gaps, counted. The Google channel’s Fields tab marks every field Google requires and shows how many products fill it. A required field some products lack raises a warning on your dashboard, with the count.
• Rules that run on every import. Strip the promotional words from 3,000 titles with one rule. Set the brand for a whole product line. Pull barcodes from the supplier feed. Each is a draft you publish, then it keeps applying as products arrive and change.
• Images Google accepts. Process your product images and the overlay-free cutout or a generated studio shot goes to Google, while the designed version goes to Meta.
• Your existing feed can stay. Renable can publish a supplementary feed that layers better titles, descriptions and images on top of the primary feed you already send Google.

Or hand the feed to Aimée, the AI agent inside Renable, and say what is wrong.

The fixes per disapproval reason are in the help center: Fix products disapproved by Google. See how Renable works with Google