Missing Size
Your apparel product doesn't have a size attribute in the feed. Size is the most critical filter dimension in apparel shopping — a shopper searching for 'women's blazer size 8' or 'men's running shoes size 12' uses size as their primary filter. Without it, your product can't appear in size-filtered results, which represent the majority of high-intent apparel purchase searches.
Missing value [size]Impact: Size is a required attribute for all clothing products (tops, bottoms, outerwear, footwear, and most apparel subcategories). Products without size are disapproved for Shopping ads and excluded from size-filtered searches — the primary way shoppers browse apparel.
Root Causes
- 1Your feed template maps only the parent product, not individual size variants — all sizes are collapsed into one row with no size value.
- 2Size values are stored in Shopify's variant 'Size' option but the feed app is configured to pull a different option, or is in 'single product per SKU' mode instead of 'one row per variant' mode.
- 3Products were added without the Size option because the merchant intended to add it later, but the products went live in the feed without it.
- 4International size formats are causing the field to be blank — the size in the feed is '38 EU' but your feed plugin isn't handling the unit correctly.
- 5Products that are 'one size fits all' are submitted without any size value — these should use 'One Size' as the size value.
Fix by Platform
- 1In your feed app (Simprosys, AdNabu, DataFeedWatch), map the 'size' attribute to 'Option: Size'. This pulls the size from each variant's Size option.
- 2Ensure your feed app is submitting one feed row per variant (not one row per product). Each size variant needs its own row with its own ID (typically ParentID-VariantID format).
- 3For 'One Size' products: add a Size option with value 'One Size' to those products in Shopify Admin → Products → [Product] → Options → Add option → Size → One Size.
- 4Verify the option is named exactly 'Size' — if it's named 'Sizing', 'Shoe Size', or 'Dress Size', either rename it or adjust the feed app's option mapping.
- 5For numeric sizes without units: Google accepts bare numbers ('8', '10', '12') or formatted sizes ('XS', 'S', 'M', 'L', 'XL', 'XXL'). Both formats are valid.
{% for option in variant.options %}
{% if product.options[forloop.index0] == 'Size' %}
{{ option }}
{% endif %}
{% endfor %}When This Doesn't Apply
Check your store now
Free compliance scan — 47 rules checked in minutes.
Frequently Asked Questions
What size format does Google accept?+
Google accepts any standard size format appropriate for your product type: alphabetic (XS, S, M, L, XL, XXL), numeric (6, 8, 10, 12), shoe sizes (7, 7.5, 8), EU sizes (36, 38, 40), or text ('One Size', 'Free Size'). The size system (US, EU, UK) can be specified separately via the size_system attribute. Avoid proprietary size codes that shoppers wouldn't recognize.
Do I need the size_system attribute along with size?+
size_system is optional but recommended for international stores. It tells Google which sizing convention you're using (US, UK, EU, IT, FR, DE, JP, CN, AU, BR). Without it, Google assumes your default market's sizing system. If you sell across multiple regions with different size conventions, submitting size_system prevents your EU size 38 from being misinterpreted as a US size 38.
My product is 'one size fits all'. What do I enter?+
Use the value 'One Size'. This is the correct way to tell Google the product has no distinct sizing. Don't leave the field empty or use 'N/A', 'None', or 'Universal' — only 'One Size' is recognized as a valid size-exempt value.
I have 8 size variants. Does each need its own image?+
Not necessarily — you can use the same image URL for all size variants of the same color. But each size variant still needs its own feed row with a unique item ID, the shared item_group_id, and its specific size value. Only color variants typically require different images (showing each specific color).