The product page has been deleted, the server returns 404 to say that the page does not exist, and the template still outputs a canonical pointing to the category. The team assumes the tag will move the page to a new address. These are two different decisions: the status of a missing resource and the designation of a preferred version of existing content.
Is the product temporarily unavailable or permanently deleted?
Google uses the HTTP status when processing a URL; a 404 response indicates that the resource is missing. Official documentation.
In the content management system (CMS), a record may still exist with an “archived” status even though its public resource has been deleted. Discuss with the catalog owner whether customers may be able to buy this product again, whether its specifications are useful, and whether a direct equivalent exists. The response depends on this. A retained product page with instructions and an accurate availability status can still be useful. A page that only says “nothing found” serves a different purpose. A canonical in a shared template does not answer whether the product has been deleted or is temporarily unavailable. First decide how the product page should behave, then configure its response and tags.
Three options for a product page
| What happened to the product | Is there a useful page? | Response from the old URL | What the customer sees |
|---|---|---|---|
| Product permanently deleted | No replacement | 404 or 410 | A useful error page |
| Product replaced by a new model | A comparable equivalent exists | Permanent redirect | The destination product page is available |
| Temporarily out of stock | The product page is useful | Keep the page | Accurate availability status |
| 404 plus canonical | Conflicting expectations | Check the deletion logic | Do not treat it as a move |
Where to check the actual response status
Open your browser’s developer tools, go to the Network tab, reload the old URL, and select the page request. Note the status, the redirect address in Location, and the returned HTML. Ask a developer to check a regular page request (GET): the server may handle a request for headers only, without content (HEAD), differently. Also check a product that never existed. If it gets the same 200 template, the problem may be in the CMS’s general routing. Comparing two missing addresses can help distinguish the configuration for a discontinued product page from the universal handling of unknown paths.
Run this command in a terminal, or give it to a developer, to save the response from the old product page.
curl -sS -D headers.txt -o response.html 'https://example.com/product/old/'Without -L, curl saves the first response from the old product page: the status and any Location will be in headers.txt. Codes 404/410 mean the resource is missing; 301/308 mean a permanent redirect; 200 means the page returned a successful response. For a deleted product, expect 404/410; for a move, expect 301/308 to the direct replacement. In response.html, check the message and make sure there is no active purchase option. Replace example.com with your domain; this GET request does not change the site settings. curl documentation.
Why a canonical to a category does not move a product page
Canonical helps select the primary URL for identical or very similar pages. A deleted product page and a category containing dozens of other products usually have different information. Even a correct tag in the HTML head does not make the browser redirect or turn 404 into 301. If you need a real move to a direct replacement, use the appropriate server rule and check where it points. If you need a 404, do not try to compensate with a canonical. For deletion, check 404/410; for a move, use a redirect to a suitable replacement. A canonical tag alone does neither.
Update the old route and links
Configure the CMS or server to determine what visitors should receive when they open an archived product page. Remove the old entry from the sitemap and update links in collections and recommendations if they should no longer lead to an unavailable product. For a direct equivalent, check that there is only one redirect, that the new product page is available, and that it has its own metadata. Do not automatically delete all historical content: editorial links to an old model in a review may be justified, but readers need a clear message that the product is no longer sold.
Remove the purchase option and price from the error page
Keep a clear heading, explanation, and working navigation on a page for an unavailable product. Do not show an active purchase button for a discontinued model if it cannot be ordered. Alternative recommendations can remain, but label them as other products. Ask a developer to check the machine-readable Product markup and Offer data in JSON-LD format: a generic template must not show the price and availability of an unavailable model on an error page. This is a separate check from canonical. For a useful product page that is temporarily unavailable, the markup and visible status should describe the same product. After changing the status, open the whole page. Visitors should not see “product deleted” beside a “Buy” button and a price, and JSON-LD should not describe a deleted model as available.
Check the old product page again
A deleted product with no replacement returns 404 or 410. An old product page with a direct replacement redirects to it once, with a permanent redirect, and the new product page returns 200. An unknown product also shows a missing-page message with the corresponding status.
Also read: HTTP status codes: complete guide (200, 301, 404, 500...) and Soft 404 with a server response of 200. Site checks are available on the reChecker technical audit page.