Renamed handles
Change a product title and Shopify may change its handle, leaving the feed pointing at the old URL. The old address 404s or lands somewhere generic while the product thrives at its new home, and Merchant Center reports a missing product page for an item that plainly exists. After any rename, fix the source of the URL in the feed rather than stacking a redirect; redirects decay and the same item fails again on the next sync.
Redirects that read as missing
A product URL ending on a collection page or the homepage is not “moved” in Google eyes. It is gone. This happens with deleted variants, unpublished products left in the feed, and collection URLs submitted instead of product URLs. Merchants often report the error clearing after a manual recrawl, which is the signature of a URL still being generated wrong at the source: the recrawl forgives it once, the next sync re-breaks it.
Soft 404s
The worst variant returns HTTP 200 with no product on the page: a template rendering an empty state, an app swallowing the error, a draft product with a live URL. Everything looks healthy to every status checker while Google decides there is no usable content. If a URL returns success but shows no buyable product, treat it as dead.
URL audit routine
- Every feed URL opens the product itself in a private window, not admin preview
- No product URL ends on a collection, search, or homepage
- Renamed handles updated at the feed source, not papered with redirects
- Unpublished and deleted products removed from the feed
- Soft 404s verified by content, not just status code
Related error guides: missing product page · product page unavailable
Shipwork requests your product URLs from outside your network and reports the status, the full redirect chain, and the final destination of each one. Free, no account, no signup. Paste your store address.
Check my URLsQuestions
Why does Google say “missing product page” when the URL exists?
Are redirects bad for product URLs?
What is a soft 404?
The error cleared after recrawl, then came back: why?
Keep reading