Merchant Center Item Disapproved for Policy? Fix (2026)

About 80 percent of Merchant Center disapprovals that owners panic over in 2026 are item-level — a single product flagged for one fixable policy issue — not the account-wide suspensions they fear, and Google keeps the rest of the feed serving the entire time. A disapproved item simply stops appearing in Shopping ads and free listings until you read the exact reason, fix the attribute or page that triggered it, and request a re-review.

This guide works through seven checks, from telling an item disapproval apart from a suspension to reading the Products and Diagnostics tabs, fixing the feed, and preventing recurrence. To check your store against the most common Shopping and account leaks automatically, run our free 5-axis Google Ads audit.

Updated 2026-05-01 with current Merchant Center Products tab, Diagnostics and Shopping ads policy behavior observed across US, UK and European accounts.

How is an item disapproval different from account suspension?

The first thing to settle is scope, because the response is completely different. An item disapproval is narrow and routine; an account suspension is broad and serious. Confusing the two leads people to over-react to a five-minute fix or under-react to a real threat.

Item-level disapproval — Google flags one product or a small set of products. The disapproved item stops serving in Shopping ads and free listings, but every other item in your feed keeps running normally. You resolve it in the Products tab, usually in minutes.

Account suspension — Your entire Merchant Center stops showing anything, typically after repeated or severe violations. This requires a formal review request and can take days. If you are here, follow our Merchant Center suspension recovery guide instead of the per-item steps below.

The signal to watch — A single disapproval is maintenance. A growing backlog of disapprovals for the same policy is a pattern Google reads as systemic, and that pattern is what escalates toward suspension. Treat scope as your first diagnostic before you touch anything.

What are the most common item-level policy reasons?

Most item disapprovals fall into a handful of repeating categories. Knowing them lets you recognize the cause the moment you read the reason, rather than guessing. These are the five you will see most often.

Prohibited or restricted products — Some categories cannot be advertised at all, and others only under conditions. Counterfeits, dangerous goods, certain healthcare items, and adult or unsupported categories are disapproved on sight. Restricted goods may serve only with the right setup, so confirm the category before re-submitting.

Misrepresentation at item level — When the feed says one thing and the landing page says another, Google flags misrepresentation. The classic case is a price or availability mismatch — the feed shows 49 dollars, the page shows 59. Our price and availability mismatch fix covers this exact reason in depth.

Image and promotional-overlay policy — Product images must show the item cleanly with no added text, watermark, logo, badge, or border. A 'Sale' banner or price burned into the photo triggers an image disapproval. Supply a clean image and keep promotional messaging in the price and promotion fields.

Editorial and landing-page issues — A broken or 404 destination, a page under construction, mismatched language, or thin product detail all draw editorial disapprovals. Together with adult, dangerous and unsupported categories, these round out the reasons that account for the large majority of item-level flags.

How do you read the exact issue in Products and Diagnostics?

You cannot fix what you have not read precisely. Merchant Center names the exact policy and the attribute at fault, and reading it verbatim saves a wasted re-review cycle spent fixing the wrong thing.

Products tab — Open Merchant Center, go to the Products tab, and filter by the disapproved status. Click any flagged item to open its detail view, which names the specific policy, the attribute involved, and links to the relevant Shopping ads policy article.

Diagnostics tab — The Diagnostics tab gives the account-wide and feed-level rollup. Use it to tell whether a single product is affected or a whole category shares the same issue, which decides whether you fix one item or write one feed rule.

Read before you edit — Note the exact wording. 'Disapproved for image with promotional overlay' points to image_link; 'mismatched price' points to the price attribute and the landing page. If your products are not appearing at all rather than disapproved, see our products not showing fix, which is a different diagnosis.

How do you fix the item or the feed attribute that triggered it?

Once you know the exact reason, the fix is usually a specific attribute or page, not a vague cleanup. Match the reason to its source and correct that, not the symptom on screen.

Attribute fixes — An image overlay reason means swapping the image_link to a clean photo. A price mismatch means aligning the price attribute with the live page. A wrong category means correcting google_product_category or removing the offending value entirely.

Landing-page fixes — A 404 or under-construction reason is fixed on the site, not the feed. Restore the destination URL, then let the feed re-crawl so the corrected page is read. Identifier errors are their own class — see our GTIN and product identifier errors fix.

Fix the class, not the case — When the Diagnostics tab shows many items sharing one fault, write a single feed rule rather than editing each product. One rule that strips overlay references or standardizes availability clears the whole batch in one pass.

Always change only the attribute the policy named. Editing unrelated fields can introduce a new disapproval while you are trying to clear the first.

How do you request a re-review and how long does it take?

A fix is not live until the corrected data is read and re-reviewed. The mechanics are simple, but a few habits decide whether the review clears in days or drags on.

Submit the corrected data — Re-upload or refresh the feed so the fixed attribute or page re-crawls. Where the interface offers an explicit request review action for the item, use it; otherwise the corrected feed re-triggers the check automatically.

Expected timeline — Most item-level re-reviews complete within three to seven business days, and many automated checks clear sooner. The Products tab status moves from disapproved to pending to approved, so watch that field rather than guessing.

Do not churn the item — Editing the same product repeatedly while it is pending resets the review queue and delays you. Make the correct fix once, submit, and wait. If a week passes with a correct fix and no change, contact Merchant Center support rather than resubmitting again.

When does one bad item put the whole account at risk?

A single disapproval will not suspend your account, but the behavior around it can. Google escalates on pattern and severity, so knowing the danger signs keeps a routine fix from becoming a crisis.

Repeated violations — Many items disapproved for the same policy, especially misrepresentation, read as systemic rather than accidental. The account-level risk grows with the count, not with any one item.

Re-submitting banned products — Re-uploading a prohibited item after it was disapproved is the fastest way to escalate. Google treats this as deliberate, and deliberate violations move toward suspension far quicker than honest mistakes.

Ignored deadlines — Account-level warnings often carry a grace period before enforcement. Letting that window lapse converts a warning into a suspension. The diagnostic table below maps each symptom to the fix and to how close it sits to account-level risk.

How do you prevent disapprovals with feed rules and pre-checks?

The cheapest disapproval is the one that never happens. Prevention lives in the feed, where a single rule guards a whole class of items, not in repeated manual fixes after the fact.

Feed rules — Use rules to enforce clean values automatically: standardize price and availability so they always match the landing page, strip references that read as overlay text, and block categories you are not allowed to sell. One rule fixes the whole class at once.

Pre-submit checks — Add a checklist that validates required attributes, GTINs, and image URLs before the feed uploads. Catching a missing or malformed value before submission avoids the disapproval entirely and saves a three-to-seven-day review cycle.

Refresh cadence — Schedule the feed to refresh often enough that price and stock never drift from the site. Most recurring misrepresentation disapprovals are simply stale data, and a tighter schedule removes the cause.

Build prevention once and you stop fighting the same flags every week. To size the budget you are protecting and the spend these disapprovals quietly waste, run the SteerAds free 5-axis audit and our wasted ad spend calculator.

Sources

Official sources consulted for this guide:

• support.google.com — disapproved products in Merchant Center

• support.google.com — Shopping ads policies

• support.google.com — product data specification

• support.google.com — about Merchant Center

FAQ