1. Separate a variant from the whole product
Check the style, colour and size separately. If a navy jacket is unavailable in medium but still sold in other sizes, the product page can remain useful. Show the actual available choices, rather than presenting the whole style as unavailable.
Record who owns the stock information and when it was checked. A supplier expectation is not a confirmed restock date. Only offer an availability alert if the store can actually deliver that service.
2. Give temporary and seasonal gaps a review date
For a temporary gap, keep the useful product information and make the current availability easy to understand. Review whether internal links still lead shoppers to a meaningful selection. The goal is an honest next step, not a page that appears purchasable until checkout.
For a seasonal collection, ask whether the same customer need will return and whether the collection URL remains accurate. A stable summer-linen collection can have a different lifecycle from a one-off collaboration. Assign merchandising and content owners before deciding to reuse last year’s page.
3. Review the destination before removing a page
For a discontinued item, assess whether a close replacement genuinely answers the original need. Do not send every removed product to a broad category by default. A shopper looking for a particular fit, material or edition may find that destination irrelevant.
Google documents permanent redirects for moved content and 404/410 responses for content that is no longer available. Choose the technical response with the developer after deciding the page’s purpose; a status code does not make an irrelevant destination useful.
Source: Google: HTTP status codes ↗ · Google: redirects and Search ↗
4. Check the complete shopper journey
Review the product card, selected variant, visible stock message and structured data together. Google’s product guidance requires accurate information; an attractive result cannot compensate for a mismatched offer. Recheck the mobile page after a stock or template change.
Keep a decision log: URL, stock scenario, customer need, chosen action, responsible owner and review date. Track search and shopping outcomes with the change date and seasonal context. Do not treat a later traffic change as proof that the URL decision caused it.
Three jackets, three different decisions
Illustration: jacket A lacks only size M, so the page shows the remaining sizes. Jacket B is awaiting a confirmed restock, so the message explains the wait. Jacket C was a one-off edition with no relevant replacement; the team reviews remaining information value before deciding whether to retire it. The stock facts, not a universal redirect rule, drive the decision.
Use this at work
- Identify the missing style, colour or size.
- Verify whether and when replenishment is confirmed.
- Match the page action to a useful customer destination.
- Recheck links, availability and structured data together.
Reference material
Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.