Google Merchant Center keeps disapproving my apparel listings for missing size, even though every variant clearly has one
Google Merchant Center requires a size value for apparel items, and Shopify only auto-detects it when your product options are named and formatted the way Google expects.
What's going on
Google Merchant Center treats size as a required attribute for products in the apparel and accessories category, covering clothing, shoes, and similar items. If Google can't find a usable size value for a variant, it disapproves that item, sometimes the whole product and sometimes just specific variants, with an error along the lines of "missing value: size" in Merchant Center diagnostics. This blocks the item from showing in the free Shopping tab and in Shopping or Performance Max ads.
The frustrating part for a lot of merchants is that the size is clearly displayed on the product page. The problem isn't that the size is missing from the store, it's that the feed built from your Shopify data doesn't reliably map whatever you've called that option, or however you've labeled its values, to Google's expected size attribute. Google's feed spec wants a recognizable size value; it generally can't infer size from a product title or description alone.
This shows up most often on stores that grew organically: some products use an option literally named "Size," others use "Fit," "Choose Size," or a combined option like "Size/Color," and older imported catalogs from migrations or bulk uploads often never had product categories assigned at all, which removes another path for Google to find the value.
Why it happens
Shopify's Google & YouTube sales channel builds your product feed automatically and tries to detect standard Google Shopping attributes, including size, color, gender, and material, from two sources: your product's assigned Shopify category, which exposes category-specific fields, and, as a fallback, your variant option names and values. When neither source gives Google a clean, unambiguous size value, the attribute comes through blank in the feed, and Google's apparel policy requires it.
The most common trigger is a variant option that isn't named "Size" and doesn't use values Google's parser recognizes, such as standard letter sizes, numeric sizes, waist and inseam formats, or "one size." A close second is products that were never assigned a Shopify product category at all, so there are no structured size or color fields to fall back on if the option-name detection also fails.
Because Google evaluates this per variant rather than per product, it's common to see only some sizes or some products in a collection flagged, which can make the pattern look random until you notice they share the same nonstandard option setup.
5 ways to fix it
Match your Shopify "Size" option name and values to what Google expects
Shopify's Google & YouTube sales channel builds your product feed automatically and tries to detect size, color, and other Google Shopping attributes from your product options. If the option is literally named "Size" and uses common values (XS/S/M/L/XL, numeric sizes, waist/inseam, or "one size"), it maps to Google's size attribute automatically at no cost. If the option is named something else ("Fit," "Dimensions," "Choose your size") or uses values Google can't parse ("Petite Curvy Fit"), the automatic mapping fails silently and every variant on that product gets flagged as missing size. This is the first thing to check and the most common root cause.
Assign the product to a Shopify category and fill in its Size and Color fields
Shopify's product category picker, found in the product's Organization section, exposes category-specific fields such as size, color, age group, and gender for apparel categories. These populate structured data that the Google & YouTube channel can read independently of your variant option names. This is often the more reliable fix for stores with inconsistent or creative option naming, since it decouples the customer-facing option label from the data Google needs, and it costs nothing beyond the time spent categorizing products correctly.
Look for a per-product attribute override for stubborn listings
For a handful of listings you don't want to restructure, check whether your feed setup supports overriding individual attributes like size at the product level without changing the storefront option. Depending on which app or channel you use to manage your Google feed, this may be available natively or may require a dedicated feed-management app; it's worth checking before assuming you have to rename options across your whole catalog for a few legacy or one-off products.
Confirm the fix actually cleared in Merchant Center, don't just assume it
After updating options, categories, or overrides, Google Merchant Center can take anywhere from a few hours to a couple of days to re-crawl the feed and clear a disapproval. Check the Diagnostics section in Merchant Center, or your sales channel's product status view in Shopify admin, to confirm the specific items are actually re-approved. Google evaluates size per variant, not per product, so a product can still show partial issues even after the main fix is in place.
For large or legacy catalogs, plan a one-time bulk cleanup instead of fixing products one by one
If disapprovals span an older catalog with mixed option naming conventions, a bulk edit (through Shopify's bulk editor, a CSV re-import, or a metafield-editing app) to standardize option names and backfill categories is usually faster than fixing products individually. Treat this as a one-time data-cleanup project rather than something that needs an ongoing dedicated app.
Bottom line
Most apparel size disapprovals come down to a mismatch between how your Shopify product options are named and valued and what Google's feed can automatically recognize. Fixing the option naming or filling in the standard category fields, both native and free in Shopify, resolves the majority of cases without installing anything. Reach for a bulk-editing tool only if you're untangling a large legacy catalog at once; this isn't a problem that needs a dedicated app to solve.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.