Gender

Gender is the product feed attribute that states which shopper demographic an item is designed for, submitted through the g:gender tag in XML or a gender column in a CSV feed to Google Shopping and Meta Catalog. It accepts a fixed set of values rather than free text — male, female, or unisex — which makes it stricter than most of the other variant-related fields and easier to get definitively wrong. Apparel, footwear, and accessories retailers rely on it both to power the gender-based navigation shoppers expect and to keep unisex product lines from being miscategorized as one gender or the other.

Why it matters

Google Merchant Center requires gender for items in the Apparel & Accessories category, and getting it wrong doesn't just risk a policy flag — it actively misdirects the ad. A men's boot listed with the wrong gender value can surface in search results and dynamic ads targeted at women, producing clicks that convert poorly and skew performance data toward a segment that was never going to buy it. Gender is also one of the attributes Google recognizes for grouping variants under a shared item_group_id, so a single "Classic Hoodie" sold in men's and women's cuts can be linked as one listing with two gender-specific options, provided the value is set correctly and consistently on both rows.

How it works

The accepted values are limited to male, female, and unisex — no other terms are recognized, so anything else risks the field being ignored or the item being flagged. Gender pairs naturally with age_group and size on apparel items, and Google explicitly lists gender among the fields, alongside color, material, pattern, size, and age group, that a retailer may use as the basis for a product variant group. Because the value set is so constrained, gender is usually the easiest of the variant attributes to validate automatically — a feed rule that rejects anything outside the three accepted values catches most errors before they ever reach a channel.

Example

<item>
  <g:id>HOOD-3390-M</g:id>
  <title>Classic Fleece Hoodie - Men's, L</title>
  <link>https://example-shop.com/products/classic-hoodie-mens-l</link>
  <g:item_group_id>HOOD-3390</g:item_group_id>
  <g:gender>male</g:gender>
  <g:size>L</g:size>
  <g:price>58.00 USD</g:price>
  <g:availability>in stock</g:availability>
</item>
<item>
  <g:id>HOOD-3390-W</g:id>
  <title>Classic Fleece Hoodie - Women's, M</title>
  <link>https://example-shop.com/products/classic-hoodie-womens-m</link>
  <g:item_group_id>HOOD-3390</g:item_group_id>
  <g:gender>female</g:gender>
  <g:size>M</g:size>
  <g:price>58.00 USD</g:price>
  <g:availability>in stock</g:availability>
</item>

The two cuts share an item_group_id but carry opposite gender values and different size labels, since the men's and women's versions of this hoodie use separate sizing scales entirely.

Related Concepts

Gender is almost always evaluated together with age group, since together they define who a product is actually for, and it frequently varies alongside size when men's and women's cuts use different sizing conventions. Getting all three right also depends on accurate placement within Google Product Category, since gender and age group requirements are triggered specifically by which apparel or accessories category an item falls into.