
Quick answer
A Google product feed is the product data you send to Google Merchant Center, one item per product, by file, app or API. As of November 2026, every product needs id, title, description, link, image_link, availability and price. Brand, GTIN, MPN, condition, color, size and shipping depend on the product and the country.
Key takeaways
- A Google product feed is the product data you send to Merchant Center, and Google now calls it a data source, whether it arrives as a file, a spreadsheet, an app sync or an API call.
- Seven attributes are required for every product (id, title, description, link, image_link, availability and price), and brand is also required for new products other than movies, books and music.
- A US apparel store must also send color, gender and age_group, plus size for clothing and shoes, and item_group_id on every variant.
- As of November 2026, google_product_category is optional, because Google assigns a category to every product automatically and accepts an override only in specific cases.
- Products expire from Merchant Center 30 days after their last refresh, so a feed needs a scheduled sync rather than a single upload.
On this page
- What is a Google product feed?
- Which attributes does Google require in a product feed?
- Which feed attributes depend on the product or country?
- Which optional attributes are worth adding?
- What does a sample product feed row look like?
- Should you use a file, the API or a platform sync?
- How do you set up a Google product feed?
- What is a supplemental feed and when do you need one?
- What are the most common product feed errors?
- How often should you update a Google product feed?
- What changed in the product data specification in 2026?
- FAQ
What is a Google product feed?
A Google product feed is a structured list of the products you sell, sent to Google Merchant Center so they can appear in Shopping ads, free listings and other Google surfaces. Each item is one product, and each fact about it (title, price, image, stock status) is an attribute. Google's product data specification says it uses this data to match products to searches, and a Shopping campaign has no keywords of its own to do that job.
A feed doesn't have to be a file. It can be a spreadsheet, an app connection or an API. Google renamed feeds to data sources when Merchant Center Next rolled out, and Diagnostics became the Needs attention tab. Most people still say product feed or Google Shopping feed, so we use feed here and data source when we point at a Merchant Center screen.
Which attributes does Google require in a product feed?
Seven attributes are required for every product: id, title, description, link, image_link, availability and price. Google's specification says that without a required attribute, a product won't be able to serve in ads and free listings. The table shows the rules as of November 2026.
| Attribute | Google's rule | Example |
|---|---|---|
id | Unique, max 50 characters. Use the SKU where possible and keep it the same when you update. | MRW-CN-NVY-M |
title | Max 150 characters. Matches the landing page, with no promotional text or all capitals. AI-written titles go in structured_title. | Mens Pique Polo Shirt |
description | Max 5,000 characters. Only about the product, with no store links or sale text. AI-written text goes in structured_description. | Made from 100% organic cotton |
link | Your verified domain, starting with http or https, as an encoded URL. | https://www.example.com/polo |
image_link | Main image as JPEG, WebP, PNG, non-animated GIF, BMP or TIFF. No promotional text, watermarks, borders or placeholders. | https://www.example.com/polo.jpg |
availability | One of in_stock, out_of_stock, preorder or backorder. Matches the landing page and checkout. | in_stock |
price | Number plus currency code. Matches the page, structured data and checkout. US prices leave out sales tax. No price of 0, apart from contract and subscription exceptions. | 15.00 USD |
Titles do the most work after approval, so our guide to Google Shopping product titles covers them by category.
Watch for old lists. Some guides still list condition as required for every product. As of November 2026, Google's specification requires it only for used and refurbished products, and it marks google_product_category as optional.
Which feed attributes depend on the product or country?
Conditional attributes apply when the product, its category or the target country triggers them. Google labels these "It depends" or lists the condition beside the attribute. For a US store, the usual triggers are identifiers, shipping, apparel, variants, used goods and preorders.
| Attribute | When a US store needs it | What to know |
|---|---|---|
brand | All new products except movies, books and musical recordings | Max 70 characters. Never "N/A" or "Generic". Leave it empty if the product truly has no brand. |
gtin | Google says it depends, and strongly recommends it if available | A product with a GTIN sent without one may get limited visibility. A wrong GTIN gets it disapproved. |
mpn | Only if the product has no manufacturer-assigned GTIN | Don't guess. An incorrect MPN also gets the product disapproved. |
identifier_exists | Optional, and the default is yes | Set it to no only when the product really lacks identifiers. A false no can get it disapproved. |
shipping | Shipping costs are required for US listings | Use this attribute when your account settings don't cover the product or you need an override. |
condition | Used and refurbished products | Values are new, refurbished or used, in English. |
availability_date | Preorder, and Google's availability rules ask for it on backorder too | Up to one year ahead, shown on the landing page. |
color | All apparel, plus anything sold in different colors | Never "multicolor" or a number. Separate several colors with a slash. |
size | Clothing and shoes, plus anything sold in different sizes | Don't put a multipack count in this field. |
gender, age_group | All apparel, plus gender-specific products and products with assigned age groups | Gender is male, female or unisex. Age group is newborn, infant, toddler, kids or adult. |
item_group_id | Every product that is a variant | Use the parent SKU. It groups variants so they show together. |
material, pattern | When they tell variants in a set apart | Separate up to three materials with a slash. |
is_bundle, multipack | Bundles and multipacks you created yourself | Don't use multipack on a pack the manufacturer assembled. |
promotion_id | Products linked to US promotions | Max 50 characters, with up to 10 IDs per product. |
shipping_weight | Carrier-calculated shipping rates | Dimensions are required for those rates too. |
For example, an illustrative sweater sold in 4 colors and 5 sizes is 20 items in your feed. Each one gets its own id, color and size, and all 20 share one item_group_id. Our guide to what a GTIN is and where to find one covers the identifier fields for private label, custom and vintage products. Shipping costs and delivery times usually live in your account, as our Merchant Center shipping settings guide explains.
Which optional attributes are worth adding?
Start with the optional attributes that change how campaigns run or what people see on the listing. Google says optional attributes are there to help performance, so add the ones you will really use and can keep accurate.
| Attribute | What it does | Limit or rule |
|---|---|---|
additional_image_link | Adds images beyond the main one, including staged and in-use shots | Up to 10 |
sale_price, sale_price_effective_date | Shows a sale against the regular price | With no date range, the sale price always applies |
product_type | Your own category path, used for bidding and reporting in Shopping campaigns | Max 750 characters. Only the first value is used. |
google_product_category | Overrides the category Google assigned | Use one category. Google prefers the numeric ID. |
custom_label_0 to custom_label_4 | Your own groups, such as margin tier or clearance, for bidding and reporting | Max 100 characters and 1,000 unique values per label |
product_highlight, product_detail | Short selling points and technical specifications | 2 to 100 highlights, up to 100 details |
video_link | Adds a product video to free listings and ad creation | Won't affect approval status |
cost_of_goods_sold | Adds gross margin insights in Merchant Center | Number plus currency code |
pause | Stops a product for a short time without changing stock status | 14 days at most, then it is disapproved |
Category choice has its own rules, so read our guide to the Google product category attribute before you add it. Google assigns a category to every product and accepts an override only in certain cases.
Google also added a group it calls conversational attributes: question_and_answer, document_link, related_product, item_group_title, variant_option and popularity_rank. They help AI systems understand a product across surfaces such as AI Mode in Search, and they won't affect approval. Google recommends sending them in a supplemental data source.
What does a sample product feed row look like?
A sample feed row holds one value for each attribute, under column headers that use Google's exact attribute names. Here is one illustrative row for a US apparel store. The store and product are made up, and the GTIN is the sample number Google uses in its specification.
| Column header | Value | Why it is there |
|---|---|---|
id | MRW-CN-NVY-M | Required. Variant SKU. |
item_group_id | MRW-CN | Required for variants. Parent SKU. |
title | Marlow Women's Merino Wool Crew Neck Sweater, Navy, Medium | Required. Names the variant. |
description | Merino wool crew neck sweater with ribbed cuffs and hem. | Required. |
link | https://www.example.com/products/merino-crew-neck | Required. |
image_link | https://www.example.com/images/merino-crew-navy.jpg | Required. |
availability | in_stock | Required. |
price | 89.00 USD | Required. No sales tax. |
brand | Marlow | Required for this new product. |
gtin | 3234567890126 | Send it when the product has one. |
color | Navy | US apparel. |
size | M | US clothing. |
gender | female | US apparel. |
age_group | adult | US apparel. |
product_type | Women > Sweaters > Crew Necks | Optional. Campaign grouping. |
custom_label_0 | bestseller | Optional. Campaign grouping. |
We left out two fields on purpose. Shipping is set at account level here, so no shipping column is needed. And google_product_category stays blank, because Google assigns a category on its own.
In a tab-delimited file, the first row holds these headers and each product takes one row below, as Google's product file guide shows. You can leave a cell empty when a value doesn't apply. In XML, each attribute becomes an element with a g: prefix, such as <g:price>89.00 USD</g:price>, inside an item, and the file declares xmlns:g="http://base.google.com/ns/1.0". That same guide's XML sample writes "in stock" with a space, while the specification lists in_stock. Follow the specification.
Should you use a file, the API or a platform sync?
Use your store platform's Google connection if it has one, a hosted file if it doesn't, and the Merchant API if prices or stock change many times a day. Google's upload guide lists each route, and you can combine them.
| Route | How updates arrive | Best for | Watch for |
|---|---|---|---|
| Platform connection | Automatic. Changes may take 24 to 48 hours. | Stores on Shopify and similar platforms | Up to 3 days for all products to appear. Make edits in the platform. |
| Hosted file (URL, SFTP or Google Cloud Storage) | Google fetches a URL every 24 hours. With SFTP or Cloud Storage, you upload new files. | Custom stores and exports from other systems | Formatting is on you. The file name must match exactly. |
| File upload from your computer | Only when you submit it again | A first test | No automatic sync, so products can expire |
| Google Sheets | Syncs every 24 hours by default | Small catalogs | Must follow Google's template |
| Merchant API | As often as you send updates | Large catalogs and frequent changes | Needs a developer. A success response doesn't mean approved. |
| Website crawl | Google reads schema.org markup on your store | Simple stores with clean markup | Doesn't work for local inventory ads or free local listings |
| Product editor | You type each product in Merchant Center | A few extra products | Only for accounts that already have products |
On Shopify, the Google & YouTube app syncs the products available to your online store. You may still need to add identifiers, such as a GTIN, or brand plus MPN. If you need more control over titles or rules, our comparison of the best Google Shopping feed apps for Shopify sets the options side by side.
Content API status. Google sunset the Content API for Shopping on August 18, 2026. Since September 1, 2026, requests without an active extension fail intermittently, and Google plans a full shutdown in early 2027. Some setup guides still recommend it, so check any old plugin or script and move it to the Merchant API.
How do you set up a Google product feed?
Set up a feed by getting the account ready, building your product data, creating a primary data source in Merchant Center, and then clearing the issues Google reports. Google recommends one primary source for all your products.
- Prepare the account. Verify your website and add shipping and return policies. Our Google Merchant Center setup guide covers this part.
- Pick your route. Use the table above. Connect your platform if you have one, and skip step 3.
- Build the data. Export your catalog, rename columns to Google's attribute names and fill the required and conditional fields. Save as .tsv, .txt or .xml in UTF-8 or UTF-16.
- Create the primary data source. In Merchant Center, go to Settings › Data sources and select Add product source. Choose a file, a Google Sheets template or the API, then enter your target countries, language and marketing methods.
- Read the first result. Open the source and check the Latest update tab, where the "What needs attention" column lists file problems.
- Fix product issues. Open Products › Needs attention, work through the summary cards first, and change values where the data comes from.
Google's big events guide says a feed can take up to 72 hours to be crawled after you submit it for an initial review. Don't start the night before a launch.
What is a supplemental feed and when do you need one?
A supplemental feed is a second data source that adds to or overrides attributes in your primary source, matched by id. Use one when you can't or don't want to change the primary data, such as adding custom labels without editing your store.
Primary data source
- The main record of your products
- The only source type that can add or remove products
- Sets language and country targeting
- Works without any add-on
Supplemental data source
- Adds or updates attributes on existing products
- Can't add or remove products or stand alone
- Matches on an identical id
- Needs the Advanced data source management add-on
Turn on the add-on under Settings › Add-ons, then add the source from the Supplemental sources tab, as Google's data source guide explains. The data source label must match the primary source exactly. If your feed comes from an app, check that its data source appears when you pick a primary source to attach to, because Google's page doesn't say either way.
For example, a store with 600 products wants to label 120 clearance items (illustrative numbers). It adds a Google Sheet with two columns, id and custom_label_0, and 120 rows. The other 480 products stay as they are, and a Shopping campaign can now bid on the clearance group separately.
The same add-on enables attribute rules, the new name for feed rules. Rules change values with logic instead of a sheet, such as setting a brand across a category. Google has also deprecated online inventory data sources, so fast price and stock updates can go through a supplemental source with the Take latest rule instead.
What are the most common product feed errors?
The most common feed errors are data that doesn't match the landing page, invalid values, missing variant attributes and file format mistakes. Product issues appear in the Needs attention tab, and file issues appear in the data source's Latest update tab.
| Problem | Usual cause | Fix |
|---|---|---|
| Price or availability mismatch | The feed and landing page differ, often during a sale | Fix the source, keep Automations on and add structured data |
| Landing page can't be checked | Page down, or Googlebot or Googlebot-Image blocked in robots.txt | Restore the page and allow the crawlers |
| Invalid value | Free text in a fixed field, such as "brand new" for condition or "various" for color | Use Google's supported values, in English |
| Missing variant data | No item_group_id, color or size on variants | Add them on every variant row |
| Incorrect GTIN or MPN | Guessed values, or a code from another product | Use the manufacturer's value, or leave it out if unsure |
| Image problems | Thumbnails, watermarks, or the warning Image too small for upcoming enforcement | Send a larger, clean image |
| File won't process | Unsupported type, missing tabs, unclosed XML tags or wrong encoding | Re-export as .tsv, .txt or .xml in UTF-8 or UTF-16 |
| Product lost its history | The id changed, so Google treats it as a new product | Keep ids stable. Approval can take up to 3 business days. |
| Edits keep reverting | A second source updated the product last | Edit one source, usually your platform |
For the full list of disapproval reasons and fixes, see our guide to fixing disapproved products in Merchant Center.
How often should you update a Google product feed?
Update your feed at least once a day, and any time price or stock changes. Google says all products expire 30 days after the last refresh. Products added directly in Merchant Center don't expire, and Google can refresh a product by crawling your site. A hosted file or Google Sheet gets a daily sync, which covers most stores.
Automations, which are on by default, use your landing page to correct price, sale price, availability and condition. Google says they don't replace regular updates. They may not work for products that change more than once a day, and a product can be disapproved instead of updated.
Timing matters most before big sales. Google suggests sending new product data 3 to 5 business days before an event, but no earlier than 30 days ahead. For Black Friday on November 27, 2026, that means new products by November 20. An item switched to in_stock can take up to 24 hours to show, and Google warns against setting a product to out_of_stock to pause it. Use the pause attribute for that.
What changed in the product data specification in 2026?
Google updates the specification every year, and the biggest open change is the 500 x 500 pixel image minimum. These are the dated changes that affect a feed, from Google's 2026 specification update and announcements log.
| Date | Change | What to do |
|---|---|---|
| April 14, 2026 | New handling_cutoff_time and minimum_order_value attributes | Use them only if a product differs from your account settings |
| April 14, 2026 | Warnings began for images under 500 x 500 pixels | Check Needs attention, then View history |
| June 30, 2026 | video_link videos became eligible to serve | Add product videos if you have them |
| August 18, 2026 | Content API for Shopping sunset | Move integrations to the Merchant API |
| October 2026 | warranty attribute added for products targeting Canada, tied to Quebec's Bill 29 | Send it if you sell covered products to Quebec |
| January 31, 2027 | 500 x 500 pixel minimum enforced on image_link and additional_image_link | Replace small images now |
Google says it will optimize some smaller images so they meet the rule, and marks them with a warning. You can replace any of them by sending a larger image, and Google recommends around 1500 x 1500 pixels or above. These dates are as of November 2026, so check the specification before you plan around them.
Feed setup and cleanup is part of our Merchant Center management at Logical Gecko, an independent agency not affiliated with Google. If products sit in Needs attention and you can't trace why, we fix values at the source so they survive the next sync.
Frequently asked questions
Is a product feed the same as a Google Shopping feed?
Yes. Product feed, Google Shopping feed, data feed and Merchant Center feed all describe the same product data. Google's own term is now data source. Shopping ads and free listings read from that one source, so you don't build a separate file for each. You only choose which Google features can use it, through the marketing methods setting on the data source.
What file format does a Google product feed use?
Google accepts tab-delimited .txt and .tsv files and .xml files, such as RSS 2.0 or Atom 1.0, up to 4 GB per file. Save them as UTF-8 or UTF-16. File types such as .html and .pdf fail, and a spreadsheet saved as .xlsx needs exporting first. Google Sheets is a separate option that uses Google's own template, so you don't need to export anything.
Is there a free Google product feed template?
Yes. In Merchant Center, go to Products, select Add products, choose Use Google Sheets and select Use template. Google opens a spreadsheet with the right columns and syncs it every 24 hours by default. If you would rather build a file, Google's product file page shows sample rows, and its tab-delimited guide links to an example .txt file you can copy.
Do I need a product feed if I use Shopify?
You need product data in Merchant Center, but you don't need to build a file. The Google & YouTube app on Shopify syncs the products available in your online store, and Google recommends managing that data in your platform. Changes may take 24 to 48 hours to appear. A separate file or feed app makes sense only when you need control the app doesn't give you.
Is google_product_category required in a product feed?
No. Google's specification marks it optional, and every product gets a category automatically. Google accepts an override when a wrong category adds requirements that don't apply, when your campaigns are built on Google product categories, or when alcohol needs the correct category. Gift cards, mobile devices sold with a contract and physical goods subscriptions must also use specific categories.
How long does a new product feed take to go live?
Google says a feed can take up to 72 hours to be crawled after you submit it for an initial review, and it suggests sending new product data 3 to 5 business days before a launch or sale. A platform connection may take up to 3 days to bring in all products. Plan for the full window, and start well before a sale.
Can I have more than one feed in Merchant Center?
Yes, but Google recommends one primary data source for all your products, with excluded_destination for anything you want to keep out of a channel. Add supplemental sources for extra attributes. If the same product arrives through two sources, Merchant Center treats it as part of whichever source updated it last, so two sources can overwrite each other.
What size should product images be in a feed?
At least 500 x 500 pixels. Google begins enforcing that minimum on January 31, 2027, for image_link and additional_image_link across all product categories, and it recommends around 1500 x 1500 pixels or above. No image can exceed 64 megapixels or 16 MB. Merchant Center already shows the warning Image too small for upcoming enforcement; Google's pages date it April 14 and July 2026.
Sources27 references
- Google Merchant Center Help: Product data specification
- Google Merchant Center Help: Merchant Center product data specification update 2026
- Google Merchant Center Help: Merchant Center announcements change log
- Google Merchant Center Help: Merchant Center Help Center now fully supports Merchant Center Next
- Google Merchant Center Help: How to upload your products to Merchant Center
- Google Merchant Center Help: Create a product file for Merchant Center
- Google Merchant Center Help: Add products from a file to Merchant Center
- Google Merchant Center Help: Create a tab-delimited product data source
- Google Merchant Center Help: Add products to Merchant Center using Google Sheets
- Google Merchant Center Help: Add products from an ecommerce platform to Merchant Center
- Google Merchant Center Help: Syncing your products (Google & YouTube app on Shopify)
- Google Merchant Center Help: Create a product data source
- Google Merchant Center Help: Manage your data sources
- Google Merchant Center Help: Set up your attribute rules
- Google Merchant Center Help: How to use conversational attributes
- Google Merchant Center Help: Google product category [google_product_category]
- Google Merchant Center Help: Item group ID [item_group_id]
- Google Merchant Center Help: Shipping [shipping]
- Google Merchant Center Help: Image link [image_link]
- Google Merchant Center Help: Video link [video_link]
- Google Merchant Center Help: Expiration date [expiration_date]
- Google Merchant Center Help: Allow Merchant Center to update product information automatically
- Google Merchant Center Help: Tips to help your products stay approved
- Google Merchant Center Help: How to prepare for big events and product launches
- Google Merchant Center Help: The Needs attention tab
- Google for Developers: Merchant API, Manage your products
- Google for Developers: Content API for Shopping, Deprecation and sunset




