Merchants often say their products are not showing on Google Shopping even though they uploaded a feed weeks ago. Usually the gap is between submitted, eligible, approved, and actually displayed. Google may accept catalog rows yet show nothing for a given search, country, or device. This troubleshooting guide explains why and how to fix the most common blockers without promising rankings or impressions.
Start in Merchant Center Diagnostics, then walk product-level and account-level checks. Pair this with Google Shopping feed errors, Merchant Center setup for beginners, and free Google product listings for full context.
Important: An approved product is not guaranteed to appear for every query or shopper. Visibility depends on relevance, competition, geographic targeting, stock status, and program participation. Fixing errors improves eligibility and data quality; it does not assure top placement.
Submitted vs eligible vs approved vs displayed
These stages are often confused. Use this mental model before changing working campaigns or feeds.
| Stage | What it means | What it does not mean |
|---|---|---|
| Submitted | Google received feed rows or structured data | Products are live on Shopping surfaces |
| Eligible | Item meets basic data requirements for a program | No policy or landing-page blockers remain |
| Approved | Item passed review for at least one destination | Guaranteed impressions or clicks |
| Displayed | Google chose to show the item for a specific query and context | Permanent visibility; listings can fluctuate |
Start with Merchant Center Diagnostics
Open Merchant Center and review Products, Diagnostics, and Notifications. Sort by disapproved and pending items first. Account-level suspensions override individual product fixes until resolved.
Check account status for policy warnings or suspensions.
Open item-level issues and read the exact attribute cited.
Fix source data, then allow reprocessing (often hours, not minutes).
Confirm the same SKU in Search Console URL Inspection if landing-page errors appear.
Feed processing problems
If the entire feed fails, no products advance to approval. Common causes include unreachable feed URLs, authentication errors, invalid XML, wrong encoding, or empty files after a deployment mistake.
Verify scheduled fetch returns HTTP 200 with expected content length.
Open the feed URL in a browser or curl and inspect a sample item.
Confirm content type and charset match what Merchant Center expects.
Remove duplicate conflicting data sources uploading different catalogs.
Detailed attribute-level fixes live in Google Shopping feed errors and fixes.
Product disapprovals and account issues
Disapprovals cite a specific reason: misleading claims, prohibited products, missing identifiers, or checkout problems. Account issues (misrepresentation, unclear return policy, unreachable site) can limit all products until corrected.
When Google supports it for your issue type, use the request review workflow after you fix the underlying problem. Requesting review before fixing the root cause delays recovery.
Price, availability, and currency mismatches
These are the highest-frequency item disapprovals for small merchants.
Price mismatch: Feed price differs from the landing page price for the linked variant.
Availability mismatch: Feed says in stock while the page shows sold out or preorder without matching markup.
Currency mismatch: Feed currency code does not match checkout currency for the target country.
Fix catalog source data first, then confirm JSON-LD Offer price and availability on the page match visible UI facts. See ecommerce product schema for structured data alignment.
Landing page mismatches and product page availability
Each feed row must link to a crawlable product URL that sells the exact item described. Redirect chains to unrelated categories, generic homepages, or login walls trigger disapprovals. HTTP 404, 500, or soft 404 pages block approval.
Missing identifiers and GTIN issues
For categories where GTINs apply, missing or invalid values cause disapproval. Do not invent GTINs or reuse another product's barcode. When no GTIN exists, follow identifier rules with brand and MPN.
Image problems
Broken image_link URLs, tiny thumbnails, placeholder graphics, promotional text burned into photos, or mismatched variant images all trigger image-related warnings. Images must be crawlable over HTTPS and show the product being sold.
Shipping, returns, and policy compliance
Shipping costs or delivery times that contradict checkout create trust issues. Return policies must be easy to find and consistent with Merchant Center settings. Policy violations can suppress listings even when product data looks clean.
Website verification and crawlability
Unverified or unclaimed domains stop new programs from working correctly. Confirm verification in Merchant Center after domain migrations.
Search crawl issues also limit organic product discovery outside Shopping. Check robots.txt, meta robots, and HTTP status for product paths.
Robots, noindex, and canonical problems
robots.txt blocks: Disallow rules on /products/ prevent crawling.
noindex: Accidental noindex on product templates removes pages from Google Search index.
Canonical tags: Product pages canonicalized to unrelated URLs consolidate signals away from purchasable URLs.
Use Google Search Console URL Inspection on affected SKUs. These issues also hurt product page SEO independently of Merchant Center.
Structured data mismatch
When Product JSON-LD on the page contradicts feed price, availability, or URL, Google may distrust both signals. Align structured data with visible content and feed rows from one inventory source.
Geographic targeting and availability
Products configured for limited countries will not appear elsewhere. Check Merchant Center target countries and shipping services. Out-of-stock items may be suppressed even when technically approved.
Feed freshness and variant grouping
Stale feeds with outdated sale prices erode trust after the first crawl. Schedule fetches often enough for your update cadence (daily for volatile catalogs is common).
Variants missing item_group_id can split parent products into competing duplicates or fail variant rules. Each variant needs a unique id, shared group id, and variant-specific attributes such as color or size in titles where applicable.
Policy compliance and restricted products
Even perfect feed mechanics fail when products violate Shopping policies. Restricted categories (certain healthcare, adult, weapons, or counterfeit-prone goods) require additional documentation or are prohibited entirely. Policy hits can be item-level or account-wide.
Misleading claims on landing pages (false discounts, hidden fees, or bait-and-switch variants) trigger misrepresentation reviews. Ensure the product at the URL matches image, title, and price in the feed.
Monitoring recovery without false expectations
During recovery, track three metrics separately: disapproval count (should fall), approved active count (should rise), and impressions in Merchant Center performance (may lag). Impressions can stay flat after fixes if queries are competitive or targeting is narrow. That is not always another technical error.
In Google Search Console, monitor indexed product URLs, soft 404 reports, and Core Web Vitals samples. Organic indexing problems can coexist with Shopping feed issues. Fixing one layer does not automatically fix the other.
Free listings vs paid Shopping ads
Free listings and ads draw from the same product data but do not behave identically. Paid campaigns add bidding, budgets, and reporting. Zero ad spend means you rely entirely on organic Shopping eligibility and relevance, which fluctuates more visibly.
Read how to get products on Google for free for program enrollment and Merchant Center performance insights for interpreting visibility trends.
How KODEEFY merchants should troubleshoot feed visibility
KODEEFY generates a Google Shopping XML feed at /feeds/google-shopping.xml on your live storefront domain. The platform does not submit feeds to Google automatically or manage Merchant Center on your behalf. When products fail to show, confirm Merchant Center scheduled fetch succeeds, then compare feed price, availability, and link values against the live product page and admin catalog. Variant rows use unique ids and item_group_id grouping; missing images or invalid URLs exclude products silently during feed generation.
Troubleshooting decision tree
Is the Merchant Center account active without policy suspensions? If no, fix account issues first.
Did the feed process successfully with expected item count? If no, fix feed delivery and format.
Are affected SKUs disapproved with a specific reason? If yes, fix cited attributes at the source.
Do landing pages return 200 OK with matching price and stock? If no, fix storefront or feed alignment.
Are products approved but invisible in search? Check targeting, stock, query relevance, and competition.
Do organic product URLs index in Search Console? If no, resolve crawl/index issues separately.
Prioritized fix checklist
Resolve account-level policy and verification issues.
Restore feed fetch reliability and remove duplicate sources.
Fix price, availability, and currency mismatches on top sellers first.
Repair broken product URLs, images, and identifier gaps.
Align JSON-LD with page content and feed rows.
Configure shipping and returns completely for target countries.
Reprocess and monitor diagnostics daily during recovery week.
Request review only after underlying fixes are live.
Frequently asked questions
My products are approved but I still cannot find them on Google Shopping. Why?
Approval means eligible to serve, not always visible. Google matches listings to queries, locations, and device contexts. Low relevance, strong competition, limited targeting, or out-of-stock status can reduce display even for approved items. Test branded queries and inspect Merchant Center performance reports rather than assuming global visibility.
How long after fixing a feed error will products show?
Reprocessing typically takes hours, sometimes longer for large catalogs. Allow time after corrections before requesting review or opening duplicate support tickets. Verify the live feed URL reflects fixes, not just admin drafts.
Can robots.txt block Shopping listings?
robots.txt affects Google Search crawling of pages. Shopping listings depend heavily on feed data, but landing-page errors from blocked or noindexed URLs still cause disapprovals. Keep product pages crawlable and indexable unless you intentionally remove items.
Do I need paid ads to appear on Google Shopping?
No. Free product listings can surface eligible products without ad spend. Ads add placement control through bidding but do not fix disapprovals or data mismatches. Many merchants use both after catalog hygiene is stable.
Should I delete and re-upload all products when troubleshooting?
Usually no. Deleting and recreating ids resets history and can create duplicate rows. Fix attributes in place, confirm feed processing, and remove only truly discontinued SKUs.
When should I request a review in Merchant Center?
Request review after you fix the cited policy or landing-page issue and confirm live pages and feeds reflect the correction. Requesting review before fixes are deployed wastes time and can delay reinstatement.
Final thoughts
When products are not showing on Google Shopping, work from account health down to SKU-level facts: diagnostics, feed delivery, price and stock alignment, crawlable URLs, and honest policies. Eligibility is achievable with disciplined catalog operations; universal visibility is not. Use feed error fixes, Merchant Center setup, and product title optimization to prevent repeat failures as you scale.