Merchant Center Product Disapproval: Causes and Fixes

Short answer
How do you fix a Merchant Center product disapproval?
A Merchant Center product disapproval means Google will not show one of your products in Shopping ads and free listings. To fix it, open the Needs attention tab, read the cause, correct your product data or store, and then request a review. The order matters: fix first, review second.
This guide focuses on one job: getting a disapproved product live again. We covered price mismatch and account level misrepresentation in separate articles, so here we only point you to them.
As Talha Aslan and our team, we handle this work in the same order every time. First, we separate the type of problem. Then we decide whether the cause sits in the product data or in the store website. Finally, we make the fix and only then ask for a review. We cannot promise an outcome, because Google decides. Still, the right order protects your limited review attempts.
So you should keep two things in mind while reading. First, every disapproval has its own root cause, so no single magic fix exists. Second, menu names and message texts change over time. So follow the logic we describe, and do not cling to one screenshot.
Where does a Merchant Center product disapproval show up?
First, product level problems appear in Merchant Center under Products, in the Needs attention tab. The list carries the heading "All products that need attention." Menu names can change, so look for the matching section in your panel.
In this tab you can do the following:
- Filter issues by impact, labels, status, or title with the filter icon.
- Also, download the affected items as a spreadsheet file with the download icon.
- Open the details page of each issue to read its impact, example products, and fix steps.
Problems that affect the whole account sit in a banner at the top and behind the "View setup and policy issues" link. Also, the split between product level and account level matters. So you fix a product problem by correcting data. In contrast, an account problem usually needs a change on your store website or in your business details. For the official wording, read the Help page on issues in Merchant Center.
What is the difference between a warning, a disapproval, and a suspension?
First, not every issue carries the same weight. The Merchant Center Help page separates four states. So if you know which one you face, you can set the right urgency.
| State | What it means | What you do |
|---|---|---|
| --- | --- | --- |
| Warning | The product keeps showing, but performance may suffer | Fix it, because an open warning can turn into a disapproval |
| Disapproval | Google stops showing the product everywhere | Fix the cause, then request a review |
| Preemptive item disapproval | A precaution when price or availability may not match | Match your data to the page, then request a review |
| Suspension | Products stop showing when an account problem stays open | Resolve the setup and policy issue |
The Help page also notes that severe violations can lead to a suspension without a warning period. So do not postpone a warning. For price and availability trouble in detail, read our guide on the Merchant Center price mismatch error.
In what order should you investigate a Merchant Center product disapproval?
In practice, random fixes use up your review attempts. Instead, follow one fixed order. It starts with the cheapest and most likely cause.
- Write down the name of the disapproval and the number of affected products.
- Then open the issue details page and pick one example product.
- Then open the same product on your store and compare the data with the page.
- Look for the cause in the product data, the image, the category, or the store website.
- Also, make the fix at the source, not only as a temporary edit inside Merchant Center.
- Wait for the data to refresh, then check whether the issue disappears.
- If it is gone, wait. If it remains, request a review.
Here is a sample scenario. For example, a store has one hundred products disapproved on the same day. Then the details page shows a shared cause, such as a missing brand. Next, the store fills the brand column in the source sheet and resends the data. So one fix can rescue all products at once. Always look for the shared cause first.
If you manage a very large catalog, feed rules and platform connections become a specialty of their own. In that case, experienced ecommerce consulting saves more time than fixing products one by one.
Do product identifier errors (GTIN, MPN, brand) trigger disapprovals?
Yes, and this is the most common group. Specifically, Merchant Center matches a product by its identifiers. If an identifier is missing, wrong, or in conflict with the brand, Google will not show the product.
The Help page lists these cases: invalid or missing GTIN, a GTIN of the wrong length, an invalid MPN, a missing brand, and a GTIN that does not belong to the submitted brand. To fix them, do the following:
- Enter the real GTIN from the manufacturer. Never invent a barcode.
- Also, do not type placeholders such as "N/A" or "Generic" in the brand field.
- For products you make yourself, use your own store name as the brand.
- Likewise, for custom or handmade items that have no GTIN, mark that in the data.
One subtle point remains. However, the GTIN must belong to the matching brand. For US brands, the Help page points to the GS1 verification tool. So do not pair a wholesale barcode with another brand name.
Also, take the barcode only from the product box or the manufacturer's paperwork. Filling the field with a guessed number may cut your disapproval count in the short run. However, Google checks the match, and a caught conflict can reach beyond the product level.
How do image problems cause a Merchant Center product disapproval?
Above all, images are the most overlooked cause. That said, you may like the picture, but policy is a separate rule. The Help page separates three image problems.
- Generic image: A logo, a placeholder, or a "no image available" graphic as the main image triggers a disapproval. Upload a photo that clearly shows the product.
- Promotional overlay: A store logo, a call to action, or a watermark on the image triggers a disapproval. Use a clean product photo.
- Image too small: An image below the minimum size triggers a disapproval. Do not scale a small file up. Upload a larger source file.
The official page advises that the product should fill most of the frame. Minimum pixel values differ by product type, so check the current numbers in the product data specification. We do not hard-code them here.
Merchant Center also has an automatic image improvement option for overlays. It tries to remove the overlay by itself. However, it may not succeed on every image, so still prepare a clean main image.
First, shoot the product on a plain, light background. Then let the product fill most of the frame and add no text, frames, or badges. Also, lifestyle photos work as extra images, but the main image must stay clean. So keep promotional badges in a separate file.
Why do titles and descriptions cause a product disapproval?
Put simply, a title and a description must say what the product really is. The Help page expects the title and description to match your store page. It also treats excessive capitalization as a problem.
In practice, we see these mistakes:
- A title written in all capital letters, or one stuffed with symbols for attention.
- Promotional phrases such as "free shipping" or "cheapest" inside the title.
- A description that differs from the page, or one left empty.
- Placeholder text left in place.
The fix is simple. First, write the title with the product name, brand, type, and one distinguishing feature. Then move promotional sentences out of the title and into the description or the ad copy. Our guide on SEO friendly product descriptions helps with the writing.
One platform detail also matters: fix the field that your store platform actually sends to Google. In practice, if you correct the wrong field, Merchant Center keeps showing the same issue.
How do you fix an invalid Google product category?
Also, the category field must match Google's product taxonomy. If the field holds an invalid value, the product gets a disapproval. The Help page gives two valid formats: the numeric ID or the full category path.
Here is a sample scenario. An apparel store typed only the last segment, the product type, into the category field. However, according to the Help page, a last segment alone fails. Then, once the store wrote the full path or the numeric ID, the issue closed.
Run these checks:
- Confirm that the category field is not empty.
- Compare the value with the official Google product taxonomy list.
- If you use a numeric ID, verify that the ID is current.
- Apply the same category to all similar products with one bulk rule.
Also, a feed rule saves time and keeps values consistent. However, test the rule on a few products first. Otherwise a wrong rule can disapprove hundreds of products at once.
Instead, pick the most specific correct branch. Instead of a broad branch such as "Apparel," use the closest sub branch. That way Google can match the product to the right searches.
How do you fix missing size, color, gender, and age group on apparel?
First, apparel and accessories need extra fields. If these fields are missing, the product gets a disapproval. The Help page names four fields: gender, size, color, and age group.
| Field | Correct use | Common mistake |
|---|---|---|
| --- | --- | --- |
| Gender | One of male, female, or unisex | Typing free text |
| Size | A consistent format, OS or OSFA for one size items | Splitting dimensions into two fields |
| Color | A recognizable color name, slashes for several colors | A non color value such as "multicolor" |
| Age group | newborn, infant, toddler, kids, or adult | Leaving the field empty |
According to the Help page, you may skip size and color if the variants already carry them. For the structure and SEO effect of variants, see our guide on product variants, size, and color SEO.
Also, write the values in the format Merchant Center expects. Your store panel may show a local label, yet the value sent in the feed must still follow the pattern.
What should you do about a price or availability mismatch?
If the price or the stock status differs between your feed and your store page, Merchant Center can apply a preemptive disapproval. This is a separate, detailed topic, so we do not repeat it here. In short, the logic is as follows.
The Help page expects the price to match on the product page, in structured data, and at checkout. Likewise, the same three places apply to availability. So instead of changing a price in the store and then waiting for the feed, turn on automatic updates. Our article on Google Merchant Center automatic item updates explains how that option works.
Out of stock products also matter. Also, deleting or redirecting a page affects the disapproval risk. For the SEO side, see out of stock product pages. To learn how price and stock appear in search results, read how to show price and stock in Google results.
One more tip: prices change often during campaigns. So in that period, review how often your feed refreshes. If the price changed on the page but the feed stayed old, the visitor and Google see different prices. In practice, the usual result is a preemptive disapproval.
Can store website problems cause a product disapproval?
Yes. The Help page names several typical store problems: placeholder content, broken links, mismatched categories, a robots file that blocks Googlebot, and slow or unavailable product pages.
To check, do these things:
- Crawl your product links in bulk and find the broken ones.
- Look in your robots file for a rule that blocks product pages.
- Confirm that product pages open in a reasonable time on a phone.
- Remove placeholders such as "lorem ipsum" that stayed on test products.
Our free tools help here. The broken link checker scans your product links. If you want to write or review a robots file, open the robots.txt generator.
If your product pages do not get indexed at all, that may have a separate cause. In that case, read why product pages are not indexed.
How do you tell a product disapproval from an account level problem?
However, sometimes not one product but all products disappear. In short, that signals an account level setup or policy problem. So you should not confuse it with a product level disapproval.
Use these hints to tell them apart:
- If all products suffer at the same moment, suspect an account level issue.
- If a banner with a "Review and fix" or "Fix" button sits at the top, it is a setup and policy issue.
- If only some products suffer and the details page talks about product data, it is a product level issue.
Also, misrepresentation or store transparency changes the scale of the work. You must verify your business details, your return and contact pages, and the match of price and stock. We cover this in detail in Merchant Center misrepresentation suspension fix. Do not try to dodge the system by opening a new account or using forged documents. Those count as circumvention, so they make things worse.
Where do you make the fix: at the source or in a rule?
First, for a lasting fix, you must go to the source. The official Help page tells you to fix product level issues by correcting the product data and uploading it again. Otherwise a temporary edit can break again in the next data run.
You have three routes:
- Fix at the source: Change the field to the right value in the store panel or the sheet. This is the most durable method.
- Fix with a rule: Use a feed rule to build or format a field in bulk. Test the rule on a small group first.
- Fix automatically: Merchant Center automatic improvements try to correct some errors in the base data.
If you use a third party platform, you often request the review through that platform too. Then make sure the platform maps its data fields to Google's fields correctly. Otherwise a mapping error can send a correct value into the wrong field.
How do you request a review?
After that, you ask Merchant Center for a review. The Help page offers two options: "I fixed the issue" and "I disagree with the issue." Then you press "Request review."
Choose the option like this:
- If you really fixed the problem, pick "I fixed the issue."
- If you believe the finding is wrong, pick "I disagree with the issue." Google may ask for more information or documents.
- For a product level issue, start from the "Fix" button next to the product in the Needs attention tab.
One limit matters: according to the Help page, you get only one chance to disagree with an issue. So use that route only when you are sure you are right. Also check the official request a review page for review times. Times change, so we do not write numbers.
What if the Request review button is inactive?
However, sometimes the "Request review" button looks unavailable. The Help page lists the typical reasons. So each one has a different fix.
| Reason | What you do |
|---|---|
| --- | --- |
| Merchant verification is incomplete | Finish the verification |
| The data source is empty | Add at least one product under All products |
| A product level review needs a site check | Use the "Request website check" option |
| A cool down period is running | Wait for the period to end |
A cool down can start after you used the disagree option and tried to fix the issue. During this time the button stays inactive, and the Needs attention tab shows when it opens again. According to the Help page, Google support cannot shorten this period.
Do not sit idle while you wait. Recheck your store transparency, your contact details, and the match between product data and website. That way your next review goes in with a stronger case.
How do you summarize the causes in one table?
The table below sums up the causes we see most often, together with the direction of the fix. Menu and message texts can change, so use the table as a checklist, not as an exact message pattern.
| Cause | Likely source | Fix |
|---|---|---|
| --- | --- | --- |
| Missing or invalid GTIN | Product data | Get the real GTIN from the manufacturer |
| Missing or placeholder brand | Product data | Enter the real brand name |
| GTIN and brand conflict | Product data | Supply a GTIN that belongs to the brand |
| Generic image | Image | Upload a photo that shows the product |
| Promotional overlay | Image | Use a clean image |
| Image too small | Image | Upload a larger source file |
| Excessive capitalization | Title | Rewrite the title in plain case |
| Invalid product category | Category field | Enter the full path or numeric ID |
| Missing size, color, gender, age group | Apparel fields | Fill in the required fields |
| Price or availability mismatch | Feed versus page | Match the data, turn on automatic updates |
| Broken link, slow page | Store website | Repair and speed up the page |
One product can appear in several rows. That is normal, because a product can carry several causes at once.
Which fields does the product data specification require?
The strongest way to prevent a disapproval is to follow the specification from the start. Google's product data specification lists which field is required. The summary below covers the core fields that we confirmed on the official page.
- id: A unique identifier for the product.
- title: The name of the product.
- description: The description of the product.
- link: The landing page address of the product.
- image_link: The address of the main image.
- price and availability: The price and the stock status.
- brand: Required for most new products, with exceptions such as books and movies.
- gtin: Supply it when it exists. The specification strongly recommends it.
- mpn: Required when the product has no manufacturer assigned GTIN.
An `identifier_exists` field also exists. If you do not send it, the default value counts as "yes." Set it to "no" only when the product truly has no identifiers. You can read the whole specification on the product data specification page.
Does structured data prevent a product disapproval?
It does not prevent one directly, but it strengthens the match between price and stock. The official specification expects the price to stay consistent on the product page, in structured data, and at checkout. Structured data is the machine readable part of that consistency.
Take these practical steps:
- Generate the price and stock on the page and in the structured data from the same source.
- Show the sale price clearly on the page.
- For preorder products, state the date on the page.
- Retest the structured data after every change.
If you do not want to write the format from scratch, our schema generator builds a basic product schema. To learn the concept, read what schema markup is. Schema alone does not solve a disapproval. Still, it narrows the gap between page and data.
How do you prioritize when many products get disapproved?
If hundreds of products get a disapproval at once, do not panic. Sort the issues by impact. The Help page notes that the "Prioritized fixes" toggle hides low impact issues and surfaces medium and high impact ones.
Prioritize with this path:
- Download the list of affected products as a spreadsheet.
- Group the products that share one cause.
- Solve the single cause that hits the most products first.
- Handle the items that a single rule or bulk edit can fix right away.
- Leave the few products that need manual work for last.
This approach pays off when the same root cause repeats across hundreds of rows. One brand field fix can rescue hundreds of products. Keep in mind that Prioritized fixes works only in accounts where Google can estimate potential product performance. If you do not see it, you must rank the issues yourself.
What should you watch after the fix?
You made the fix and sent the review. Now watch the result. According to the Help page, approved products can show across Google again after a short time. Still, check the current timing on the official page.
Watch these points:
- Whether the issue disappears from the Needs attention tab.
- Whether the products show again in Shopping ads and free listings.
- If spend and impressions recover in your ad campaign.
- Whether the same cause repeats on newly added products.
If you run Performance Max or a standard Shopping campaign, disapproved products drag down your campaign. So check the campaign side too. For the setup logic, see how to set up Performance Max for ecommerce. For the general workings of Shopping ads, what Google Shopping ads and free listings are is a useful read.
How do you stop the disapproval from coming back?
A disapproval you fixed once can return when you add new products. So turn the process into a rule. A small checklist for new products blocks most repeats.
When you add a product, check these items:
- Are the real GTIN and the brand filled in?
- Is the main image clean, large enough, and showing the product?
- Does the title follow plain case rules and avoid promotional phrases?
- Did you enter the Google product category with the full path or ID?
- For apparel, are gender, size, color, and age group filled in?
- Do price and stock match between the product page and the feed?
- Does the product link open fast and lead to the right page?
Share this list with everyone who adds products. A short glance at the Needs attention tab each week also gives a good early warning. To strengthen the product page itself, read the ecommerce product page guide.
When does a Merchant Center disapproval call for an ecommerce consultant?
You will solve most disapprovals yourself. Identifier, image, title, and category fixes need no special skill. In some situations, however, outside help saves time and review attempts.
These signs say it is time:
- You have thousands of products and complex feed rules.
- You keep receiving the same disapproval even after you fixed it.
- An account suspension and a product disapproval have tangled together.
- The platform, the feed, and the ad account sit with different people, and nobody sees the whole.
In such a case, working with an ecommerce consultant to review product data, store website, and ad account together makes sense. As Talha Aslan and our team, we first separate the root cause of the disapproval. Then we list the order of the fixes. We do not promise that the disapproval will lift, because Google decides. We do, however, make clear what was disapproved, why, and in which order you should fix it.
If you want to do it yourself, follow the order in this guide. Separate the cause, fix the source, and request the review last. That order protects both your time and your limited review attempts.
Core guide: What Is Digital Marketing? Its types, examples and how it is done, on one page with an interactive film that travels through the brain.



