Product page unavailable

Product page unavailable means Google could not access the landing page in the link, link template, or mobile link. The fix guide is How to fix: Product page unavailable. A 5xx, a timeout, or a URL that never returns a page sits here. A 404 is often reported as Destination not working as well. Google’s crawl overview is Product crawl issues.

Shopify causes

The theme or an app proxy returns 500. A liquid error, an app embed, or a broken section can fail the product template for every product or for one template only. A storewide outage flags every URL at once.

The fetch times out. A slow app proxy on the product page, or a store under load, can exceed the crawler’s wait. Google and this app can disagree on the timeout. Retry before you treat one slow response as an outage.

The store is password protected or geo-blocked. Crawlers that are challenged do not get the product. Google notes that it often crawls from the United States, so a geo rule that blocks the US blocks the check.

The URL is not http or https, or the host is wrong. A feed that submits a handle without the shop domain, or a preview-theme URL that expires, does not resolve to a public product page. The online store URL in Shopify is the one the Google & YouTube app normally uses.

What to change

1. Open the product URL in a browser and on the storefront status page. A 500 in the theme editor logs is a theme or app error, not a feed typo.
2. Disable the app embed or section that throws, publish, and request the URL again until it returns 200.
3. Remove the storefront password and geo rules that block US crawlers while you need the destination checked.
4. Confirm the catalog URL is the public `https://…/products/…?variant=` URL, not an admin link and not an expired preview.
5. After the store is stable, scan again. If every product failed together, fix the store before you edit the feed item by item.

How PageCop detects it

The app files Product page unavailable when the product URL returns HTTP 500–599, or when the fetch itself fails (timeout, DNS, connection reset). The evidence includes the status or the error text. It files Destination not working for 404, 410, and bad redirects, because those are a different landing-page result. One timeout is recorded as unavailable and the suggestion says to retry, since the failure can be this app’s network path.

FAQ

A single 500 flagged every product. Do I edit the feed?

Not first. If the same 500 hits the whole catalog, the storefront is down. Fix the theme or the app that throws, then scan again. Removing items from Merchant Center does not repair a 500.

How is this different from Destination not working?

Destination not working is the crawler landing in the wrong place or on a missing URL: 404, 410, home page, collection, or a robots.txt block. Product page unavailable is the server failing to return the page: 5xx or a fetch that did not complete. Google’s help page uses Product page unavailable for several of these. This app keeps the two names apart so the fix is different.