Attribute Guide
size_type Attribute in Google Shopping: Regular, Plus, Petite & Maternity Guide
Complete guide to the size_type attribute in Google Merchant Center. All valid values, the difference from the size attribute, plus/petite/maternity filter…
Curve Fit Maxi Dress — Sizes 18–28
Appears in "Plus" filter → reaches exactly the shoppers looking for plus-size options → higher purchase intent match
Curve Fit Maxi Dress — Sizes 18–28
Product is plus-size but tagged "regular" → invisible to every shopper using the "Plus" filter → missing an entire high-intent audience segment
"Plus size" is one of the fastest-growing fashion search segments. Tagging a plus-size product as regular — which is the default when size_type is omitted — makes it invisible to every shopper who filters specifically for plus-size products. One attribute, zero cost, significant audience impact.
What is the size_type attribute?
The size_type attribute indicates which fit category or size range an apparel product belongs to: regular, petite, plus, tall, or maternity. It is distinct from the size attribute (which contains the actual size value like “M” or “14”) — size_type defines the sizing universe that size value belongs to.
When omitted, Google defaults to regular. For merchants selling in specialised size categories, this default silently makes their products invisible to the shoppers most likely to buy them. The “plus size” Shopping filter segment in particular is among the fastest-growing in fashion e-commerce, and it is populated only by products explicitly tagged with size_type = plus.
Technical specifications
| Feed name | size_type |
| Required | Optional (default is regular if omitted) |
| Applies to | Apparel & Accessories products |
| Single values | regular, petite, plus, tall, maternity |
| Compound values | big and tall, petite and plus |
| Max values per product | 1 (either a single value or one compound value) |
What each value means
regular | Standard fit — the default for most clothing. Do not submit for non-regular products. |
petite | Designed for shorter women (typically under 5'4″ / 163cm). Shorter inseams, proportional cuts. |
plus | Extended sizes (typically US 14+ / UK 18+ / EU 44+). Wider fit designed for larger frames. |
tall | Designed for taller individuals. Longer inseams, extended torso/sleeve length. |
maternity | Designed for pregnancy. Extra room in the abdomen, specific waistband construction. |
big and tall | Compound — designed for men who are both larger build AND above-average height. |
petite and plus | Compound — designed for shorter women who also wear plus sizes. |
Rules
-
Must use one of the exact allowed values above — no creative substitutes
-
Submit only one value per product (compound values are one string, not two separate submissions)
-
Do not use “big and tall” to mean simply “large” — it is specifically for men’s combined height+build sizing
-
Do not submit for non-apparel products — the attribute is ignored outside clothing/accessories categories
-
Omitting is acceptable for genuinely regular-fit products — the default is correct
Best practices
-
Audit your catalogue for non-regular products — scan titles and descriptions for keywords like “curve”, “plus”, “petite”, “maternity”, “tall”, “big” to identify products that should have a non-regular
size_typebut are currently untagged. -
Align size_type with size values — a plus-size product should have both
size_type = plusand plus-appropriate size values (e.g., 1X, 2X, 3X or 16W, 18W). Mismatched type and size is a data quality signal. -
Use with size_system for full context — together,
size_typeandsize_systemgive Google complete sizing context: which number system (US, EU, etc.) and which fit universe (regular, plus, etc.). -
Include size_type in title and description — for plus, petite, tall, and maternity products, explicitly mention the fit type in the title (e.g., “Women’s Plus Size Wrap Dress”). This reinforces the
size_typeattribute with text-based query matching.
Common mistakes
-
Omitting for plus, petite, tall, or maternity products — they default to “regular” and disappear from relevant filters
-
Using “big and tall” for a standard XL product — this value has a specific meaning for combined height+build sizing
-
Using invalid values: “curvy”, “extended”, “large”, “oversize”, “standard” — none are accepted
-
Submitting two separate values (e.g., “big” and “tall” as separate entries) instead of the compound “big and tall”
-
Not updating when you expand into new size categories — a merchant that adds a plus-size range to their catalogue must tag those new products, not rely on the feed to auto-detect
Frequently asked questions
What are the valid values for size_type?
regular, petite, plus, tall, maternity. Additionally, two values can be combined for products that span two size categories: big and tall (as a single compound value) and petite and plus. All other values are invalid and will be rejected or ignored. Do not use "big", "large", "standard", "normal", "curvy", or any other non-listed value.What is the default value if I omit size_type?
size_type is omitted, Google defaults to regular. This means if you sell a plus-size or petite product and do not submit size_type, it is classified and displayed as a regular-fit product. It will not appear in the "Plus" or "Petite" Shopping filters. The shoppers most likely to buy it — those specifically filtering for their size category — will never see it.What is the difference between size_type and the size attribute?
size contains the actual size value (e.g., XL, 14, 42). size_type indicates the fit category or size range the product belongs to. A "16W" plus-size garment has size = 16W and size_type = plus. A petite XS has size = XS and size_type = petite. The two attributes work together: size tells Google the number/letter; size_type tells Google which sizing universe that number belongs to.What does "big and tall" mean as a compound value?
big and tall as a single string (not two separate values). It represents products designed for men who are both larger in build (big) and above-average height (tall). This is a specific market segment with its own fit conventions, distinct from a standard XL or a tall-only product. Only use it when the product is genuinely designed for this combined fit category.Does size_type affect search query matching beyond filters?
size_type to match products to searches like "plus size dress", "petite women's trousers", or "maternity jeans". Without the attribute, your products are less likely to appear for these queries even in non-filtered search results. The attribute acts as a relevance signal for fit-specific search language.Is size_type required or just recommended?
size_type is optional according to Google's specification — there is no required-attribute warning in Diagnostics for omitting it. However, for any product that is not standard (regular) fit, omitting it is a significant missed opportunity. A plus-size product with no size_type effectively disappears from one of the fastest-growing shopping filter segments in fashion. Treat it as a business-critical attribute for non-regular products.