5 min read
In brief
- An item-level disapproval and an account-level suspension are different failures with different fixes. Chasing one while the other is broken is the most common wasted week in Merchant Center.
- Check price, availability and the landing page before you check policy. Most disapprovals are a disagreement between the feed and the page, not a rule being broken.
- There is a third reason ads stop showing that is not a disapproval at all: the item is out of stock in the feed, so there is nothing eligible to serve.
Item level and account level are different failures
Merchant Center reports problems at two altitudes, and merchants routinely confuse them. An item is disapproved when that specific product cannot be served. The account is suspended when nothing can be served. The first is a data problem; the second is a judgement about the business.
| Item disapproved | Account suspended | |
|---|---|---|
| Blast radius | One product, or a group sharing the same fault | Every product, immediately |
| Typical cause | Feed and landing page disagree, or a policy rule fails | Verification of the business or the site as a whole |
| Where it is fixed | Product data, images, identifiers, landing page | Site, business information, policies |
| Time to resolve | Hours to days, per item | Days to weeks, and depends on a review |
The check that saves a week
Open Merchant Center and look at the top of the Products tab, not at the individual items. If the header says the account is suspended, stop fixing products. Nothing you change at item level will matter until the account is reinstated.
The four reasons items are disapproved
- Price or availability disagreement: the feed says one price or stock state and the landing page shows another. Currency and tax handling are the usual culprits.
- Image or landing page problems: an image with promotional text burned into it, a watermarked supplier photo, or a landing page that returns an error, redirects to a category, or is blocked from crawling.
- Identifier problems: a missing or wrong GTIN, a made-up MPN, a brand field that does not match the product. Assigned identifiers from a supplier are frequently invalid.
- Policy: a restricted or prohibited product, an unsupported claim (medical, safety, environmental), or content that reads as misleading relative to the landing page.
The order matters. Nine times in ten the first three are the cause and the fourth is what the email subject line suggests. Read the specific reason attached to the item, not the category label on the account.
Why the ads stop showing when nothing looks wrong
Shopping ads stop for reasons that never appear as a disapproval. The most common is stock: an item marked out of stock in the feed has nothing to sell, so it silently stops serving while the product page still shows it as available.
The second is eligibility rather than approval: an approved item can still be ineligible to serve — for a destination mismatch, a country or language mismatch between the feed and the campaign, or a missing shipping service. Approval and eligibility are separate gates.
The third is the landing page itself. If the URL returns a 404, a redirect, a login wall or a page whose price differs, the item can be approved and still not serve.
| Symptom | First place to look | Usually means |
|---|---|---|
| Ads vanished, products show as available | Feed stock status | Stock sync is not updating the feed |
| Some products never served at all | Eligibility in the campaign | Country, language or shipping mismatch |
| Clicks dropped with no data change | Landing page status and mobile rendering | Page error, redirect or a price the crawler cannot see |
| Everything stopped at once | Account status | Suspension, not an item problem |
The twenty-minute test per product
- 1
Open the item's own issue detail
Not the account summary. Each disapproved item carries a reason and usually a field name. Write the reason down verbatim before changing anything.
- 2
Compare the feed row against the live page
Price, currency, availability, title, image URL, GTIN. In a clean browser, with no cache and no logged-in session. Every difference is a candidate cause.
- 3
Open the landing page as a crawler would
Check the response code first, then whether the content is server-rendered or appears only after JavaScript runs. A price that only exists after hydration is a price Google may not see.
- 4
Check the identifiers
Search the GTIN. If it resolves to a different product, or to nothing at all, the identifier is wrong and the item will keep failing regardless of everything else.
- 5
Change one field, then refetch
Fix, request a refetch for that item, and confirm the status changes before touching the next product. Batch-editing fifty items teaches you nothing about which change worked.
Which one is actually wrong — the feed or the site
Fixing the wrong side is what turns a one-day problem into a two-week one. The symptom usually tells you which side to trust.
| What you see | Likely fault | Correct the |
|---|---|---|
| Feed price differs from page price for many products | A feed rule or currency setting applied incorrectly | Feed |
| Feed matches page, but the page price changes by locale | Geo or currency logic on the site | Site |
| Feed shows in stock, page shows sold out | Stock sync failing one direction | Feed ingestion |
| Page shows in stock, feed shows sold out | Stock sync failing the other direction | Feed ingestion |
| Identifiers rejected across a category | Supplier-supplied GTINs that are not valid | Feed, by removing or correcting identifiers |
Prevention beats repair
- Review disapprovals weekly by reason, not by count. Twenty items failing for one cause is a single fix; twenty failing for twenty causes is a catalogue problem.
- Watch price drift between the feed and the site — a scheduled discount that ends is the most common source of a sudden wave of disapprovals.
- Keep stock sync honest in both directions. A feed that only pushes out-of-stock when an order is placed will always lag the site.
- Remove products you cannot verify rather than leaving them to fail repeatedly; a smaller clean catalogue reviews faster than a large broken one.
If you are looking at a wall of disapprovals, the useful first step is grouping them by reason rather than fixing them one by one. We do that as part of the initial audit, and it usually turns fifty problems into two.
