When the page loads for you but returns an error to Google

What the error means

Google could not fetch your landing page. The item is disapproved even though the page opens perfectly in your own browser.

Why Google rejects it

This is almost always the crawler being refused rather than the page being broken: bot protection, a firewall rule, or rate limiting triggered by fetching many URLs quickly. You see the site from your own network, warmed and often whitelisted. Google does not.

How to fix it

1. Check what an outside request actually receives, rather than what your browser shows.
2. Look at bot-protection settings if you are behind a CDN or WAF, and allow legitimate crawlers.
3. Check whether the errors cluster in time rather than on particular products. That pattern points at rate limiting, not a bug.

Common causes

Bot protection or WAF rules

Security products that challenge unknown visitors, block data-centre IP ranges or rate-limit bursts of requests can answer Google's crawler with a 403, a CAPTCHA page or a timeout while your browser sees a normal page.

Rate limiting during feed verification

Merchant Center fetches many landing pages in a short window. If errors appear in batches on a few days rather than on the same products every time, the server or CDN is throttling the crawler.

Country or IP blocking

Geo-blocking rules that allow only your home country can block Google, which crawls mostly from the United States. The page is fine for customers and unavailable to the one visitor that approves your listings.

Slow or failing server responses

Pages that take many seconds to respond, or return 5xx errors under load, time out for the crawler. Heavy apps and uncached product pages are the usual cause.

Password or maintenance mode

A storefront password, a coming-soon plugin or a maintenance page left on for one domain or subdomain makes every landing page unavailable to anyone who is not logged in.

Fix it on your platform

On Shopify

1. Confirm the storefront password is off under Online Store > Preferences for the domain in your feed.
2. If a third-party CDN or proxy sits in front of Shopify, check its firewall and bot settings and allow verified search engine crawlers.
3. Check that the domain in the feed is the primary domain or redirects to it cleanly, not to a password page.
4. Remove apps that block visitors by country if you advertise in countries they block.

On WooCommerce

1. Check security plugins (login protection, firewall, country blocking) for rules that block Googlebot or data-centre IPs.
2. Look at the server access log for requests with the Googlebot user agent and the status codes they received.
3. Enable page caching for product pages so crawler bursts do not overload PHP.
4. Disable maintenance or coming-soon mode for the public site.

On other platforms

1. In your CDN or WAF, allow verified search engine bots and avoid challenge pages for them.
2. Check server logs for 403, 429 and 5xx responses to Googlebot in the window when errors appeared.
3. Make sure product pages respond in a few seconds without JavaScript.

How to confirm it is fixed

1. Run the product page check on an affected URL to see the status an outside request receives.
2. Use URL Inspection's live test in Search Console on the same URL; a successful live test means Googlebot can fetch it now.
3. Re-run the check at a different time of day to catch rate limiting that only appears under load.
4. Once fetches succeed, wait for Merchant Center to recrawl or request a review of the affected items.

Other errors like this