Why do pages load for me but fail for Google?

Bot protection, firewall rules and rate limiting often treat crawlers differently than your warmed browser session. Only an outside request shows what Google sees.

What statuses disapprove products?

5xx errors, 404/410 dead pages, 403/401 blocks and 429 rate limits. Redirects do not disapprove outright but the feed should carry the final URL.

How many pages are checked?

A sample of up to 12 product pages, fetched politely with concurrency limits so your server is not hammered.

What your product pages return to Google

Your pages load fine in your browser. Google crawls them from somewhere else, and a 500, a block or a slow response there quietly disapproves the product. This checks them from outside your network.

Shipwork requests a sample of your product pages the way a crawler would, and reports exactly what came back. Nothing is stored.

Questions

Why do pages load for me but fail for Google?: Bot protection, firewall rules and rate limiting often treat crawlers differently than your warmed browser session. Only an outside request shows what Google sees.
What statuses disapprove products?: 5xx errors, 404/410 dead pages, 403/401 blocks and 429 rate limits. Redirects do not disapprove outright but the feed should carry the final URL.
How many pages are checked?: A sample of up to 12 product pages, fetched politely with concurrency limits so your server is not hammered.