Google Shopping for Fashion: How to Fix Disapproved Apparel Feeds and Win Clicks (2026)

You uploaded the collection. Half of it shows up in Shopping. The other half sits in Merchant Center with a red "Disapproved" label and a reason you have read four times and still cannot act on.

This is normal for fashion. Apparel has more required fields than almost any other category, and most of them are the exact fields a design-first brand never fills in cleanly. The product is fine. The feed is the problem.

This guide covers what Google Shopping actually needs from a fashion product, the attributes that decide whether you get approved, the disapproval reasons you will hit most, and a step-by-step way to fix a rejected feed and keep it clean.

If you only read one thing

• A disapproved apparel feed is almost always a data problem, not a product problem. Google rejects the listing, not the garment.
• Apparel has extra required attributes most categories do not: color, size, age group, gender, and often GTIN. Miss one and the item drops.
• Image rules are stricter than people expect. No promotional text, no watermarks, no placeholder, correct aspect, real product shown.
• Google and Meta want the same product described differently. One clean source of truth, two export formats.
• Kampana builds the feed from one approved product, so every variant ships with attributes that match the spec.

What is Google Shopping for fashion?

Google Shopping is the product listing surface that shows photos, prices, and store names across Google Search, the Shopping tab, and Images. For fashion brands it is often the highest-intent place a product can appear, because someone searching "black linen midi dress" is closer to buying than someone scrolling a feed.

The listings are fed by structured data, not by your website design. You send Google a product feed through Google Merchant Center, and each row describes one product or variant with a fixed set of attributes. Google reads that data, checks it against its policies, and decides whether the item is eligible to show.

For apparel, the catch is that "one product" usually means many rows. A dress in three colors and five sizes is fifteen variants, and each one needs its own correct color, size, image, price, availability, and identifier. That is where fashion feeds get heavy and where they break. Cleaning that up is the whole job of the optimize fashion products for marketplaces workflow.

Why apparel feeds get disapproved more than other categories

Most product categories need a title, a price, an image, and an identifier. Apparel needs all of that plus a stack of attributes that describe fit and audience.

Google treats "Apparel & Accessories" as a special category with its own required fields. According to the apparel product data requirements, items in this category must include color, size, age group, and gender on top of the standard fields. A blank in any one of them can pull the variant from Shopping.

There are three structural reasons fashion brands hit this harder than, say, electronics:

• Variants multiply the surface for errors. One mistake in a color value repeats across every size of that colorway.
• The data lives away from the people who own it. Designers and merchandisers know the real color name. The feed is built by someone else, later, from a spreadsheet.
• Imagery rules collide with brand imagery. The campaign shot with text on it, the lifestyle crop, the watermark for a lookbook. All great for the site. All rejected by the feed.

The product is not the problem. The handoff is. A garment that is perfectly real gets disapproved because a field is blank or an image has a logo in the corner.

How Google reads a fashion product

Google does not see your product page the way a shopper does. It reads the structured attributes you send and, where present, the product structured data on the page. Then it matches that data to search queries and to its own category taxonomy.

Three things drive whether your item shows and where:

What Google reads	Why it matters for fashion
Title and description	Carries the keywords shoppers type: fabric, fit, color, occasion
Required attributes	Decides eligibility. Missing color or size can disqualify a variant
Product identifiers (GTIN, MPN, brand)	Lets Google match your item to known products and other sellers
Image	Must show the real product, no text or watermark, correct format
Price and availability	Must match the landing page exactly, or the item is disapproved

The takeaway: Google is matching data to intent. A title that reads "Aria Dress" tells it nothing. A title that reads "Aria Black Linen Midi Dress, Women's" tells it the color, fabric, length, and audience, which is exactly what a query contains. Good feed data is just your product described the way people search for it.

The apparel attributes that actually matter

You do not need to perfect every optional field. You need the required ones correct and the high-impact ones filled. Here is the short list that decides approval and performance.

Required identity attributes

These apply to almost every product and are non-negotiable:

• id: a unique identifier per variant, stable over time.
• title: clear, keyword-aware, front-load color and product type.
• description: fabric, fit, care, occasion. Real detail, no fluff.
• link and image_link: the landing page and the main image, which must match Google's image requirements.
• price and availability: must match the page exactly.
• brand and gtin or mpn: identifiers Google uses to match your item.

Apparel-specific attributes

These are the ones fashion brands forget, and they are required for the Apparel & Accessories category per Google's apparel rules:

• color: the real color, in words, consistent across variants. Use your customer-facing name, not a hex code.
• size and size_type and size_system: the size plus whether it is regular, petite, plus, and which system (US, EU, UK).
• age_group: newborn, infant, toddler, kids, or adult.
• gender: male, female, or unisex.
• item_group_id: the attribute that ties all variants of one product together so Google knows the five sizes are the same dress.

