Google Merchant Center guide

How to Create a Data Feed for Google Merchant Center

Build a structured product feed for Merchant Center, map the required fields, preserve product IDs, and validate the processed result.

A Google Merchant Center data feed is a structured way to provide product information. Google now commonly refers to these inputs as product data sources.

To create one, define the catalog fields, use a supported file or source method, and validate what Merchant Center receives. A CSV-like export of your store is not automatically a compliant product source.

Choose the workflow

Decide whether you need a generated product file, a maintained spreadsheet, or a platform integration.

A manually updated file may be reasonable for a stable small catalog. A frequently changing inventory needs a process that can keep pace.

Choose based on update ownership and data quality, not only on how quickly the first upload can be completed.

Build the field mapping

Map your internal fields to Google’s required attributes. Core product descriptions commonly involve an ID, title, description, price, image, landing page, and availability, with additional requirements depending on the offer.

Use the current specification for your categories and target markets. Attribute names and accepted values must match the required format.

Document any field that is calculated or transformed before export.

Preserve stable product identity

The same product should remain traceable across updates. Maintain a consistent mapping between the store item and the ID sent to Google.

Variants need particular care. Make sure the exported item describes the actual purchasable variant and uses the appropriate landing page.

Avoid regenerating arbitrary IDs on every refresh; it makes investigation and comparison harder.

Create and submit the source

In Merchant Center, use the product data-source setup and choose the appropriate supported method.

For a product file, follow Google’s format guidance. An unsupported format can prevent processing.

Start with a representative sample. Inspect processing errors before assuming the full export is ready.

Validate beyond successful processing

A file can be readable while containing inaccurate offers. Compare received data with real product pages.

Check one standard item, a variant, an unavailable item, and a product with unusual delivery conditions. Review required information and any reported issues.

Then run the next planned refresh to confirm the process remains reliable.

Frequently asked questions

Is a supplemental source the same as a primary source?

No. Google distinguishes sources that add products from sources that supplement information.

Can I use a store connection instead?

Yes, when a suitable supported integration fits your setup.

What should I maintain after launch?

Field mappings, source ownership, update frequency, stable IDs, and a record of recurring errors.

Related reading

What Is Google Merchant Center? A Beginner’s Guide

How to Fix a Google Merchant Center Suspension

Official sources

https://support.google.com/merchants/answer/12631822?hl=en

https://support.google.com/merchants/answer/14989239?hl=en

https://support.google.com/merchants/answer/14990942?hl=en

https://support.google.com/merchants/answer/7052112?hl=en-GB

Looking for Merchant Center support?

Explore the Merchant Fix service for account and suspension issues.

Explore Merchant Fix