Google Shopping Feed for Magento: Pass First-Time Review
Google Shopping Feed for Magento: Pass First-Time Review

Google Shopping Feed for Magento: Pass First-Time Review

3 min read 14 views

Google Shopping feed for Magento: pass the first-time review

A Google Shopping feed is one of the highest-intent traffic sources a store can have — and one of the most frustrating to get live, because Google Merchant Center rejects feeds for reasons it explains badly. Get the feed right the first time and you skip weeks of back-and-forth. Here's what a compliant Magento feed needs, and the mistakes that get stores suspended.

The feed tooling here is part of the AgenticEcom Suite, but the compliance checklist below applies to any Magento store feeding Google.

The attributes Google actually requires

Every product in the feed needs the core set, accurately: id, title, description, link, image_link, price, availability, brand, and a product identifier (gtin or mpn). Beyond the basics, condition, google_product_category and, for variants, item_group_id with the right size/colour attributes. Missing or mismatched identifiers are the single most common rejection.

The mistakes that get feeds rejected

  • Price mismatch. The feed price must exactly match the price on the landing page, including currency and tax treatment. Any discrepancy is an instant flag.
  • Missing GTINs. For branded products that have them, omitting GTINs gets items disapproved. Map them properly.
  • Availability drift. If the feed says "in stock" and the page says sold out, Google notices. Keep stock in sync.
  • Thin or keyword-stuffed titles. Titles should be descriptive and match the page — not stuffed, not vague.
  • Broken or wrong image links. Images must be live, high-quality and match the product.

Why doing it from Magento by hand is painful

Building this feed manually means exporting data, mapping attributes to Google's schema, formatting prices and availability correctly, and regenerating it every time stock or pricing changes — for your whole catalogue. Do it once by hand and you'll never want to again. This is squarely an automation job: generate a compliant feed straight from the catalogue, keep it in sync, and deliver it to Merchant Center (and Meta, and the marketplaces) on a schedule. It's part of the wider Magento growth stack.

Beyond Google

The same clean product data powers Meta (Facebook/Instagram) shopping and marketplace feeds — so getting your Magento feed right once opens several channels at once.


Compliant feeds, generated and synced for you. Product Feeds is one of 40+ modules in the AgenticEcom Suite — Google, Meta and marketplace feeds from your catalogue, owned not rented, from £9,995 a year. See the Suite →

Frequently asked questions

Why does Google Merchant Center reject my Magento feed?

Most often: price mismatches between the feed and the landing page, missing GTINs/identifiers, availability that doesn't match stock, or poor titles and image links. Fixing those clears the majority of rejections.

What attributes does a Google Shopping feed need?

At minimum id, title, description, link, image_link, price, availability, brand and a gtin or mpn, plus condition and google_product_category — and item_group_id for variants. They must be accurate and match the page.

Can one feed cover Google and Meta?

Clean Magento product data can be formatted for Google, Meta and marketplace feeds, so getting it right once opens several channels from the same source.