Roughly half of Shopping non-serving cases that advertisers blame on a "broken account" in 2026 are actually item-level blocks under a perfectly active Merchant Center, according to the issue patterns Google surfaces in its own Products diagnostics — yet sellers often re-create the feed or open a support ticket, which fixes nothing and loses a week of sales. When your account is green but your products won't show, the problem is almost always a fast, mechanical fix once you check the causes in the right order.
This guide walks the 12 most common item-level causes from the fastest to confirm to the deepest, so you resolve the problem in hours instead of guessing. To check your Shopping setup against the most frequent serving blockers automatically, run our free 5-axis Google Ads audit.
Updated 2026-05-24 with current Merchant Center item diagnostics, GTIN validation and Performance Max listing-group behavior observed across US, UK and European stores.
- An active account is not the same as eligible products — read item status, not the account banner. 2. Item disapprovals and GTIN errors explain roughly half of partial non-serving and are the fastest to confirm. 3. A missing required attribute — GTIN, availability, image or price — quietly pulls an item from the auction. 4. Bids, budget or listing groups explain approved items with zero impressions, not the feed. 5. Use Merchant Center Diagnostics, never search Google for your own product.
Are your products disapproved at the item level?
Item-level disapproval is the first thing to check because it is the fastest to confirm and the single most common reason a healthy account still won't serve. Account approval and product eligibility are two different layers — a green account can sit on top of thousands of blocked items.
Open Products, then Diagnostics — The item table shows each product's status. Filter for Disapproved to see exactly which products are blocked and why.
Price and availability mismatch — If the price or stock in your feed does not match the landing page, Google disapproves the item. This is the most common trigger and the easiest to overlook. Sync your feed so both match.
Images and content — A broken image link, a placeholder, or promotional text in the image disapproves the item. Misrepresentation and prohibited-content rules apply at the product level too.
One disapproved product blocks only that product. But a feed-wide issue — a template error or a sitewide price mismatch — can disapprove a whole catalog at once, so check whether the disapprovals share a single root cause before fixing them one by one. For an account-wide suspension instead of item issues, follow our Merchant Center suspension recovery guide.
Are GTIN, brand or identifier errors blocking items?
Product identifiers are the second big cause. A wrong or duplicated GTIN is one of the most frequent item disapprovals in any catalog.
Incorrect GTIN — The number fails Google's check-digit validation. Pull the exact code from your supplier or the GS1 database and resubmit. A valid GTIN is 8, 12, 13 or 14 digits.
Duplicate GTIN — Two different products share one identifier, so Google cannot tell them apart. Each variant needs its own correct code.
Missing identifier — For branded products, Google expects GTIN plus brand. For genuinely identifier-less items — custom, handmade, or your own private label — set identifierExists: to false and supply brand plus MPN instead of inventing a number.
Getting identifiers right does more than clear disapprovals — accurate GTINs match your products to the right queries and improve eligibility. Our Shopping setup and optimisation guide covers a clean identifier structure from the start.
Are required feed attributes missing or stale?
If disapprovals and identifiers are clean, the next question is whether every required attribute is present and current.
Required attributes — Every item needs id, title, description, link, image link, availability, price and condition. A single missing required field pulls the product from the auction. Check the Diagnostics view for "missing attribute" warnings.
Stale data — An expired feed, an out-of-stock availability that never refreshed, or a price that drifted from the landing page all quietly stop serving. Schedule a feed fetch frequent enough that stock and price stay accurate.
Recommended attributes — Adding product type, GTIN and detailed titles is not strictly required, but thin data narrows the queries you match, so eligible products still get few impressions. Richer attributes widen reach. Our Q4 Shopping feed optimization guide shows which fields move the most volume.
Feed handling differs by platform. If you are on Shopify or PrestaShop, our Shopify vs PrestaShop setup guide covers the attribute mapping each one gets wrong.
Are bids or budget too low for products to serve?
An approved, fully-attributed product can still show zero impressions if it never wins an auction. This is where many sellers waste days — the feed is fine, but the bid or budget is not.
Bids too low — In a Shopping or Performance Max auction, products with bids well below their category's competitive range rarely show. Raise the bid or target ROAS for the affected product groups and watch impressions respond.
Budget runs out early — If the campaign budget empties before the day is over, lower-priority products simply never get impressions. Google can spend up to 2 times your average daily budget on a high-opportunity day, capping the month near your daily budget times 30.4. A budget too low for your catalog size starves the tail.
Check serving, not just approval — In the Google Ads product report, an item marked Active in Merchant Center but showing 0 impressions is a bid, budget or structure problem, not a feed one. Model the ROAS a budget change buys you with our ROAS calculator before you raise spend blindly.
Is PMax or campaign setup excluding products?
Campaign structure is the deepest and most overlooked cause. A product can be perfectly approved and still never serve because no active campaign is bidding on it.
Listing groups — A Performance Max or Shopping campaign serves only the products inside its selected listing groups. Anything filtered out by product type, brand, custom label or item ID never enters the auction. Confirm every product you expect to serve sits inside an active listing group.
Campaign overlap and priority — When two campaigns claim the same products, the higher-priority or higher-bidding campaign wins and the other's products go dark. Each product should serve through exactly one un-paused campaign.
Exclusions — A negative keyword in a Shopping campaign, a brand exclusion, or a paused ad group can quietly remove products. Review exclusions before assuming a feed fault.
If your structure mixes Shopping and Performance Max, decide which owns which products deliberately rather than letting overlap pick the winner for you.
The Shopping-not-serving fix table
Work this table top to bottom — it is ordered by how fast each cause is to confirm and how often it is the real reason products won't serve.
Searching Google Shopping for your own product to check if it shows is unreliable: results are personalized, location-bound and auction-dependent, so a product can be perfectly eligible yet absent from your screen. You may also burn no-cost impressions that distort your data. Use the Merchant Center Diagnostics and the Google Ads product report instead — they tell you eligibility and serving without guessing from a single search.
How to verify a product is eligible to serve
The Merchant Center Diagnostics view is the single most useful check in this whole guide. It lists every item's status and, for each issue, the exact attribute at fault and how to fix it. Confirm approval there before assuming a deeper fault.
Once your products are serving again, a few habits prevent most repeat blackouts:
Schedule frequent feed fetches so price and availability never drift from your landing pages — the mismatch that causes most item disapprovals.
Run a weekly diagnostics sweep across disapprovals, expiring items and missing attributes — ten minutes catches most issues before they cost a week of sales.
Keep identifiers clean — one correct GTIN: per variant, brand on every branded item, and identifierExists set false only where it truly applies.
Audit before you scale. A clean feed rarely goes dark. Estimate the profit a serving gap costs you with our ROAS calculator, and to find serving blockers across your account automatically, run the SteerAds free 5-axis audit.
Sources
Official sources consulted for this guide:
-
support.google.com — product data specification
-
support.google.com — GTIN requirements
-
support.google.com — fix disapproved products
-
support.google.com — product status and diagnostics
FAQ
Why are my Shopping products not showing?
An active Merchant Center account whose products won't serve almost always traces to one of five buckets: item-level disapprovals (a subset of products violates a policy), identifier errors (a wrong, duplicated or missing GTIN, brand or MPN), feed gaps (a required attribute is missing, expired or stale), auction inputs (bids or budget too low to enter Shopping auctions), or campaign structure (a Performance Max or Shopping setup that excludes the products through listing groups). Work them in that order: disapprovals and identifier errors explain roughly half of partial non-serving and are the fastest to confirm in the Merchant Center Products diagnostics. Your account being active is not the same as every product being eligible.
My account is active but products aren't serving — why?
Account-level approval and item-level eligibility are two different things. A green, unsuspended Merchant Center can still hold thousands of disapproved or pending items underneath it. Open the Products then Diagnostics view and read the item issues: 'Disapproved', 'Pending', 'Limited' or 'Not eligible' each mean a specific block. A single failing required attribute — a missing GTIN, an out-of-stock availability, a broken image link, or a price mismatch with your landing page — can pull an item out of the auction even though the account itself is perfectly healthy. Fix the item, not the account.
How do I fix GTIN errors in Google Shopping?
Most GTIN errors fall into three types: 'Incorrect GTIN' (the number fails Google's check-digit validation), 'Invalid GTIN' (wrong length or a non-existent code), and 'Duplicate GTIN' (two different products share one identifier). Pull the exact code from your supplier or the GS1 database, confirm it is 8, 12, 13 or 14 digits with a valid check digit, and submit it in the gtin attribute. If a product genuinely has no GTIN — a custom or handmade item — set identifierExists to false and provide brand plus MPN instead, rather than inventing a number.
Does Performance Max hide some of my products?
It can, through listing-group structure. A Performance Max or Shopping campaign serves only the products inside its selected listing groups; anything filtered out — by product type, brand, custom label or item ID — simply never enters the auction. A common trap is two campaigns claiming overlapping products, where the higher-priority campaign wins and the other one's products go dark. Check that every product you expect to serve sits inside an active listing group in exactly one un-paused campaign, and that no exclusion silently removes it.
How do I check if a Shopping product is eligible to serve?
Use the Merchant Center Products and Diagnostics views rather than searching Google yourself. The item table shows each product's status — Active, Pending, Expired or Disapproved — and clicking an issue reveals the exact attribute at fault and how to fix it. For a live serving check, the Google Ads Shopping campaign reporting shows impressions at the product level: zero impressions on an approved item points to bids, budget or listing-group exclusion rather than a feed problem. Confirm approval first, then serving.
Why are only some of my products showing on Shopping?
Partial serving is the classic signature of item-level rather than account-level problems. The products that show are approved and inside an active listing group with enough bid and budget; the ones that don't are usually disapproved, missing a required attribute, out of stock, excluded by a listing group, or starved by a budget that runs out before they get impressions. Sort your product report by impressions, isolate the zero-impression items, and check each against the five buckets — disapproval, identifier, feed, bids and structure — in that order.
How long do Merchant Center fixes take to go live?
After you correct an item, the change must be re-fetched and re-reviewed. A scheduled or API feed update can take from a few hours up to one to two days to reprocess, and a re-review of a previously disapproved item can take a similar window. Forcing a manual fetch or using the Content API speeds the data update, but the policy re-review still runs on Google's clock. Plan for up to two days before judging whether a fix worked, and avoid re-editing the item repeatedly, which can restart the review.