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
4K members online now
4K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

products still disproved

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

My products have been disproved for about a month now. I use an API service to upload my feed to google and they were all running fine. It wasn't until I re-uploaded the API address that I started getting errors that didn't make sense. I contacted google support and they told me to insert micro data. I ALWAYS had the micro data so clearly google support is no help. The current error showing is this: "Preemptive item disapproval (availability): Ensure that availability in your product data matches your landing page". I have 1 product in my feed to make life easier. Link below:

 

http://www.morrisbuildingsupply.com/white-40-vanity-with-ceramic-top-p/mt9-137cw.htm

 

 

 

 

1 Expert replyverified_user
1 ACCEPTED SOLUTION

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

products still disproved

[ Edited ]
Top Contributor
# 2
Top Contributor

for shopping-ads, the merchant-center crawls typically must be able
to exactly match the microdata on the landing-page to one, exact,
item-offer displayed on the landing-page, and match the one, exact,
item-offer on the website to only one, exact, item-offer within the
submitted-data (feed) for the shopping-ad.

the match is usually accomplished via global-trade-data, or sku/id, or both.

for example, shopping-ads must have proper global-trade-data (gtin/brand)
both submitted within the feed and within the website's microdata --
to match the submitted data to the microdata on the website.

otherwise, the item must be submitted with identifier_exists set to no,
without any brand, without any gtin, and without any mpn, and the site's
microdata must have a corresponding sku that exactly matches the id.

note that if valid global-trade-data currently exists for an item,
as assigned by the manufacturer, then valid global-trade-data is
required to be submitted; conversely, if valid global-trade-data
does not currently exist, then gtin, brand, and mpn cannot be
submitted and identifier_exists no is required -- or is otherwise
a policy violation and grounds for disapproval or suspension
from the program, at any time.

related -- any variants submitted that effect price, must display the exact
variant to users and have corresponding microdata, on the landing-page,
by default -- usually via a server-side-script or a separate landing-page,
with identical, item_group_id for all items in the variant-group, submitted
to google in the feed, or the variants cannot be submitted for shopping-ads.

 

be certain that the new api-service is submitting proper global-trade-data,

or proper identifier_exists no without any brand, gtin, or mpn, and any

variants are being submitted with proper item_group_id and variant

attributes, and the website displayed-data and microdata exactly

matches each submitted item-offer for id/sku or global-trade-data.

 

each variant must be a separate physical inventory item --

submitted-data, microdata, displayed-data, and the actual

physical inventory availability during e-commerce checkout,

must all match, at all times.

 

generally, what is valid microdata, syntactically,
is not necessarily valid with respect to the rules
and policies related to shopping-ads.

otherwise, the optional automatic-item-updates feature
must be disabled within the merchant-center-account and
all microdata must be removed from the website; google
will then attempt to match the one displayed item-offer
to the submitted-data, for the shopping-ad -- although,

this alternative is usually not the best choice.

that said, this is mainly a peer-to-peer public forum, forum-members cannot
look into any submitted-data or accounts and can mainly offer suggestions
based on the information posted here in public -- posting, here in public,
more specific details, such as all the specific attributes and values that
are being submitted for the item-offer, the current automatic-item-updates
settings and any related history, screen-captures of any specific messages
and anything else that is being seen, etc. may allow other forum-members
to offer more specific suggestions.

otherwise, the best likely course is to re-contact google --
sometimes, contacting google at a different time, weekdays,
during normal business-hours, or asking for a shopping-ads,
merchant-center, support-specialist may help.

see also
https://support.google.com/merchants/topic/6386199
https://search.google.com/structured-data/testing-tool#url=http%3A%2F%2Fwww.celebird.com%2Fresources...

 

View solution in original post

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

products still disproved

[ Edited ]
Top Contributor
# 2
Top Contributor

for shopping-ads, the merchant-center crawls typically must be able
to exactly match the microdata on the landing-page to one, exact,
item-offer displayed on the landing-page, and match the one, exact,
item-offer on the website to only one, exact, item-offer within the
submitted-data (feed) for the shopping-ad.

the match is usually accomplished via global-trade-data, or sku/id, or both.

for example, shopping-ads must have proper global-trade-data (gtin/brand)
both submitted within the feed and within the website's microdata --
to match the submitted data to the microdata on the website.

otherwise, the item must be submitted with identifier_exists set to no,
without any brand, without any gtin, and without any mpn, and the site's
microdata must have a corresponding sku that exactly matches the id.

note that if valid global-trade-data currently exists for an item,
as assigned by the manufacturer, then valid global-trade-data is
required to be submitted; conversely, if valid global-trade-data
does not currently exist, then gtin, brand, and mpn cannot be
submitted and identifier_exists no is required -- or is otherwise
a policy violation and grounds for disapproval or suspension
from the program, at any time.

related -- any variants submitted that effect price, must display the exact
variant to users and have corresponding microdata, on the landing-page,
by default -- usually via a server-side-script or a separate landing-page,
with identical, item_group_id for all items in the variant-group, submitted
to google in the feed, or the variants cannot be submitted for shopping-ads.

 

be certain that the new api-service is submitting proper global-trade-data,

or proper identifier_exists no without any brand, gtin, or mpn, and any

variants are being submitted with proper item_group_id and variant

attributes, and the website displayed-data and microdata exactly

matches each submitted item-offer for id/sku or global-trade-data.

 

each variant must be a separate physical inventory item --

submitted-data, microdata, displayed-data, and the actual

physical inventory availability during e-commerce checkout,

must all match, at all times.

 

generally, what is valid microdata, syntactically,
is not necessarily valid with respect to the rules
and policies related to shopping-ads.

otherwise, the optional automatic-item-updates feature
must be disabled within the merchant-center-account and
all microdata must be removed from the website; google
will then attempt to match the one displayed item-offer
to the submitted-data, for the shopping-ad -- although,

this alternative is usually not the best choice.

that said, this is mainly a peer-to-peer public forum, forum-members cannot
look into any submitted-data or accounts and can mainly offer suggestions
based on the information posted here in public -- posting, here in public,
more specific details, such as all the specific attributes and values that
are being submitted for the item-offer, the current automatic-item-updates
settings and any related history, screen-captures of any specific messages
and anything else that is being seen, etc. may allow other forum-members
to offer more specific suggestions.

otherwise, the best likely course is to re-contact google --
sometimes, contacting google at a different time, weekdays,
during normal business-hours, or asking for a shopping-ads,
merchant-center, support-specialist may help.

see also
https://support.google.com/merchants/topic/6386199
https://search.google.com/structured-data/testing-tool#url=http%3A%2F%2Fwww.celebird.com%2Fresources...