Merchant Center

Google Merchant Center Product Disapprovals Explained

What a disapproved product actually means, where to find the real reason, and how to fix each common type of issue without making things worse.

A disapproved product can’t show in Shopping ads or free listings until the issue is fixed. Most disapprovals come from a small set of problems: missing or wrong product data, a mismatch between your product data and your website, or a page or image Google can’t use.

This guide is the hub for disapprovals. It explains how product issues differ from account issues, how to read the Needs attention tab, the main disapproval families with a link to the full fix guide for each, the difference between a website check and a review request, and how long each step takes according to Google’s documentation.

Short answer: A product disapproval means Google has blocked one product from Shopping ads and free listings because its data, landing page, image or content breaks a Merchant Center requirement or policy. Find the exact reason under Products > Needs attention, fix the source (website, product data or settings), then request a website check or review. Account-level issues are different and can affect every product.

Key Takeaways

  • Product issues affect individual items; account issues (warnings, suspensions) can affect every product.
  • Products > Needs attention and the Issue Details Page show the reason, affected items and suggested actions.
  • Fix the source of the problem, not just the copy in Merchant Center, or a sync can bring it back.
  • A website check can take up to 12 hours; a review request can take up to 7 business days.
  • Repeated price or availability mismatches can lead to account suspension, so recurring issues deserve real fixes.

What a product disapproval actually means

Google enforces its Shopping ads and listings policies with a mix of automated systems and human review. The enforcement actions it lists include disapproving listings, temporarily capping impressions for some accounts flagged by its systems, and suspending accounts for repeat or egregious violations.

A disapproval is the narrowest of these. It applies to a product (sometimes only for a specific country or marketing method), and the rest of your catalog keeps running. Google says you can fix or appeal a listing disapproval, and appeal an account suspension.

Not every flagged item is disapproved. Some issues only limit performance or show as a warning on the product. A missing description, for example, produces a warning and limited performance rather than a block. Read the status before deciding how urgent an item is.

Product issues vs account issues

Product-level issueAccount-level issue
ScopeOne product or a group of productsThe whole account, often every product
Typical causesMissing identifiers, price or availability mismatch, missing shipping, image problems, broken landing pageMisrepresentation, missing contact details or policies, website requirements not met, repeated violations
What you seeItem status and issue in Products > Needs attentionBanner on Home, summary card in Needs attention, warning or suspension email
Usual route backFix the data or page, then website check or reviewFix the website and account, then request a review (identity verification may be required)
Where to read moreMerchant Center diagnosticsaccount suspensions explained

The two are connected. Google states that repeated price mismatches may lead to account suspension, and that too many incorrect availability values risk the same. Treat a product issue that keeps coming back as an early warning for the account.

How to find the reason a product is disapproved

Everything starts on the Needs attention tab under Products. It is built to show the issues with the highest impact first.

Read the summary cards

At the top, up to three summary cards show the highest-impact issues, whether account-level or product-level, with the number of affected products. Each card offers options to fix the issue, view the affected products or view all issues.

Check the Prioritized fixes toggle

The Prioritized fixes toggle shows only medium- and high-impact issues. That is useful for triage, but it hides smaller issues. Turn it off when you want to see every issue in the account, for example during an audit.

Use click potential to sort the list

The full product list can be filtered by click potential, issue, status and title, and it can be downloaded. Click potential is rated High, Medium or Low based on past traffic, product data and demand. A blank value means Google is still estimating it.

Open the Issue Details Page

Selecting an issue opens its Issue Details Page (IDP). It shows an overview of the issue, suggested actions (such as automatic improvements or an appeal), the business impact and samples of affected products. Read the overview before changing anything: the wording usually tells you which attribute or page element Google compared.

Look at the product’s history

View history shows how a product’s status changed over time, with filters for time, country, product type and status. It helps you see whether an issue started after a site change, a feed change or an app update.

Write down the exact issue name, the affected item IDs and the date the issue first appeared before you change anything. It makes it much easier to tell later whether your fix worked.

Deciding what to fix first

When many issues appear at once, a simple order of work keeps you focused on what matters:

  1. Account-level issues first. A warning or suspension can stop every product, and warnings have a deadline.
  2. Issues that put the account at risk. Price and availability mismatches can escalate if they keep repeating.
  3. High click potential products. These are the items Google expects to get the most traffic.
  4. Issues affecting many products. One fix in your platform or data source often clears hundreds of items.
  5. Warnings and recommended attributes. These limit performance but do not block products.

Group issues by cause, not by product. Fifty disapprovals for missing GTINs usually share one root cause, such as a field your platform never sends to Google.

