Google Merchant Center Disapprovals: How to Fix Them (2026)

Google Merchant Center disapprovals are one of the most common emergency calls in Shopping ad management. The notification arrives, products vanish from Shopping results, revenue drops, and Google’s explanation is vague enough to leave most operators guessing about the actual cause.

This guide takes a diagnostic-first approach. It separates the two big categories (account-level suspensions vs product-level disapprovals), prioritises the fixes that actually move the needle, and addresses the misrepresentation suspension specifically because it’s the most catastrophic and most misunderstood.

In real-world audit work, the single largest disapproval cause is data mismatch between the feed and the live website. Bigger than image quality. Bigger than restricted content. Bigger than account-level enforcement. Most generic GMC content treats all disapproval reasons as equally weighted, which is why most fix attempts target the wrong things first. Keeping the feed and the site in sync is part of ongoing ecommerce account management.

2025-2026 has brought meaningful platform changes that older content misses entirely: a new mandatory in-account identity verification step for misrepresentation handling, raised minimum image resolution requirements (500×500 from April 2026 warnings, full enforcement January 2027), expanded misrepresentation rules around delivery accuracy and refund handling, and an AU-specific political content policy update (effective April 16, 2026). This article reflects the 2026 state.

The article assumes you already use Merchant Center for Shopping or Performance Max campaigns. For platform-specific feed setup on Shopify, the Shopify Google Ads and Shopping setup guide covers the technical layer. For WooCommerce, the WooCommerce setup guide does the same. If your PMax campaigns are inheriting disapproved feed health, the Performance Max campaign structure guide addresses structure-level issues that compound feed problems.

Feed health is the foundation, but once your products are approved and serving, the campaign management decision that moves profit most is the bid strategy you run. For how to choose between volume-based and value-based bidding, and why I manage ROAS through budget pacing instead of a Target ROAS target, see the Performance Max bidding guide for ecommerce. Feed and Merchant Center fixes are included in Google Shopping management at Adgenix.

Account-level vs product-level disapprovals (the most important distinction)

The first diagnostic question is which category you’re actually in. The fix paths are completely different and one approach won’t solve the other.

Signs of account-level suspension

All products show as disapproved
“Account suspended” banner across Merchant Center
Shopping ads stopped entirely, not just specific products
Email from Google with policy violation language (misrepresentation, customer service, account integrity, etc.)

Signs of product-level disapprovals

This is the more common scenario:

Some products approved, others disapproved
No account suspension banner
Shopping ads still running for approved products
Disapproval reasons listed per product in the Products tab

Why this distinction matters for fix priority

Account-level suspensions require formal reconsideration requests after structural fixes. They cannot be resolved by fixing individual products, no matter how many you fix. The entire account is suspended for a site-wide or business-level reason.

Product-level disapprovals usually have specific, identifiable causes you can address per product (or in batches by reason category). Submitting an account-level appeal won’t help with product-level issues because there’s no suspension to appeal.

Trying to fix products won’t lift an account suspension. Submitting an appeal won’t fix individual product issues. Get the category right before spending time on the wrong path.

Account-level suspensions: what they are and how to handle them

Account suspensions are the catastrophic case. Most operators handle them wrong, and the cost of mistakes is high because each rejected appeal triggers progressively longer cool-down periods.

The most common account suspension reasons in 2026

Misrepresentation (by far the most common, covered in detail below)
Customer service requirements (missing or broken contact info)
Editorial and professional requirements (low-quality content, broken pages)
Trust issues (typically new GMC accounts with limited GMC history; note that this is GMC account age specifically, not store age, so an established Shopify or WooCommerce store creating a fresh GMC account can still trigger trust issues despite the store itself having years of history)
Account integrity (typically duplicate account suspicions or recent account changes)
Promotional tactics (deceptive pricing, fake urgency, manipulated reviews)

Misrepresentation suspensions: what they actually mean

Despite the name, misrepresentation is almost never about specific products or specific ads. It’s about the website overall.

Google’s algorithm checks for what it calls “trust signals” across the entire store. The absence of trust signals triggers the suspension, even if no individual product violates any policy.

