Google Merchant Center Crawl Errors: Fix All Issues 2026
Crawl errors in Google Merchant Center are distinct from feed errors. They occur after the feed is processed successfully, when Google's Shopping crawler visits your actual product pages and hits a problem. Each crawl error disapproves the affected product. This guide covers every crawl error type and the exact fix for each.
Feed Errors vs. Crawl Errors: The Difference
Feed errors happen during feed processing, before Google even visits your pages. Crawl errors happen when Google's Shopping crawler goes to the product landing page URL from your feed and cannot verify the page content. Your feed can process without a single error, but if the landing pages are misconfigured, you will still accumulate crawl errors and product disapprovals.
Both error types appear in Merchant Center diagnostics, but they require completely different fixes. Feed errors are fixed in your data. Crawl errors are fixed on your website itself.
Every Crawl Error Type and How to Fix It
1. Robots.txt Blocking the Crawler
If your robots.txt file disallows Googlebot, the Shopping crawler (which also respects robots.txt directives), or a wildcard user agent on your product URL paths, Google cannot access those pages. This is one of the most common crawl errors on Shopify stores, where the robots.txt is sometimes auto-generated with overly broad disallow rules.
Check your robots.txt at https://yourstore.com/robots.txt. Look for Disallow: /products/ or Disallow: / with a User-agent that includes Googlebot or a wildcard. Remove the disallow directive for your product URL paths. On Shopify, you can only edit robots.txt through a theme liquid file in some plan tiers. Confirm the change with Google Search Console's robots.txt tester, then trigger a re-crawl in GMC.
2. Noindex Tags on Product Pages
A product page with a meta robots noindex tag or an X-Robots-Tag: noindex HTTP response header tells Google not to index the page. The Shopping crawler respects this directive and will not process the page content for feed verification. The product gets disapproved as a crawl error because Google cannot confirm the price, availability, or other attributes.
Search your product page templates for any noindex directives. These sometimes appear when developers add noindex to template files during staging and forget to remove them before launch, or when a third-party app (review apps, A/B testing tools) injects noindex headers. Check both the HTML meta tag and the HTTP response headers using curl -I on a product URL.
3. Redirect Chains on Product URLs
When a product URL in your feed redirects, then that redirect redirects again, and possibly again, you have a redirect chain. Google's Shopping crawler follows redirects but has a limit. Long redirect chains sometimes result in crawl errors, and some intermediary redirects return incorrect status codes that terminate the chain early.
Audit your product URLs for redirects using a tool like Screaming Frog or a simple curl -L command that follows redirects. Update the URLs in your feed to point directly to the final destination URL. Never rely on redirects to carry GMC's crawler where you want it. The feed should contain the exact URL Google should crawl, with no intermediate hops.
4. Page Load Timeout
If a product page takes longer than a few seconds to respond or fully render, Google's Shopping crawler may timeout before it can verify the page content. This is increasingly common on stores that rely heavily on client-side JavaScript rendering for price and availability data, because the crawler needs the rendered output, not just the raw HTML.
Ensure that price, availability, and condition are present in the server-rendered HTML of your product pages, not just loaded via JavaScript after page load. Use Google's Rich Results Test tool to see what the crawler actually sees when it renders your product page. If critical data only appears after JavaScript execution, move that data into the initial HTML response.
5. Access Denied or Login-Required Pages
If your product pages require a login, show a paywall, or return a 403 status to non-authenticated visitors, the Shopping crawler cannot access them. This also applies to pages behind country-based IP restrictions, where users from outside your target region see a different page than local users.
Confirm that your product pages are publicly accessible without authentication by testing them in a private/incognito browser window and from an external IP (use a VPN or a service like GTmetrix). Geo-restricted storefronts are a particularly tricky case, as the pages may be accessible in your target country but blocked to Google's crawl infrastructure originating from different regions.
Using GMC Diagnostics to Prioritize Crawl Error Fixes
In Merchant Center, go to Products > Diagnostics and filter by the crawl error issue type. Export the full list to a spreadsheet. Sort by the number of affected products to identify which error type is causing the most disapprovals. Fix the highest-impact error type first.
For stores with thousands of products, not every crawl error requires individual attention. Look for patterns: if 800 products all have crawl errors and they all follow the same URL pattern, a single template or robots.txt fix will resolve all 800 at once. Check if affected URLs share a category, a product type, or a URL structure before investigating individual products.
After fixing crawl errors, request a re-crawl through Merchant Center. Go to the affected product, open the issue details, and use the "Request review" option if available for that error type. For widespread crawl errors affecting entire product categories, use the Google Search Console URL Inspection tool to test a sample URL and confirm the fix is working before waiting for GMC to crawl the full set.
Find Crawl Errors Across Your Entire Catalog
Our audit tool scans your Merchant Center account for crawl errors, robots.txt conflicts, noindex issues and redirect chains. Get a prioritized fix list in minutes.
Run Free AuditCrawl Errors and Suspension Risk
Crawl errors cause product disapprovals, not account suspensions directly. However, if crawl errors prevent Google from verifying your product data and the cached data in your feed no longer matches your store's actual prices or availability, you are at risk of a misrepresentation violation. That escalation path from technical crawl error to policy violation is the primary suspension risk.
Fix crawl errors before they age. An error that persists for more than 14 days while your products remain active in Shopping ads with unverifiable data is the profile that triggers manual reviews. If you are already under review, check whether your appeal covers the crawl error root cause as part of the broader suspension fix process.
Crawl errors on competitor analysis: if you have a large number of crawl errors alongside policy flags, reviewers sometimes treat the combination as evidence that the account is not properly maintained. The GMC suspension checklist helps you confirm that both technical and policy issues are resolved before submitting an appeal.
Frequently Asked Questions
What are crawl errors in Google Merchant Center?
Crawl errors in GMC occur when Google's shopping crawler visits a product landing page listed in your feed and encounters a problem: the page blocks crawling via robots.txt, returns a noindex directive, has a redirect chain that leads to a dead end, or takes too long to load. These errors result in product disapprovals because Google cannot verify the page content matches the feed data.
How do I check which product pages have crawl errors in GMC?
In Merchant Center, go to Products > All Products and filter by the 'Crawl errors' issue type. Each affected product shows the specific error. You can also export the diagnostics report to a spreadsheet to see all affected URLs at once, which is much faster than checking pages individually when you have a large catalog.
Does a noindex tag on a product page cause a GMC crawl error?
Yes. If a product page carries a noindex meta tag or an X-Robots-Tag: noindex HTTP header, Google's Shopping crawler will not process that page's content. GMC then cannot verify the product data and disapproves the item. Remove the noindex directive from any page you want to include in Shopping ads.
Can a slow product page cause a crawl error in GMC?
Yes. Google's Shopping crawler applies a page load timeout. If a product page does not fully respond within that window, the crawler records a timeout crawl error. Pages with heavy JavaScript rendering, unoptimized images, or slow server response times are the most common triggers.