The main disapproval families and how to fix each

Most product disapprovals fall into one of the families below. Each has its own detailed guide.

FamilyWhat Google foundFull guide
Product identifiersGTIN, brand or MPN missing, incorrect or used where none existsFix missing product identifiers
Price mismatchPrice in your data differs from the landing page or structured dataFix price mismatches
Availability mismatchStock status in your data differs from the landing pageFix availability mismatches
Missing shippingNo shipping cost for a country where shipping is required, or a currency mismatchFix missing shipping information
Return policyReturn policy missing or inconsistent with your siteFix missing return policy information
ImagesPromotional overlays, placeholders, unsupported formats or uncrawlable imagesFix product image issues
Landing pageProduct page returns an error, redirects too often or can’t be crawledFix landing page errors
Data source and formattingInvalid values, wrong attribute formats, processing errorsDiagnose data source errors

Product identifiers

Google asks for brand plus GTIN or MPN according to its unique product identifier rules. Products that have a GTIN but are submitted without it may have limited visibility, and identifiers that are made up, guessed or copied from similar products can cause disapproval. Custom, handmade, vintage and one-of-a-kind items have their own rules, including identifier_exists.

Price mismatch

Googlebot crawls your landing pages and compares the price in your data source with the price on the page or in structured data. Common causes are a slow feed schedule, sale prices handled differently on the site and in the feed, prices injected with JavaScript after the page loads, and currency differences.

Availability mismatch

The availability value in your data must match the landing page. The most common cause is timing: stock changes on the site before the next product data update. Using out_of_stock to pause products is another, because Google wants pause or excluded_destination for that.

Missing shipping information

In countries such as the US, Canada, the UK, Australia, Germany and the Netherlands, Google requires shipping settings or the shipping attribute. Items can also be disapproved if no shipping service matches the product’s currency and target country.

Return policy issues

Your website must state a return and refund policy, even if you don’t accept returns. Return policies configured in Merchant Center must be clear, accessible without a login, and consistent with what your site says, according to Google’s return policy requirements.

Image problems

Images with promotional overlays (calls to action, price text, watermarks, added logos), placeholders such as “No image available”, borders, or the same photo reused across different products can be disapproved. Images Googlebot can’t crawl, or with a file extension that doesn’t match the real format, cause issues too.

Landing page errors

If the page in your link attribute returns a 404, a server error, too many redirects or a DNS failure, the product is disabled until the page is accessible again. Google recommends no more than two redirects.

Policy violations

Some disapprovals have nothing to do with data quality. Products in prohibited or restricted categories (for example, counterfeit goods, dangerous products, or restricted areas like alcohol, healthcare and medicines) can be disapproved or limited under the Shopping ads and listings policies. These usually need a decision about the product itself, and sometimes preauthorization, rather than a data fix.

When the cause is the whole website

If many products are disapproved for reasons like misrepresentation or missing business information, the problem is usually account-level. See how to troubleshoot misrepresentation and the account warning guide.

Fixing one product vs many products

Google’s fix articles describe two routes, and choosing the right one saves time.

SituationRouteWatch out for
A handful of productsProducts > Needs attention > open the product > Edit productIf the product comes from a feed or app, the next sync can overwrite your edit
Many productsDownload the affected products as a .csv, fix the values in your source, then re-upload or resyncFix the source system (platform, feed plugin, spreadsheet), not only the export
Shopify, WooCommerce or another platform appEdit the product in the platform and let the app syncFollow the platform’s instructions; Merchant Center edits may not stick
A value you can’t change at the sourceSupplemental data source or attribute rulesBoth need the Advanced data source management add-on in many setups

Attribute rules (previously called feed rules) can transform values in bulk, for example appending a brand or setting a value based on conditions. They are covered in the feed rules guide, and supplemental sources in the supplemental feeds guide.

Automatic fixes and suggested values

Some issues offer an automatic fix that Google applies as a persistent rule, or suggested attribute values. Google advises checking suggested values against your landing page before accepting them. Accepted fixes override later changes from other methods, such as file uploads, so a wrong suggestion can stick. You can view and revert them from the product’s Edit product screen.

For price and availability, automatic item updates (the Automations tab) can correct occasional mismatches using your landing page data. Google designed it for sporadic problems on a small share of products, not as a replacement for regular data updates.

Website check vs review request

After fixing an issue, there are two ways to ask Google to look again. They are not the same thing.

