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.
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 — A “disapproval” means Google (or Bing) has stopped showing one of your products — or, in the worst case, your whole store. It happens when your product data breaks a rule, doesn’t match your own website, or violates a Shopping policy. One bad product is common and easy to fix. A whole-account suspension is the scary one, and it usually needs you to fix the problem and ask Google to re-review.
What “disapproved” actually means
When you sell through 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., Google checks every product you submit. If something’s wrong, it flags an issue. Depending on how serious it is, that issue can:
- Warn you — the product still shows, but its performance may be limited.
- Disapprove the product — it stops showing across Google entirely.
- Suspend your account — every product stops showing, not just one. Evidence for this claim Merchant Center issues can affect individual items or an account and can limit product visibility. Scope: Issue impact and review options depend on severity and policy. Confidence: high · Verified: Google: Issues in Merchant Center
So there are really two questions to ask about any disapproval: how big is the blast radius (one product, or the whole account?) and what caused it (a data problem, or a policy problem?).
The two kinds of problems
Data-quality problems are the routine, boring kind. Your product title has all caps, an image is too small or watermarked, a barcode (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.) is missing or wrong, or the price on your feed doesn’t match the price on your actual product page. These are usually item-level — one product gets pulled — and you fix them by correcting the feed. Google recrawlsCrawl 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. and puts the product back. (Building feeds that avoid these in the first place is the whole job of 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..)
Policy problems are the serious kind. These are about trust: is your business who it says it is? Are your prices and fees honest? Do you have a clear return policy? The most feared one is called misrepresentation, and it can suspend your entire account without advance warning in egregious cases. Evidence for this claim Egregious policy violations can lead to account suspension without advance warning. Scope: Google determines severity and enforcement under current Shopping policies. Confidence: high · Verified: Google: Account warnings and suspensions
Where to look
Everything shows up in one place: Products > Needs attention in Merchant Center. (You may have seen older tutorials call this the “Diagnostics” tab — Google renamed it. Same feature, new name.) It lists every issue, how many products are affected, and what to do about each one.
How you fix it
For a simple data problem: fix the feed, and Google usually re-checks within a day or two. For a policy problem or a suspension: fix the underlying issue, then click the button to request a review. Google looks at it again — this can take up to a week — and if you’ve genuinely fixed things, your products come back.
One warning that trips up a lot of people: if you get suspended for misrepresentation, you cannot just create a new account and start over. Google’s own guidance says a new account for the same business will likely get flagged again too — it’s not about creating a new login, it’s about the underlying business. Fix the real problem instead.
Want the full mechanism — the four types of disapproval, how the appeal cool-downs work, the 2026 rule changes, and how Bing differs? Switch to the Advanced tab.
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
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 violation | Policy violation | |
|---|---|---|
| Item-level | Bad 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, recrawl | Single-product policy issue (e.g. a restricted item) → fix + often review |
| Account-level | Rare — systemic data problems | Misrepresentation, 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.
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
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
- Use Needs attention to separate item data issues from account policy issues.
- Run the affected feed rows and fix duplicated IDs or invalid image URLs.
- Re-upload and confirm the processed data before using a limited review attempt.
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_linkandadditional_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_linkattribute — 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:
- “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.
- “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.
AI summary
A condensed take on the Advanced version:
- Two axes: disapprovals sort by scope (item vs. account) and cause
(data-quality/spec vs. policy). The four resulting quadrants tell you the stakes
and the fix path. Item status also isn’t a single global flag — Google reports it
per country/destination (
destinationStatuses), so check which one a report means. - Item-level data-quality issues (bad 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/watermarked image, price/ availability mismatch, all-caps title, missing attribute) are routine: fix the feed, Google recrawlsCrawl 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. within 3–5 business days; a formal review request is separate and typically takes up to 7 business days.
- Preemptive item disapproval (PID) is predictive — Google disapproves products it thinks are likely to have a price/availability mismatch based on account history, not only confirmed ones. Clearing it may need a manual review even after a fix (practitioner-reported).
- Policy violations run a warning-first flow (a 7- or 28-day courtesy-review window, depending on the issue) — fix during the window and no review is needed — unless the violation is egregious.
- Misrepresentation is the egregious exception: immediate suspension, no warning. Google organizes it into four current categories (unacceptable business practices, misleading/unrealistic offers, omission of relevant information, unavailable offers) and warns that deleting a suspended account and starting a new one for the same business will likely just get flagged again — it doesn’t spell out a domain-matching mechanism, but the practical advice is the same either way. Intent isn’t required for the flag.
- 2026 triggers: 500×500px image floor (warnings from April 2026, enforced Jan
2027);
video_link; and an AI-content disclosure requirement viastructured_title/structured_description+digital_source_type. - Diagnose in Needs attention (formerly Diagnostics); severity = errors → warnings → notifications.
- Appeals: “I fixed the issue” or, sparingly, “I disagree with the issue” — you may only get one disagree attempt, and failed reviews trigger escalating cool-downs. Approval makes products/accounts eligible to show again — it isn’t a guarantee of impressions, rankings, or that a similar issue won’t recur.
- Bing is different: three tiers (disapproval / three strikes per category / immediate suspension), product disapprovals don’t count as strikes, appeals go through support within six months, one store per domain.
Official documentation
Primary-source documentation from Google and Microsoft.
- Issues in Merchant Center — the warning → disapproval → suspension taxonomy and the PID definition.
- Fixing disapprovals for product data quality violations — data-quality causes and 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./review timelines.
- Fixing warnings and account suspensions for policy violations — the warning flow and the egregious/no-warning exception.
- Misrepresentation policy — the policy definition, current category headings, and the immediate-suspension/new-account language.
- Clarifying Misrepresentation policy for Shopping ads and free listings — Google’s October 2025 update adding examples and appeals guidance.
- Request a review of your issues — the review flow, the “one chance to disagree” line, and cool-downs.
- Needs attention tab (glossary) and Needs attention tab (detail) — summary cards, priority fixes, IDP, view history.
- Issue severity and Merchant Center Diagnostics — the errors / warnings / notifications severity mapping.
- Product data specification update 2026 — the 500×500 image floor dates,
video_link, and new shipping attributes. - Title and structured title attributes and AI-generated content — the AI-disclosure requirement.
Microsoft / Bing
- What happens when an ad policy is violated (Microsoft Learn) — the three-tier enforcement model, the 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.-specific rules, and the appeals window.
Quotes from the source
On-the-record statements from Google and Microsoft. Each link is a deep link that jumps to the quoted passage on the source page.
Google — preemptive item disapproval
- “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.” — 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. Help. Jump to quote
Google — misrepresentation (the account-suspension policy)
- “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 Shopping again.” — Merchant Center Misrepresentation policy. Jump to quote
Google — starting over doesn’t work
- “It’s not recommended to delete your suspended account and create a new one for the same business. Deleting an account won’t fix the suspension issue, it’ll be flagged again as the newly created account may also be suspended.” — Merchant Center Misrepresentation policy. Read the guidance
Google — the standard warning flow
- “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 warnings and account suspensions for policy violations. Read the guidance
Google — the appeal you only get once
- “You may only have one chance to disagree with the issue.” — Request a review of your issues. Read the guidance
Microsoft — the three-tier model
-
“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.” — Microsoft Advertising, What happens when an ad policy is violated. Read the doc
-
“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.” — Microsoft Advertising. Read the doc
-
“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.” — Microsoft Advertising. Read the doc
My product/account got flagged — what do I do?
The right move depends entirely on which quadrant you’re in. Start by checking Products > Needs attention for the specific issue, then click through.
Diagnosing and fixing a Merchant Center disapproval
Runbook: recovering from a misrepresentation account suspension
The worst-case scenario — the whole account is suspended, no warning email, and Shopping/free-listing traffic dropped to zero. Work it in order; don’t skip to the appeal.
- Confirm the cause. Open Products > Needs attention and the Issue Details Page. Confirm it’s misrepresentation (or another egregious category) and not a recoverable warning-flow issue. This determines everything downstream.
- Do NOT create a new account. Google’s own guidance says a fresh Merchant Center account — new email, new CSS provider — for the same business will likely be caught and re-suspended too. This step is mostly resisting the temptation.
- Audit business identity. Make your legal business name, physical address, phone, and email visibly consistent between your live site and your Merchant Center account. Add or fix an About/Contact page.
- Audit transparency. Publish clear, findable return, refund, and shipping policies. Remove undisclosed fees; make currency and total price obvious; kill misleading CTAs and any inactive promotions still live on-site.
- Complete Identity Verification (IDV). Google’s account-level fix flow calls for IDV; complete it before you appeal.
- Fix the offer data. Remove out-of-stock/discontinued items still being promoted; make feed price/availability match the landing pages (this also prevents PID from re-firing later).
- Request the review — once, carefully. Use “I fixed the issue” with the above genuinely done. Reserve “I disagree with the issue” only for a flag you truly believe is wrong and can evidence — you may only get one disagree attempt.
- Wait it out. Reviews take up to ~7 business days; approved accounts become eligible again within ~24 hours of approval. If it fails, expect a cool-down before you can re-request, lengthening with each failed attempt — so fix thoroughly before re-appealing rather than firing off a second weak request.
- Set expectations honestly. None of the above guarantees a specific outcome. An approved review makes your products/account eligible to show again — it’s not a promise of impressions, rankings, or that a similar issue won’t recur if the underlying business practice slips again. Fixing the checklist above improves your odds; it doesn’t lock in reinstatement.
Mistakes that keep merchants stuck
Concrete misconceptions I see repeatedly — why they’re wrong, and what to do instead.
“I’ll just make a new 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. account to escape the suspension.” Wrong because Google’s own guidance says a new account (even a new email or CSS provider) for the same business will likely be flagged again — the fix isn’t a new login, it’s the underlying trust problem. Instead: fix the real problem on the site and appeal the existing account.
“The Diagnostics tab will show me my issues.” Wrong because Google renamed it to Needs attention (Products > Needs attention). Older tutorials and screenshots still say “Diagnostics.” Instead: look under Needs attention — same feature, current name.
“A disapproved product means my whole account is in danger.” Wrong because item-level data-quality disapprovals are common and routine and don’t, by themselves, trigger account suspension. Instead: fix the feed and move on; only unresolved policy issues (especially egregious ones) escalate to the account level.
“I can appeal as many times as I want until one sticks.” Wrong because reviews are rate-limited by escalating cool-downs, and you may get only one “I disagree” attempt. Instead: fix thoroughly before appealing, use “I fixed the issue” when you actually fixed it, and save “I disagree” for a genuinely wrong flag with evidence ready.
“Misrepresentation means I must have lied on purpose.” Wrong because the flag doesn’t require intent — an incomplete return policy or inconsistent business info is enough to trigger it. Instead: treat it as a completeness/consistency audit, not a confession.
“Fixing the feed is always enough — Google will pick it back up automatically.” Wrong for PID and most account-level/policy issues, which need an explicit review request even after the underlying problem is fixed. True only for many item-level data-quality issues (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.-based). Instead: fix, then check whether the issue type needs a review, and request one if so.
“Bing disapprovals work the same as Google’s.” Wrong because Microsoft uses a three-tier model (ad/component disapproval, a three-strikes system per policy category, and immediate suspension), product disapprovals don’t count as strikes, and appeals go through support rather than a self-serve dispute button. Instead: handle Bing on its own terms — appeal via Microsoft Advertising support within six months.
Merchant Center disapproval symptoms and fixes
One product is disapproved for price or availability mismatch
Likely causes: The feed, landing page, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., or checkout reports a different price, currency, sale window, or stock state. A history of mismatches may also trigger preemptive item disapproval.
Fix: Compare the same SKU and market across all submitted and visible sources, correct the source that is stale, and resubmit. If the issue is PID, use the review path after the data agrees rather than assuming 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. alone will clear it.
Many products suddenly fail image requirements
Likely causes: A catalog image pipeline is producing undersized, placeholder, watermarked, or inaccessible assets, or a newer specification now applies.
Fix: Filter Needs attention by the image issue, inspect sample affected products, and repair the source image transformation rather than editing items one at a time. Confirm the submitted URLs return the intended image and meet the current live spec.
The whole account is suspended without a warning email
Likely cause: Google classified the issue as egregious, commonly misrepresentation, counterfeit, or another immediate-suspension category.
Fix: Open the account-level Issue Details Page, audit business identity and offer transparency across the site, complete required verification, and fix the site before requesting a review. Do not create a replacement account for the same business.
The review button is disabled
Likely causes: A prior review failed and the account is in a cool-down, a review is already in progress, or the issue has prerequisites that remain incomplete.
Fix: Check the review status and issue history, finish the underlying corrections, and wait for the platform’s permitted next action. Use the time to assemble evidence; repeated weak requests lengthen the recovery path.
”I fixed the issue” review is not approved
Likely causes: The visible site and account still disagree, a sample fix did not cover the whole catalog, cached/feed data remains stale, or identity/policy evidence is incomplete.
Fix: Reopen the issue scope, test representative affected items, and document each required correction at its system of record. Request another review only after the live feed, site, checkout, and account settings all show the fix.
Products are fine in Google but rejected in Microsoft Merchant Center
Likely cause: Microsoft applies its own product, store, and enforcement rules; Google approval is not evidence of Microsoft compliance.
Fix: Diagnose the Microsoft issue separately, correct its feed/store requirement, and use Microsoft Advertising support for the appeal route. Product disapprovals do not follow Google’s self-serve review model.
Before fixing or appealing a Merchant Center issue
Triage
- Opened Products > Needs attention and the issue’s details/history.
- Recorded the exact issue name, severity, affected count, and account- vs. item-level scope.
- Classified the cause as data/spec or policy rather than relying on the email subject alone.
- Exported or recorded representative affected products before changing data.
- Checked whether the issue is a warning, current disapproval/suspension, or non-blocking notification.
Item-level data issues
- Feed, landing page, structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding., and checkout agree for SKU, price, currency, availability, and condition.
- Brand, 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./MPN, category-specific attributes, and current image requirements are satisfied where applicable.
- Image URLs return the intended non-placeholder asset to an anonymous fetch.
- AI-generated titles/descriptions use the currently required structured fields and disclosure sub-attribute.
- The corrected feed was processed and the current item record reflects the fix.
- PID or policy-related items use the appropriate review path after correction.
Account-level policy issues
- Legal business name, address, phone, email, and domain are consistent between 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. and the visible site.
- Contact, About, shipping, return, refund, payment, and pricing information is clear and reachable.
- Checkout works, 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.' is present, and no placeholder/broken pages remain in the purchase path.
- Out-of-stock, discontinued, misleading, restricted, or unsupported offers were corrected or removed.
- Required Identity Verification is complete.
- No replacement account was created to evade a domain/business-level issue.
Review request
- Chosen I fixed the issue when a genuine correction was made.
- Reserved I disagree with the issue for a documented false positive, given that the option may be limited.
- Verified every correction on the live site/account, not only in a staging or source system.
- Saved evidence and the request date, then monitored status without firing duplicate appeals.
Frameworks for resolving disapprovals safely
Scope × cause
Start with the article’s two axes:
| Data/spec issue | Policy issue | |
|---|---|---|
| Item-level | Correct the feed/page attribute; many clear on processing/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. | Correct/remove the item, then review when required |
| Account-level | Look for a systemic source or catalog pipeline failure | Repair domain/business trust; review only after the whole issue is fixed |
Scope determines blast radius. Cause determines whether the fix is mechanical or requires policy/trust evidence.
Severity → action → evidence
- Notification: Improve quality when worthwhile; it is not blocking serving.
- Warning: Fix before the deadline and preserve proof that the live system changed.
- Error/disapproval: Restore compliant item data and confirm processing.
- Suspension: Stop, audit the entire account/domain cause, complete verification, and build a review-ready evidence set.
Do not let a low-impact notification displace a blocking error, and do not treat an account suspension like a feed typo.
The review-readiness gate
Request a review only when all four are true:
- Source fixed: The feed, site, account setting, or policy content was corrected at its system of record.
- Live proof: An anonymous user and crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. can see the correction now.
- Scope covered: The fix applies to every affected item or the full domain, not only the first sample.
- Request type fits: “I fixed” describes a correction; “I disagree” has evidence that the classifier/policy application is wrong.
If any gate fails, the next move is more remediation, not another appeal.
Google and Microsoft are separate enforcement systems
Google uses item/account scope, warning flows, immediate egregious suspension, and self-serve review choices. Microsoft uses component disapprovals, repeated-violation strikes, immediate suspension, and support-led appeals. Share product-data hygiene between them, but keep policy status, evidence, and appeals in separate workflows.
Merchant Center disapprovals quick reference
Symptom → likely class → next move
| Symptom | Likely class | First move |
|---|---|---|
| One SKU has bad 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./image/title | Item data/spec | Correct the attribute and reprocess |
| Price/stock differs from page | Item mismatch or PID | Align all sources; review if PID requires it |
| Warning email with a fix window | Non-egregious account policy | Repair before the deadline |
| Immediate whole-account suspension | Egregious policy category | Audit domain/business trust before review |
| Review button disabled | In review, cool-down, or unmet prerequisite | Check status/history; finish remediation |
| Microsoft product rejected | Microsoft component policy | Fix there; appeal through Microsoft support |
Needs attention severity
| Severity | Meaning |
|---|---|
| Error | Already blocks an item or account |
| Warning | Can become blocking if unresolved; may already limit performance |
| Notification | Optional quality improvement, not a serving block |
Review choices
| Choice | Use when | Avoid when |
|---|---|---|
| I fixed the issue | The underlying feed/site/account problem is corrected and live | Only a sample or staging version was changed |
| I disagree with the issue | The flag is genuinely wrong and evidence supports that conclusion | A fix is possible, evidence is weak, or you are guessing |
Common issue owners
| Issue family | Likely owner/system |
|---|---|
| GTIN, brand, title, attributes | Product information/feed source |
| Price/availability mismatch | Commerce platform, feed sync, cache |
| Image requirements | DAM/image transformation pipeline |
| Shipping/returns/contact transparency | Ecommerce operations + site content |
| Identity verification/business consistency | Account owner/legal/operations |
| Appeal evidence and status | 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. account owner |
Remember: a new account does not solve a domain/business-level suspension; fixing the underlying cause does.
Test yourself: Merchant Center disapprovals
Five quick questions on why products and accounts get disapproved and how to fix it. Pick an answer for each, then check.
Resources worth your time
This is a new topic area for my byline, so the writing below is the sibling context on my site plus the verified third-party and official sources I’d send you to.
On this site
- 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. — what GMCGoogle 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. is, 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., and the srsltid parameter. Read this first if disapprovals aren’t your immediate problem yet.
- Google Merchant Center 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. — how to build feeds (titles, 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. coverage, image quality, required attributes) so you avoid most data-quality disapprovals in the first place.
- 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. — the pillar that ties the merchant-center cluster to product pages, category pages, and site structureWebsite structure (site architecture) is a site's visible hierarchy, navigation, breadcrumbs, and URL organization — how pages relate and how people and search engines move between them. Internal linking is the primary signal Google reads to understand that structure, not URL folders..
Official
- Google — Issues in Merchant Center, Fixing data-quality disapprovals, Fixing policy warnings & suspensions, Misrepresentation, its October 2025 clarification, and Request a review.
- Google — 2026 product data specification update — the 500×500 image floor and new attributes.
- Microsoft — What happens when an ad policy is violated — Bing’s three-tier model.
From around the industry
- How to fix a suspended Google Merchant Center account (Search Engine Land, John Horn/StubGroup) — suspension-cause taxonomy, appeal steps, and a case study.
- Resolving a Google Merchant Center account suspension (misrepresentation) (Feedonomics) — a practitioner walkthrough of the misrepresentation category specifically.
- Google Merchant Center disapprovals: common causes and fast fixes (Launchmind) — a concise causes-and-fixes reference.
- Top reasons for Google Merchant Center disapprovals (2026 guide) (Productsup) — a 2026-dated common-causes overview.
- Fix Google Merchant Center disapprovals: prevention & recovery (TrustedWebServices) — prevention-and-recovery framing.
Merchant Center Disapproval
A 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.
Related: Google Merchant Center, Google Merchant Center Feed Optimization, Ecommerce SEO
Merchant Center Disapproval
A 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. disapproval is when Google (or Microsoft) stops showing a product, or in more serious cases an entire Merchant Center account, across Shopping ads and free product 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.. It happens for one of three broad reasons: the submitted product data doesn’t comply with the product data specification, the data doesn’t match what’s on the merchant’s own website (price, availability, identifiers), or the offer or store violates a Shopping policy.
The key distinction to keep straight is scope: an item-level disapproval stops a single product from showing, while an account-level suspension takes out every product in the account at once. Both surface from the same place — an “issue” flagged in Merchant Center’s Needs attention tab (formerly called Diagnostics) — but the fix path and the stakes are very different. Item-level data-quality issues are usually fixed by correcting the feed and letting Google 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.; account-level policy issues, and especially egregious ones like misrepresentation, require an explicit review request and can suspend with no warning.
Related: Google Merchant Center, Google Merchant Center Feed Optimization, Ecommerce SEO
Build-time retrieval analysis plus live signals for this exact article. The automatic chunk report includes a deterministic readiness score and is ready without a model download.
Search Console
sampleGA4 traffic (28d)
sampleCloudflare traffic (7d)
sampledCrUX field data (28d, phone)
sampleGoogle NLP entities
localChangelog
Revision history
Compare the published article with an archived editorial snapshot. Added and removed words are shown only after you open a comparison.
Updated Jul 19, 2026.
Editorial summary and recorded change details.Summary
Dead-link fix: replaced a 404'd Microsoft Learn ad-policy citation (all 9 occurrences) with Microsoft's current live policy-impact URL.
Change details
-
Replaced the dead https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_policy_impacttoyourmicrosoftadsaccount link, used 9 times across the body and Official Docs/Resources lenses, with the current live https://about.ads.microsoft.com/en-us/policies/impact-to-your-microsoft-advertising-account page covering the same three-tier enforcement model.
Full comparison unavailable — no prior snapshot was archived for this revision.
Updated Jul 18, 2026.
Editorial summary and recorded change details.Summary
Verified every disapproval reason name, timeline, and the misrepresentation new-account claim against Google's live Merchant Center help docs (platform-drift pass): corrected the recrawl timeframe, the warning-period length, and Google's current misrepresentation category names, and softened the domain-binding claim to match what Google actually documents.
Change details
- Before
Feed fixes 'usually resolve within 24-48 hours' and the policy warning window was described as 'commonly 28 days.'AfterCorrected to Google's documented figures: feed-fix recrawl typically takes 3-5 business days, and the warning-first window is 7 or 28 days depending on the issue (Google's docs don't specify which triggers which). - Before
Misrepresentation categories were paraphrased as 'business identity / offer / pricing transparency / post-purchase transparency / health-medical' and the new-account workaround was described as blocked because the suspension is 'domain-bound.'AfterReplaced the category list with Google's current live headings (unacceptable business practices, misleading/unrealistic offers, omission of relevant information, unavailable offers) and reworded the new-account guidance to match Google's actual wording — a new account for the same business gets flagged again, not a stated domain-matching mechanism. -
Added a note that item-level product status is reported per country/destination (Merchant API destinationStatuses), and added an explicit no-guarantee caveat to the recovery playbook and quiz.