Google Merchant Center: what it is, how a product feed works, and how to set one up

Google Merchant Center is a free Google account where you keep the data about the products you sell, so Google can show those products in Shopping results, in the Shopping tab, in free product listings and in Shopping ads. The data goes in as a product feed, which is a table with one row per product and one column per attribute. Merchant Center reads each row, checks it against Google's product data specification, and either approves the item or tells you what is missing. To set an account up you need three things: a website you can verify and claim, a feed of your products, and shipping and returns settings for every country you sell to.

This page covers Merchant Center whole: what the account is, how a feed is built, and how to get a clean one live. One job has its own narrow reference, and that is working through a queue of rejected items: for feed rules, supplemental feeds and disapprovals one by one, go to Merchant Center setup, feed rules and the disapprovals that stop your products showing.

What the account is, in one minute

Merchant Center is your product database inside Google. Nothing in it advertises anything by itself. It holds facts: this item has this title, this price, this availability, this image, at this URL. Google uses those facts across several surfaces.

• Free product listings in the Shopping tab and some standard search results, which cost nothing.
• Shopping ads, bought in Google Ads but built from the feed rather than from ad copy you write.
• Local inventory, if you run shops and upload what is in stock at each.

One point matters more than anything else here: in Shopping, the feed is the creative. A weak title or a missing attribute is a weak advert, not a small data problem.

Three Google accounts get mixed up. Merchant Center holds product data plus shipping, tax and returns settings. Google Ads holds campaigns and bidding, and buys placement for products Merchant Center has approved. Google Business Profile holds the business itself, for Maps and local results. You can run Merchant Center with no ad spend and still appear in free listings, and you cannot run Shopping ads without it.

A product feed is a spreadsheet, and that is the whole idea

Strip away the file formats and a feed is a table. The first row is a header naming each attribute. Every row after it is one thing a customer can buy. A shirt in three sizes and two colours is six rows, grouped so Google reads them as variants of one product rather than six unrelated items.

Google accepts that table as a delimited text file such as TSV or CSV, an XML file using the RSS structure with Google's namespace, a Google Sheet read on a schedule, or a direct connection from your shop platform. The shape changes nothing about the content, so use whatever your platform exports most reliably.

The anatomy of one row

Google's product data specification is the authority on each attribute. Below is the working subset: what decides whether an item is approved, and what each attribute controls once it is.

Attribute	Status	What it decides
id	Required	Your permanent SKU. Never reuse an id for a different product.
title	Required	Most of the matching and nearly all of the clicking.
description	Required	Secondary matching. Product facts, not marketing lines.
link	Required	The exact landing page for that variant, on the domain you claimed.
image_link	Required	A plain product shot with no added text, logos or borders.
availability	Required	in_stock, out_of_stock, preorder or backorder.
price	Required	Value plus currency code, matching the landing page.
brand	Required for most	The manufacturer brand. Your shop name only if you made the item.
gtin or mpn	Conditional	The unique identifier. Branded retail goods normally need the GTIN; own label goods declare that none exists.
condition	Conditional	new, refurbished or used. Required whenever the item is not new.
item_group_id	Conditional	Ties variant rows together so size and colour behave as one product.
google_product_category	Recommended	Google's own taxonomy value. Set it yourself where the automatic guess is loose.

Writing titles that do the work

Put the words a buyer would type at the front, in the order they would type them: brand, then product, then the distinguishing attribute, then size. Leave out promotional words such as sale or free delivery, which the Shopping policies treat as a reason to disapprove an item. A catalogue line beats a headline.

A feed you can copy and adapt

The simplest working feed is a tab separated file: a header row, then one row per item. Columns are shown below separated by pipe characters for legibility. Save the real file with a tab between each column.

id | title | description | link | image_link | availability | price | brand | gtin | condition | item_group_id

SKU-1001 | Acme Trail Runner Mens Running Shoe Blue UK 9 | Road and trail running shoe with a mesh upper. | https://example.com/shoes/trail-runner-blue-9 | https://example.com/img/trail-runner-blue.jpg | in_stock | 4999.00 INR | Acme | 00012345678905 | new | TRAIL-RUNNER

