Google product feed: how it works, IDs, sync and fixes

A Google product feed is the product data you send to Google Merchant Center: one item per product, with attributes such as id, title, price and availability.

Every Shopping ad and free listing starts from it.

Approval is the easy half. The feed also has to keep each product’s identity fixed and its price current, and approval says nothing about which products earn paid clicks.

I checked every Google rule here against Google’s documentation on 24 October 2026.

How does a Google product feed work?

A Google product feed works as a data source: Merchant Center reads it, checks each item against Google’s rules and uses approved items in Shopping ads, Performance Max and free listings.

In a text file, one line is one item. Google uses the attributes “to match your products to the right queries”, says its product data specification. A vaguely described product matches the wrong searches, or none.

Products reach Merchant Center in four ways (Google Merchant Center Help and Google Ads Help, checked 24 October 2026):

If a plugin or feed tool still uses the Content API for Shopping, check its move to the Merchant API now. Google’s sunset notice, checked 24 October 2026, sets these dates:

How does Shopify or WooCommerce product data reach Google Merchant Center?

Shopify and WooCommerce product data reaches Google Merchant Center through an official app that syncs each product change automatically, so neither store needs a feed file. Shopify Help, Merchant Center Help and WooCommerce.com, checked 25 October 2026:

Once connected, each app keeps the products in step:

When price, availability or a GTIN disagrees with the page, fix it in the store: both apps send what the product record holds.

On Shopify, a product marked Under review has changes that haven’t synced yet, so wait before editing it again. On WooCommerce, a GTIN set on the product’s own tab overrides the global attribute rules.

Version 3.8.1 of Google for WooCommerce moved the extension to the Merchant API. Update anything older before the Content API shuts down.

Product Metrics doesn’t replace these apps. It connects to the store for orders and to your Google account, reads Google Ads and Merchant Center data, and adds each product’s segment as a custom label once you approve it.

Which attributes does a Google product feed need?

Every product needs seven attributes: id, title, description, link, image_link, availability and price. Google’s product data specification adds these limits and conditions:

Optional attributes such as colour, size, material and a specific Google product category widen the searches a product can match.

Why must the id never change?

The id must never change because it is the product’s identity in Merchant Center and Google Ads. Google’s product data specification asks you to use the SKU, keep the ID on every update and reuse it across countries and languages.

A changed ID doesn’t rename a product. It creates a new one with no history, and every label or rule keyed on the old ID stops matching.

Each variant gets its own id, and item_group_id ties variants to their parent. Never build an ID from the title, price or stock, because those fields are meant to change:

Migrating platforms? Keep the old IDs, or map each one to its new record before the switch.

How often should a Google product feed update?

A Google product feed should send the full file at least daily and push price and stock changes as they happen. Google’s limits on 24 October 2026:

Thirty days is the cliff, not the schedule: a price that changed this morning stays wrong in Shopping until the next update.

A new product that hasn’t served within those 72 hours isn’t a broken feed: its checks are still running.

The third layer has an exact requirement. Google’s structured data guide requires price, priceCurrency, availability and condition for automatic item updates, which correct a feed value from your page.

Google adds that these automations don’t replace regular updates. The PIM-to-Merchant Center workflow keeps all three layers on one record, with one owner per field.

How do you diagnose a Google product feed problem?

Diagnose a feed problem by separating status from performance. A product that never served has a data problem; one that served and disappointed has a commercial one. The Google Ads API keeps them apart in its Shopping reporting resources:

Then group symptoms by cause, not by Merchant Center’s order: one wrong export rule can fill hundreds of rows.

The first three are data errors. The Merchant Center errors guide lists each by Google’s issue name and traces it to the first wrong value.

The last two aren’t errors at all, so no diagnostics screen will flag them.

Does an approved product deserve ad budget?

No, an approved product doesn’t automatically deserve ad budget: approval means Google accepted the product’s data, not that paid clicks on it will pay back. Google’s guide to correcting an existing feed stops once items are accepted.

A hard risk stops the product serving, and Merchant Center flags it. A soft risk lets the product serve while it loses money:

Give every approved product one of four actions:

1. Fix now: disapproved, or approved with a mismatch that wastes the next click.
2. Promote: in stock, a margin that clears its break-even ROAS, a competitive price and a page that converts. Increase its priority.
3. Delay: too few units to fulfil more orders, or too little data to judge. Hold its priority.
4. Free listing only: sells without ads, or returns eat the profit. Lower its priority or exclude it from Shopping ads.

The fourth action is where feeds get damaged: deleting a product also removes its free listings. The same specification offers gentler switches:

The Performance Max exclusion guide compares these switches inside Performance Max.

By hand, this works for a short product list. Across thousands of products, each action needs recalculating as clicks, margin and stock move, then writing back as a label campaigns can read.

That is what Product Segmentation does.

Product Metrics segments every product into six segments on advertising clicks and ROAS or POAS against your target. It writes each segment to a custom label in Merchant Center, and only the labels you approve go out.

With the GA4 BigQuery export connected, Product Journeys shows whether a click bought that product or another one. Competitor Prices and Inventory Insights add the price position and stock cover behind the promote and delay calls.

Which tool fixes which feed failure?

Pick the tool by the failure you have: data tools fix what Google receives, and a decision layer fixes which products get priority.

Merchant Center by hand works while one person can read every issue, but it never shows margin.

Feed rules stay as current as the condition someone wrote: a custom_label_2 of “high margin” still says so after returns have erased the margin.

For the data layer, start with the 12 feed fixes ranked by profit.

Final thoughts

Every row in a Google product feed promises the same product, under the same ID, at the price on the page. Approval checks that promise. It doesn’t tell you which products to back.

This week, pull shopping_product for the products that never served and fix those. Then decide which of the approved ones deserve paid clicks before you touch a target.

For the business case behind Merchant Center work, 3228 Digital explains why Google Merchant Centre matters for ecommerce in 2026.

If you also run Search campaigns next to Shopping, landing-page experience is one of three Quality Score signals there. This Google Ads Quality Score guide covers how to improve it.

When you map a PIM or shop system into Merchant Center, RUIT’s documentation on product attributes is a compact reference for what product and custom attributes are for.