Google Shopping feed errors are one of the fastest ways to lose free product listings, paid Shopping visibility, or both. Merchant Center compares your product data file against your live store pages, shipping settings, and policy requirements. When something does not match, products get warnings, limited serving, or full disapproval until you fix the root cause.
This guide walks through 15 common feed problems, how to diagnose them inside Merchant Center, and practical fixes you can apply without guessing. If you are new to listing products on Google, start with our guide on how to get products on Google for free in 2026. For ongoing monitoring, see Google Merchant Center AI Performance Insights and use it alongside the diagnostics below.
Merchants on KODEEFY can supply product data through the storefront feed at /feeds/google-shopping.xml on their live store domain (for example, yourstore.kodeefy.com/feeds/google-shopping.xml). That XML feed is generated from your catalog, prices, availability, and images. Even with an automated feed, you still need accurate source data and landing pages that match what Google receives.
1. Price mismatch between feed and landing page
Price mismatch is among the most frequent Google Shopping feed errors. Google compares the price in your feed (or structured data) with the price a shopper sees on the product landing page, including any default variant selection.
Common causes include sale prices updated on the site but not in the feed, variant-level pricing where the feed shows a base price, and tax display rules that differ from feed values. Align the visible price and feed price for the same item ID, update your catalog source, regenerate the feed, and review Google's price attribute documentation. Confirm sale_price and price use the same effective dates on site and in the feed.
2. Availability mismatch (in stock vs out of stock)
Availability errors happen when your feed says in stock but the landing page shows sold out, pre-order without proper labeling, or backorder without matching availability values. The reverse also triggers warnings: the site shows buyable inventory while the feed says out of stock.
Inventory sync delays are a typical culprit. Pre-order and backorder products need explicit availability values, not generic in stock labels. Map stock status to Google's allowed values using Google's availability specification, then allow time for Merchant Center to reprocess the item.
3. Missing GTIN for branded products
A missing GTIN (Global Trade Item Number) blocks eligibility for many branded catalog items. Google uses GTINs to match products across merchants and reduce duplicate listings.
If you sell established brands and omit gtin, Merchant Center often flags missing identifier exists. Handmade or private-label goods may qualify for identifier_exists set to false when no GTIN truly exists. Add correct GTINs from packaging or supplier data. Do not invent numbers. For custom goods without a GTIN, use brand plus MPN or follow Google's unique product identifier rules.
4. Invalid identifier combinations (GTIN, brand, MPN)
Invalid identifiers mean the GTIN does not match the brand, the MPN is generic or duplicated across unrelated SKUs, or required fields contradict each other. Merchant Center validates whether the identifier set looks like a real catalog entry.
Audit identifier fields per SKU. Each variant with a unique barcode needs its own GTIN. When GTIN is unavailable, provide consistent brand and MPN pairs. See Google's product identifier best practices.
5. Image link errors and low-quality images
Image issues include broken image_link URLs, redirects to HTML pages instead of image files, images smaller than Google's minimum size, watermarks or promotional text overlaid on the main image, and multiple products in one primary image.
Google requires a clear primary image without excessive padding for most categories. Serve images over HTTPS with direct URLs that return 200 status codes. Use at least 100 x 100 pixels for apparel and 250 x 250 for most other categories. Follow Google's image link requirements, then refresh the feed and check Diagnostics for lingering crawl errors.
6. Missing or incorrect shipping information
Shipping problems surface when Merchant Center cannot calculate delivery cost for the target country, shipping labels in the feed conflict with account-level shipping settings, or handling times exceed what your policy promises on site.
Configure shipping in one authoritative place and keep account settings aligned with feed attributes. Read Google's shipping attribute documentation and test with Merchant Center shipping diagnostics.
7. Landing page mismatch and unreachable URLs
Landing page errors occur when the link in your feed does not resolve to the exact purchasable product, returns 404 or 500 errors, redirects through long chains, or lands on a generic homepage instead of the SKU page.
Use stable, canonical product URLs that match the item id and variant selection. Consult Google's link attribute guidelines and fix server errors before resubmitting.
8. Variant and item group errors
Variant issues include missing item_group_id for color or size variants, mixing parent and child IDs inconsistently, duplicate ids across variants, or submitting configurable products without size and color attributes where required.
Apparel and shoes have strict variant rules. Group variants with a shared item_group_id, unique id per variant, and accurate attributes. Review Google's variant submission guide and regenerate grouped data from your platform rather than hand-editing rows.
9. Currency and target country mismatches
Currency errors happen when price uses NPR in the feed but the target country expects USD, decimal separators are wrong, or multiple currencies appear for the same country feed. Merchant Center ties currency to the country of sale configured in your feed and account.
Match currency ISO codes to each target country feed and keep feed currency identical to checkout currency. See Google's price currency rules. Use separate country-specific files when selling in multiple markets.
10. Policy violations and restricted product content
Policy problems are not always syntax errors. Merchant Center may disapprove products for misleading claims, prohibited items, counterfeit signals, adult content in the wrong context, or missing contact and business information at account level.
Read Google Merchant Center policies for your category. Rewrite descriptions to be factual, remove prohibited SKUs, and resolve account-level policy strikes before expecting product fixes to stick.
11. Account and product disapprovals after review
Disapprovals differ from warnings. A disapproved product stops serving until you fix the cited issue and request review, or until automated systems reprocess a valid update.
Repeated identical disapprovals usually mean the underlying data still fails validation. Open the product detail in Merchant Center, read the reason code, fix that field first, then use Needs review when available. Refer to Google's guide to fixing disapproved products. Fix recurring patterns in bulk rather than one SKU at a time.
12. Incorrect or missing Google product category
google_product_category tells Google what kind of item you sell. Wrong categories lead to attribute requirements you did not satisfy, unexpected policy checks, and poor query matching.
Use the taxonomy search in Merchant Center or Google's product category documentation. Align category with what the product actually is, not how you merchandize it internally.
13. Title and description formatting problems
Title errors include missing brand where expected, all-caps promotional text, keyword stuffing, or titles that do not describe the specific variant. Description issues cover hidden policy phrases, HTML that breaks parsing, or content that does not match the landing page.
Write concise titles with brand, product type, and variant facts. Keep descriptions factual and consistent with the page. Follow Google's title and description best practices.
14. Duplicate IDs and conflicting feed sources
Duplicate id values across rows cause unpredictable overrides: one row wins, others drop, or Merchant Center reports conflicting data. This often happens when merchants upload a manual spreadsheet while also fetching an automated XML feed from /feeds/google-shopping.xml without removing the older source.
Maintain one primary data source per country and language. Review Google's product data specification for required unique keys and allow a full processing cycle after consolidating sources.
15. Feed fetch failures and XML format errors
Fetch failures mean Merchant Center never reaches your file: wrong URL, expired SSL certificate, firewall blocking Googlebot, HTTP auth without credentials, or timeouts on large files. Format errors include malformed XML, unescaped special characters, wrong encoding, or missing required attributes at file level.
Scheduled fetches show last attempt status in Merchant Center. Test the feed URL externally and validate XML formatting. See Google's feed setup troubleshooting. For KODEEFY stores, confirm the public feed URL loads without login and returns fresh timestamps after catalog edits.
Troubleshooting workflow for Google Shopping feed errors
Use a consistent workflow so fixes stick and you do not chase the same warning repeatedly.
| Step | Where to look | Action |
|---|---|---|
| 1 | Merchant Center Diagnostics | Filter by issue type and export affected item ids |
| 2 | Sample product landing page | Compare live price, availability, image, and title to feed row |
| 3 | Source catalog or platform | Correct SKU-level fields once, not per channel copy |
| 4 | Feed regeneration | Refresh XML or re-upload after source fix |
| 5 | Reprocessing wait | Allow processing time before requesting manual review |
| 6 | Documentation cross-check | Verify attribute against current Google spec |
When errors cluster on one attribute, fix in bulk with a spreadsheet or script rather than one SKU at a time. Pair this workflow with AI Performance Insights to spot trends early.
Prevention checklist
Use this checklist after major catalog changes, sales events, or platform migrations.
Prices and sale dates match between storefront and feed for every active SKU
Inventory status updates within your agreed sync window
GTIN, brand, and MPN validated for branded catalog lines
Primary images resolve over HTTPS and meet minimum dimensions
Shipping and handling times reflect current checkout behavior
Product URLs return 200 and show the purchasable variant
Variant groups use consistent item_group_id and unique id values
Currency and country targets align per feed
google_product_category assigned from the official taxonomy
Only one authoritative feed source connected per market
Account business, return, and contact policies complete in Merchant Center
Feed fetch URL tested after DNS, SSL, or deployment changes
Frequently asked questions
How long does Merchant Center take to clear a feed error after I fix it?
Processing times vary by issue type and volume. Some attribute updates resolve within hours; policy reviews can take longer. Fix the root cause in your source catalog, refresh the feed, then monitor Diagnostics instead of repeatedly re-uploading unchanged files.
Do I need both a product feed and structured data on my site?
Many merchants use both. Structured data on product pages helps Google verify landing page content. A supplemental or primary feed still supplies full catalog data at scale. Keep prices, availability, and identifiers consistent across both surfaces.
Can I ignore warnings if products still show in some surfaces?
Warnings can become disapprovals after reprocessing. Limited serving may reduce impressions over time. Treat warnings as required fixes, especially for price, availability, and identifier issues that affect trust.
Where does the KODEEFY Google Shopping feed fit in?
KODEEFY generates a storefront XML feed at /feeds/google-shopping.xml on your public store domain. Connect that URL in Merchant Center as a scheduled fetch or download and upload while testing. The feed reflects your KODEEFY catalog, so fixes start in admin product records, variants, images, and stock settings before you expect Merchant Center to change.
Final thoughts
Most Google Shopping feed errors come from small mismatches between what you publish and what shoppers experience. Align feed data, landing pages, and Merchant Center account settings, then use Diagnostics plus a repeatable troubleshooting workflow. Steady prevention beats emergency fire drills during peak sales seasons.