A zero stock level does not determine the fate of a product URL. A shipment may be delayed, a model may disappear permanently, and the instructions and specifications for an old product may still be useful to its owners. Automatically deleting every out-of-stock product page conflates these situations.
Make the decision based on the offer’s status, the page’s usefulness, and whether an equivalent replacement is available. Choose the technical action afterward. A page that answers 200 should clearly state what visitors can do now; a redirect should lead to a suitable offer; deletion should be intentional and verifiable.
Confirm the product’s status with the person responsible for the assortment
Distinguish at least four states: temporarily unavailable, expected delivery with no confirmed date, discontinued, and removed from the store’s assortment. The last two states also differ: the manufacturer may still sell a model that a particular store no longer offers.
For each candidate, record the SKU, URL, source of the status, expected return date, and decision owner. If the date is unknown, state that. A manager’s expectation of a new shipment must not become a promise on the page or in structured data.
Check product variants separately. One unavailable size does not mean all sizes are out of stock. A hypothetical jacket page with several variants requires checking the selected size and the overall purchase flow. If the template shows “in stock” for a product with an unavailable selected variant, fix this inconsistency first.
Choose an action using the matrix, not the stock level
Match the commercial status to the visitor’s task. A product page may be useful for comparison, finding consumables, checking compatibility, viewing instructions, or learning about a confirmed successor.
| Status | Preferred decision | What to confirm |
|---|---|---|
| Product temporarily unavailable | Keep the product page active with an accurate status | Whether it may return and that purchasing is disabled |
| Delivery not confirmed | Keep useful information without promising a date | Who will review the decision and when |
| Model discontinued but still useful to owners | Keep it as an archive page | Instructions, specifications, and a prominent status |
| Direct successor exists and the old page is no longer needed | Consider a permanent redirect | Whether the purpose and specifications match |
| Product and useful page are both gone | Return 404 or 410 | No suitable replacement and correction of links |
This is an editorial decision matrix, not a universal search engine rule. Two products with the same zero stock level may require different decisions. For a detailed analysis of the value of a URL to keep, see the article on what to do with an outdated page.
Do not change the URL, name, and product identity all at once just to preserve an old product page. Visitors following a saved link should be able to tell which model they opened. A new SKU and a different set of specifications usually require a separate decision about the URL and the relationship between the models.
Align the product page, purchase flow, and availability data
If the page remains available, check every place where it offers the product for sale: the text status, purchase button, quick order, selected variant, similar products block, internal search results, and structured data. Changing a label does not help if another button still accepts orders for an unavailable product.
For a temporary sales suspension, Google recommends keeping the site accessible and updating product data. This helps people find the description and return later. The recommendation concerns a temporary business suspension; its applicability to a specific product page should be assessed based on the actual status of the offer. Google guidance on temporarily suspending sales.
In Product markup, the availability property can reflect, for example, OutOfStock, BackOrder, or Discontinued. Choose the status that matches the visible offer, and check that the CMS updates the active Offer block. Google reference for product snippets.
If the store sends product feeds, include them in the task separately. Confirm who owns the feed and when it updates: a corrected product page does not confirm that an external channel has received the new availability status. Record the responses and the time each channel was checked.
Check whether the replacement is suitable
A similar product is not always a replacement for the original. Compare purpose, compatibility, key specifications, price range, and what the user expects from the old link. For a spare part, compatibility matters more than visual similarity; for a license, the terms of use; for a consumable, the equipment model.
In a hypothetical assortment, a discontinued filter and a new filter of the same size may have different mounting connections. Redirecting between them would make people check compatibility again. Keeping an archived product page that explains the differences and links to an available option may be more useful.
Assign an owner to confirm the match and record the basis for the decision. Do not redirect the entire discontinued assortment to the homepage just because it is available. The user loses a specific answer, and redirect reports no longer show the purpose of the transition.
If you choose 301, check the destination page without signing in: it should work, describe the intended replacement, and not send the visitor further along a chain. Do not leave the new product page’s canonical pointing to a deleted URL.
Delete the page with an explicit HTTP response
When a product page is genuinely no longer needed and there is no replacement, its handling should reflect its removal. Google states that responses 404 and 410 are not indexed, and that old URLs with these responses are eventually removed. A 200 response does not by itself guarantee indexing and may accompany a soft 404 when the page is effectively empty. Google documentation on HTTP status codes.
A custom error page can suggest a category and search while retaining the 404 status. Check the response from the original URL, not just the error template’s address. Redirecting to a polished placeholder with a 200 code conceals the removal.
For a recurring issue, see the analysis of soft 404 with status 200. Do not add an empty product page to the sitemap or navigation if the decision is to delete it. The list of URLs to be removed must be approved before changing the template.
Send a decision register to development
Prepare a table with the SKU, original URL, product status, action, destination URL if redirecting, availability status, owner, date, and verification criterion. A separate “reason” field helps prevent automatic synchronization from reactivating the product.
Before processing in bulk, check one example of each action. It is useful to include a product with variants, an archive with instructions, and a product that has returned to stock. When it returns, the old purchase restriction should be removed, and the status and offer data should be updated consistently.
The reChecker technical audit helps check responses and links on crawled pages. It does not determine whether replacements are compatible or the actual delivery date: the person responsible for the assortment confirms this information.
Accept the changes and schedule a review
For a page that is kept, check its availability, prominent status, the actual behavior of its buttons, and consistent markup. For a redirect, check the source response, destination URL, and replacement content. For a deletion, check for 404 or 410 and confirm there are no active internal links to the deleted product.
First request the original URL with a regular GET request, without following redirects:
curl --silent --show-error --dump-header - --output /dev/null \
'https://example.com/catalog/product'Here, example.com is a placeholder URL. Replace it with the URL being checked from the decision register. The command outputs the headers from the first response, including the HTTP status and Location if the server sent a redirect; the page body is not saved.
If a redirect is selected, check the entire chain and the destination URL separately:
curl --silent --show-error --location --max-redirs 10 \
--dump-header - --output /dev/null \
--write-out '\nFinal HTTP: %{http_code}\nFinal URL: %{url_effective}\nRedirects: %{num_redirects}\n' \
'https://example.com/catalog/product'The output will include the headers for each response, followed by the final status, URL, and number of redirects. Compare them with the chosen action:
- For a useful product page that is kept, the expected source response is 200. Open the page separately and check its content and buttons: the headers do not confirm these.
- For an approved permanent replacement, the expected source response is 301 with
Locationpointing to the intended product page, and the final response is 200. Check that the redirect leads directly to the selected replacement, with no unnecessary intermediate URLs. - For an intentional deletion, the expected source response is 404 or 410. Following redirects must not conceal this response behind an error page with a 200 code.
This check confirms that the decision in the register was implemented; the status alone does not determine what to do with the product and does not prove indexing.
Do not include traffic growth as a technical acceptance criterion. A decision may be correct even if demand for a discontinued model declines. Monitor search performance separately and compare it with seasonality, assortment size, and the history of changes.
For the “delivery unknown” status, assign a review date and a specific owner. This prevents the product page from remaining for years with a promise that it will be available soon. The outcome is a verified register of different actions for different statuses, not one rule for every out-of-stock product.