When a single apparel item group contains variants aimed at different genders—think a unisex hoodie line that also ships in a cut explicitly sized for women—catalog operators often ask the same question: does every row in the feed need its own gender value, or is one value at the "parent" level enough? The short answer is that Google's product data specification has no concept of a parent row. Every submitted variant is a standalone product, and each one carries its own attribute values, including gender.

Every Variant Is a Separate Product Row

Google Merchant Center does not accept a hierarchical parent–child feed structure where a parent row sets default attribute values that child rows inherit. When you submit apparel variants, Google documentation requires you to "Submit each variant as a separate product" and use the same item_group_id value across all of them to signal that they belong together. That grouping mechanism is item_group_id; it does not make one row's attributes apply to another.

This means if your item group includes a men's size-M jacket and a women's size-M jacket, each of those rows must carry its own gender value. There is no inheritance, fallback, or default from a notional parent. If you omit gender from one row, that row is missing the attribute entirely.

The item_group_id attribute also comes with a strict uniqueness rule. Google documentation states that you should "use the same value for the item group ID [item_group_id] attribute for all variants of the same product" and that "each distinct item group must have a unique value." This keeps your men's and women's variants correctly associated while remaining distinct products in the catalog.

When Gender Becomes a Variant-Identifying Property

Most apparel item groups vary by size and color, with gender fixed across the whole group—for example, a women's blouse line that only comes in women's sizing. In that case every row shares the same gender value (female), and the attribute is still required on each individual row even though it never changes.

The more complex scenario is when gender is itself the differentiating axis—for example, a base-layer T-shirt sold in both men's and women's cuts under a single brand SKU family. Here gender is a variant-identifying property alongside size. The item group documentation lists gender explicitly among the standard variant attributes that should be specified per row: "Use all standard variants: Specify the standard color [color], pattern [pattern], material [material], age group [age_group], gender [gender] and size [size] attributes in addition to variant option [variant_option] even when these are part of the set of variant-identifying properties."

In practical terms this means:

  • If gender varies across variants, every row gets the value that applies to that specific variant.
  • If gender is constant across the group, every row still gets that same value—you do not omit it just because it is uniform.

Size and Gender Work Together at the Variant Level

Size and gender are closely linked for apparel. Google documentation specifies: "For apparel products, use this attribute when your product is a variant that is distinguished by its size. For example, use 'S' as the value for a 'small red T-shirt' and use 'L' as the value for a 'large red T-shirt'. Also submit each variant as a separate product with the same value for the item group ID [item_group_id] attribute."

Sizing systems also differ by gender in some markets and categories. A US women's coat size 12 and a US men's coat size 12 reference different physical dimensions. When gender varies across your item group, using item-level gender values alongside item-level size values ensures the correct size system is interpretable for each row. Submitting a single gender at the group level—which is structurally impossible anyway—would leave this ambiguity unresolved.

One more constraint worth noting from the size attribute requirements: Google documentation states "Submit only one attribute per product. If you provide multiple size attributes for the same product, only the first will be applied." The same logic applies generally—each row is treated as one product, and attributes on that row describe that product only.

Hypothetical Example: A Base-Layer T-Shirt With Mixed-Gender Variants

The following is a hypothetical example for illustration only.

Imagine a brand called Ridgeline Apparel (fictional) that sells a thermal base-layer T-shirt under a single internal SKU family RL-BASE-01. The shirt comes in:

  • Men's: S, M, L, XL
  • Women's: XS, S, M, L

All eight rows share item_group_id = RL-BASE-01. The feed rows might look like this:

iditem_group_idgendersize
RL-BASE-01-M-SRL-BASE-01maleS
RL-BASE-01-M-MRL-BASE-01maleM
RL-BASE-01-M-LRL-BASE-01maleL
RL-BASE-01-M-XLRL-BASE-01maleXL
RL-BASE-01-W-XSRL-BASE-01femaleXS
RL-BASE-01-W-SRL-BASE-01femaleS
RL-BASE-01-W-MRL-BASE-01femaleM
RL-BASE-01-W-LRL-BASE-01femaleL

Note that two rows share size = S within the same item group, but they have different id values and different gender values. Each row is a distinct product. The item_group_id tells Google these eight rows belong together; the per-row gender and size values describe what each individual variant actually is.

If the catalog operator had omitted gender from the women's rows and left it only on the men's rows, those women's rows would be missing a required attribute for apparel. This is a common source of Merchant Center disapprovals for mixed-gender item groups.

Aligning Your Feed Structure With Landing Page Experience

Attribute accuracy at the variant level has a secondary requirement: your landing page must match what you submit. Google requires that you "make sure the product details displayed on your landing page match the variant-identifying values you provide for the variant like title [title], variant option [variant_option], color [color], price [price], availability [availability], and image link [image_link]."

If your Shopify or WooCommerce store uses a single product page where shoppers select gender, size, and color from dropdowns, each variant should have a unique URL that pre-selects (or at minimum identifies) that specific combination. Submitting distinct id and URL values per variant row, as illustrated in the hypothetical above, satisfies this alignment requirement and helps Google correctly associate each feed row with the right landing page state.

Practical Checklist for Mixed-Gender Item Groups

  • Assign a unique id to every variant row—do not reuse IDs across men's and women's cuts.
  • Set item_group_id to the same value across all variants in the group.
  • Set gender on every row individually: male, female, or unisex as appropriate.
  • Set size on every row using a value appropriate for the target country and category.
  • Confirm each row's URL resolves to a landing page that matches that variant's attributes.
  • Review Merchant Center Diagnostics after uploading; disapprovals tied to gender on only a subset of rows within a group are a signal that some rows are missing the attribute.

Managing these per-row attribute requirements across a large catalog is where feed tooling pays off. Magicfeedpro is built to handle exactly this kind of item-level attribute mapping—keeping gender, size, and item_group_id consistent across every variant row without manual row-by-row edits.


MagicFeedPro Team

Feed Optimization Practitioners

We're a team of e-commerce and paid-search practitioners who have spent the last decade running Google Shopping campaigns at scale. We write about what actually moves the needle on product feed quality, CTR, and conversion.

Related articles