How many top-level categories should a fashion ecommerce taxonomy have?

Most fashion stores work well with 6 to 8 top-level departments: Women's Clothing, Men's Clothing, Kids' Clothing, Footwear, Accessories, Swimwear, Lingerie and Nightwear. The exact number depends on catalog depth — avoid creating top-level categories for product types you carry fewer than 20 products in.

How do you handle unisex products in a fashion product taxonomy?

Set gender = unisex in the product attributes and assign the product to the most appropriate department based on primary customer intent. For products genuinely sold to both genders, use gender = unisex in your Google Shopping feed and surface them in both Men's and Women's navigation via tags or multi-category assignment, depending on your platform.

Which size system should I use in my Google Shopping apparel feed?

Use the size_system attribute to declare your regional size standard: AU, BR, CN, DE, EU, FR, IT, JP, MEX, UK, or US. This is especially important for international catalogs where a size 10 means different things in different regions.

Tag: Apparel

Product Taxonomy for Fashion Ecommerce: The Complete Industry Guide

Fashion is the most complex product taxonomy challenge in ecommerce. No other category has the same combination of variant depth (size × colour × material), seasonal rotation, brand complexity, and the need to align with both customer search language and Google’s own category hierarchy simultaneously.

This guide covers how to structure a fashion taxonomy that works for site navigation, Google Shopping, and internal catalog operations at the same time.

Why Fashion Taxonomy Is Uniquely Difficult

High variant depth: A single jacket style can generate 40+ variants (4 colours × 5 sizes × 2 materials). Each needs proper categorisation.
Seasonal rotation: Categories like “Summer Dresses” need to exist, disappear, and reappear without breaking your taxonomy structure.
Cross-gender categorisation: Unisex products that appear in both Men’s and Women’s categories require clear rules.
Trend-driven additions: New product types appear faster in fashion than almost any other category — your taxonomy needs to accommodate them without restructuring.

For the full taxonomy build process that applies to all industries before you get into fashion-specific requirements, see How to Build a Product Taxonomy From Scratch.

Recommended Top-Level Structure for Fashion

Level 1 (Department)	Level 2 Examples (Category)	Level 3 Examples (Subcategory)
Women’s Clothing	Dresses, Tops, Bottoms, Outerwear, Knitwear	Midi Dresses, Wrap Dresses, Formal Dresses
Men’s Clothing	Shirts, Trousers, Jackets, Knitwear, Activewear	Casual Shirts, Formal Shirts, Linen Shirts
Kids’ Clothing	Girls’ Clothing, Boys’ Clothing, Baby & Toddler	School Uniforms, Outerwear, Swimwear
Footwear	Women’s Shoes, Men’s Shoes, Kids’ Shoes	Heels, Flats, Boots, Trainers, Sandals
Accessories	Bags, Belts, Scarves, Hats, Jewellery	Handbags, Crossbody Bags, Tote Bags
Swimwear	Women’s Swimwear, Men’s Swimwear	Bikinis, One-pieces, Board Shorts
Lingerie & Nightwear	Bras, Underwear, Nightwear, Shapewear	Padded Bras, Sports Bras, Balcony Bras

Attribute Sets by Fashion Subcategory

Each subcategory needs a defined attribute set. Below are the recommended required and optional attributes for key fashion categories.

Outerwear (Jackets, Coats, Gilets)

Required: Brand, Colour, Size, Material, Gender, Age Group
Recommended: Waterproof (yes/no), Insulation type, Fill power, Packable (yes/no), Season
Google category: Apparel & Accessories > Clothing > Outerwear > Coats & Jackets

Women’s Dresses

Required: Brand, Colour, Size, Neckline, Length, Occasion
Recommended: Pattern, Sleeve length, Care instructions, Season
Google category: Apparel & Accessories > Clothing > Dresses

Footwear

Required: Brand, Colour, Size, Size system, Gender, Heel height (where applicable)
Recommended: Material (upper), Sole material, Closure type, Occasion, Width
Google category: Apparel & Accessories > Shoes > [specific shoe type]

For the full list of apparel attributes required by Google Shopping feeds, see the Google Shopping Apparel Requirements guide.

Managing Colour in a Fashion Taxonomy

Colour management is where fashion taxonomy most often breaks down. Fashion brands use marketing colour names (“Dusty Rose”, “Storm Blue”) that are meaningful to buyers but problematic for Google Shopping and site search filtering.

The solution is a two-field colour approach:

Marketing colour name: Used in product titles and descriptions facing customers — “Storm Blue Puffer Jacket”
Normalised colour value: Used for feed submission and filter attributes — “Blue”. This maps to Google’s accepted colour values and makes site filters work correctly (“Filter by: Blue, Green, Red”).

Without normalised colour values, your “Navy”, “Dark Navy”, “Midnight Navy”, and “Storm Blue” all appear as separate filter options rather than grouping under “Blue”. Customers cannot find what they are looking for and conversion on filtered searches drops.

Size Management and International Sizing

Fashion brands selling internationally face size system conflicts. A UK 10 dress and a US 10 dress are different sizes. A European 40 and a US 8 are the same women’s dress size. Declare your size system in every product record using the size_system attribute.

For brands selling across regions from a single catalog, the cleanest solution is to store size in your primary size system and maintain a size conversion reference table as a documented data standard — not as additional product fields that will create mapping errors when updated.

Seasonal Category Management

Fashion taxonomy needs seasonal flexibility without permanent structural changes. Two approaches work well:

Season as an attribute, not a category: Keep “Summer Dresses” as a filter value (season = Summer) rather than a permanent subcategory. This prevents your taxonomy from accumulating dead branches as seasons pass.

Evergreen subcategories with seasonal tags: “Dresses” is the permanent subcategory. “Summer” is a tag or attribute. Products appear in the Dresses subcategory year-round; the Summer filter surfaces them seasonally. This is the more scalable approach for catalogs with high seasonal turnover.

Mapping Fashion Taxonomy to Google Product Categories

Every fashion subcategory needs a Google product category mapping. Use Google’s leaf-node values (the most specific level) for best Shopping performance. The mapping should be documented and applied consistently — not manually re-entered per product.

The difference between flat and hierarchical taxonomy structures for fashion is covered in detail in the Flat vs Hierarchical Taxonomy guide — worth reading before finalising your structure.

Once your fashion taxonomy is structured correctly, implementing it at scale requires a system that can enforce attribute validation and apply category-level rules automatically. The PIM Readiness Score takes 5 minutes and shows you where your current product data setup has gaps.

Download the free Product Taxonomy Template at lynkpim.app — the Fashion & Apparel tab includes the full category hierarchy, attribute set, and Google mapping pre-built for clothing, footwear, and accessories.

Frequently Asked Questions

How should fashion ecommerce handle seasonal categories in a product taxonomy?

Use season as an attribute rather than a permanent category. Keep “Dresses” as the permanent subcategory and assign season = Summer as a tag or attribute value. This prevents the taxonomy from accumulating obsolete branches (Summer Dresses 2024, Summer Dresses 2025) that clog navigation and require ongoing cleanup.

What is the two-field colour approach for fashion product data?

Store two colour values per product: a marketing colour name for customer-facing content (Dusty Rose, Storm Blue) and a normalised colour value for feed submission and site filters (Pink, Blue). Without normalised values, multiple shades of the same colour appear as separate filter options — “Navy”, “Dark Navy”, “Midnight Navy” become three separate filter choices instead of one “Blue” group.

How many top-level categories should a fashion taxonomy have?

Most fashion stores work well with 6 to 8 top-level departments: Women’s Clothing, Men’s Clothing, Kids’ Clothing, Footwear, Accessories, Swimwear, and Lingerie & Nightwear. Avoid creating top-level categories for product types you carry fewer than 20 products in — use attributes and filters instead.

How do you handle unisex products in a fashion taxonomy?

Set gender = unisex in the product attributes and assign the product to the most appropriate department based on primary customer intent. For your Google Shopping feed, use gender = unisex and surface products in both Men’s and Women’s navigation via tags or multi-category assignment depending on your platform.

What Google product category should I use for women’s dresses?

Use the leaf-node value: Apparel & Accessories > Clothing > Dresses. Avoid the parent category Apparel & Accessories > Clothing — the more specific your Google product category, the better your Shopping feed relevance. For formal dresses, go one level deeper if possible.

April 27, 2026

Google Shopping Feed for Apparel: All Requirements Explained (2026)

Apparel is the most attribute-heavy category in Google Shopping. Miss a required field and your products either disapprove or lose out in auctions to competitors whose feeds are complete. This guide covers every attribute Google requires or strongly recommends for clothing, footwear, and accessories — with the exact values and format Google expects.

Why Apparel Feeds Are Different

Google’s feed requirements for apparel go beyond the standard required attributes that apply to all products. Clothing and shoes have mandatory variant attributes, specific size system declarations, and stricter image requirements. A feed that works fine for non-apparel will generate warnings and limited performance for clothing.

For a full foundation on how Shopping feeds work, the Google Shopping Feed Guide covers the base layer before you add apparel-specific requirements on top.

Required Attributes for All Apparel Products