Google treats misrepresentation as an “egregious policy violation.” There’s often no warning period before suspension. Products are removed from Shopping immediately. Reported ROAS goes to zero overnight. This is not the kind of disapproval you can sit on for a few days while figuring out the fix.

Common trigger categories:

Incomplete About Us page
Missing or hard-to-find returns and refund policy
Unclear pricing or hidden fees
Customer service gaps (no phone, no email, no physical address where applicable)
Inconsistencies between Merchant Center business info and website data
Print-on-demand businesses (Google policy generally requires merchants to physically stock finished products ready for immediate shipping; POD’s “manufactured after order” model often triggers misrepresentation flags)

The 2025 misrepresentation policy expansion broadened the rules around delivery accuracy, refund handling, and transparency disclosures. Stores compliant in 2024 may now trigger suspension under stricter 2025-2026 enforcement without changing anything on their end.

How to actually fix a misrepresentation suspension

Steps in order:

Complete the in-account identity verification (new 2026 mandatory step, covered next)
Audit the website (not the feed) for trust signals
Fix any inconsistencies between Merchant Center and website
Submit a reconsideration request with specific changes documented
Wait 7-14 days for review without submitting follow-up requests

Trust signal audit covers:

Complete About Us with company info, business address, ABN or equivalent business registration
Returns and refund policy clearly accessible from header or footer
Contact information including phone, email, and physical address where applicable
Privacy policy and terms of service
SSL certificate active on every page (https everywhere)
Customer reviews integrated where possible

This is the standard list. Real misrepresentation fixes often require deeper work than the surface items, but the surface items are the table stakes Google’s automated review checks first.

GMC identity verification: the new mandatory 2026 step

The single most important change to misrepresentation handling in 2026 is the in-account identity verification step. Many stores skip this entirely because they don’t realise it exists.

Required: business identity must match exactly across three places.

Merchant Center business information
Google Ads account settings
Google Payments profile

Any mismatch can trigger or sustain a misrepresentation suspension regardless of how clean the website looks. Different business name spellings, address formatting differences, phone number variations, currency inconsistencies, language settings drift. Google’s verification cross-references all three.

Common identity verification gaps:

Merchant Center registered under personal name; Google Ads under business name
Different address formats across the three accounts (street vs road, abbreviated vs full)
Phone number formatting inconsistency (+61 vs 0, with vs without spaces)
Currency mismatch between Merchant Center settings and store country
Business registration number missing or differently formatted

Fix path:

Open Merchant Center → Business information → ensure complete and accurate
Open Google Ads → Settings → ensure business identity matches the Merchant Center entry
Open Google Payments profile → ensure business name, address, contact details match
Standardise formatting across all three (identical spelling, capitalisation, address format)
Complete any incomplete verification steps Google flags within each account

This step alone resolves a significant share of misrepresentation suspensions where the website looks compliant but the account-level identity layer is mismatched. Many stores have appealed multiple times while ignoring this step entirely.

The “I appealed and was rejected” trap

Most rejected appeals fail because the appeal didn’t address the actual cause. Google’s response is typically generic and doesn’t tell you which specific issue remained unresolved.

Each rejected appeal triggers a progressively longer cool-down period before the next appeal can be submitted. After 3 failed appeals, reinstatement becomes substantially harder. Google’s tolerance shrinks with each rejection.

Practical implication: fix everything before the first appeal, not after a rejection. The first appeal is the highest-probability shot. After two rejected appeals, two paths exist: bring in someone who has resolved repeated rejections before, or consider a fresh GMC account (covered next).

Some accounts never get reinstated. Google’s decision is final after exhausted appeals, and for some account histories no amount of fixing changes that outcome.

Starting over with a new GMC account (when appeals run out)

The honest operator reality: after two or three rejected appeals on a suspended GMC account, creating a fresh GMC account is often faster and more reliable than continued appeals. This isn’t officially recommended by Google but it’s a recognised path among operators when the appeal route has failed.

The critical caveat: this only works when the underlying issue is genuinely fixed. If the suspension was for misrepresentation triggered by website trust signal gaps, those gaps must be closed first. A fresh GMC account on the same suspect website will likely re-suspend immediately, often within days.

