Unrecognized attribute
What causes the "Unrecognized attribute" error in Merchant Center and how to fix it.
This error means a field name in your feed doesn't match any attribute Google recognises, usually a typo or a custom field submitted under the wrong name. Fix it by matching attribute names to the spec exactly and moving custom data into custom_label_0-4 instead of inventing new field names.
What triggers it
"Unrecognized attribute" fires when a column or field name in your feed doesn't match anything in Google's product data spec. It's usually one of two things: a genuine typo or casing mismatch on a real attribute name, or a custom field submitted as if it were a standard attribute when Google has no such attribute defined.
This is closely related to the column mapping problems covered in feed processing errors: a header that doesn't match the spec often produces this error at the item level even though the real fault is the feed's mapping.
Enrichment writes fields under Google's exact attribute names on a supplemental layer, so mismatched or invented field names in your source feed don't carry through to what's actually submitted.
Step by step
- Find the exact attribute name flagged. Diagnostics or the feed processing report shows the specific field name Google didn't recognise.
- Check spelling and casing against the product data spec. Attribute names must match exactly, including underscores and casing. A near-miss like producttype or Product_Type won't be read as product_type.
- Move genuinely custom data into custom_label_0-4. If the field is something you invented for your own reporting or campaign structure, it belongs in one of the five custom_label slots, not as a made-up attribute name.
- Re-submit and confirm the flag clears. Once the header names match the spec and Google re-fetches the feed, the error should clear within the normal crawl window.