Google Shopping Size Attribute: Requirements, Size Systems & Best Practices

What is the size attribute?

The size attribute tells Google the size of an apparel or accessory product. It is one of three primary variant attributes for clothing and footwear — alongside color and material — and it directly determines whether your products appear in Google Shopping’s size filter, one of the most-used filters in the Apparel category.

When submitted correctly, size data allows Google to build a variant selector on Shopping product cards, showing available sizes at a glance. More importantly, it prevents you from wasting budget showing ads — or appearing in free listings — to shoppers who would only be disappointed to discover their size is unavailable. Accurate size data means better-qualified traffic and fewer abandoned sessions.

Technical specifications

Where it displays

• Shopping Ads — Google displays a variant selector on product cards when multiple products share the same item_group_id. Shoppers see available sizes and can select their size before clicking — reducing bounce rate on PDPs. The size filter in the Shopping panel also relies entirely on this attribute.

• Free Listings (Shopping Tab) — Free Listings include a size filter that is used by a large proportion of apparel shoppers. Products without size are filtered out when shoppers refine by size — they simply don’t appear. Accurate size data is non-negotiable for free listing coverage.

• Dynamic Remarketing — Google’s Display & Remarketing system uses size to show users the specific size variant they interacted with. If someone added a Size L hoodie to their cart, the remarketing ad will feature the L variant, not a generic product image. This one-to-one matching requires per-size product entries with correct size values.

Rules

• One size per product — Submit one size value per product entry. If you offer S, M, and L, submit three separate products with the same item_group_id.

• Declare the size system — Always pair size with size_system (e.g., EU, US, UK). Without it, Google may misinterpret your values for international shoppers.

• One size fits all — If the product genuinely has no size variation (e.g., a belt, a hat), submit one size as the value. Do not leave the attribute empty.

• Must match the product — The size must accurately reflect the product available at the linked URL. Listing a product as “L” when the landing page shows it is out of stock in L will cause policy violations.

• No promotional text — Do not add text like “XL — Free Shipping” to the size field. The field is for size data only.

• Apparel category is strictly enforced — Missing size for apparel products in major markets will trigger disapprovals. This is one of the most actively enforced attribute requirements.

Best practices

Size system selection

Choose the size system that matches your target market. Use the size_system attribute to declare it:

• EU — Continental Europe (DE, FR, IT, NL, ES, CZ, PL, etc.) — numeric sizing (36, 38, 40…)

• US — United States (XS, S, M, L, XL or numeric for shoes)

• UK — United Kingdom (numeric for shoes: 6, 7, 8; S/M/L for clothing)

• JP, FR, IT, AU, CN, BR, MEX — Country-specific systems

Footwear sizing

For shoes, always submit the numeric size in the appropriate system: 42 (EU), UK 8, US 9. Avoid vague labels like “large” for footwear — shoppers search for exact shoe sizes and the filter will not match imprecise values.

Use size_type for extended sizing

If you carry petite, plus, tall, or maternity sizes, use size_type (petite, plus, tall, maternity). This unlocks query coverage for searches like “plus size women’s blazer” and “maternity jeans UK” — queries that size alone cannot match.

Include size in the product title

For variant-level titles, append the size at the end: Nike Air Max 90 Men’s Sneakers — Black — EU 44. This makes the title more relevant to size-specific searches and helps Ad Relevance scoring.

Impact on performance

• Size filter visibility — Apparel products without size are excluded from size-filtered Shopping results. For categories like shoes, dresses, and jeans where shoppers almost always filter by size, missing this attribute can reduce impressions by 60–80%.

• Ad relevance — Accurate size data improves the alignment between searcher intent and your product, which is a factor in Google’s ad relevance scoring and Quality Score for Shopping.

• Bounce rate reduction — Variant selectors on Shopping cards let shoppers choose their size before clicking. Shoppers who land on your PDP already knowing their size is available are far less likely to bounce immediately.

• Dynamic Remarketing ROAS — Size-accurate remarketing ads showing the exact size the user viewed deliver significantly higher click-through and conversion rates than generic product ads. Brands using per-variant size data in remarketing typically see 20–35% higher ROAS on Display.

Common mistakes

• Submitting all sizes in one product — E.g., size: "S, M, L, XL" in a single product entry. Google will not split these into variants. Each size must be its own product.

• Missing size_system — Submitting size 38 without declaring whether it’s EU, UK, or another system. Google may display it incorrectly or misclassify the product.

• Size mismatch with landing page — Showing a size as available when it’s OOS on the product page. This leads to negative user experience, higher bounce, and potential policy warnings.

• Inconsistent size naming across products — Using M for some products and Medium for others. Pick one convention and apply it consistently across your feed.

• Not updating availability per variant — If Size S goes out of stock, set availability: out_of_stock for the S product specifically. Do not keep all variants as “in stock” when some sizes are unavailable.

• Omitting one size fits all value — Leaving size blank for accessories (scarves, hats, belts) that genuinely have no size. These need one size to satisfy the requirement.

Pro tips

• Map size data at the variant level in your PIM/feed tool — The cleanest implementation is to have your product information management system or feed management tool (Mergado, DataFeedWatch, Channable) generate one feed row per SKU. Each SKU is one size-colour combination. This avoids manual variant splitting downstream.

• Use supplemental feeds to update size availability fast — Primary feeds refresh once per day. Supplemental feeds can update every 15-20 minutes. When a size sells out, a supplemental feed push of id + availability updates GMC in near-real time — preventing ads from running on OOS sizes and wasting budget.

• Segment campaigns by size tier for footwear — In shoes, popular sizes (EU 40-44 for men, 36-40 for women) have much higher search volume and competition than extreme sizes. Segmenting by size in your campaign structure lets you bid higher on popular sizes and lower on niche sizes for better ROAS efficiency.

• Test size in title vs. omitting it — For some categories, Google may prefer shorter titles without size for the Shopping card headline, but longer, size-specific titles for query matching. Run an A/B test via feed rules: half your products with size in title, half without — and compare CTR and conversion rate over 4 weeks.