When this path makes sense:

Account suspended for reasons that have been fixed (website trust signals, customer service info, policy issues)
Continued appeals have been rejected despite documented fixes
Time pressure (revenue stopped, holiday season, product launch on hold)
No clear specialist available to escalate the appeal further

When this path doesn’t make sense:

Underlying issue is not actually fixed (the new account will suspend for the same reason)
Account in a regulated category where the suspension was for substantive policy reasons
Misrepresentation suspension where the website still lacks trust signals

How Google detects duplicate accounts:

Business name, address, phone number matches
Payment method on file (same card, same bank account)
IP address overlap during account setup
Website domain matches (same site, same products)
Linked Google Ads account or Google Analytics account

For a fresh account to actually be fresh:

Use a different business email (separate Google account)
Use a different payment method
Set up from a different IP if possible
Address the website issues that triggered the original suspension first
For some operators in some categories, this means setting up a new business entity entirely

This is a pragmatic path that some operators take when appeals fail. It is not the right answer for every suspension. Misrepresentation suspensions with unresolved website trust signal gaps will recur on any new account, no matter how clean the account setup itself looks.

Product-level disapprovals: the diagnostic order that matters

For product-level disapprovals, the fix order matters. Not all disapprovals are equal in revenue impact or fix complexity. Working through them in the wrong order wastes hours.

Run the diagnostic in this order

Identify the reason for each disapproval (Merchant Center → Products → filter by status)
Group disapprovals by reason category
Identify the highest-impact group (most products affected, or highest-revenue products affected)
Fix that group first
Re-submit the feed and wait for re-review (24-72 hours typically)
Move to the next group

This is the opposite of how most operators approach it. The instinct is to start with whichever disapproval is “easiest” to fix, but that often means hours of work on low-impact issues while the high-revenue products stay disapproved.

The most common product-level disapproval reasons

In real audit work, the dominant pattern is data mismatch between the product feed and the live website. This single category accounts for more disapprovals than the more dramatic categories combined.

Disapproval reasons in approximate frequency order across ecommerce stores:

