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

Data feed failing using Lengow feed optimisation

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi - I am new to Google Merchant Centre and I am using Lengow feed optimisation to create my product feed from a Magento store. After mapping my products to export on the feed and then mapping the Magento categories to Googles categories for the feed when I add the optimised URL to Merchant centre it rejects every single product.

 

This is the URL of my feed. http://flux.lengow.com/shopbot/google-shopping/LGW-2c5b8ce506a50bc0febc3b602229c07f/txt/export.txt the guys at Lengow have looked at it and say they cannot find an issue with the feed so wondering if there was something else I was missing. Some of the reasons the feed is rejected are unrecognised attributes that are blank and not mandatory. 

 

Does anyone have a solution to this or need more info in order to debug?

 

Thanks in advance

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
September 2015

Re: Data feed failing using Lengow feed optimisation

[ Edited ]
Top Contributor
# 2
Top Contributor

 

(1) be certain that is a u.k. registered feed --
those are not valid values for a u.s. data-feed.

(2) the values used for google_product_category must
be up-to-date and exactly as google defines for the
exact target-country registered (or all u.s. values) --
currently, there are no such categories as flats or boots.

(3) for a u.k. registered feed, all such items might use the exact value:
Clothing & Accessories > Shoes

(4) product_type might be used to submit more granular,
private, (full) taxonomy, values to help improve quality --
product_type values should be relevant to the physical
item; values such as view-all are generally not allowed
and will reduce overall quality.

(5) importantly, link landing-pages must show the same item,
price, and currency for all users -- regardless of where
the user is physically located; or is otherwise a policy
violation and grounds for disapproval or suspension, at any time.

(6) the same data-feed or link landing-page typically
cannot be used for more than one target-country.

user-specific landing-pages based on personal, location,
or browser information are not allowed -- and grounds for
all items to be disapproved or a suspension, at any time.

(7) global-trade-data (brand, mpn, gtin) must be from the manufacturer;
merchant-assigned global-trade-data are not allowed and is grounds for
disapproval or suspension, at any time -- the shops (brand) name is set
within the account for all items.

(8) for shoes, the manufacturer's brand value and
either the manufacturer's mpn or a valid gtin
value from the factory bar-code is required --
merchant-assigned values are not allowed.

(9) there are other strict rules for apparel shoes --
for example, valid and accurate age_group and
gender values are required for all such items.

(10) images with too much whitespace can trigger
a review, disapproval, or suspension, at any time;
apparel product images must be at least 250x250
pixels and the product must take up 75%-90% of
the entire image space -- or is a policy violation.

(11) descriptive color values are generally not allowed --
color values should be simple color names such as brown
or three-dominate-order values such as brown/black/white.

(12) items with a price of zero cannot be submitted, at all --
or otherwise risks a disapproval or suspension, at any time.

(13) variant items cannot be submitted without valid, identical
item_group_id values for all items in the variant-group -- or is
otherwise is a policy violation and grounds for a disapproval or
suspension, at any time.

(14) variants that differ by color, pattern, or material, must
have a unique and specific image_link that corresponds
to the exact, variant, product that is being purchased --
or, such variant items cannot be submitted.

(15) the only officially documented data-feed file
formats are either .txt tab-delimited or google-xml.

see also
https://support.google.com/merchants/answer/6231410
https://support.google.com/merchants/answer/1344057
https://support.google.com/merchants/#topic=3404779

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by MosheTLV (Top Contributor)
September 2015

Re: Data feed failing using Lengow feed optimisation

[ Edited ]
Top Contributor
# 2
Top Contributor

 

(1) be certain that is a u.k. registered feed --
those are not valid values for a u.s. data-feed.

(2) the values used for google_product_category must
be up-to-date and exactly as google defines for the
exact target-country registered (or all u.s. values) --
currently, there are no such categories as flats or boots.

(3) for a u.k. registered feed, all such items might use the exact value:
Clothing & Accessories > Shoes

(4) product_type might be used to submit more granular,
private, (full) taxonomy, values to help improve quality --
product_type values should be relevant to the physical
item; values such as view-all are generally not allowed
and will reduce overall quality.

(5) importantly, link landing-pages must show the same item,
price, and currency for all users -- regardless of where
the user is physically located; or is otherwise a policy
violation and grounds for disapproval or suspension, at any time.

(6) the same data-feed or link landing-page typically
cannot be used for more than one target-country.

user-specific landing-pages based on personal, location,
or browser information are not allowed -- and grounds for
all items to be disapproved or a suspension, at any time.

(7) global-trade-data (brand, mpn, gtin) must be from the manufacturer;
merchant-assigned global-trade-data are not allowed and is grounds for
disapproval or suspension, at any time -- the shops (brand) name is set
within the account for all items.

(8) for shoes, the manufacturer's brand value and
either the manufacturer's mpn or a valid gtin
value from the factory bar-code is required --
merchant-assigned values are not allowed.

(9) there are other strict rules for apparel shoes --
for example, valid and accurate age_group and
gender values are required for all such items.

(10) images with too much whitespace can trigger
a review, disapproval, or suspension, at any time;
apparel product images must be at least 250x250
pixels and the product must take up 75%-90% of
the entire image space -- or is a policy violation.

(11) descriptive color values are generally not allowed --
color values should be simple color names such as brown
or three-dominate-order values such as brown/black/white.

(12) items with a price of zero cannot be submitted, at all --
or otherwise risks a disapproval or suspension, at any time.

(13) variant items cannot be submitted without valid, identical
item_group_id values for all items in the variant-group -- or is
otherwise is a policy violation and grounds for a disapproval or
suspension, at any time.

(14) variants that differ by color, pattern, or material, must
have a unique and specific image_link that corresponds
to the exact, variant, product that is being purchased --
or, such variant items cannot be submitted.

(15) the only officially documented data-feed file
formats are either .txt tab-delimited or google-xml.

see also
https://support.google.com/merchants/answer/6231410
https://support.google.com/merchants/answer/1344057
https://support.google.com/merchants/#topic=3404779