AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Ads
5K members online now
5K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Unknown 'google product category' value

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Little confused here, I am getting the the following error for all my products using this value as a category?

 

The 'google product category' value must be a recognised product category in the content language or in English

 

For this line

 

<g:google_product_category>Furniture > Beds & Accessories > Mattresses​</g:google_product_category>

 

Which is encoded in my feed as it's supposed to be

 

<g:google_product_category>Furniture &gt; Beds &amp; Accessories &gt; Mattresses​</g:google_product_category>

 

But it's a valid category  as per this page

 

http://www.google.com/basepages/producttype/taxonomy.en-US.txt

 

Anyone know what is going on?

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by topic author Lee M
October 2015

Re: Unknown 'google product category' value

[ Edited ]
Top Contributor
# 2
Top Contributor

 

assuming that is the exact value being submitted, there seems to be
a multi-byte, zero-width-space, within the posted, encoded, version.


the value must be exactly:

<g:google_product_category>
Furniture &gt; Beds &amp; Accessories &gt; Mattresses</g:google_product_category>

 

also, be certain that no other values are from any other country;
values should be either all from the u.s. taxonomy or all from
the registered-deed's target-country taxonomy -- but not mixed.

see also
# celebird check in help-forum-au.xml for bad products attributes
entry 1 google_product_category error invalid taxonomy [Furniture > Beds & Accessories > Mattresses​???]
# celebird check in help-forum-au.xml for character-encoding (details)
entry 5 encoding error encoded at position 200 [0xE2:0342:226]
# celebird check in help-forum-au.xml for character-encoding (details)
entry 5 encoding error encoded at position 200 [0xE2:0342:226]
entry 5 encoding error encoded at position 201 [0x80:0200:128]
entry 5 encoding error encoded at position 202 [0x8B:0213:139]
entry 5 encoding invalid consider using ascii (<space>) [near ies . Mattresses???]
entry 5 encoding invalid bad characters [found 1]
# 1 probable character-encoding detailed defect in help-forum-au.xml

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by topic author Lee M
October 2015

Re: Unknown 'google product category' value

[ Edited ]
Top Contributor
# 2
Top Contributor

 

assuming that is the exact value being submitted, there seems to be
a multi-byte, zero-width-space, within the posted, encoded, version.


the value must be exactly:

<g:google_product_category>
Furniture &gt; Beds &amp; Accessories &gt; Mattresses</g:google_product_category>

 

also, be certain that no other values are from any other country;
values should be either all from the u.s. taxonomy or all from
the registered-deed's target-country taxonomy -- but not mixed.

see also
# celebird check in help-forum-au.xml for bad products attributes
entry 1 google_product_category error invalid taxonomy [Furniture > Beds & Accessories > Mattresses​???]
# celebird check in help-forum-au.xml for character-encoding (details)
entry 5 encoding error encoded at position 200 [0xE2:0342:226]
# celebird check in help-forum-au.xml for character-encoding (details)
entry 5 encoding error encoded at position 200 [0xE2:0342:226]
entry 5 encoding error encoded at position 201 [0x80:0200:128]
entry 5 encoding error encoded at position 202 [0x8B:0213:139]
entry 5 encoding invalid consider using ascii (<space>) [near ies . Mattresses???]
entry 5 encoding invalid bad characters [found 1]
# 1 probable character-encoding detailed defect in help-forum-au.xml

 

Re: Unknown 'google product category' value

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
Thanks, you were right there was a hidden character in the field.