{"id":4385,"date":"2026-07-28T17:02:02","date_gmt":"2026-07-28T14:02:02","guid":{"rendered":"https:\/\/ivitskiy.com\/blog\/?p=4385"},"modified":"2026-07-28T17:02:02","modified_gmt":"2026-07-28T14:02:02","slug":"merchant-center-product-disapprovals","status":"publish","type":"post","link":"https:\/\/ivitskiy.com\/blog\/en\/merchant-center-product-disapprovals\/","title":{"rendered":"Why products get disapproved in Merchant Center"},"content":{"rendered":"\n
In short:<\/strong> Merchant Center has three distinct states, and confusing them is expensive. A warning: the product still shows, but performs worse. A disapproval: the product stops showing. An account suspension: the entire catalogue goes dark. The timings differ too: a recrawl after a fix usually clears in 24-48 hours, the initial review takes up to 3-5 business days, and a review after an account suspension can take up to 7 days. Below: how to read your product status to tell which state you are in, what to do in each, and what an appeal should actually contain.<\/div>\n\n\n\n

The familiar pattern: a merchant sees red in the console, spends an evening rewriting product titles, checks in the morning and nothing has changed. Then comes a second round of edits, then a third, and finally the conclusion that «Google broke something». In reality the problem is almost always that nobody knows which state they are actually in, or how long that state lasts.<\/p>\n\n\n\n

Start with the product status<\/h2>\n\n\n\n

This is the shortest route from «something is red» to knowing what is happening. Google shows five product states in the console, and each one means something specific.<\/p>\n\n\n\n

\n
Status<\/th>What it means (verbatim from the documentation)<\/th>What to do<\/th><\/tr><\/thead>
Processing<\/strong><\/td>«Google is processing updates to the product, which may take up to 15 minutes»<\/td>Nothing. You just changed something, give it 15 minutes<\/td><\/tr>\n
Under review<\/strong><\/td>«Google is reviewing the product for any issues. Reviews may take up to 3-5 business days for Shopping ads»<\/td>Wait. Editing now only lengthens the queue<\/td><\/tr>\n
Approved<\/strong><\/td>«Google has completed reviewing the product, and the product is now showing on Google»<\/td>Nothing, the product is working<\/td><\/tr>\n
Limited<\/strong><\/td>«The product is showing on Google, but only in some instances, or all of the product data may not be shown on the ad»<\/td>Showing, but not everywhere. Look for what the data is missing: this is your time budget, before anything is switched off<\/td><\/tr>\n
Not approved<\/strong><\/td>«The product can’t be shown on Google. There may be one or more errors that are preventing it from showing»<\/td>The product is off. Read the stated cause literally and fix it<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

Source of the wording: Google’s documentation on product statuses<\/a>. The most useful thing here is that Processing and Under review are not problems, they are waiting. Half of all «endless editing» starts with someone rewriting a product that has not even been reviewed yet.<\/p>\n\n\n\n

Three states that all look equally red<\/h2>\n\n\n\n
\n
State<\/th>What happens to impressions<\/th>Scope<\/th>How long<\/th><\/tr><\/thead>
Warning<\/strong><\/td>The product keeps showing, but performance is limited<\/td>Individual products<\/td>You still have time before consequences<\/td><\/tr>\n
Product disapproval<\/strong><\/td>The product stops showing<\/td>Individual products<\/td>24-48 hours after the updated data reaches Google<\/td><\/tr>\n
Account suspension<\/strong><\/td>Every product is switched off<\/td>The whole catalogue<\/td>Up to 7 days for review<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n\n

There is an important detail in the timing column: the clock starts not when you fixed something on the site, but when the updated data reached Google. Those are two separate events, and conflating them is exactly what makes fixes look ineffective.<\/p>\n\n\n\n

The verbatim wording leaves no room for interpretation. On warnings: «Products that receive warnings will continue to show across Google, however their performance may be limited»<\/a>, so the product is alive, just weaker. On disapprovals, same page: «Disapproved products stop showing across Google», so there are no impressions at all. On the account: «Your account will be suspended and your products will be disabled from appearing across Google», so everything goes off.<\/p>\n\n\n\n

The practical takeaway for an owner: a warning is a time budget, not an interface glitch. Merchants routinely ignore yellow until it turns red, when yellow is exactly the state in which everything can be fixed calmly and without losing a single impression.<\/p>\n\n\n\n

«I fixed everything and nothing changed»<\/h2>\n\n\n\n

The most common question has the simplest answer: you are looking too early. Google re-reads the corrected data, and the documentation states that after edits issues «usually resolve within 24\u201348 hours»<\/a>. The initial review of a new catalogue, meanwhile, takes up to 3-5 business days for Shopping ads and may take longer for other programs.<\/p>\n\n\n\n

Which gives you a working routine:<\/p>\n\n\n\n

    \n
  1. Fix the whole batch of causes at once,<\/strong> not one at a time. Every iteration costs you a day or two of waiting, so ten fixes in one pass is far cheaper than ten passes.<\/li>\n
  2. Confirm the update actually reached Google.<\/strong> You changed the data on the site, but the product table may not have refreshed yet. These are two separate events, and the clock starts on the second one.<\/li>\n
  3. Give it 48 hours<\/strong> before drawing any conclusion.<\/li>\n
  4. If 48 hours pass and nothing moves,<\/strong> the cause is probably not the one you assumed. Read the issue wording literally rather than by general impression.<\/li>\n<\/ol>\n\n\n\n\n\n\n\n

    When the cause is the store, not the products<\/h2>\n\n\n\n

    The tell is simple: catalogue edits change nothing, and the problem affects everything at once. Then look at the site rather than the product data. Google explicitly requires that a user can add products to the cart and fully complete the checkout process<\/a>, that at least one conventional payment method is offered, that contact information is clearly available, and that every condition of the purchase is disclosed clearly and conspicuously.<\/p>\n\n\n\n

    Two technical trifles that produce a disproportionate share of disapprovals:<\/p>\n\n\n\n