Merchant Center Disapprovals: Common Causes and How to Fix Them

The short answer

Merchant Center disapprovals stop or limit products before your Shopping campaigns get a fair chance. If important products are disapproved, limited, or affected by diagnostics, campaign optimisation will not solve the real issue.

The first job is to separate small hygiene problems from issues that affect revenue.

Types of Merchant Center problems

Not every issue has the same urgency.

Issue type	What it means
Disapproved products	Products cannot serve until fixed
Limited products	Products may serve with reduced visibility
Account warnings	Broader issue that can escalate
Price mismatch	Feed price and landing page price do not align
Availability mismatch	Feed says in stock but page says otherwise, or the reverse
Missing identifiers	GTIN, MPN, or brand data may be incomplete
Image issues	Image does not meet requirements or is low quality
Policy issue	Product or landing page may violate Google policy

The commercial question is: which issues affect products that matter?

Price mismatches

Price mismatches are common and frustrating.

They happen when the price in the feed does not match the price on the landing page. This can be caused by sale prices, variants, currency, tax, dynamic pricing, delayed feed updates, or page markup issues.

Fixes can include:

• Updating feed price more frequently
• Using sale price fields correctly
• Checking variant URLs
• Making sure structured data matches the visible page
• Reviewing tax and shipping handling
• Checking feed app timing

For high-volume products, price mismatches can quietly damage Shopping performance.

Availability mismatches

Availability issues happen when Google sees a different stock status from the feed or page.

Common causes:

• Slow feed updates
• Variant-level stock problems
• Products marked in stock but unavailable at checkout
• Pre-order products handled incorrectly
• Landing page caching
• Feed app sync delays

If stock changes quickly, feed freshness matters. A product that sells out regularly may need more careful budget control as well as feed fixes.

Missing identifiers

Identifiers help Google understand products.

Depending on the product, important fields can include GTIN, MPN, and brand. Missing or incorrect identifiers can affect eligibility, matching, and trust.

Do not invent identifiers. If a valid GTIN exists, use it. If it does not, handle the identifier fields correctly rather than guessing.

Image issues

Images affect both eligibility and performance.

Problems can include overlays, promotional text, watermarks, low resolution, broken URLs, placeholder images, or images that do not match the variant.

Even when images are approved, weak images can hurt click-through rate. A technically valid image is not always a commercially strong image.

Policy issues

Policy issues need careful handling.

Some are straightforward: missing returns information, unsupported claims, restricted products, unclear pricing, or landing pages that do not meet requirements.

Others need deeper review. Do not repeatedly resubmit without understanding the issue. That can waste time and may make the account riskier.

How to prioritise fixes

Prioritise by impact:

1. Account-level warnings
2. Disapprovals affecting best sellers or high-margin products
3. Issues affecting whole categories
4. Price and availability mismatches on high-spend products
5. Missing identifiers across important brands
6. Image issues affecting products with demand
7. Low-priority hygiene fixes

This keeps the work commercial. Not every warning deserves the same urgency.

How disapprovals affect agency work

A Google Shopping agency should not ignore Merchant Center. If products are not eligible or trusted, bidding changes are secondary.

The agency should be able to tell you:

• Which issues affect revenue
• Which issues need feed changes
• Which issues need website changes
• Which issues need policy review
• Which products should be paused or excluded
• Which fixes should happen first

The answer should not simply be "ask your developer". It should be a precise diagnosis.

Prevention

Prevention is better than emergency fixes.

Set a rhythm for checking diagnostics, especially before launches, sales, catalogue changes, feed migrations, or major pricing updates.

If your catalogue is large, build a process for monitoring issues by product group and commercial value. A disapproval on a hero product should not sit unnoticed for weeks.

What to document

Keep a simple issue log for Merchant Center problems.

Document the affected products, issue type, likely cause, owner, fix date, and whether visibility recovered afterwards. This helps avoid solving the same problem every month.

It also makes developer, feed-app, and ecommerce-team conversations much easier because the problem is specific rather than vague.

When to request a review

Request a review only after you understand and fix the issue. Repeatedly requesting review without changing the underlying problem wastes time.

For policy-sensitive products, read the policy carefully, check the landing page, check claims, check imagery, and make sure the feed reflects the product accurately.

For price or availability issues, check the product page, structured data, variant URLs, feed timing, and cache behaviour before assuming Google is wrong.

Commercial impact example

Imagine 3% of products are disapproved. That sounds small. But if those products include your top-margin best sellers, the impact is not small.

This is why disapproval reporting should be weighted by revenue, margin, and strategic importance, not only product count.