Incorrect value [size]

What Google requires

Free-text size, but fixed lists around it

The size value is free text, one size per variant. size_type must come from Google's set, regular, petite, plus, big and tall, or maternity, and size_system from its country codes, such as US, UK, EU or JP. The multipack count belongs in the multipack attribute, not the size string. Google reports an unrecognised value as Incorrect value [size].

What Google does

The product drops out of size-filtered results

A size_type or size_system outside the allowed list, or a size that hides a pack count such as M 3-pack, is not recognised, so the product does not appear when shoppers filter by size. In an apparel item group, where variants differ only by size, an unrecognised size also stops the group resolving cleanly.

How to fix it by hand

Split the qualifiers out cleanly

• Map size_type to one of the five allowed words and nothing else.
• Set size_system to the country code that matches the number, so a UK 10 is not read as a US 10.
• Move any pack count into multipack and leave the size as the garment size alone.
• Send one size per variant; use the item group to express the range.

What FeedMender checks today

3 checks apply, read from the scanner's registry

The scan checks size_type and size_system against Google's lists and catches the multipack count smuggled into the size field.

• size_holds_multipackblocks
• size_type_valueblocks
• size_system_valueblocks

What the scan does not check today: whether the free-text size value is the correct size for the garment; it checks the qualifiers against Google's lists, not the product.

The quicker way

Let the scan check the lists

Run the free scan and it flags every size_type and size_system outside Google's set, and every size that is really a pack count. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed