Merchant Center Product & Account Disapprovals

Why products and accounts get disapproved in Merchant Center, how to diagnose it in the Needs attention tab, and how the appeal and review process actually works.

First published: Jul 3, 2026 · Last updated: Jul 19, 2026 · Advanced
demand #6 in Google Merchant Center#23 in Ecommerce SEO#381 on the site

Disapprovals in Merchant Center operate on two axes: scope (a single item vs. the whole account) and cause (a data-quality/spec violation vs. a policy violation). Item-level data-quality issues — bad GTINs, undersized images, price/availability mismatches — are the routine, fixable kind: correct the feed, Google recrawls, done. Policy violations follow a warning-first flow (a 7- or 28-day courtesy-review window, depending on the issue) UNLESS they're classed egregious, like misrepresentation, which suspends the whole account immediately with no warning; Google warns that a new account for the same business will likely be flagged again, so spinning up a fresh account won't save you. Preemptive item disapproval (PID) is a predictive mechanism that disapproves products it thinks are likely to have a price/availability mismatch. Diagnose everything in the Needs attention tab (the old 'Diagnostics'), then use 'I fixed the issue' or, sparingly, 'I disagree with the issue' — you may only get one chance to disagree, and failed reviews trigger escalating cool-downs. Bing's model is different: three enforcement tiers, three strikes per policy category, and product disapprovals don't count as strikes. 2026 brings new triggers: a 500×500px image floor and an AI-content disclosure requirement.

TL;DR — Disapprovals sort onto two axes: scope (item vs. account) and cause (data-quality/spec vs. policy). Item-level data-quality issues are recrawlCrawl frequency is how often a search engine comes back to re-fetch a page it already knows about. Popular pages that change often get refreshed many times a day; stable pages can go weeks or months between crawls — and you influence it indirectly, not by setting a dial.-fixable and routine. Policy violations run a warning-first flow (a 7- or 28-day courtesy-review window, depending on the issue) unless they’re egregious — misrepresentation suspends the whole account immediately, no warning, and Google warns that a new account for the same business will likely be flagged again too. Preemptive item disapproval (PID) is a predictive mechanism for price/ availability mismatches. Diagnose in Needs attention (formerly Diagnostics); severity runs errors → warnings → notifications. Appeals go through “I fixed the issue” or, carefully, “I disagree with the issue” — you may only get one disagree attempt, and failed reviews escalate cool-downs. Bing uses a different three-tier model. 2026 adds a 500×500px image floor and an AI-content disclosure requirement as new triggers.

The mental model: two axes, four quadrants

Classify scope and cause before acting. A bad field, a systemic process problem, and an account-level policy suspension do not share a remedy.

The horizontal axis separates data or specification failures from policy failures. The vertical axis separates an affected item from the whole account. Item data failures usually need feed corrections and recrawling. Item policy failures may need a review. Systemic account data failures need a catalog-wide process correction. Account policy failures need the trust or policy problem fixed before review.

Almost every specific reason a product or account gets flagged slots into one of four boxes, and getting the box right tells you how much trouble you’re in and what the fix path is:

Data-quality / spec violationPolicy violation
Item-levelBad GTINProduct identifiers are the standardized values — GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand — that shopping feeds like Google Merchant Center and Microsoft Merchant Center use to match a product listing to the correct item in their catalog. A GTIN alone is usually enough; without one, brand + MPN is the fallback; products with none declare that with the identifier_exists attribute., undersized image, price mismatch, missing attribute → fix feed, recrawlSingle-product policy issue (e.g. a restricted item) → fix + often review
Account-levelRare — systemic data problemsMisrepresentation, counterfeit, dangerous products → warning flow or immediate suspension

Most competing “reasons for disapproval” articles are a flat, undifferentiated list that mixes an all-caps title (trivial) with a misrepresentation suspension (existential). Keeping the axes separate is the single most useful thing you can do here. Google’s own Issues in Merchant Center overview draws the warning → disapproval → suspension escalation; the account-level version of that flow just takes out every product at once instead of one. Evidence for this claim Merchant Center documents warnings, item disapprovals, and account suspensions as distinct issue outcomes. Scope: Not every issue follows the same escalation sequence. Confidence: high · Verified: Google: Issues in Merchant Center

One more wrinkle worth knowing before you diagnose: item-level status isn’t a single global flag. Google’s Merchant API exposes destinationStatuses per product — the same item can be approved for Shopping ads in one country and disapproved in another, or approved for one destination (Shopping ads) but not another (free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts.). If a product looks fine to you but a report says otherwise, check which country and destination the report is about before assuming Needs attention is wrong.

Why items get disapproved (data-quality violations)

