Unable to check product pages
What Google Merchant Center's Unable to check product pages error means, why the crawler can't do quality and policy checks on your landing pages, and how to fix it.
This error means Google's crawler couldn't reach your landing pages at all, so it can't verify anything about them. Fix it by confirming your pages load reliably for an anonymous visitor and that robots.txt isn't blocking Google's Shopping crawler.
What triggers this error
Google's crawler visits every landing page in your feed to verify the product actually exists and matches what you've claimed. "Unable to check product pages" fires when the crawler can't get a page back at all: it's being blocked, the request times out, or the server never responds. Common causes are a robots.txt disallow rule (often added during a site redesign or by a platform app), a firewall or bot-protection service treating Google's crawler as suspicious traffic, or an authentication wall in front of the page.
This is different from the page loading fine for you in a browser. You're logged in, cookied, and on a UK IP; Google's crawler is anonymous, cold, and mostly hits from US IPs. A page that works perfectly for your customers can still fail this check if it's set up to challenge or block unfamiliar bots.
Work through the landing page crawl errors guide if you're seeing several different crawl-related reason strings at once, it covers all six failure modes in one place.
/tools' feed health scoring flags landing pages that fail to respond during enrichment, so a crawler-blocking issue on your site surfaces before Google's own diagnostics catch it.
Step by step
- Fetch the landing page cold, as Googlebot. Request the exact `link` URL from your feed using a Googlebot user agent, from outside your own network. If it hangs, times out, or errors, that's the root cause, not the Merchant Center message.
- Check robots.txt for the crawler specifically. Fetch /robots.txt and confirm no disallow rule covers your product paths for Google's user agents. This is the single most common cause of this error, and it often appears after a redesign or a platform app change.
- Rule out server-side blocking. Check for bot protection, CAPTCHAs, or firewall rules that challenge datacentre IPs. Google crawls mostly from US IPs with no cookies or login, so anything that treats an anonymous first-time visitor as suspicious will block it too.
- Resubmit and let the crawl re-run. Once the block is lifted, Google needs to re-crawl before the error clears. There's no button to force this, it happens on the next scheduled crawl.
Frequently asked questions
Is this the same as Product page unavailable?
No. Unable to check product pages means the crawler couldn't reach the page at all (blocked, timed out, no response). Product page unavailable means it reached the URL and got back an error like a 404 or 5xx.