# Google Merchant Center: what it is and how it works

> What Google Merchant Center is, how your product data gets there, where Google shows it and how to check that the feed and the product page match.

URL: https://clione.ai/glossary/google-merchant-center/
Lang: en

Google Merchant Center is the door through which a store's products enter Google's shopping surfaces. It is not Google Ads, although Shopping ads come out of it, and it is not [Search Console](/glossary/google-search-console/), which reports how your site appears in Search but does not receive product data. It matters to a store for two reasons that now go together: free listings, which show your products without paying for ads, and Google's AI answers, which according to Google can include product listings and information. **Google expressly says that [product feeds](/glossary/product-feed/) in Merchant Center help your products show up in AI answers as well as in the rest of the results**.[^google-ai-guide]

## How it works

**What it receives.** Product data in a fixed format, the product data specification. Among the attributes it asks for are the identifier, the title, the description, the link to the [product page](/glossary/product-page/), the main image, the availability, the price and, for new products, the brand. Each has its limits: the title allows up to 150 characters and the description up to 5,000.[^gmc-spec] [Product attributes](/glossary/product-attributes/), such as color, size or material, complete that base.

**How it gets there.** Google supports five routes: uploading files by hand or over SFTP, using a Google Sheets spreadsheet, sending the products through the Merchant API, connecting an ecommerce platform such as Shopify, or letting Merchant Center read your website's [structured data](/glossary/structured-data/).[^gmc-data-source] Any of them is a [product feed](/glossary/product-feed/) in the broad sense: a list of products with their attributes that Merchant Center reads.

**Primary source and supplemental source.** The primary source is the base information Merchant Center uses to access your products and show them, and it is the only one that can add or remove them. A supplemental source adds more details or updates existing ones, such as price or availability, but **it cannot create or delete products, or work on its own**.[^gmc-data-source] It is the way to complete a catalog without touching the main connection.

**Where they appear.** With free listings, products can be shown in Google Search (including [rich results](/glossary/rich-results/) and knowledge panels), in the Shopping tab, in Images and Lens, on YouTube, in [Gemini](/glossary/gemini/), in Maps and in the product module of the Business Profile. To use them you need a Merchant Center account, you have to meet the product policies, have the [return policy](/glossary/return-policy/) on your site and set up shipping. And a nuance worth reading twice: **the status of free listings gives permission to show your products, but it does not guarantee they will be shown**.[^gmc-free-listings]

**Its relationship with the product page.** Google recommends providing the data both ways, the markup on the page and Merchant Center, because that way you qualify for more experiences and help it understand and verify your data. Some experiences combine the two sources: a product snippet can take the price from the feed if it is not in the markup.[^google-product-intro] That is why the feed and the product page have to say the same thing.

**The API changed in 2026.** Google shut down the Content API for Shopping on August 18, 2026; since September 1, requests to that API get progressive errors, and every integration has to move to the Merchant API.[^merchant-api-updates] If an app or a connector sends your products by API, this is the first place to look when something stops arriving.

## In a store

A **fictitious example**: the same product from a mountain gear store, as Merchant Center has it and as it looks on the published product page.

| Attribute    | In the primary source                   | On the published page                  | What happens                                                                |
| ------------ | --------------------------------------- | -------------------------------------- | --------------------------------------------------------------------------- |
| Title        | "Cima 3"                                | "Cima 3 waterproof trail running shoe" | The product matches, the title does not: the feed's does not say what it is |
| Price        | The pre-sale one                        | The discounted one                     | They do not match: the feed was not updated with the sale                   |
| Availability | In stock                                | Sold out in size 9                     | Depends on how [variants](/glossary/product-variants/) are sent             |
| Color        | Empty                                   | Red and gray                           | The data exists in the store and never reached Merchant Center              |
| Description  | Manufacturer copy, with "free shipping" | Own text                               | The feed breaks the rule against promotional text                           |

Each row is a different kind of failure: a title that does not describe, a price that did not sync, variants sent wrong, an attribute lost along the way and a text that does not follow Merchant Center's rules. **The color row is the one a supplemental source fixes without touching the primary**.[^gmc-data-source] It is what Clione does from the enriched catalog: a supplemental feed for Merchant Center that fills in color, material, size, gender and age group when the store provides them, and Google's product category only when it matches its official list exactly.


That a supplemental source can be used to add missing products. It cannot: **it only updates or completes products that are already in a primary source**, and it does not work as an independent source.[^gmc-data-source] If a product does not show up in Merchant Center, the problem is in the primary source or in the platform connection, not in the supplemental feed.


## How to check it

1. **Look at which data sources you have and which one is the primary.** If there are several, note what each one does: the primary creates the products, the supplemental ones only complete them.[^gmc-data-source]
2. **Pick five products and compare them with their product pages**: title, price, availability and image. Google combines the page and the feed, so a difference between the two is a problem in both.[^google-product-intro]
3. **Read the feed descriptions** looking for links, capital letters used for emphasis or promotional text such as prices or shipping: the specification does not allow them.[^gmc-spec]
4. **Check the status of the free listings**, knowing that being approved gives permission to show the products, not a guarantee that they will be shown.[^gmc-free-listings]
5. **If your products arrive by API, confirm the integration uses the Merchant API.** The Content API for Shopping is no longer available.[^merchant-api-updates]

## Related concept: product feed

The product feed is the file or the connection that carries the data; Merchant Center is the destination that receives it, validates it and decides where it can appear. The same feed can supply Google and other destinations, and Merchant Center can receive several at once, one primary and as many supplemental ones as needed.[^gmc-data-source] **When a product does not show up on Google, the diagnosis starts in Merchant Center**, which says what it received and what it rejected; when the received data is wrong, the fix is in the feed or in the store it comes from.

To go on, the [catalog and entities reading path](/learn/catalog-and-entities/) puts the rest of the terms in order.