Mismatch between feed data and website data (the #1 cause in real audits, covered in detail below)
Missing required attributes (GTIN, brand, MPN, condition)
Image issues (placeholder images, promotional overlays, watermarks)
Variant or configurable product structure issues
Landing page issues (404, mobile usability, slow page speed)
GTIN errors (incorrect format, invalid checksum)
Restricted or prohibited content
Tax and shipping setup errors

Feed-to-website data mismatch: the #1 disapproval cause in real audits

Across actual ecommerce audit work, the single most common disapproval pattern is mismatch between what the feed claims and what the website shows. Google’s automated checks crawl the landing page and compare its data against the feed submission. Any drift triggers a disapproval.

Common forms of mismatch:

Price drift: feed shows $89.95, landing page shows $79.95 (sale price applied to site but not synced to feed)
Availability drift: feed says “in stock,” landing page says “out of stock” or “back order”
Currency mismatch: feed in AUD but landing page displays USD, or vice versa for international stores
Title or description drift: product renamed on the site but feed still has old title
GTIN drift: product variant changes triggered new GTIN on site but feed unchanged
Image URL drift: site moved images to a new CDN but feed still points to old URLs (404s)
Sale or promotion drift: promotional pricing applied to site but not pushed to feed

Common triggers:

Manual feed management without automation
Sales and promotions applied to the website but not the feed
Currency conversion handled at display time on the site but not in the feed
Dynamic pricing systems updating site prices but not pushing to feed
Abandoned product pages where the product was archived but feed entry remained
Platform sync issues (less common on Shopify or WooCommerce, more common on custom builds and migrations)

Fix path depends on platform. Shopify and WooCommerce stores typically have feed apps that sync automatically; if mismatch is occurring on these platforms, the diagnostic is usually app configuration or sync timing rather than a manual feed issue. See the Shopify setup guide and the WooCommerce setup guide for platform-specific feed setup detail.

Custom builds, BigCommerce, Neto, or manual CSV feeds require feed update frequency tuning. For high-velocity stores with frequent price or stock changes, hourly updates may be required. For stable catalogues, daily can work.

Why this category dominates in audit work: it’s invisible to the operator. Disapproval reports show the symptom (product disapproved) but not the underlying cause (data drift). Operators often spend time on image quality or attribute completeness when the actual fix is a feed sync issue affecting dozens of products at once.

GTIN errors and missing attributes

GTIN must be the actual GTIN of the product (UPC, EAN, ISBN, etc.). Don’t fabricate GTINs. Google checks against the GTIN database and fabricated values trigger immediate disapproval and can flag the account for further review.

For products without genuine GTINs (truly unique items, custom-made, store-branded private label), submit identifier_exists: false rather than a placeholder. This is the correct way to signal “this product doesn’t have a standard identifier” without triggering GTIN validation failures.

Brand attribute must match the actual brand, or be marked as the store’s own brand if applicable. Submitting a manufacturer brand when the product is white-label can trigger misrepresentation flags.

MPN can be the SKU for many products but not for products with manufacturer codes. Where a manufacturer code exists, use it.

Variant and parent-child product disapprovals

Variant disapprovals deserve their own section because they’re structurally different from single-product disapprovals and confuse most operators.

Why variant disapprovals look weird

A parent product may appear approved while specific variants are disapproved
A variant disapproval can cascade to other variants in the same group
Fixing one variant often requires addressing the parent product structure

This is why variant fix attempts often fail. Operators fix the symptom variant without addressing the structural issue affecting the entire group.

Common variant issues

item_group_id missing or inconsistent across variants
Variant-specific attributes (size, colour, material) missing or generic
Same image used for all variants when colours or styles differ visibly
Inconsistent pricing across variants without is_bundle or proper structuring
Variants of out-of-stock products treated differently than in-stock counterparts

Fixing variant structure

Audit the entire variant group, not just the disapproved variant. The structural issue affecting one variant usually affects the others. Fixing them as a group prevents cascade re-disapprovals after the next feed update.

Ensure item_group_id is consistent across all variants of the same product. Provide variant-specific images where colour or style differs. Standardise variant attributes using Google’s controlled vocabulary where applicable (sizes, colours, materials all have standardised values).

Image and visual content disapprovals

Why image disapprovals are increasing in 2026

Google’s automated review uses computer vision more aggressively now than in prior years. Promotional overlays (sale badges, free shipping banners, watermark text) flag as disapproval. Lifestyle or composite images often flagged for “image quality” even when high-resolution.

Image requirements that actually matter

Clean white or neutral background for non-lifestyle product shots. No promotional text, badges, watermarks, or overlays. Product is the dominant subject (no busy backgrounds).

Resolution: Google’s official minimum is 500×500 pixels. Warnings began April 14, 2026, with full enforcement starting January 31, 2027. This is a freshly active disapproval trigger many stores don’t know about, especially stores with catalogues built on older supplier image assets.

Operator recommendation: 800×800 minimum to comfortably clear Google’s bar and look sharp on retina displays. 1500×1500 or higher for apparel where detail matters.

File format: JPEG or PNG, sRGB colour profile.

Stores running catalogues built on older supplier image assets are frequently non-compliant without realising it. Audit image dimensions now if you haven’t recently. By 2027 the 500×500 minimum becomes a hard disapproval rather than a warning.

When lifestyle images are allowed

Acceptable for apparel and home goods where context matters. Must show the product clearly. Cannot have text overlays or promotional language. Avoid models posing in ways that obscure the product.

The image_link vs additional_image_link strategy

image_link should be your cleanest product shot (white background, no overlays, product centred). This is the asset Google’s automated review checks against image policy. Use additional_image_link for lifestyle or contextual shots that wouldn’t pass strict policy review on their own.

This separates compliance (image_link) from creative (additional_image_link). Operators who use lifestyle shots in image_link see far more image disapprovals than operators who follow this convention.

Landing page issues that trigger disapprovals

The feed can be perfect and products still disapprove if the landing pages fail Google’s checks.

The 404 or dead landing page problem

Products linked to deleted or moved pages disapprove immediately. The most common trigger is product page URL changes during site migration without redirects.

Fix path: 301 redirects from old URLs to new, or update feed URLs to point to the new structure. Whichever approach is faster given your platform.

Mobile usability failures

Pages must pass Google’s mobile usability tests. Common failures include text too small, tap targets too close together, content wider than screen, missing viewport meta tag.

Check via Google Search Console → Mobile Usability report for any page-level issues that might be cascading into Merchant Center disapprovals.

Landing page speed

Slow landing pages can trigger disapprovals, not just degrade Quality Score. Especially relevant for image-heavy product pages. Core Web Vitals metrics matter here, particularly Largest Contentful Paint on image-dominant pages.

Restricted product or content on the page

Even if the product itself is allowed, page content can trigger restrictions. Common triggers include weight loss claims, before-and-after images for cosmetics, supplement effect claims, financial promises.

For regulated categories, review the page copy for any phrasing that could be interpreted as a regulated claim. The product page itself often contains language the operator forgot was there.

AU operators specifically: Google’s Shopping ads political content policy update (effective April 16, 2026) requires election advertiser verification for any Shopping ad featuring political content in Australia. If your products, titles, descriptions, images, or landing pages could be interpreted as political content (campaign merchandise, political apparel, advocacy products), additional verification is required and some content categories are prohibited entirely.

AI-generated descriptions specifically: Google requires AI-generated content to be submitted via the structured_description attribute rather than the standard description field. Stores using AI for product descriptions and submitting via the wrong field can trigger disapprovals.

The reconsideration and appeal process

When to appeal vs when to fix and resubmit

Product-level disapprovals usually don’t need formal appeals. Fix the underlying issue, re-submit the feed, and the next feed processing cycle picks up the fix. No appeal required.

Account-level suspensions require a formal reconsideration request after fixes are complete. The “Request Review” button appears in Merchant Center once the suspension is active.

Edge case: products disapproved for “policy violation” with no clear cause may need a formal appeal even at product level, particularly for regulated categories where the disapproval reason is opaque.

How to submit a good reconsideration request

Be specific about what was wrong, what was changed, and why the change addresses the issue. Provide URLs to the updated pages. Link to specific sections that were updated, not just the homepage.

Don’t write generic appeals. Google’s reviewers see thousands of appeals and skip non-specific ones. The appeal that gets read first is the one with concrete evidence of fixes.

Document the identity verification step if you completed it. This is a 2026 addition many appeals skip.

Realistic timeframes

Product-level review after feed re-submission: 24-72 hours typically
Account-level reconsideration: 7-14 days typically, can be longer
During this window: don’t submit multiple appeals (resets the clock)

When appeals fail

After two rejected appeals, two paths forward exist: bringing in someone who has navigated multiple successful appeals, or creating a fresh GMC account with the underlying issues fully fixed (covered earlier in the account suspensions section).

Generic appeal advice doesn’t work for repeated rejections. The pattern of repeated rejections usually indicates a deeper issue the operator hasn’t identified.

Some accounts never get reinstated despite proper fixes. The fresh account path becomes the only practical option in those cases.

Prevention: proactive feed and account hygiene

The most expensive disapprovals are the ones that could have been prevented.

Weekly hygiene checks

Run the Diagnostics tab in Merchant Center weekly. Address warnings before they escalate to disapprovals. Warnings are notice periods (typically 7 or 28 days) before enforcement, so catching them at the warning stage saves the recovery cycle.

Monitor disapproval trends. A sudden spike usually indicates a recent change (site update, feed change, policy update on Google’s side).

Pre-launch checks for new products

GTIN validity (use a GTIN check tool or verify with manufacturer)
Image compliance (no overlays, clean background, minimum 500×500 actual size)
Landing page tested for mobile and page speed
All required attributes populated

After-site-change checks

Site migrations: ensure 301 redirects for all product URLs before launching. Theme updates: re-test mobile usability and page speed after deployment. Policy updates from Google: re-check returns, shipping, and contact info accessibility against the new requirements.

Feed cadence

Set feed updates frequent enough to match site state. For high-velocity stores with frequent price or stock changes, hourly or real-time updates may be required. For stable catalogues, daily updates may be sufficient.

The February 2026 GMC processing disruption demonstrated that stores with low-frequency feed updates were hit hardest. Stores using near real-time inventory synchronisation recovered faster. This is a structural argument for higher feed update cadence even outside of disapproval contexts.

When to consider professional help

Bringing in outside paid media help is the same decision regardless of which platform’s enforcement triggered the issue.

Signs you need help with disapprovals

Misrepresentation suspension that you’ve appealed unsuccessfully
Disapprovals affecting more than 30% of catalogue with no clear pattern
Variant structure issues that recur after fixes
Repeated suspensions despite stated fixes
Account in a regulated category (supplements, financial services, healthcare)

What a specialist actually does differently

Resolves misrepresentation suspensions by addressing the trust signal layer Google’s algorithm is actually checking, not just the obvious surface fixes
Audits the feed structure and identifies systemic issues, not just per-product fixes
Has appeal templates and submission strategies that work for repeated rejections
Knows when continued appeals are realistic vs when a fresh GMC account is the pragmatic path, and how to execute the fresh account path properly when chosen
Knows the policy interpretations that change quarterly and the enforcement patterns that aren’t documented publicly

For the broader question of whether to hire a Google Shopping specialist for ongoing work, when to hire a Google Shopping specialist walks through the signals that warrant Shopping-specific expertise versus generalist Google Ads support.

Frequently asked questions

My account got suspended for misrepresentation but my products are fine. What’s going on?

Misrepresentation suspensions are almost never about specific products. They’re about trust signals on the website overall: incomplete About Us, missing returns policy, unclear contact info, inconsistencies between Merchant Center and website data. As of 2026, also check the in-account identity verification step (Merchant Center → Business information). Business identity must match exactly across Merchant Center, Google Ads, and Google Payments. Many 2026 misrepresentation suspensions sustain through appeals because operators fix the website but miss the identity layer.

How long does it take to get an account un-suspended?

After submitting a reconsideration request with specific fixes: 7-14 days typically. Don’t submit multiple requests during the review window because it resets the clock. Each rejected appeal triggers progressively longer cool-down periods before the next can be submitted. After three failed appeals, reinstatement becomes substantially harder. Practical implication: fix everything before the first appeal. The first attempt is your highest-probability shot. After two rejected appeals, two paths exist: bring in a specialist who has navigated multiple successful appeals, or set up a fresh GMC account with the underlying website issues fully fixed first.

Should I fix the feed or the landing pages first?

Depends on the disapproval reason. Pricing or availability mismatches: fix the feed update cadence or the landing page data, whichever is faster. GTIN errors: feed only. Mobile usability failures: landing page only. Always check the specific disapproval reason in Merchant Center before assuming a fix path.

Can I just delete and re-create the disapproved products?

This usually makes things worse. Google’s policy enforcement is tied to your account, not specific product IDs. Re-creating a disapproved product without fixing the underlying issue results in immediate re-disapproval and can trigger account-level scrutiny.

What happens if I keep getting disapprovals for the same reason?

Repeated disapprovals for the same reason indicate a structural issue, not a per-product fix. Audit the entire product category or feed section affected. If still unresolved, consider professional help. The pattern usually points to something deeper than the specific symptom.

How do I avoid disapprovals when launching new products?

Pre-launch checklist: GTIN valid, images clean (no overlays or watermarks, minimum 500×500 actual size), all required attributes populated, landing page tested for mobile and speed, page content checked for restricted language. Catching issues before submission saves the re-review cycle.

Where Adgenix sits

Adgenix manages Google Shopping and Performance Max campaigns for ecommerce DTC brands across Australia. GMC disapprovals are one of the top three findings in audit-first engagements. Most stores have unresolved disapprovals they don’t realise are bleeding revenue.

Best fit: stores at $5,000 a month and up in monthly ad spend, 50 to 5,000 SKUs.

Google Shopping specialist track for stores where Shopping and PMax are the primary growth lever.

The Free Revenue Leak Report identifies what’s disapproved, what’s fixable, and what the revenue uplift looks like once the GMC and feed issues are resolved. No commitment beyond the audit. No sales calls during it. No hand-off to junior staff after.

Book the Free Revenue Leak Report.