The same item as XML, which is what most shop platforms generate:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:g="http://base.google.com/ns/1.0">
  <channel>
    <item>
      <g:id>SKU-1001</g:id>
      <g:title>Acme Trail Runner Mens Running Shoe Blue UK 9</g:title>
      <g:link>https://example.com/shoes/trail-runner-blue-9</g:link>
      <g:image_link>https://example.com/img/trail-runner-blue.jpg</g:image_link>
      <g:availability>in_stock</g:availability>
      <g:price>4999.00 INR</g:price>
      <g:brand>Acme</g:brand>
      <g:gtin>00012345678905</g:gtin>
      <g:condition>new</g:condition>
      <g:item_group_id>TRAIL-RUNNER</g:item_group_id>
    </item>
  </channel>
</rss>

Those values are placeholders on a reserved example domain. Swap in your own SKUs, URLs, identifiers and currency.

Setting the account up, in order

• Create the account with the business name customers recognise, and set your country of sale and currency.
• Verify and claim the website. Verification proves you control the domain, through Search Console, a meta tag or a file upload. Claiming ties that domain to this account so nobody else can feed products from it. Google's notes on store URL verification cover the methods.
• Fill in shipping and returns. Rates and delivery times are account settings, and an item with no deliverable shipping option is not eligible. Google documents account level shipping settings step by step.
• Choose how data gets in. A platform connection from Shopify, WooCommerce or Magento, a scheduled fetch of a feed URL on your server, a Google Sheet, a manual upload, or the Content API for large catalogues. Platform connection first; the API only when you have a real reason.
• Upload a small batch first. Ten representative items and read every warning before you push the full catalogue.
• Set the refresh schedule so price and stock in Google match price and stock on your site at least daily.

Feed, product page and structured data have to agree

This is the part that quietly costs sellers the most. Google compares what your feed claims against what it finds when it crawls the landing page, and a mismatch on price or availability is a serious problem, not a typo.

• Price must equal the price shown on the landing page in the same currency, before any code the buyer has to enter.
• Availability must match what the page says, for the specific variant the link points to.
• Product schema should carry the same price, currency, availability and identifier as the feed row. Google's product structured data documentation lists the properties, and our note on the properties that matter gives a copyable block.
• Landing page must be the variant page, reachable without a login, on the claimed domain.

Build it so one system publishes all three. If a person updates the price in two places by hand, the two will disagree by Friday.

Where to go next

Once the feed is clean, see how to advertise on Google Shopping for campaigns built on it, and the feed, the margin and the account structure for the commercial side. The authority on every attribute remains Google's own product data specification, and the Shopping ads and listings policies are worth one careful read before you launch.

What gets asked about Google Merchant Center

Does Google Merchant Center cost anything?

The account is free and free product listings cost nothing. You pay only when you choose to run Shopping ads through Google Ads, and that spend is set and billed there.

Do I need a Google Ads account to use Merchant Center?

No. Many sellers run it purely for free listings, and link Google Ads later when they decide to buy placement on top.

How often should the feed update?

Daily at minimum, and faster for anything whose price or stock moves during the day. Platform connections and the Content API handle this automatically, which is the main reason to prefer them over a manual upload.

What if my products have no barcode?

Handmade and own label goods often have none. Declare that no identifier exists and supply the brand and MPN instead, exactly as the unique product identifiers guidance describes, rather than inventing a GTIN.

Can one feed serve more than one country?

Yes, with the right currency, language and shipping configuration per target country. Set up one country properly, then clone the arrangement once it is clean.

The product question your feed misses

Your feed answers Google Shopping's questions: price, availability, identifiers. Shoppers also put plain questions to an assistant, like which pan is best for induction hobs, and the answer draws on reviews and descriptions beyond the feed.

Make sure the descriptions on your product pages say what the product is good for in the same plain words. Then ask three such questions and see which products are named. If yours is absent, compare its page with the cited ones. AI Knows Us covers product questions across the assistants and lists the sources behind each reply.