Product Feed Unavailable
Google Merchant Center is trying to fetch your product feed from the URL you configured, but the request is failing. This means the server hosting your feed URL is returning an error, the URL has changed, requires authentication, is blocking Googlebot's user agent, or is returning something other than a valid feed file. Unlike a website-unreachable error (which affects your product pages), this error specifically affects the URL where your feed file lives.
Fetch error [feed URL]: URL fetch failedImpact: A feed-unavailable error means Google cannot fetch your product data at all. If this persists for more than 7–14 days, all products in the affected feed will be disapproved and your Shopping ads will stop running entirely. This is the highest-priority technical error to fix.
Root Causes
- 1Your feed URL changed — either you migrated feed hosting, changed your subdomain, or updated your feed app settings — but the old URL is still registered in Merchant Center.
- 2Your feed requires HTTP Basic Authentication (username/password), but the credentials stored in Merchant Center are wrong or expired.
- 3Your hosting provider or CDN is blocking requests from Google's crawler IP ranges (66.249.0.0/16 for IPv4, 2001:4860::/32 for IPv6) with a 403 Forbidden response.
- 4The feed file generation is failing silently — your feed app is producing an empty file, a PHP/Python error page, or an HTML error page instead of a valid XML/TSV/CSV feed.
- 5Your feed is hosted on a server with a misconfigured SSL certificate, causing HTTPS fetches to fail with SSL handshake errors.
Fix by Platform
- 1In Google Merchant Center → Feeds → click on your feed → look at the 'Fetch status' — it shows the last fetch time and the HTTP status code returned.
- 2For Shopify's native Google & YouTube Channel: the feed is hosted on Google's servers (not your own URL), so classic feed URL errors don't apply. If you're seeing this error with Shopify's native integration, re-disconnect and reconnect the Google channel in Shopify Admin → Sales Channels → Google & YouTube → Settings.
- 3For third-party feed apps (Simprosys, AdNabu, DataFeedWatch): go to your feed app and verify the feed URL it's generating. Copy the URL and open it in an incognito browser — can you access it? Does it return valid XML/TSV or an error page?
- 4Update the feed URL in Merchant Center if it changed: Feeds → click feed → Edit → update the Fetch URL → Fetch Now.
- 5If your feed requires authentication: in GMC → Feeds → your feed → access the authentication settings and update the username/password.
When This Doesn't Apply
Check your store now
Free compliance scan — 47 rules checked in minutes.
Frequently Asked Questions
How often does Google try to fetch my feed?+
Google fetches feeds based on the schedule you configured in Merchant Center — daily, every 4 hours, or weekly. Beyond scheduled fetches, you can always trigger a manual fetch via GMC → Feeds → your feed → Fetch Now. If you've fixed the issue and don't want to wait for the next scheduled fetch, always use 'Fetch Now' to speed up recovery.
My feed URL returns a 301 redirect. Does that cause this error?+
Most redirect chains work fine — Googlebot follows up to 5 redirects. However, if your feed redirects from HTTP to HTTPS, ensure the final destination is a valid feed file, not another redirect. Circular redirects or chains longer than 5 hops will cause fetch failures. The cleanest fix is to update the feed URL in Merchant Center to point directly to the final HTTPS URL.
How long does it take for products to reappear after I fix the feed URL?+
After a successful feed fetch, products go into review. For established accounts, products typically re-approve within 24–72 hours. If your feed was unavailable for more than 14 days, Google may have removed all products from its cache — in that case, you'll need a full re-approval cycle (up to 5 business days). Trigger a manual fetch immediately after fixing to start the clock.
Can my feed generation fail silently without showing an error?+
Yes. Some feed apps generate a technically valid (parseable) XML file that contains 0 products or contains error HTML wrapped in XML tags. Google processes the file but disapproves all products for 'no items' or 'invalid format'. Always verify your feed file content by downloading it and inspecting the first few rows — not just checking that the URL returns a 200 HTTP status.
My feed is very large (50,000+ products). Does size cause fetch failures?+
Not directly — Google accepts feeds up to 8GB in size per file. However, large feeds take longer to generate on your server (potentially timing out) and longer to process after fetch. For catalogs over 20,000 products, consider splitting into multiple supplemental feeds in Merchant Center (organized by category or brand), or use the Google Content API for real-time updates instead of scheduled feed fetches.