Skip to main content
FHAVI

Free resource

What the disapproval actually says

Google's disapproval reasons are accurate and almost unreadable. They describe a rule, not your mistake. This decodes the ones that account for nearly every item-level failure — what it means in plain language, where to look, and what to change.

How to read a disapproval

Three pieces of information, in this order

Open the item's detail panel rather than the summary list. The summary gives a category; the detail gives the attribute or policy that failed, and often the value that failed it.

Then decide which of three things it is: a data error (the field says something untrue), a policy issue (the product is restricted or the claim is not allowed), or a destination problem (the landing page disagrees with the feed). The fix is completely different for each, and this is where most merchants waste a week.

Finally, fix one item and request a re-review of that item before touching the other nine hundred. A single-item check costs nothing and tells you whether your diagnosis was right.

The decoder

The reasons you will actually see

01

Data errors

A field is wrong, missing or inconsistent.

  1. “Incorrect price” — the feed price does not match the landing page. Check for a currency mismatch, a sale price live on site but not in the feed, or a region-specific price.
  2. “Missing or incorrect availability” — the item is out of stock but advertised, or the landing page shows a different state. Sync stock hourly at minimum.
  3. “Invalid GTIN” or “Incorrect identifier” — a fabricated number, a check-digit failure, or the parent product's identifier used on every variant.
  4. “Image issues” — a watermark, another brand's logo, promotional text burned in, or a placeholder image.
  5. “Title mismatch” — the title names a brand or product the page does not support. Usually supplier copy left in place.
02

Policy issues

The product or the claim is restricted.

  1. “Restricted content” — the category needs approval, disclosures or is prohibited outright. Read the specific policy named, not the summary.
  2. “Trademark” — a brand name used without authorization, in the title, description or image.
  3. “Healthcare claims” or “unapproved substances” — the product makes a medical claim it cannot support.
  4. “Misleading promotion” — a discount, countdown or stock claim that does not hold up when checked.
  5. Repeated identical policy violations on the same account escalate from item-level to account-level action.
03

Destination problems

The feed is fine and the site is not.

  1. “Landing page mismatch” — the page shows a different product, price or currency than the feed promised.
  2. “Unreachable or unavailable landing page” — 404, redirect loop, a login wall, or a page that renders empty to a crawler.
  3. “Checkout not available” — the item cannot be bought in the target country, or the only payment method is local.
  4. These look like feed failures in the summary and are never fixed by editing the feed. Check the page in a private window first.

After decoding

What the pattern tells you

04

Read the distribution, not the list

  1. One item, one reason, everything else clean → fix the item and move on.
  2. Many items, the same reason → a feed-level or process-level defect. Fix the source, not the rows.
  3. Many items, different reasons → usually a supplier data problem; the catalogue was imported without review.
  4. Every item, one reason → stop looking at products. Check business identity, policy pages or the site's availability to crawlers.
  5. Approved but never shown → not a disapproval at all. Look at bids, budget, country targeting and shipping settings.
05

What not to do

  1. Do not delete and re-upload an item to “reset” it — the history goes with the id, and you lose the record of what failed.
  2. Do not request an account-level review while items are still disapproved.
  3. Do not rewrite titles for a policy problem; the text was never the issue.

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Same disapproval coming back after every fix?

Send the reason text and the product URL. If the cause is upstream — supplier data, a policy category, the site itself — we will tell you before you spend another week on fields.

Prefer email? Write to md@fhavi.com