Google Merchant Center Feed Fetch Errors: Fix Guide 2026
Feed fetch errors are different from feed format errors. Your feed file might be perfectly formatted, but if Google's crawler cannot retrieve it from your server, none of those products will process. This guide covers every reason Google Merchant Center fails to fetch a feed and the precise fix for each scenario.
How GMC Feed Fetching Works
When you register a feed URL in Merchant Center, Google schedules periodic fetches from that URL using its Feedfetcher crawler. The crawler sends an HTTP request to your server, expects to receive the feed file in return, and then processes the content. If anything disrupts that HTTP exchange, GMC records a fetch error and the feed does not update.
The key difference from a manual browser request: Google's crawler does not carry cookies, does not execute JavaScript, and originates from specific Google IP ranges (listed in Google's published IP address range documentation). Any server configuration that distinguishes between Google's crawler and a regular user can cause a fetch failure that you would never see when testing the URL yourself.
Common Feed Fetch Error Types and Fixes
1. Server Timeout (HTTP 408 or Connection Timeout)
The most frequent fetch error. Google's feed fetcher has a strict time limit, roughly 30 seconds for the entire download. If your server takes too long to respond or your feed file is large enough that it cannot download within the window, the fetch fails with a timeout. Large catalogs (50,000+ products) without compression are the most common culprit.
Enable gzip compression on your feed URL. Most web servers can compress the response with a single configuration directive. A 500 MB uncompressed feed file can compress to under 50 MB, which typically resolves timeout errors on its own. If compression is not enough, move the feed to a CDN endpoint so the file serves from an edge location close to Google's crawl infrastructure.
2. Authentication Failure (HTTP 401 or 403)
If your feed URL sits behind HTTP basic authentication, a login wall, or an IP allowlist that excludes Google's IP ranges, the crawler gets a 401 or 403 response and records an authentication failure. This happens frequently when stores use security plugins that block crawlers, or when staging environments require password protection.
The cleanest fix is to create a dedicated public endpoint for your GMC feed. This can be a separate URL pattern like /feeds/gmc-products.xml that bypasses your authentication middleware. If you need to use basic auth, embed the credentials directly in the feed URL registered in Merchant Center: https://username:password@yourstore.com/feed.xml. For IP-based restrictions, add Google's crawl IP ranges to your allowlist.
3. Server Error (HTTP 500 or 503)
If your feed generation script crashes or your server is under heavy load when Google attempts the fetch, it returns a 500-series error code and the fetch fails. This is particularly common for dynamically generated feeds on shared hosting where the feed script times out under concurrent load.
Switch to a statically generated feed file. Instead of generating the feed on each request, run a scheduled job that builds the feed file and saves it as a static file to your server. Google then fetches a static file that serves instantly with no processing overhead. Most e-commerce platforms have plugins or export tools that support this pattern.
4. DNS or URL Errors (HTTP 404 or DNS Failure)
If your feed URL has changed (domain migration, URL restructure) or the file was deleted, Google records a 404 or DNS failure. This also happens after SSL certificate expiry, because GMC requires HTTPS and a certificate error causes the connection to fail before any HTTP response is sent.
Update the feed URL in Merchant Center immediately when your URL changes. Do not rely on redirects to carry Google's feed fetcher to the new location. GMC does not always follow redirects reliably for feed fetches. Go to Products > Feeds, edit the feed, and update the URL directly. For SSL issues, renew the certificate before the next scheduled fetch.
5. Firewall or Bot Protection Blocking Google
Cloudflare, Sucuri, and similar WAF services sometimes classify Google's Feedfetcher user agent as a bot and challenge or block the request. The feed URL works fine in a browser but returns a challenge page or a block response to the crawler. You will see either a 403 error or a fetch that "succeeds" but imports a challenge HTML page instead of product data.
In your WAF settings, add a rule that allows requests from the Feedfetcher user agent or from Google's published IP ranges to bypass bot protection for the specific feed URL path. In Cloudflare, this is a Firewall Rule set to "Allow" for the path matching your feed endpoint combined with the Feedfetcher user agent string.
Testing Your Feed URL Before Google Fetches It
Use the "Fetch now" button in Merchant Center's Feed detail page to trigger a manual fetch and see the exact error response in real time. GMC shows you the HTTP status code and a brief description of the failure, which usually points directly to the correct fix category.
For deeper testing, use curl from a server (not your local machine) with the Feedfetcher user agent string to simulate what Google's crawler sees: curl -A "Feedfetcher-Google; (+http://www.google.com/feedfetcher.html)" -I https://yourstore.com/feed.xml. The -I flag shows only headers, so you can see the response code and any redirect chains without downloading the full file.
If your feed fetch errors persist after fixing the obvious issues, check whether the problem occurs consistently or only on specific days and times. Intermittent fetch errors often indicate server load issues during peak traffic periods. Compare your server access logs with the GMC fetch timestamps to confirm the pattern, then adjust your feed regeneration schedule to a lower-traffic window.
Audit Your Merchant Center Feed Setup
Our audit tool checks your feed configuration, fetch history and error patterns to identify exactly what is blocking Google from processing your products.
Run Free AuditFeed Fetch Errors and Account Suspension Risk
A prolonged fetch error that prevents your feed from updating means Google is serving outdated product data in Shopping ads. If the outdated data includes prices or availability that no longer match your landing pages, that discrepancy can trigger a misrepresentation flag, which is a much more serious problem than the fetch error itself.
Fix fetch errors within 48 hours. Google typically retries failed fetches multiple times before marking the feed as stale, but you do not want to rely on retry timing. If your feed has been failing for more than a few days and you already have disapprovals, review your account status against the full GMC suspension checklist to confirm no policy issues have compounded on top of the technical problem.
For accounts already under suspension review, a fetch error that prevents Google from verifying your product data can delay reinstatement. Fix the fetch error before submitting your GMC appeal, and confirm via "Fetch now" that the feed processes cleanly before sending.
Frequently Asked Questions
What is a feed fetch error in Google Merchant Center?
A feed fetch error occurs when Google's servers try to retrieve your feed file from the URL you registered in Merchant Center but cannot complete the download. This can happen due to server timeouts, authentication requirements, IP blocks, or the feed URL returning an error status code instead of the actual feed data.
Why does Google Merchant Center show a fetch error even though my feed URL works in a browser?
Google's fetch crawler uses a specific user agent and originating IP ranges. Your server or CDN may be blocking those IPs, or your site may require cookie-based authentication that a plain HTTP request cannot pass. The URL works in your browser because you are authenticated and not being blocked, but Google's crawler is not.
How do I allow Google to fetch my feed if it is behind authentication?
In Merchant Center, you can configure feed authentication credentials under the feed settings. For basic HTTP authentication, enter the username and password directly in the feed URL. For more complex auth systems, generate a public, unauthenticated feed URL on a separate endpoint specifically for GMC's crawler.
How long does Google Merchant Center wait before declaring a fetch timeout?
Google's feed fetcher applies a timeout of approximately 30 seconds for the initial connection and the full download. If your server takes longer than that to respond or the feed file is large enough that the download exceeds the time limit, GMC records a timeout error. Compressing your feed and using a CDN are the most effective fixes.