Skip to main content

Google Merchant Center for apparel stores

In a clothing feed every color and every size goes to Google as its own item. Most apparel problems are one of those items saying something its page does not.

So check the variants, not just the parent product. That is where the gaps are.

What trips apparel stores up

Size, color, gender and age group

The parent product has a color and a size. The variants in the feed have none, or carry values like multi, see image or n/a.

What Google’s page says: Google lists color, size, gender and age_group as required for clothing in free listings, and for Shopping ads in the countries each page names. Variants share one item_group_id, each variant carries its own value, and placeholders such as see image, N/A, variety or multisize are not accepted. The color page also requires the same color in your product data as on the landing page. Google: Color [color], Google: Size [size], Google: Gender [gender], Google: Age group [age_group], Google: Item group ID [item_group_id]

What we would check: Export the feed and filter to clothing. Every row has a real color, a standard size, a gender and an age group, and every variant of one product shares the same item_group_id.

The guide that fixes it: How to audit your product feed for misrepresentation

One photo for every color

Every color of the same shirt, and only a photo of the black one. Or a group shot of all of them on every listing.

What Google’s page says: As a best practice, Google’s image page recommends a distinct image for every variant that shows the exact color, pattern and finish being sold, and only that variant, and recommends against group photos of several colorways together. Google: Image link [image_link]

What we would check: Open the feed’s image link for each color variant. The photo shows that color, alone.

The guide that fixes it: Product images in Merchant Center: what the feed needs

Sale prices across sizes and colors

The sale applies to some sizes. The feed marks every variant down. Or the page swaps the price with a script after it loads, and Google reads the old one.

What Google’s page says: Google wants each variant’s price in the feed to match the page and checkout, with variant prices shown in a straightforward way. Googlebot compares the feed against the page’s HTML and structured data, a price added by JavaScript after the page loads can trigger a mismatch, and wrong sale dates or time zones cause them too. Google: Price [price], Google: How to fix: Mismatched product price, Google: Sale price [sale_price]

What we would check: For one product on sale, open each size and color. The price on the page, in the structured data and in the feed row for that variant is the same, and the sale dates in the feed match the sale.

The guide that fixes it: Variant prices in Merchant Center: matching every option

Sold out in one size

Medium sold out. The feed still says in stock for every size because availability is set once, on the parent.

What Google’s page says: Google wants the availability in your product data to match the landing page and checkout, and the landing page to show availability clearly. Google: Availability [availability]

What we would check: Pick a sold-out size. The page, the checkout and that variant’s feed row all say out of stock.

The guide that fixes it: Variant stock status: Merchant Center data vs product page

Returns on worn or tried-on items

The returns page says unworn with tags only. Merchant Center was set to accept slightly used. Or the reverse.

What Google’s page says: In Merchant Center’s return settings you choose whether returns are accepted only new or also slightly used, and set any restocking fee. Google asks for the same policy in Merchant Center and across the site, covering buyer’s remorse as well as faults, and for the returns attribute to match the site’s policy exactly. Google: Set up your return policies, Google: Returns [returns]

What we would check: Read your returns page, then your Merchant Center return settings. Condition rules, who pays and any restocking fee say the same thing in both.

The guide that fixes it: How to match your Merchant Center return policy to your site

Vintage and second-hand pieces

A vintage or pre-worn shop sends every piece to Google as new.

What Google’s page says: Google’s condition attribute is required for every used product. Used covers second-hand items, items that show wear, and items that have been altered from how they were first sold. Google: Condition [condition]

What we would check: Every second-hand or altered piece carries condition used in the feed, and the product page says the same.

The guide that fixes it: Condition in Merchant Center: new, used or refurbished

The Merchant Center terms on this page, in plain words: Availability, image_link, sale_price, Price mismatch, Return policy settings.

Checklist

Or skip the checklist and look at your own store. The free scan reads your public pages against Google’s misrepresentation policy and shows what is wrong before you pay anything.

Run the free scan

Read next

StoreVerifier is not affiliated with Google. Each rule above links the Google help page it comes from; when Google changes a page, that page wins.