Image rules that trip up fashion

Imagery is where brand instinct and feed rules disagree most. Google's image link requirements reject images that include promotional text, watermarks, borders, or placeholder graphics, and they expect the image to show the actual product. A campaign still with a price burned into the corner is a guaranteed disapproval, even though it is your best shot.

This is why a feed-ready image is often a different asset than a campaign image. You want a clean product or on-model shot, no text, correct aspect, real garment. Generating that clean variant from the same approved product is part of the ecommerce PDP asset pack.

The most common disapproval reasons and how to fix them

Most disapprovals cluster into four buckets. Here is each one and the fix.

Image issues

The single most common apparel rejection. Usually text or a watermark on the image, a placeholder, or a generic image reused across variants.

1. Replace any image with overlaid text, logos, or watermarks with a clean product shot.
2. Give each color variant its own correct image, not a shared one.
3. Meet the format basics: large enough, real product shown, no borders.
4. Re-submit and let Merchant Center recrawl.

Missing or wrong GTIN

Google uses GTINs to match your product to a known catalog entry. A wrong or invented GTIN is worse than a missing one.

1. If the product has a real GTIN, send it exactly, with no spaces.
2. If it genuinely has none (many small fashion labels), set the correct identifier-exists handling and provide brand plus MPN instead.
3. Never make up a GTIN to fill the field. That triggers a different, harder disapproval.

Mismatched price or availability

If the feed says $90 and the page says $80, or the feed says in stock and the page is sold out, Google disapproves the item for a mismatch.

1. Make the feed read from the same source as the live page.
2. Keep currency and value formatting correct.
3. Use automated item updates or structured data so price and stock stay in sync.

Policy and prohibited content

Some fashion items hit policy edges: certain materials, claims, or imagery. Read the specific reason in Merchant Center against the Shopping ads policies, correct the field or image named, and request review. Do not bulk-resubmit without changing anything, since repeated identical resubmissions can slow your account review.

Google Shopping vs Meta catalog: same product, different rules

You will almost always run the same products on Google and on Meta. The product is identical. The required formatting is not.

	Google Merchant Center	Meta commerce catalog
Spec source	Product data spec	Commerce catalog
Variant linking	item_group_id	Variants under one item group
Color and size	Separate required attributes	Supported, formatted differently
Image rules	No text or watermark	No text or watermark, similar but not identical
Identifiers	GTIN strongly preferred	Retailer ID required, GTIN helpful

The lesson is not "learn two systems by hand." It is to keep one clean source of truth for each product and export it twice. When the underlying data is right, the platform-specific formatting is a transformation, not a rewrite. That mapping is the core of the optimize fashion products for marketplaces workflow.

How to optimize a fashion feed step by step

You do not need to redo the whole catalog at once. Fix the disapprovals first, then raise quality. A working sequence:

1. Sort Merchant Center by disapproval reason, not by product. Patterns appear fast.
2. Fix images first. It is the biggest bucket and the fastest win. Clean shots, no text, per-variant.
3. Backfill the apparel attributes: color, size, size_system, age_group, gender, item_group_id.
4. Resolve identifiers. Real GTIN where it exists, brand plus MPN where it does not.
5. Sync price and availability to the live page source.
6. Rewrite titles to front-load color, product type, fabric, and audience.
7. Re-submit and recrawl, then watch the disapproval count fall.
8. Export the same clean data to Meta, mapped to its format.

Do one collection end to end before you scale the fix. Once the path works for one drop, the end-to-end fashion collection launch carries feed-ready attributes from the start, so new products arrive approved instead of getting fixed later.

Common mistakes that quietly kill performance

Treating the feed as an export, not an asset

A feed dumped from a store template inherits every gap in the store data. Treat feed attributes as something you build, not something you extract.

Reusing one image across colorways

A blue and a green dress sharing the same photo confuses shoppers and risks disapproval. Each color variant needs its own correct image.

Vague titles

"Aria Dress" wins nothing. "Aria Black Linen Midi Dress, Women's" matches real queries. Front-load the words people type.

Inventing identifiers

A made-up GTIN causes a worse problem than a blank one. Declare honestly when an item has no GTIN and use brand plus MPN.

Fixing once and walking away

New products, restocks, and price changes reintroduce errors. A feed is a living thing. Keep the source clean so new items arrive correct.

What to look for in a feed workflow

A short checklist when you evaluate how to handle marketplace feeds:

