Out-of-Stock Products: What to Do With the URL

Every store faces it weekly: a product sells out, gets discontinued, or vanishes from the supplier — and its URL, possibly carrying rankings, links and bookmarked demand, needs a decision. The wrong defaults (mass 404s, instant redirects-to-home, zombie pages selling nothing) each leak equity or trust; the right answer is a policy tree keyed to one question: is it coming back? Here's the tree, the implementation details per branch, and the template work that makes it automatic.

The policy tree

1. Temporarily out of stock (restock expected): keep the page live, status 200, honest. The page keeps its rankings and links (de-indexing and re-indexing on every stock cycle would churn positions permanently); the visitor gets truth plus options: restock date if known, email-me-when-available capture (turning dead visits into demand data and a sales list), and alternatives cross-linked. Update the schema availability to OutOfStock/BackOrder — honest markup keeps the SERP listing accurate and penalty-free.
2. Discontinued, direct successor exists (new model, replacement SKU): 301 to the successor — the equity and the intent both transfer to the page that genuinely answers the old demand, the textbook relevant-redirect case per the equity findings. Add one line on the successor page acknowledging the lineage ("replaces [old model]") for arriving searchers' orientation.
3. Discontinued, no successor, category still served: 301 to the closest genuinely relevant level — usually the subcategory, never the homepage (bulk home-redirects read as soft 404s and transfer nothing, per the standing rule). Exception worth making: pages with meaningful external links or steady search demand can stay live as honest "no longer available" pages with alternatives — preserving the URL-level equity while still serving the visitor — a judgment call the links data decides.
4. Discontinued, category dead too (exited the line entirely): 410 the products, redirect the category only if a truly adjacent one exists — honest deletion beats forced relevance, per the no-fake-counterparts rule.

The operational layer

Policy only works automated: the platform should key the behaviours to inventory status (temporary vs discontinued as a product field driving template state and redirect creation), the redirect map lives in version control like the migration estate it gradually becomes, and the quarterly audit sweeps for the failure modes: zombie pages (discontinued items still 200 with no path forward), 404s carrying referring domains (the free-equity recovery, always), and redirect chains bred by successive successor hops (A→B→C when B also died — flatten to A→C, per hygiene).

Frequently asked questions

Won't keeping out-of-stock pages live hurt conversion or quality signals?

A store full of dead grids, yes — which is the category-level pruning rule. Individual OOS pages behaving honestly (status shown, capture offered, alternatives linked) serve visitors fine and hold rank position for the restock — the churn of toggling them dead costs demonstrably more. Watch the ratio, not the instance.

Seasonal products — same as temporary out-of-stock?

Yes, with the calendar advantage: keep the URL alive year-round (the equity accumulates across seasons — annual URL churn is the classic seasonal mistake), let it hold "returns in [season]" state off-peak, and re-merchandise the same page each cycle. The URL is the asset; the stock is just its current contents.

What about variant-level stockouts (one size gone)?

Page stays fully live (the product exists), variant marked unavailable in UI and offer markup, restock capture per variant if the platform allows. Only full-product decisions climb the tree. Like every policy in this silo, the payoff compounds quietly: URLs that never leak keep every link they ever earned working — and earning those links stays the parallel programme (ours to run, if you'd like).