These come from Google’s fix guide for product data quality violations: the submitted data either doesn’t match your own website or doesn’t comply with the product data specificationGoogle Merchant Center feed optimization is the process of improving the quality, accuracy, and completeness of the product data you submit to Google Merchant Center — titles, identifiers, images, and attributes — so your products show up more often and in more relevant places across Shopping ads, free listings, and AI shopping surfaces.. The usual triggers:

  • Missing or incorrect GTIN, invalid MPN, missing brand.
  • Generic, placeholder, or watermarked images; images below the minimum pixel dimensions.
  • Apparel attribute gaps (gender, size, color, age group).
  • Excessive capitalization in titles, or an invalid Google product category.
  • Price or availability that doesn’t match the landing page.
Evidence for this claim Price or availability mismatches between submitted data and landing pages can cause item issues. Scope: Google verifies product data and may use automatic updates where eligible. Confidence: high · Verified: Google: Product data quality violations

The fix path is genuinely easy: correct the offending attribute(s) in the feed and resubmit. Per Google’s own fix guide, after you update your products it can take 3–5 business days for Google to review them on recrawl; a formal review request is separate and typically takes up to seven business days (Google’s request-a-review page says “up to 7 business days”; the data-quality fix guide says “3–7 business days” — treat both as the same rough window rather than a precise commitment). For how to build feeds that don’t trip these in the first place — feed-specific titles, GTIN coverage, image standards — that’s the job of the feed optimizationGoogle Merchant Center feed optimization is the process of improving the quality, accuracy, and completeness of the product data you submit to Google Merchant Center — titles, identifiers, images, and attributes — so your products show up more often and in more relevant places across Shopping ads, free listings, and AI shopping surfaces. article; here I’m only naming them as disapproval causes.

Preemptive item disapproval (PID) — the predictive one

TIP Preflight the feed defects you can fix before appealing

A local feed check cannot reproduce Merchant Center policy enforcement, but it can remove concrete identity and image defects before you request another review.

Check a representative feed sample with my free AI Commerce Validator Free

  1. Use Needs attention to separate item data issues from account policy issues.
  2. Run the affected feed rows and fix duplicated IDs or invalid image URLs.
  3. Re-upload and confirm the processed data before using a limited review attempt.
This check covers observable feed defects only; it does not diagnose misrepresentation or predict Google's review decision.

The AI Commerce Validator warns that product ID sku-1 is duplicated in rows one and two and that both sampled image URLs are missing or invalid. These are feed-quality findings, not a Merchant Center policy verdict.

This is the mechanism most competing content skips, and it’s worth leading on because it behaves differently from an ordinary data-quality flag. Google’s definition:

“Preemptive item disapproval (PID) occurs if the price or availability of your products don’t match between your product data and website landing pages. When a PID is in place, we err on the side of caution and disapprove products that are likely to violate our requirements.” — Issues in Merchant Center

The important word is likely. PID is predictive: once your account has a history of price/availability mismatches, Google will disapprove products it thinks are probably wrong, not only the ones it has directly caught being wrong. That’s why merchants sometimes see disapprovals on products that look correct at a glance. Practitioners also report that clearing a PID takes a manual review request even after the data is fixed — an auto-recrawl alone may not lift it. Treat that review-required behavior as practitioner-reported and verify it against Google’s current copy, since PID mechanics have shifted across updates.

2026 spec changes that will cause new disapprovals

Google’s 2026 product data specification update introduces genuinely new triggers — this is the strongest “why read a 2026 article over a 2024 one” material:

  • Image resolution floor raised to 500×500px for image_link and additional_image_link, across all categories. Warnings started April 14, 2026; full enforcement (actual disapprovals) begins January 31, 2027. Google says it may auto-optimize some undersized images (via near-duplicateThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. high-res images or AI upscaling), but don’t rely on that as a fix.
  • A new optional video_link attribute — technical validation errors began April 14, 2026; serving plus policy/quality validation begins June 30, 2026.
  • New shipping attributes (handling_cutoff_time, minimum_order_value) introduced April 14, 2026.

Separately — and this is the one almost nobody’s top-ranking content connects to disapproval risk — AI-generated titles and descriptions now have a disclosure requirement. If a title or description was created with generative AI, Google’s guidance is to submit it via the structured_title / structured_description attributes rather than the plain title / description fields, with a digital_source_type sub-attribute set to trained_algorithmic_media. Putting AI-generated copy in the plain fields risks disapproval under data-spec non-compliance, and if you submit both, Google uses the plain title anyway. See Google’s title and structured title attributes and AI-generated content docs.

Why accounts get suspended (policy violations)

The standard warning-first flow