Attribute	Required?	Notes
id	Yes	Unique per variant, not per style
title	Yes	Include colour, size, material in title
description	Yes	150+ characters recommended
link	Yes	Must land on the specific variant page
image_link	Yes	800×800px minimum, no overlays
price	Yes	Must match landing page exactly
availability	Yes	in stock / out of stock / preorder
google_product_category	Yes	Use specific leaf node, not parent category
brand	Yes	Required for all apparel
item_group_id	Required for variants	Same value for all variants of one style
color	Required for variants	Up to 3 values separated by /
size	Required for variants	One value per product
age_group	Required for variants	adult / kids / newborn / infant / toddler
gender	Required for variants	male / female / unisex

item_group_id — The Most Important Apparel Attribute

If you only fix one thing in your apparel feed, fix item_group_id. This attribute tells Google which products are variants of the same style. Without it, Google treats a navy size S jacket and a navy size L jacket as two completely unrelated products — and cannot display them as one listing with size options.

The rule: every size, colour, and material variant of the same product must share the same item_group_id value. The parent SKU is the natural choice — if your base product code is JK-2401, all variants carry JK-2401 in item_group_id regardless of their individual IDs.

For GTIN compliance per variant, see the GTIN requirements guide — each variant needs its own valid GTIN in apparel.

Colour Requirements

Colour values must be descriptive and human-readable. Google rejects values that are not recognisable colour names.

Acceptable: Navy, Coral, Charcoal, Slate Blue, Off White
Not acceptable: #003366, Color-4, 01, N/A
Multi-colour: Separate up to 3 values with a forward slash — Navy/White/Red
Maximum length: 100 characters per colour value

Size Requirements and Size Systems

Size values should reflect the labelled size on the product, not a numeric internal code. Use the size_system and size_type attributes to add context to your size values.

size_system

Declares which regional size standard you are using. Accepted values include: AU, BR, CN, DE, EU, FR, IT, JP, MEX, UK, US. This matters for international catalogs — a “10” in US women’s shoes is not the same as a “10” in UK shoes.

size_type

Describes the cut: regular, petite, plus, tall, big, maternity. Use this when your sizing differs from standard. It helps Google match your products to queries like “plus size summer dress”.

Image Requirements for Apparel

Apparel has stricter image rules than other categories because product appearance drives click decisions more directly.

Minimum 800×800px — 1000×1000px or larger recommended for Shopping ads
White or neutral background strongly preferred
No watermarks, promotional text, or overlays of any kind
The image must show the specific colour variant — do not use one image for all colour variants
Use additional_image_link (up to 10 images) — alternate angles, flat lay, and detail shots all improve CTR

Google Product Category for Apparel — Go Deep

Broad category values are one of the most common apparel feed mistakes. “Apparel & Accessories” as a category value is almost useless for relevance. Google’s taxonomy goes 5–7 levels deep for clothing and footwear — use the deepest applicable level.

Product	Lazy (Wrong)	Correct
Women’s running jacket	Apparel & Accessories	Apparel & Accessories > Clothing > Activewear > Track Jackets & Hoodies
Men’s leather Oxford shoes	Apparel & Accessories > Shoes	Apparel & Accessories > Shoes > Men’s Shoes > Oxfords
Girls’ school uniform skirt	Apparel & Accessories > Clothing	Apparel & Accessories > Clothing > Skirts

Title Formula for Apparel Products

Google matches your title against search queries. For apparel, the title is the single highest-impact attribute for relevance. Use this formula:

Brand + Gender + Material/Attribute + Product Type + Colour + Size

Example: Columbia Women’s Waterproof Softshell Jacket Navy Size 12

For seasonal products, add the season before the product type: Columbia Women’s Summer Lightweight Running Jacket Coral Size 10

Before You Submit — Validate Your Feed

Apparel feeds have the highest disapproval rates of any Shopping category because of the variant attribute requirements. Before submitting, check:

Every variant has a valid GTIN — use the GTIN Validator to check in bulk
All variants of the same style share the same item_group_id
Colour values are human-readable, not codes or hex values
Size values are declared with size_system if selling internationally
Images are per-colour-variant, not one image reused for all variants

Managing apparel variant data at scale — especially across multiple channels — is where spreadsheet-based approaches break down. Learn how LynkPIM handles variant management without the manual overhead. For campaign performance after your feed is clean, see how to use custom labels for bid segmentation.

Frequently Asked Questions

Is GTIN required for all apparel products?

Yes, for products that have manufacturer-assigned GTINs. Custom or handmade products with no GTIN should set identifier_exists to FALSE in the feed — do not leave GTIN blank without this declaration or you will receive a Limited Performance warning.

Do I need separate products for each size and colour?

Yes. Each unique size/colour/material combination is a separate product in your feed with its own ID. They are linked back to the parent style via item_group_id.

Can I use the same image for different colour variants?

Technically Google will not always disapprove this, but it will hurt your CTR significantly and may trigger a mismatched colour warning. Use colour-specific images wherever possible.

April 27, 2026