Handle a discontinued product page according to what replaces it. Keep the URL live with useful alternatives when customers still search for the model or need support. Use a 301 redirect when there is a close successor that satisfies the same intent. Return 404 or 410 when the product is gone and no relevant replacement exists. Good ecommerce SEO preserves useful demand without redirecting every retired SKU to an unrelated category.
Before changing the URL, check organic traffic, backlinks, internal links, product relationships, support demand and stock status. A discontinued page with manuals, compatibility information and a clear successor can remain valuable long after purchasing stops.
Quick answer: keep, redirect or remove?
| Situation | Best default | Why |
|---|---|---|
| Temporary stockout or planned return | Keep 200 and mark unavailable | The product is not discontinued |
| Permanent discontinuation with close successor | 301 to successor | The new page fulfills nearly the same need |
| Permanent discontinuation with useful support demand | Keep 200 as an archived product resource | Customers still need specifications, parts or manuals |
| Several retired products consolidated into a true replacement | 301 to the consolidated destination | The destination meaningfully replaces them |
| No replacement, demand, links or support value | 404 or 410 | The resource no longer exists |
| Only a broad category is available | Redirect only if it solves the same shopping task | Irrelevant redirects can behave like soft 404s |
Step 1: confirm that the product is truly discontinued
Do not treat a stockout, seasonal pause, supplier delay or temporarily hidden variant as permanent discontinuation. Ask merchandising for a written status and expected return date. If the item may return, keep the page accessible, show accurate availability and offer a back-in-stock path.
Removing a temporarily unavailable page forces search engines and customers to rediscover it later. It can also break wish lists, campaign links, saved carts and support references. The page should clearly say what is known without promising a restock date the supplier has not confirmed.
Step 2: collect the evidence before deciding
Build a retirement sheet with one row per URL and these fields:
- Product name, SKU and canonical URL
- Permanent or temporary status
- Organic clicks and impressions over the last 12 months
- External referring pages and link quality
- Internal links, campaigns and marketplace references
- Support visits, manuals, warranty or compatibility demand
- Closest replacement and similarity score
- Current structured-data availability and feed status
- Recommended action and owner
Do not choose solely from backlink count. A page with no links may still be the best support resource for thousands of existing customers. A page with links may still have no honest replacement.
Step 3: keep the page when it remains useful
A permanently discontinued product page can keep returning 200 when it provides information people still need. Replace purchase pressure with a clear status, last-known specifications, compatible parts, manuals, warranty details, safety notices and carefully selected alternatives.
The page should state:
- This product has been discontinued and will not be restocked.
- The date or model generation, if relevant.
- Whether support, warranty or replacement parts remain available.
- The closest current alternative and the important differences.
- Links to related support or category resources.
Keep the canonical self-referencing if this archived page is the intended indexable resource. Remove active-sale language, stale price claims and misleading in-stock schema. Schema.org provides a specific Discontinued item availability value that can describe the status in product markup where appropriate.
Step 4: use a 301 only for a genuine successor
A successor should satisfy the reason someone visited the old URL. It might be the next model with the same core use, a renamed product with equivalent specifications, or a consolidated page that explicitly covers the retired variants.
Before redirecting, compare product type, use case, audience, price tier, compatibility and search intent. A discontinued 12-volt charger should not redirect to a general electronics category merely because both sit in the same catalog.
Google’s guidance on redirects and Google Search recommends permanent server-side redirects for permanent URL changes. Update internal links, canonicals and sitemaps to the destination instead of relying on a long chain.
Step 5: return 404 or 410 when nothing replaces the page
If the product and information are gone and no close replacement exists, a real 404 or 410 is appropriate. This is not an SEO failure. It accurately tells browsers and search engines that the resource is unavailable.
Google’s crawling-error documentation says removed content with no replacement should return 404 or 410. The same guidance recommends a 301 when a clear replacement exists. A useful custom error page can offer search, popular categories and support while still returning the correct error status.
Should discontinued products redirect to a category?
Sometimes, but the category must be a credible continuation of the task. Redirect a retired color variant to the parent product, or a discontinued product family to a tightly matched subcategory that prominently offers replacements. Do not redirect every deleted SKU to the home page or a broad catalog.
Google warns against sending many old URLs to one irrelevant destination because that can confuse users and be treated as a soft 404. Its site-move guidance allows consolidation when the new page genuinely contains the replacement content.
What should happen to internal links and navigation?
Remove discontinued items from current-sale navigation, feeds and automated merchandising unless an archive is intentional. Update editorial links to the closest useful destination. Keep links from support content when the retired page remains the correct resource.
Run an internal-link crawl after implementation. Look for old URLs in product recommendations, comparison tables, downloadable PDFs, email flows, help-center articles and structured data. Redirects are a fallback for external and historical links, not a reason to leave internal links outdated.
What should happen to the XML sitemap?
Keep a discontinued URL in the sitemap only when it remains an indexable 200 page that you want in search. Remove URLs that redirect, return errors or carry noindex. Add the successor URL and use an accurate last-modified value when its content changes.
A sitemap is a preferred-URL signal, so do not list a retired URL while canonicalizing or redirecting it elsewhere. This is a common contradiction in automated catalogs.
What should happen to product feeds and structured data?
Keep storefront, structured-data and Merchant Center availability aligned. If a retained archive cannot be purchased, do not mark it in stock. Remove products from active advertising destinations when required, and use the platform’s supported discontinued or unavailable state.
Validate one sample of each template in a structured-data testing tool. Watch for old price, availability, shipping or return values being injected by cached apps after the visible page changes.
How do Shopify and WooCommerce stores implement the decision?
For Shopify, keep the product available to the Online Store only when the archived page should remain public, then remove purchasing and update its template carefully. Create URL redirects for genuine successors and update collection links. A focused Shopify SEO review should also check feeds, Markets domains and app-generated schema.
For WooCommerce, product status, catalog visibility and theme behavior can differ. Use a redirect manager or server rule for permanent replacements, and make sure retired products do not remain in active loops. A WooCommerce SEO check should test the actual response, canonical and schema rather than trusting the dashboard label.
How long should redirects remain?
Keep a useful permanent redirect for as long as old URLs receive users or remain referenced externally. Product URLs can persist in reviews, manuals, social posts and customer accounts for years. Do not remove a redirect simply because a migration spreadsheet is old.
Avoid redirect chains. If product A redirected to B and B is later replaced by C, update A directly to C when C remains relevant. Test loops, hops and destination status in every release.
Discontinued-product SEO checklist
- Confirm permanent versus temporary status.
- Export traffic, backlinks, internal links and support demand.
- Identify a successor and score its intent similarity.
- Choose keep 200, redirect, 404 or 410.
- Update visible availability and purchase controls.
- Align canonical, sitemap, structured data and feeds.
- Update internal links and merchandising modules.
- Test desktop, mobile and Googlebot rendering.
- Monitor Search Console and server logs after release.
- Keep a retirement map for future catalog changes.
FAQs
Should a discontinued product page stay indexed?
Keep it indexable when people still search for the model and the page provides useful support, specifications or alternatives. Remove it when no meaningful resource remains.
Is a 301 redirect always better than a 404?
No. A 301 is appropriate for a close replacement. A 404 or 410 is more honest when no relevant destination exists.
Can I redirect all discontinued products to the home page?
No. Broad irrelevant redirects frustrate users and may be treated as soft 404s. Map each URL to a close successor or return a correct error status.
Should temporarily out-of-stock products be removed?
Usually not. Keep the page live, show accurate availability and offer a restock notification when the item is expected to return.
Do discontinued pages belong in the sitemap?
Only retained, indexable 200 pages should remain. Redirected, noindexed, 404 and 410 URLs should be removed from the sitemap.
Leave a Reply