When your Shopping products get disapproved, check Merchant Center Diagnostics and the Products tab first, then open Policy Manager in Google Ads to read the Policy details column. Work out immediately whether you’re facing a product-level issue (fixable through your feed or destination) or account-level enforcement (which needs a formal review). The sections below give you the full checklist, in order.
TL;DR:
- Most disapprovals are caused by price or availability mismatches, often flagged as preemptive item disapprovals that allow a 28-day fix window before suspension risk.
- Image-related rejections usually result from overlays, watermarks, or stock photos with logos, which can often be addressed by enabling automatic image improvements.
- Common feed attribute errors include missing GTINs, brand, or category mismatches, which are mechanical issues that require direct feed updates and re-exports to resolve.
- Fixing land page issues like broken links, redirects, or robots.txt blocks can prevent disapprovals that stem from destination problems, which are often overlooked causes.
- Proper review procedures involve correcting the root issue first, then submitting a targeted appeal with supporting evidence, while repeated or premature appeals can worsen resolution delays.
Table of Contents
- How to locate and interpret disapproval signals in Merchant Center and Google Ads
- Common causes of Shopping ad disapprovals and concrete examples
- Prioritised, step-by-step fixes to re-enable disapproved items quickly
- How to verify fixes, submit a review and manage appeals
- How to prevent future disapprovals with automation, monitoring and feed hygiene
- Oxedent’s checklist and when to call an agency
- What the disapproval fire drill usually gets wrong
- Get disapproved Shopping ads back to work with Oxedent
- Sources
- FAQ
How to locate and interpret disapproval signals in Merchant Center and Google Ads
Speed matters here, and the fastest triage route runs through two dashboards, not one. Start in Merchant Center: go to Products, then Diagnostics, and click into any issue to see the affected SKUs and Google’s stated reason. The Products tab shows you exactly which items are ineligible to serve, whether that’s due to disapproval, stock status or a broken link between your Merchant Center and Google Ads accounts.
Then switch to Google Ads and add the Policy details column to your Shopping campaign view. This column, part of Policy Manager, tells you precisely why an ad sits at “Not eligible” or “Eligible (limited)”, which is the detail most PPC managers skip past when they only check Merchant Center.
You’ll typically see four statuses, and each means something different for serving:
- Warning: the item still serves, but Google has flagged a problem you need to fix before a deadline.
- Disapproved: the item has stopped serving and needs a fix plus resubmission.
- Eligible (limited): the ad serves but with restrictions, often geographic or audience-based.
- Not eligible: the ad is blocked entirely until the underlying issue is resolved.
Watch for preemptive item disapproval (PID) language in Diagnostics, which signals a price or availability mismatch rather than a content problem, and for any banner referencing account suspension, which changes your whole response plan. Export the affected SKU list, the stated reason and the item ID, then hand that export straight to whoever owns your feed or your website, because guesswork wastes the hours you don’t have.
Common causes of Shopping ad disapprovals and concrete examples
Most disapprovals trace back to one of five root causes, and matching the Diagnostics message to the right category saves you from fixing the wrong thing.
Price and availability mismatches are the most frequent trigger. If your feed says a jacket costs £45 but your product page charges £55, or the feed marks an item in stock when the page shows “sold out”, Google treats that as a preemptive item disapproval. Google’s own guidance on fixing data quality violations explains that PID exists specifically to stop shoppers landing on pages that don’t match what they clicked, and a warning typically gives you a 28-day window to resolve it before suspension risk increases.
Image issues come next: promotional overlays, watermarks, placeholder graphics or stock photography with a logo splashed across it. Merchant Center’s image improvements feature can strip promotional overlays automatically in some cases, which is worth enabling before you rebuild image assets from scratch.
Feed attribute errors cover missing GTINs, absent brand or MPN fields, and category mismatches where a product is filed under the wrong Google product category. These are mechanical errors, but they account for a large share of rejected items because feeds are often built once and rarely re-audited.
Landing-page problems include server errors, redirect chains, robots.txt rules blocking Googlebot-image, and placeholder or “coming soon” pages sitting behind a live ad. Google’s guidance on common website issues lists broken links and inconsistent page information among the recurring causes it sees.
Policy violations round out the list: excessive punctuation or capitalisation in titles, restricted product categories, and unsupported claims such as “cures” or “guaranteed results” in descriptions.
Ignoring any of these at account level carries real consequences. Google’s Shopping ads policies confirm that repeated or serious violations can lead to impression caps or full account suspension, and advertisers remain responsible for compliance regardless of how the error occurred.
Pro Tip: Before assuming a policy violation, check whether the issue is actually a price or availability mismatch, since PID messages sometimes get misread as content policy breaches.
Prioritised, step-by-step fixes to re-enable disapproved items quickly
Work through fixes in this order to stop wasted spend and get products back in front of buyers as fast as possible.
- Isolate the affected SKUs in Merchant Center Diagnostics and decide whether to pause the related campaigns or simply restrict bids while you fix the underlying issue, so budget doesn’t burn on ads that can’t serve properly.
- Correct the feed attribute causing the flag: update price, availability, GTIN, brand or category fields directly in your product data source, then re-export the feed rather than editing Merchant Center manually, so the fix holds after the next scheduled fetch.
- Fix images where overlays, watermarks or placeholders triggered the rejection, or turn on image improvements and let Google attempt an automatic correction first.
- Repair the destination, checking for broken links, redirect loops, server errors and any mismatch between your final URL and the page a shopper actually lands on.
- Remove non-compliant language from titles and descriptions, tightening punctuation and cutting unsupported claims before resubmitting.
- Trigger a fresh crawl by making a small, deliberate edit, either to a feed attribute or by adding a harmless parameter to the landing page URL, then re-upload the feed in Merchant Center and request a review rather than waiting for the next scheduled fetch.
Work feed fixes before image fixes, and image fixes before policy language edits, because a single feed error can cascade into false image or policy flags further down the pipeline.
Pro Tip: Never resubmit the same fix twice without changing something measurable, Google’s system needs a genuine edit to justify a fresh crawl.
How to verify fixes, submit a review and manage appeals
Once you’ve made your fixes, the review path differs slightly depending on where the disapproval originated. For product data issues, use “Request review” inside Merchant Center Diagnostics on the specific issue. For ad-level policy disapprovals, go through Policy Manager’s appeal flow in Google Ads.
A few things to get right before you submit:
- Choose the correct appeal reason from the list Google presents, matching it to what you actually fixed rather than a generic “I disagree” option, since mismatched reasons slow the review.
- Attach supporting evidence where the form allows it, such as a screenshot of the corrected landing page or a note on the feed change you made.
- Expect a 24 to 72 hour turnaround for most recrawls, though Google’s own ad status guidance notes that complex policy reviews or account-level suspensions can take considerably longer.
- Respect appeal limits: Google caps repeated appeals on the same disapproval, and submitting duplicate appeals without changes can flag your account for review misuse.
If an appeal fails, re-read the specific reason given, make a further edit that addresses it directly, and resubmit rather than appealing again on the same version. When a fix genuinely resolves the issue but the appeal still fails, escalate through Google Ads support with your evidence attached.
How to prevent future disapprovals with automation, monitoring and feed hygiene
Fixing disapprovals one at a time is a losing game if your feed keeps generating the same errors. A handful of operational habits cut recurrence significantly.
- Turn on item disapproval email alerts and automatic updates in Merchant Center so price and availability corrections often apply without manual intervention.
- Run feed validation checks before every upload, catching missing GTINs, malformed categories or blank required fields before Google does.
- Automate price and availability synchronisation between your website and feed, since manual updates are the single biggest cause of PID.
- Standardise image rules across your catalogue and enable image improvements so promotional overlays get resolved automatically where possible.
- Keep a change log and a staging feed, testing major catalogue updates before pushing live, and schedule a fresh recrawl immediately after any bulk change.
Our guide on structuring your Google Ads product feed effectively covers the attribute mapping that underpins most of this, and our breakdown of feed errors that cost you sales digs deeper into the mechanical side. If your product pages route through wishlists or saved-item flows, it’s worth checking that those destinations stay crawlable too, WantThis’s guide to retailer wishlist links is a useful reference for keeping those journeys clean.
Pro Tip: Schedule a full feed audit monthly, not just when disapprovals spike, since small attribute drift builds up quietly between major catalogue changes.
Oxedent’s checklist and when to call an agency
A tight agency-style triage runs in four stages: diagnose (Merchant Center Diagnostics plus Policy details), prioritise (fix feed and destination issues before content edits), verify (request review, confirm re-crawl), and monitor (alerts and scheduled audits so the same SKU doesn’t reappear next month).
Oxedent works exclusively on eCommerce PPC, which means Shopping feed troubleshooting sits inside our core operational focus rather than being a side task. Our approach leans on data-led optimisation and feed hygiene as levers for reducing wasted spend, not just fixing what’s broken today.
Some situations are worth escalating to outside help rather than absorbing internally: cross-account suspensions that touch both Merchant Center and Google Ads, recurring PID triggered by a complex inventory or ERP system that resists simple syncing, or simply not having the internal hours to run monthly feed audits alongside everything else. When disapprovals become a weekly fire drill rather than an occasional fix, that’s usually the signal to bring in specialist support.
What the disapproval fire drill usually gets wrong
Most advice on this topic treats every disapproval as an emergency requiring an immediate appeal. That’s backwards. The teams who resolve issues fastest treat the appeal as the last step, not the first, they diagnose the exact cause through Diagnostics and Policy details, fix the root attribute, and only then request review. Appealing before the underlying fix is confirmed just burns one of your limited appeal attempts on a submission Google will reject again.
The other blind spot is treating PID as a policy problem when it’s really an operations problem. A price mismatch isn’t a content violation, it’s a sync failure between your website and your feed, and no amount of rewording a product title will fix it. Readers chasing “policy compliance” often miss that the highest-leverage fix is automating price and availability updates so the mismatch never happens.
Prioritise the boring fix: feed accuracy first, then destination integrity, then language. Everything else is downstream of those three.
— Biplab
Get disapproved Shopping ads back to work with Oxedent
Diagnosing disapprovals is one job. Keeping your feed, your account and your ad spend clean month after month is another, and it’s the one most in-house teams don’t have the hours for. Oxedent runs eCommerce PPC exclusively, which means feed remediation and Shopping campaign management aren’t add-ons, they’re the core of what we do every day for established online retailers.
If you’re facing a live disapproval right now, or your Shopping feed keeps throwing the same errors month after month, start with a free Google/Facebook Ads audit to see exactly where the problem sits. For ongoing management once the fire’s out, our PPC management service starts from £350 per month, and our dedicated Google Shopping management service focuses specifically on feed optimisation and waste reduction for brands ready to scale past manual fixes.
FAQ
How do I appeal a disapproved Shopping ad?
Fix the underlying issue first, whether that’s a feed attribute, an image or a landing page, then use “Request review” in Merchant Center Diagnostics or the appeal option inside Policy Manager in Google Ads. Choose the appeal reason that matches your actual fix and attach evidence where the form allows it.
Why are my Shopping ads getting rejected?
Most rejections come from a price or availability mismatch between your feed and your website, a feed attribute error such as a missing GTIN, an image with a promotional overlay, or a landing page problem like a broken link or robots.txt block. Check the Policy details column in Google Ads and Merchant Center Diagnostics to see the exact stated reason for your account.
What can I do about products disapproved in Google Merchant Center?
Open Diagnostics under the Products tab, identify the specific reason given for each SKU, and fix the root cause in your feed or on your website before resubmitting. Preemptive item disapprovals specifically need price and availability corrected to match your live pages, after which a small feed edit and re-upload will trigger a fresh crawl.
How long does a Google review take after fixing a disapproval?
Most product recrawls complete within 24 to 72 hours, but complex policy reviews or account-level suspensions can take considerably longer. Repeated appeals on the same issue without a genuine fix can also delay resolution, since Google limits how many times you can appeal a single disapproval.