For ordinary, non-egregious policy problems, Google gives you a runway. From the fix guide for warnings and account suspensions and the request-a-review page: a warning email, then a courtesy-review window while products may still show with limited visibility, and only then a suspension if it’s unresolved. Google’s request-a-review page puts that window at 7 or 28 days depending on the issue (it doesn’t spell out which issues get which length, so don’t assume every warning gives you a full 28 days — check the specific issue’s timeframe in Needs attention). The reassuring part is that fixing it during the window can be enough on its own:

“If the violating products are removed from your account during the warning period, you won’t need to request an account review or take any additional action.” — Fixing Merchant Center warnings and account suspensions

Common non-egregious triggers on that page include a missing or unclear return/refund policy, inconsistent business contact info between your site and account, broken links or placeholder text or a non-functional checkout, and missing HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.'. (If you haven’t moved the store to HTTPSHTTPS is the encrypted version of HTTP — it uses TLS to authenticate the server and protect data in transit between a browser and a website. Google announced it as a lightweight ranking signal in 2014 and today conditionally prefers HTTPS pages as canonical; Chrome marks plain HTTP pages 'Not Secure.' yet, that alone can be a flag.)

Misrepresentation: the egregious, no-warning exception

Misrepresentation is the nuclear option, and it does not get the warning runway. Google’s framing of the policy itself:

“Google doesn’t want customers to feel misled by the content promoted in your offers, and that means being upfront, honest, and providing them with the information that they need to make informed decisions.” — Misrepresentation policy

And the consequence, in Google’s own words:

“If violations of this policy are foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore., your Google accounts will be suspended upon detection and without prior warning, and you won’t be allowed to promote with Google ShoppingGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. again.” — Misrepresentation policy

The fix-guide is explicit that this is by design. As it puts it, in some cases when an egregious policy issue is detected, no warning is given and the account is suspended immediately. So if you got suspended with no warning email, that’s not a glitch — it’s the policy working as written.

Google organizes the policy itself into four current categories (this replaces an older, more granular breakdown some competing content still cites — check the category names against the Misrepresentation policy page directly if you’re diagnosing a specific flag):

  • Unacceptable business practices — impersonation or a false business identity, promoting products you don’t actually have available, and phishing techniques.
  • Misleading or unrealistic offers — false health claims, falsely implying an endorsement or affiliation, and (per Google’s own examples) election/public-figure misinformation and climate-change denial.
  • Omission of relevant information — undisclosed fees or payment models, and missing shipping, return, or refund terms; also undisclosed charity/political donation details.
  • Unavailable offers — promoting out-of-stock or inactive deals.

Google published an October 2025 clarification adding more examples around non-delivery and inoperable return/refund processes, plus more appeals guidance — worth reading if you’re actively appealing a flag, since it’s newer than most third-party writeups.

A myth worth killing here: misrepresentation does not require that you did something dishonest on purpose. The flag can fire on an incomplete return policy or inconsistent business info — intent isn’t a prerequisite for the trigger. On the new-account question, Google’s own guidance is narrower than a lot of practitioner writing implies: it doesn’t spell out a domain-matching mechanism. What it does say is that deleting a suspended account and creating a new one for the same business won’t fix anything — “it’ll be flagged again as the newly created account may also be suspended.” Treat that as the operative rule (don’t spin up a replacement account for the same business) rather than assuming Google is technically fingerprinting your domain; either way, the practical advice is identical: fix the underlying trust problem instead of trying to start over.

Diagnosing: the Needs attention tab (formerly Diagnostics)

Google renamed the Diagnostics tab to Needs attention (Products > Needs attention). This matters more than it sounds: most top-ranking competitor guides — and the screenshots in them — still say “Diagnostics,” so readers following an older tutorial hit a UI that no longer matches. Same feature, new name. Google’s own docs for it are the Needs attention glossary entry and the detailed page.

What it gives you:

  • Account-level and product-level issues consolidated in one place.
  • Three summary cards highlighting the highest-impact issues and how many products each affects.
  • A Priority fixes filter that surfaces only medium/high performance-impact issues, cutting the noise from cosmetic ones.
  • A sortable, filterable list of every affected product (by click potential — High/Medium/Low — issue type, status, and title).
  • An Issue Details Page (IDP) per issue type: overview, suggested action, business-impact estimate, and sample affected products.
  • A View history button showing status changes over a date range.

Severity runs in three tiers, per Google’s severity-mapping developer doc (verify directly against the live page):

  • Errors — already causing an item disapproval or account suspension; fix first.
  • Warnings — not yet disapproving, but likely to if unresolved; performance may already be degraded.
  • Notifications — optional data-quality optimizations; not blocking.

The review and appeal process

