Warning Affects: color data quality

Fix “Invalid value [color]” on Google Merchant Center

The color attribute is populated but with a value Google can't recognise — usually free-text marketing names ('Midnight Whisper', 'Sahara Sunset') that don't map to standard colours. Items still serve but with reduced filter eligibility.

What you see in Google Merchant Center:

Invalid value [color]

API identifier: invalid_value_color

Invalid colour is most often Google's classifier rejecting brand-marketing colour names. "Midnight Whisper", "Sahara Sunset", "Coastal Dream" — these are marketing names, not colours. Google can't map them to its colour taxonomy for filtering, so the field gets flagged as invalid.

The strategic compromise that works: keep the marketing colour name in the title for brand positioning, use standard colour names in the colour field. "Midnight Whisper Wool Coat" in title, "Navy" in colour. Users searching the marketing name still find the listing via title; users filtering on colour find it via the standard colour value.

For multi-colour items, the slash separator is the rule: "Red/White/Blue", up to three colours. Comma-separated values, semicolons, "and"-joined lists all get rejected. Beyond three colours, use "Multicolour" as the single value.

For colour codes (hex values, RGB, brand-specific codes), the field is for human-readable colour names, not codes. `#1A2B3C` doesn't work — use the standard name closest to the hex. Some categories where colour matters precisely (paint, dye, makeup) might benefit from including the brand colour code in description while keeping the colour field standard.

The Optimiser can map brand marketing colour names to standard equivalents at scale — feeding it your colour-name mapping table and applying it as a feed-generation rule.

Top causes

  • 1

    Brand-specific colour names like 'Midnight Whisper' or 'Sahara Sunset'

  • 2

    Colour codes (#FF5733) instead of colour names

  • 3

    Multiple colours combined in one string ('Red, Blue, Green') without proper separator

  • 4

    Locale mismatches (colour spelled 'colour' or in another language)

How to fix it

  1. 1

    Identify affected items

    Merchant Center → Needs attention → 'Invalid value [color]'.

  2. 2

    Map brand colours to standard names

    Build a translation table: 'Midnight Whisper' → 'Navy', 'Sahara Sunset' → 'Orange'. Apply this mapping in the feed-generation step.

  3. 3

    Handle multi-colour items correctly

    For products with multiple colours, separate with '/' (slash): 'Red/Blue/Green'. Google accepts up to three colours separated this way.

  4. 4

    Refresh and verify

    Force-fetch the feed and verify clearance.

Related fields

FAQ

Should I keep my brand colour names anywhere in the feed?

Yes — in the title or description. The colour field needs standard names for filtering, but customers searching for 'Midnight Whisper' should still match your listing via title text.

Does Google have a list of accepted colour names?

Yes, but it's loose — any common English colour name works (Red, Blue, Green, Black, White, Navy, Beige, Brown, etc.). Marketing names that aren't recognisable colours fail.

Last reviewed: 26 May 2026

Free plan · No card

Why wait? Try it free today.

Stop managing feeds manually. Start optimising with AI in 30 seconds.

  • Free plan, no credit card required
  • 1 brand, 1 feed, 100,000 products per feed
  • Full AI Product Optimisation, Rule Engine, and 200+ channel exports
  • Pay only for AI credits when you need them