• Maps to the real specs, the Google product data spec and the Meta catalog, not a generic template.
• Handles variants properly with correct color, size, and item grouping.
• Generates feed-ready images that are clean of text and watermarks.
• Keeps one source of truth that exports to multiple marketplaces.
• Has a review step so a person approves attributes before they go live.
• Pricing that fits a fashion calendar, not per-seat fees that punish a team fixing a feed together.

How a clean feed affects your revenue

Here is the part that gets skipped. A disapproved variant is not a minor data issue. It is a product that cannot be bought through your highest-intent channel.

When a feed is clean, every variant is eligible, every color has its own image, and every title matches the way people search. The same garment shows for more queries and looks right when it shows. When a feed is messy, your bestsellers can be the ones sitting disapproved, and you never see the sales you did not get.

So the real question is not "is my product good." It is "can every variant of my product actually show up and get clicked." That is a data question, and it is the one a feed workflow exists to answer.

How Kampana optimizes fashion products for marketplaces

Kampana is an AI product creation OS for fashion brands. It builds marketplace feeds from one approved product on a node-based canvas, so the attributes, images, and copy that ship are consistent across every variant and every channel. Product-accurate assets pass an approval gate and a product-fidelity check before they go out.

What you get

• Marketplace-ready attributes per variant: color, size, size_system, age_group, gender, item grouping
• Clean, feed-compliant images, no text or watermark, one per colorway
• Titles and descriptions written to match how shoppers search
• One source of truth that exports to Google Merchant Center and Meta formats
• A review step so a person approves the feed before it goes live

The old way vs Kampana

	The old way	With Kampana
Source	Exported from a store template	Built from one approved product
Images	Campaign shots that get rejected	Clean, feed-ready per variant
Attributes	Backfilled by hand in a spreadsheet	Generated per variant to spec
Multi-channel	Rebuilt for each marketplace	One source, mapped to each
Approval	Find out at disapproval	Approval gate + product-fidelity check

How it works

1. Drop one product on the canvas.
2. Wire it to the feed, image, and copy nodes.
3. Approve the attributes and feed-ready images.
4. Export Google and Meta feeds, channel-ready.

Pricing is credit-based. One shared pool for the whole workspace, unlimited users, no per-seat fees, and credits do not expire. You spend on what you actually generate, so a one-time feed cleanup and an ongoing per-drop feed cost different amounts. See pricing for current credit packs, and start with the free credits to fix one collection first.

Frequently asked questions

Why does Google keep disapproving my apparel products?

Almost always a data issue, not a product issue. The common causes are images with text or watermarks, missing apparel attributes like color or size, identifier problems, or a price that does not match the landing page. Read the specific reason in Merchant Center against the apparel requirements and fix the named field.

What attributes are required for fashion on Google Shopping?

On top of the standard fields, the Apparel & Accessories category requires color, size, age_group, and gender, and you should include item_group_id to link variants. See the apparel product data requirements.

Do I need a GTIN for clothing?

Many fashion items have GTINs and you should send the real one. If a product genuinely has none, declare that correctly and provide brand plus MPN instead. Never invent a GTIN, since a false identifier causes a harder disapproval per Google's GTIN guidance.

Can I use my campaign images in the feed?

Usually not as-is. Google's image requirements reject promotional text, watermarks, and borders, which most campaign shots have. Use a clean product or on-model image with no overlay for the feed, and keep the campaign shot for ads and the site.

What is item_group_id and do I need it?

It is the attribute that ties all variants of one product together, so Google understands the five sizes and three colors are the same dress. For fashion it is important for showing the right variant and for clean reporting.

How is a Meta catalog different from a Google feed?

The product is the same but the formatting differs. Meta uses its own commerce catalog rules and identifiers. Keep one clean source of truth and export it to each platform's format rather than maintaining two by hand.

How long does it take a disapproved item to come back?

After you fix the field and request review, Merchant Center recrawls and updates eligibility. Timing varies, so make the correction once and avoid resubmitting an unchanged item repeatedly.

Does feed quality affect more than approval?

Yes. Better titles, correct attributes, and clean images influence which queries your products match and how they look when they show. Approval is the floor. Match and presentation drive the clicks.

The bottom line

A disapproved fashion feed feels like a product problem. It almost never is.

Google Shopping reads structured data, and apparel needs more of it than any other category: color, size, age group, gender, clean images, honest identifiers, and a price that matches the page. Get those right and your variants become eligible, match more searches, and look right when they show. Get them wrong and your bestsellers can be the ones sitting in red.

If you want every variant of every product to ship marketplace-ready from one approved source, with a review step before it goes live, that is what Kampana is built for. Start creating, free, or explore the marketplace feed workflow to see it on one collection.