Specify the gender your product is designed for using the gender [gender] attribute. When you provide this information, potential customers can accurately filter products by gender to help narrow their search. Keep in mind that we use the gender information together with the values you provide for the size [size] and age group [age_group] attributes to standardize the sizes that are shown to users.
On this page
When to use
Apparel & Accessories (ID 166) products.
Apparel & Accessories (ID 166) products when targeting these countries:
- Brazil
- France
- Germany
- Japan
- United Kingdom
- United States
Apparel & Accessories sub-categories:
Pinback Buttons(ID4179)Tie Clips(ID180)Wristbands(ID1893)Shoe Covers(ID5385)Shoelaces(ID1856)Spurs(ID2427)Watch Bands(ID5123)Keychains(ID175)Wallet Chains(ID5841)Lanyards(ID6277)Checkbook Covers(ID6460)Badge & Pass Holders(ID6170)Watch Winders(ID6870)Watch Stickers & Decals(ID7471)Handkerchiefs(ID5207)Decorative Fans(ID5114)
If your product varies by gender, submit the gender [gender] attribute. Use this attribute when your product is a variant that is distinguished by its gender (for example, "mens black tennis shoes" and "womens black tennis shoes"), and also submit each variant with the same value for the item group ID [item_group_id]attribute.
Format
Follow these formatting guidelines to make sure Google understands the data you're submitting. Learn when and how to submit your product data in English.
| Formatting specifications | |
|---|---|
| Technical name | gender |
| Supported values |
Note these values must be submitted in English. |
| Repeated field | No |
| Schema.org property (What’s this?) |
Product.audience.suggestedGender, Type: Text |
File format examples
To ensure your attribute is recognized correctly, use the formatting specific to your data source type.
| Data source format | Examples |
|---|---|
| Text data sources | male |
| XML data sources | <g:gender>male</g:gender> |
| Merchant API | To format your data for Merchant API, check the Merchant API resource. |
Minimum requirements
There are no minimum requirements for this attribute. Keep in mind that you still need to follow the formatting guidelines or the information you submit can't be used.
Best practice
This best practice can help you go beyond the basic requirements to optimize your product data for performance.
- If gender is a variant-identifying property, then we recommend you provide it using both the variant option
[variant_option]attribute and the gender[gender]attribute. Providing both attributes will help our systems better understand your products and variants.
Examples
Apparel products| Product data for Google logo T-shirt, unisex, size medium | |
| Attribute | Value |
Gender [gender] |
unisex |
Size [size] |
M |
Size system [size_system] |
US |
Size type [size_type] |
regular |
| Product data for mens running shoes, size 8.5 | |
| Attribute | Value |
Gender [gender] |
male |
Size [size] |
8.5 |
Size system [size_system] |
US |
Size type [size_type] |
regular |
Note: Gender is relevant for most apparel products. To help show your product for the most relevant searches, you can also include the size [size], size system [size_system], and size type [size_type] attributes.
| Product data for a men’s Android smartwatch, gold | |
| Attribute | Value |
Title [title] |
Men’s Android Smartwatch - Gold |
Gender [gender] |
male |
Material [material] |
Gold |
ID [id] |
9856-m-gld |
Item group ID [item_group_id] |
12345 |
| Product data for a women’s Android smartwatch, gold | |
| Attribute | Value |
Title [title] |
Women’s Android Smartwatch - Gold |
Gender [gender] |
female |
Material [material] |
Gold |
ID [id] |
9856-w-gld |
Item group ID [item_group_id] |
12345 |
Note: If your product comes in different versions for each gender, submit the gender for each variant.
