How a disapproval works
When you submit a product to Merchant Center or an ad to Google Ads, it passes through a review that is largely automated with human checks layered on top. If the item breaks a policy rule, or the data behind it does not hold up, the item is marked disapproved and stops serving. Everything else in the account carries on, which is exactly why a disapproval can go unnoticed for a long time — spend continues, it is simply spread across fewer items.
Every disapproval carries a stated reason. In Merchant Center it appears against the product; in Google Ads it appears against the ad, keyword or asset with a policy label. The reasons fall into two families. Policy reasons cover what you are selling or how you describe it: restricted goods, misleading claims, adult content, healthcare rules. Data reasons cover the mechanics: a price on the page that does not match the price in the feed, a missing required attribute, a landing page that will not load or that demands a login.
Why disapprovals matter
A disapproved item is invisible, not merely demoted. If it was one of your best sellers, the loss is immediate and nothing in the campaign reporting labels it as a policy problem — you simply watch impressions and revenue fall. Because bidding systems push budget towards whatever remains eligible, an account can look busy while the products you actually wanted to sell sit silent.
There is a second cost. Repeated or serious disapprovals accumulate against the account, and an account with a pattern of them stands closer to suspension than one with an isolated fault. Clearing them promptly is partly about the item and partly about the account’s standing.
Where disapprovals go wrong
The usual mistake is treating the stated reason as the whole diagnosis. A price mismatch is often a caching, currency or stock-update problem rather than a wrong price, so correcting the feed value without finding the cause means it returns on the next refresh. A misleading claim flag frequently points at wording the business considers ordinary and Google does not.
The second mistake is appealing before fixing. An appeal on an unchanged page tends to be rejected, and a rejected appeal makes the next one harder. Fix first, let the page and the feed refresh, then appeal once with a note of what changed.
What to do about it
Work from the reason text back to the underlying cause rather than towards a quick edit. Open the landing page as an anonymous visitor, on a phone, in the country you are targeting, and check that price, availability and product description match the feed exactly. Where the reason is a policy one, read the policy itself rather than a summary of it, then change the claim instead of softening it. If disapprovals keep returning across the account, the cause is usually structural — a page template, a currency rule, a plugin — and that is worth working through with policy compliance and suspension support before the account’s standing degrades further. Blocks confined to particular products are tracked as item-level issues in Merchant Center.
