Google Merchant Center Integration

A Merchant Center account is the entry point to both of Google's product-discovery channels: free listings, which can appear on the Shopping tab, Search, Images, and Lens at no cost, and paid Shopping ads, which run through Shopping campaigns or Performance Max. Both channels pull from the same product feed, so a single, well-structured feed lets you appear in unpaid shopping results while also feeding paid campaigns that use machine learning to match your catalog to purchase-intent queries. Because eligibility for both channels depends on feed data quality — accurate pricing, live stock status, complete required attributes — keeping the feed synced with your actual catalog is what keeps products approved and visible rather than disapproved or suppressed.

Free listings and Shopping ads both surface products from the same Merchant Center feed, but they work differently. Free listings cost nothing to appear — Google can show them on the Shopping tab, Google Maps, Search, Images, and Lens without you bidding on placement. Shopping ads, by contrast, are paid placements run through Shopping campaigns or Performance Max, and they also compete for space on general Search results pages. Most merchants run both from the same account: free listings build baseline visibility, while Shopping ads let you bid for placement and get standardized product traffic reporting. Because both depend on the same underlying feed, fixing a data quality issue makes products eligible for both channels at once rather than requiring separate cleanup work for each.

Merchant Center accepts product data in a few documented formats and submission methods, so you can choose whichever fits your existing systems:

1. Text feed (.txt/.tsv): A tab-delimited file with one product per row and one attribute per column. Google recommends this or XML for most catalogs.
2. XML feed: A structured XML file following Google's product schema; well suited to larger or more complex catalogs.
3. Google Sheets: A shared spreadsheet built from Google's template, which Merchant Center reads directly — practical for very small, manually managed catalogs.
4. Content API / Merchant API: A programmatic interface for pushing product data with near real-time updates instead of waiting on a scheduled crawl.

File-based feeds (text or XML) can be delivered by direct upload or by scheduled fetch from a URL you host, and can be compressed as .zip, .gz, or .bz2.

Google's product data specification documents required, conditionally-required, and optional attributes. The table below lists the core set every feed should account for, verified against Google's individual attribute pages.

1. Connect your store or product catalog to Feedance and select Google Merchant Center as a feed destination.
2. Feedance maps your catalog fields onto Google's documented attribute names — id, title, description, price, availability, image_link, gtin, brand, and so on — and flags any required attribute your catalog doesn't currently populate, such as a missing GTIN or an unmapped google_product_category, so you can fill the gap before the feed goes live.
3. Generate the feed in your chosen format (XML or text) and either let Feedance host it for Merchant Center's scheduled fetch, or submit the feed URL directly as a data source in your Merchant Center account.
4. Confirm the feed in Merchant Center's Diagnostics tab, resolve any flagged item- or account-level issues, and — if you haven't already — set account-level shipping rates for your target countries so a per-product shipping attribute isn't required for every item.

Merchant Center's scheduled fetch lets you set how often it re-reads a hosted text or XML feed. Documented cadences are hourly, daily, weekly, or monthly, each requiring the relevant time fields (for example, an hour for a daily fetch, or a weekday and hour for a weekly one). For catalogs where price or stock changes constantly, a fixed schedule can leave a gap between what's live on your site and what Google is showing; the Content API (now part of the Merchant API) exists specifically to close that gap by letting connected systems push updates as they happen rather than waiting for the next fetch. Whichever cadence you use, Google is explicit that feed data must stay consistent with your live landing pages — price or availability mismatches get flagged as disapprovals regardless of how frequently the feed itself refreshes.

A few practices consistently reduce disapprovals and keep products eligible for both free listings and Shopping ads:

1. Populate every required attribute for every product, not just a representative sample — Google evaluates and can disapprove items individually.
2. Only submit a GTIN when you're certain it's correct; if a product genuinely has none, use identifier_exists = false with brand and a full title/description rather than leaving it blank or guessing a value.
3. Front-load description content with the details that matter for matching — size, material, intended age range, key features — since only part of a long description is guaranteed visibility before a shopper expands it.
4. Use real product photography that meets the 500x500px minimum, but target 1500x1500px or larger for the best placement across Shopping formats.
5. Set shipping once at the account level for each target country, and only use the per-product shipping attribute to override rates for exceptions like bulky or fragile items — don't leave a target country uncovered by either method.
6. Recheck Merchant Center's Diagnostics tab after every catalog or pricing change rather than treating it as a one-time setup step; disapprovals can accumulate silently between checks.

Do I need a GTIN for every product in my Google Merchant Center feed?
Only if the manufacturer assigned one — Google documents this as strongly recommended, and it becomes effectively mandatory in categories where GTIN is the standard identifier. If a product genuinely has no manufacturer-assigned GTIN, submit identifier_exists = false with brand and a descriptive title/description instead of guessing at a number.

What's the difference between free listings and Shopping ads?
Free listings appear at no cost on surfaces like the Shopping tab, Search, and Images; Shopping ads are paid placements run through Shopping campaigns or Performance Max. Both draw from the same product feed in your Merchant Center account.

What image size does Google require for image_link?
At minimum 500x500 pixels, with Google recommending 1500x1500 pixels or larger for the best display across Shopping formats. Files over 16MB or 64 megapixels aren't accepted.

How often does Google re-crawl my feed?
Depends on your scheduled fetch setting — hourly, daily, weekly, or monthly. For catalogs with fast-changing price or stock, the Content API/Merchant API allows near real-time updates instead of waiting for the next scheduled fetch.

Why was my product disapproved even though the feed looked fine?
The most common causes are a price or availability value that doesn't match the landing page, a missing or incorrect GTIN, or an image that's a placeholder or below Google's minimum size — Merchant Center's Diagnostics tab identifies these per item.

Do I need to include the shipping attribute for every product?
No — if you've already configured shipping rates for your target countries at the account level in Merchant Center, a per-product shipping attribute isn't required. Use it only to override account-level settings for specific products, such as oversized or fragile items.

What file formats can I submit to Google Merchant Center?
Text (.txt/.tsv) or XML files — uploaded directly, fetched by Google on a schedule from a URL you host, or pulled from a Google Sheet — plus the Content API/Merchant API for programmatic, near real-time submission.