Blog / Technical SEO /
Technical SEO: 404s from discontinued variants
The blue one sold out for good. Someone removed it from the catalogue. Tidy.
Except a customer bookmarked that variant’s URL. Another site linked to it. Search engines found it months ago. And now it returns a 404.
A discontinued variant can leave more behind than an empty option in a selector. The right response depends on whether that URL still serves a purpose, and what replaced the item.
A 404 isn’t automatically an SEO emergency. It just says the requested resource wasn’t found. The problem comes when a useful, linked or still-wanted page disappears with no sensible way forward. So first find out which URLs are affected and why they exist.
Find the variant URLs that matter
Start with the product catalogue and the platform’s URL rules. Some stores expose each variant as a query parameter on one product page. Others create separate paths or indexable URLs. Don’t assume every variant has its own page. Crawl the site and compare the results with Search Console, analytics and server logs where you have them. External links and bookmarks can reveal URLs the current navigation no longer shows.
Group the URLs by product and variant. Record the response code, destination, any traffic or link evidence, and whether the variant is truly discontinued. A temporary stock-out is not a permanent retirement. An item that’s coming back shouldn’t be treated like an obsolete model.
Decide what a shopper should see
If the main product is still available and only the variant has gone, the product page may be the best destination. Make clear which options remain, and don’t preselect a different variant in a misleading way. If the whole product is discontinued, is there a direct successor or a useful category page? Redirect only when the destination genuinely meets what the visitor came for.
Don’t send every retired variant to the homepage. It strips the context and gives visitors no clue what happened. If there’s no suitable replacement and nothing useful to keep, a 404 or another appropriate unavailable response can be the honest answer. Don’t build a thin “discontinued” page just to keep a URL alive if it helps nobody.
For products with safety, compatibility or warranty implications, be careful recommending a substitute. A similar model might not fit the same device or use. Confirm compatibility with an authoritative source before redirecting or suggesting a replacement on the page.
Implement a narrow, testable rule
If redirects make sense, map each old URL to the right destination and test the exact variant path. It should resolve in one step where possible, with no loop or chain. Keep the destination canonical and indexable if it’s meant to appear in search. Check how the platform handles variant parameters, because a broad redirect could break live variants along with the retired ones.
Test on staging or a small set of URLs before rolling a pattern out site-wide. Keep a redirect map with the reason, date, owner and destination. If the platform manages variant URLs automatically, read its documentation or ask the provider before adding custom rules that fight its routing. I’ve learnt to distrust any redirect rule that can’t be explained in one sentence.
Update internal references and product data
Remove or update links to unavailable variants in navigation, product recommendations, comparison tables, feeds and structured data. Make sure the product page doesn’t keep presenting a retired option as buyable. If stock data drives availability, check the product record and the template agree.
If old variant URLs had meaningful links or visits, keep them on a monitoring list for a while. Use that to find references you missed. But don’t treat every crawler request to an old URL as a customer problem. Separate real demand from stale bots and malformed links.
Monitor after the change
Check server responses after deployment, and watch Search Console for indexing or crawl issues over time. Reports lag, so don’t judge the change on a single day. If tracking is set up, compare the relevant product journeys in analytics, but don’t claim a redirect changed sales without evidence.
If a customer reports a broken bookmark, find out what they were trying to buy and whether there’s a better destination. That kind of feedback exposes a missing successor explanation, or a product page that needs a clearer “no longer available” message.
Make retirement part of the product lifecycle
Plan how variants will be retired before the catalogue changes. Who confirms whether a variant is temporarily unavailable or gone for good? Who chooses the destination? Who updates the feed and related content? A short checklist stops a stock update turning into an accidental URL migration.
Not every variant needs its own redirect, either. If a colour, size or pack option was never a separate URL, creating one now just adds complexity. Base the work on how URLs actually behave and on real demand. The cleanest fix might be a message on the product page, a corrected internal link or a more useful successor page, not a new redirect rule.
When a product is retired, keep enough information internally to answer support questions, even if the public page goes. The customer-facing destination and the internal record have different jobs. Keeping them separate lets the store be clear online without losing the details needed for fulfilment or warranty conversations.
Related reading
- Technical SEO: soft 404s on retired products
- A method for prioritising crawl errors by affected page group
- Technical SEO: JavaScript errors in rendered pages
A discontinued variant URL deserves a decision, not a reflex. In my book that means three steps: check whether the page still helps anyone, choose an honest destination or response, and test the result. So, which retired variant on your site still has a customer path worth preserving?