The [size] attribute might seem like a small detail, but in Google Merchant Center, it carries a lot of weight. When size data is missing, inconsistent, or formatted incorrectly, it can limit visibility, break variant logic, or lead to outright disapprovals.
More importantly, size impacts how your products appear when shoppers filter by size, and how Google groups and displays your variants. If size isn’t clean, your Shopping performance won’t be either.
Let’s break down how to fix it, and how to prevent issues going forward.
What the [size] Attribute Does
The [size] attribute is used to describe the standardized size of your product. When submitted correctly:
- Your products can appear in size-filtered search results
- Variants are displayed properly within a single product group
- Google can accurately match your products to shopper intent
This attribute directly affects both visibility and user experience.
When the [Size] Attribute Is Required
Size is required in the following cases:
Free Listings
- Apparel & Accessories > Clothing (ID 1604)
- Apparel & Accessories > Shoes (ID 187)
Shopping Ads (Required When Targeting These Countries)
- Brazil
- France
- Germany
- Japan
- United Kingdom
- United States
If you’re advertising apparel or shoes in these regions, size is not optional.
For countries within the EU and regions like Australia, the requirements may also vary. Always consult the Google Merchant Center help documentation for the specific sizes needed for images and data feeds in each country you are targeting.
Minimum Requirements You Must Meet
If you don’t follow these rules, Google will disapprove the product.
Here’s what Google expects:
- Use a standard size value for your target country
- Submit only one size value per product
- If multiple size attributes are submitted, only the first is used
- Submit only the size value
- Don’t use “n/a,” “none,” or “multisize”
- Submit non-size details using the correct attributes:
- [color], [material], [pattern], etc.
- Submit size for all products that vary by size
- Each size variant must:
- Be submitted as a separate product
- Share the same item_group_id
- Don’t separate multiple sizes with commas
- Use slashes instead (e.g., S/M/L, not S, M, L)
- For products with multiple dimensions, condense them into one size value
- Example: 16/34 for neck/sleeve measurements
- For non-apparel products, submit the most relevant size when applicable
Step-by-Step: How to Fix Size Issues
Step 1: Find the Error
Go to Products → Diagnostics in Google Merchant Center and click into the [size] issue. Google will show you exactly which products are affected and why.
Step 2: Confirm the Category Is Correct
Many size errors are caused by misclassification.
If a product is categorized as apparel or shoes, size is required, even if the item is “one size.” Make sure the category truly matches the product.
Step 3: Clean Up Your Size Values
Your size values should:
- Match what’s shown on the product page
- Use consistent formatting
- Contain only size information
Good examples:
- S, M, L
- 8, 10.5
- 38 regular
Bad examples:
- Medium – In Stock
- Size 10 (Ships Today)
- One Size Fits All (when multiple sizes exist)
Step 4: Validate Variant Structure
Each size must:
- Have a unique product ID
- Share the same item_group_id
- Use the correct size value for that specific variant
This tells Google these products are variations – not duplicates.
Size Formatting by Product Type
Shoes
You can submit a numeric size plus width.
Width abbreviations: XXN, XN, N, M, W, XW, XXW
Letter widths: 4A, 3A, 2A, A, B, C, D, E, 2E–6E
Examples
- 6 XN
- 10.5 C
- 11.5 W
Pants
Submit a numeric size plus length descriptor.
Examples
- 38 regular
- 42 short
- 12 long
Underwear & Swimwear
Include cup measurements when applicable.
Examples
- 32 B
- 38 DD
- 30 AA
Sporting Goods
For left- or right-hand–dependent products, include hand orientation like golf clubs or baseball mitts.
Examples
- 10.5–11.25”/LH
Baby & Toddler (US Only)
Use numeric sizing plus age descriptors.
Examples
- Preemie
- Newborn
Best Practices That Improve Performance
Once you meet the minimum requirements, optimization matters.
- Use values shoppers understand – these can appear publicly
- Keep size formatting consistent across all variants
- Use:
- [size_type] for fit or cut
- [size_system] for country sizing conventions
- Submit the complete size
- If shoes come in widths, include width in the size value
- For multipacks, use the [multipack] attribute
- Never include quantity in the size field
[size] attribute issues are one of the most common, and most fixable, Merchant Center problems. Clean size data improves approvals, ensures proper variant display, and helps your products reach the right shoppers at the right time.
Google Shopping can get complicated. If you need assistance, reach out to us. We’d love to help!