ShipworkSite inspection
Checks
Every error, explainedGuides →
Pricing Learn Guides

Which products has Google actually disapproved?

The public catalogue and the page markup can both look correct while Google holds a disapproval from an earlier snapshot. This is the one check that reads the Google side: the products Google has flagged, and the reason attached to each.

Reads the connected Merchant Center account with read-only access. Without a connection it says so rather than guessing.

What this check inspects

When a Merchant Center account is connected with read-only access, Shipwork reads the product statuses for the account and reports every item whose destination status is disapproved, with up to three item-level reasons for each product, such as a missing value, a policy problem or a landing page mismatch. It reports how many products were examined. Without a configured merchant id or a connection it says so plainly rather than guessing.

What a failure means

A disapproved product is an error, because it is removed from Shopping ads and free listings until it is fixed. The product id together with the reason is the actionable part: it names the rule Google applied, which is usually specific to that product rather than to the whole catalogue. When the account is not connected, or when no product statuses are returned, the check reports informational findings rather than inventing a verdict.

How to fix it

  1. Connect the Merchant Center account with read-only access so the Google disapproval list can be read rather than inferred.
  2. Work the list by reason: a title or image problem is fixed in the feed or the theme, a landing page problem in the page itself.
  3. Fix the cause and request a review for products that draw preemptive disapproval, since a data fix alone may not clear them.
  4. Re-run after a feed refresh, because the statuses update on the Google side rather than yours.

A typical failure, worked through

The setupA store corrected the prices in its feed, but Google still shows a set of products as disapproved with a price mismatch reason attached to the landing pages.

What the check reportsThe check lists the disapproved product ids and the reason Google attached to each, which points at the landing pages rather than the feed.

The pointThe account shows what Google currently thinks, which can lag a fix by days. The public checks show what a crawler sees now; this check shows what Google has already recorded.

Questions

Why can this check not read my feed?
The feed and the account are private. Reading them needs the owner to grant read-only access once, which is why the check reports that it is not connected until you do.
What do the reasons mean?
They are the item-level issues Google attached to a destination status, such as a missing value, a policy problem or a landing page mismatch. They point at the rule that was applied.
Do I still need the merchant readiness check?
Yes. That check reads the public page and reports what is missing before Google flags it. This one reads the account and reports what Google has already flagged.

Related checks and guides