Once an issue is flagged, Google’s request-a-review page gives you two doors:

  1. “I fixed the issue” — you’ve corrected the underlying data or site problem. For account-level policy issues, Google’s fix flow also calls out completing Identity Verification (IDV) and making sure your legal business name, address, phone, and email are visibly consistent between your site and your account.
  2. “I disagree with the issue” — the dispute path, for when you genuinely believe the flag is wrong. Use it carefully:

“You may only have one chance to disagree with the issue.” — Request a review of your issues

That single line is the whole strategy: don’t burn your one disagreement on a weak case. If you can legitimately fix the problem, fix it and use “I fixed the issue” instead of disputing.

Timelines and mechanics (paraphrased — confirm against the live page):

  • Reviews typically take up to seven business days (some docs say 3–7).
  • Status progresses Review Requested → Under Review → Review Approved / Review Not Approved.
  • Approved products or accounts generally become eligible to show again within about 24 hours of approval.
  • Cool-down periods apply after a failed review — the review button greys out for a period that lengthens with each subsequent failed attempt (a first cool-down around seven days is commonly reported, escalating from there). This is why the “I can just keep appealing until it works” assumption is wrong.

Bing / Microsoft Merchant Center: a different model

Almost no “Merchant Center disapprovalsA Merchant Center disapproval is Google (or Microsoft) refusing to show a product — or, in severe cases, an entire account — across Shopping ads and free listings because the submitted data doesn't match the product data specification, doesn't match the merchant's own website, or violates a Shopping policy. Disapprovals are resolved by fixing the underlying issue and, in most cases, explicitly requesting a review.” content covers Bing, and its enforcement is structurally different from Google’s — worth understanding rather than assuming it mirrors Google. Microsoft’s ad-policy enforcement doc lays out three tiers:

“When ads violate Microsoft Advertising policies, we may apply one or more of our three enforcement impact types: ad and ad component level disapprovals, repeated violation strikes, or immediate account suspension.” — What happens when an ad policy is violated (Microsoft Learn)

So: (1) ad/ad-component disapprovals (which includes product feed data), (2) a three-strikes system per policy category, and (3) immediate suspension for egregious violations:

“If we detect an egregious violation, we will suspend your access to the service, including access to all information contained therein, immediately and without prior warning.” — What happens when an ad policy is violated (Microsoft Learn)

The easily-missed distinction is that Microsoft product-level disapprovals don’t count toward the three-strikes system:

“We will not consider Microsoft Merchant CenterMicrosoft's free platform (inside Microsoft Advertising, formerly 'Bing Merchant Center') where retailers create a store and submit a product feed. One feed powers both free Product Listings on the Bing Shopping tab and paid Microsoft Shopping Campaigns — the Bing/Copilot-side twin of Google Merchant Center. As of 2026 it's also the product-data foundation Copilot draws on for AI-assisted shopping and checkout. product disapprovals when applying the Repeated violations policy.” — What happens when an ad policy is violated (Microsoft Learn)

Store-level is stricter — if your store violates policy, Microsoft disapproves the whole store and none of its products can serve. Appeals go through Microsoft Advertising support (there’s no self-serve “I disagree” button like Google’s), within six months of the decision. And Microsoft, like Google, is domain-bound: you can create only one store per top-level domain — same logic that makes a new-account workaround pointless.

Practitioners also report Bing-specific quirks: stricter in-stock requirements in some flows, and automated-classifier false positives — apparel size abbreviations misread as adult-content signals, or “toy gun” flagged as weapons content. Treat those as anecdotal/practitioner-reported color, not official Microsoft guidance.

A note on rep statements

Unlike crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. or indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., Merchant Center policy enforcement doesn’t get the Search Off the Record / office-hours treatment — it’s run by the Google Ads/Shopping policy teams, who are far less publicly vocal than the Search Relations team. I couldn’t find on-record statements from named Google or Bing reps specifically about Merchant Center disapprovals or misrepresentation. So for this topic, the written policy language above is the authoritative source — I’d rather tell you that plainly than paraphrase a “rep said X” claim I can’t point you to.

Where to go next

This is the “something’s wrong, here’s why, here’s how to fix and appeal it” article. For the platform itself and how free listings work, see the Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. hub; for building feeds that avoid these disapprovals in the first place, see feed optimizationGoogle Merchant Center feed optimization is the process of improving the quality, accuracy, and completeness of the product data you submit to Google Merchant Center — titles, identifiers, images, and attributes — so your products show up more often and in more relevant places across Shopping ads, free listings, and AI shopping surfaces.. For the broader picture, the ecommerce SEOEcommerce SEO is the practice of optimizing an online store so its product and category pages rank in organic search and attract purchase-intent visitors. It uses the same Google algorithm as any other site, but compounds the usual SEO work with commerce-specific challenges like faceted navigation, product variants, and platform-imposed URLs. pillar ties the merchant-center cluster to product pages, category pages, and site structure.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.