Website checkReview request
Use it whenYou changed the website or data so it now matches (price, availability, landing page)You fixed a policy issue, or you believe the issue is wrong
WhereOffered on the issue after you fix it“I disagree with the issue” > Request review, or Request review in the account’s issue view
How longUp to 12 hours; you can’t submit a new request during that timeUp to 7 business days
LimitsOne check at a timeLimited number of attempts; cool-down periods can apply

Google’s review request documentation says you may only get one chance to disagree in some cases. After a second unsuccessful attempt, a cool-down of about a week may begin, and it can get longer with later attempts. Google support can’t shorten it.

That is why the order matters: fix first, confirm the fix by hand, then request. Our guide to preparing for a Merchant Center review covers what to check before you submit.

Steps after a fix

  1. Confirm the fix on the live page (view the page as a logged-out visitor, and check structured data where relevant).
  2. Confirm the corrected value has reached Merchant Center, through a sync, upload or reprocessing of the data source.
  3. Request a website check if the issue offers one, and wait for it to finish.
  4. If the issue persists and you are confident it is resolved, use “I disagree with the issue” to request a review.
  5. Check Needs attention and the product’s history over the following days.

How long things take

These timings come from Google’s Merchant Center Help articles. They are upper limits or typical ranges, not guarantees.

StepTiming per Google
Website check after a fixUp to 12 hours
Re-crawl of disapproved products after a price fixOver the next few hours or days (subject to your server’s crawl capacity)
Landing page errors clearing after a fixWithin a couple of days
Review requestUp to 7 business days (an article for Shopify app users says typically 3 to 7 business days)
Approved products becoming eligible after a reviewWithin about 24 hours
robots.txt changes affecting image crawlingMay take 24 to 48 hours
GTIN fixes showing in Needs attentionTakes time to reflect (no fixed period given)
Cool-down after a second unsuccessful reviewAbout a week, can increase for later attempts

If nothing has changed after these periods, recheck the source data before submitting again. The usual reasons are a sync that overwrote the fix, a cached page that still shows the old value, or a second issue on the same product.

Preventing disapprovals from coming back

Most recurring disapprovals have a process cause. A theme update changes how prices render, an app starts sending a new field, or the feed runs once a day while stock changes every hour. A short routine catches these early.

  • Check Needs attention weekly with Prioritized fixes turned off.
  • Schedule product data updates to match how often prices and stock change on your site.
  • Put product structured data in the initial HTML so Google sees the same price and availability as shoppers.
  • Re-test a sample of product pages after theme, app, currency or checkout changes.
  • Keep a simple change log of feed, app and site changes so you can match them to new issues.
  • Store identifiers (GTIN, MPN, brand) in your platform, not only in a spreadsheet or feed tool.
  • Keep shipping, returns and contact details consistent between your site and Merchant Center.
  • Use pause or excluded_destination to hide products temporarily, not out_of_stock.

For a fuller routine, see the product feed optimization checklist.

When to get help

Most single-issue disapprovals can be fixed in-house with the guides above. Outside help makes sense when the same issue keeps returning after fixes, when many issue types appear at once after a migration or app change, when a review has already been rejected, or when product issues start to look like an account-level problem.

We diagnose the cause in your website and product data, fix it at the source and prepare review requests through our Merchant Center disapproval service. Google makes the final decision on every review, and we don’t have special access to Google support.

Frequently asked questions

How long does it take for a disapproved product to be approved again?

It depends on the route. A website check can take up to 12 hours, a review request up to 7 business days, and Google says approved products become eligible within about 24 hours.

Will a product disapproval affect my whole account?

A single disapproval affects only that product. Repeated price or availability mismatches can, according to Google, lead to account suspension, so recurring issues should be fixed at the source.

Why did my product get disapproved again after I fixed it in Merchant Center?

Usually because your platform, app or feed sent the old value again on the next sync. Fix the value in the system that supplies your product data, then let it sync.

What does click potential mean in Needs attention?

It is Google’s High, Medium or Low estimate of a product’s potential traffic, based on past traffic, product data and demand. A blank value means Google is still estimating.

Should I request a review or a website check?

Request a website check when you’ve changed your site or data so it now matches. Request a review when you believe the issue is wrong or you fixed a policy issue. Reviews are limited and can trigger a cool-down.

Can I delete disapproved products and re-add them?

Google advises against deleting items to hide them because re-added items take significant time to show again. Fix the issue, or use pause or excluded_destination.

Need help fixing disapprovals?

We find the real cause of disapprovals in your website and product data, fix it at the source and prepare honest review requests.

Sources

Last reviewed October 10, 2026 against the official documentation listed above. Google changes Merchant Center features and policies regularly — always confirm details in your own account.

Similar Posts