What Should You Do When Products You No Longer Sell Still Get Traffic?

Discontinuing a product in PrestaShop shouldn't mean abandoning its URL or throwing away hard-earned organic traffic and backlinks. Leaving retired product pages unmanaged creates soft 404s, wastes crawl budget, and leads prospective buyers straight into dead ends.

Choosing between a 301 redirect, a 410 removal, or an informative archive page depends entirely on what the URL is currently worth. By using a clear triage system, you can protect your store's search rankings and guide shoppers toward relevant, available alternatives.

Why A Discontinued Product Page Still Matters

Redirect a discontinued product page when the URL still earns traffic, links or rankings, and remove it when it does not. A 301 passes visitors and search equity to a live page, while a 410 Gone tells search engines the item is permanently gone. A dead product page is an asset you either route or retire, never one you abandon.

A product you no longer sell can keep pulling visitors and search value long after it leaves your catalogue. Best practice is usually a 301 redirect to the closest equivalent product, the parent category, or a successor page. Use a 410 only when no relevant destination exists. In PrestaShop, that decision shapes how you handle the product's URL, its category associations and its search engine indexing. Get it wrong and the outbound links, rankings and direct traffic the page earned quietly evaporate.

Those old URLs carry more weight than most store owners assume. A discontinued product page may still collect backlinks from review blogs, forum threads and press mentions, and it may rank for model names and part numbers that newer products don't target. Shoppers searching for a specific item can land there months after you stopped stocking it. What happens next decides whether that visit becomes a sale or a bounce.

Leaving dead pages untouched causes three quiet problems:

• Soft 404s: PrestaShop still returns the product page with its old template, empty stock and a dead "Add to cart" button. Google reads this as a low-quality page, and shoppers see a product they can't buy.
• Wasted Crawl Budget: Search engines keep recrawling URLs that no longer serve a purpose, pulling attention away from pages you want indexed.
• Lost Conversions: A visitor who wanted that exact item gets no alternative, no explanation and no route back to a live product.

Triage starts with one question: does this URL still earn traffic, links or rankings? If yes, it deserves a deliberate destination. If no, it deserves a clean removal. PrestaShop gives you the tools for both, but only once you know which bucket each page falls into.

Should You Redirect or Delete a Discontinued Product Page?

The short answer: redirect when the URL still has traffic or links worth keeping, and delete with a 410 when it does not. Redirecting passes visitors and search equity to a relevant live page. Deleting removes the URL entirely, so any remaining links point at nothing.

Most stores get this wrong in one direction only, blanket-redirecting every dead product to the homepage. That flattens relevance: a shopper hunting a specific discontinued item lands on a general home page and leaves. The better move is to triage each URL by its traffic value and pick the lightest-touch option that fits.

Redirect when the URL earns its keep, remove it when it doesn't, and never send a dead product to the homepage by default. The next sections map each branch to specific PrestaShop steps.

One archive-friendly detail: if you keep a page live, you can repurpose it to explain the item is no longer stocked while surfacing alternatives. You could use the PrestaShop Module Tabs | Add Extra tabs on Product Pages with Tabs Module to add a "why it was discontinued" or "recommended replacement" tab, so the page still answers the shopper's question instead of leaving them stuck.

The Decision Tree: 301, 410, Archive or Keep Selling

Work through these yes/no questions in order, one URL at a time, and the correct action usually falls out on its own. Skipping straight to "delete it" is how stores lose rankings they never notice were carrying traffic.

Question 1: Does A Direct Replacement Exist?

If the discontinued item has a true successor (last year's model replaced by this year's, a 500ml bottle replaced by a 750ml version), the answer is a permanent 301 redirect straight to that product page. In PrestaShop, open the product in the Catalog > Products list, edit the outgoing item, and use the SEO tab's redirect option to point old traffic at the new URL. This is the only case where passing link equity and buyer intent to a single product page is the clean answer.

Question 2: Is There A Close Variant, Not An Exact Match?

Think a different colour of the same jacket, or a component that fits the same range. A variant deserves a 301 too, but to whichever product best matches what the shopper was originally looking for. Do not dump five discontinued variants onto the homepage just to save time; a relevant variant page keeps the visit alive, and a homepage bounce kills it.

Question 3: Does A Strong Category Page Exist?

When nothing close is in stock, redirect the dead URL to the most specific category or subcategory that still sells the same kind of thing. This is the right call for ranges that get refreshed often, where a category URL stays stable while individual product pages churn. A 301 to a relevant category beats a 301 to the homepage every single time. Shoppers land somewhere they can actually browse, and search engines see a topical match rather than a dead end.

Question 4: Is There Genuinely No Equivalent?

Then you have two honest choices. Return a 410 to tell search engines the page is permanently gone, which suits one-off or seasonal items you will not restock. Or keep the page live as an archive and give it real value: a "discontinued" note, a successor recommendation, and extra content such as a fitting guide or spec comparison. This archive route is where the PrestaShop Module Tabs module earns its place, letting you add extra tabs with fitting advice, care instructions or related-product links so a dead item still answers questions. If you would rather guide visitors elsewhere, the Quick Buy Now with redirection module can push shoppers toward a live product instead.

Work through the questions in order every time, and you avoid the two most common mistakes: redirecting everything to the homepage, and deleting pages that were quietly earning organic traffic. If an archived page needs a form to collect restock requests, the CMS page form module covers that side of things.

What Is A 301 Redirect and When Should You Use One?

A 301 is a permanent redirect: a server instruction that sends both visitors and search engines from an old URL to a new one. For a discontinued product page, it tells Google to drop the dead URL from its index and credit the destination instead, so the links and ranking signals you built up over time pass to a live page rather than vanishing.

That permanence is the whole point. A 301 passes link equity and removes the old URL from search results, while a 302 (temporary) keeps the old page indexed and is the wrong signal for a product that will never come back. Use a 302 only for something genuinely short-lived, such as pausing a listing for a week.

In practice, a 301 makes sense when you have a clear, relevant destination:

• The item has a direct successor (a new colour, an updated model, a replacement), so point the old URL at the new product page.
• No successor exists, but the product belongs to a category that still does, so route shoppers to that category.
• The old page still earns links or traffic worth preserving, making a redirect better than a flat 410.

One warning: never redirect every retired SKU to your home page. Google treats mass redirection to irrelevant pages as a soft 404, and shoppers land somewhere that does not answer what they searched for. The destination has to match the old page's intent.

How To Set Up Redirects in PrestaShop Without Breaking URLs

Set the redirect first, then make the product unavailable, then test. In that sequence, the old URL never has a window where it returns a 404 to customers or crawlers. Everything below lives in the PrestaShop back office or your site's .htaccess file.

Use the SEO & URLs Page for A Single Product

Open Shop Parameters, then Traffic & SEO, and scroll to the SEO & URLs list using the URL Search filter. Each entry has a Redirect target field. Add the destination for the discontinued product's friendly URL and save. This is the cleanest route when you are retiring one specific item and want PrestaShop to handle the mapping without touching server files.

Install A Redirect Module for Bulk Changes

When you are discontinuing a whole category, the built-in list becomes slow to edit one row at a time. The PrestaShop marketplace offers a free redirect and 404 management module that lets you add many source-to-target pairs at once and manage them in one table. Add the discontinued product URLs as sources and the successor or category URLs as targets.

When .htaccess is the Better Tool

• You are moving a large number of URLs and want a single rules block.
• The target lives outside PrestaShop, such as a blog subdomain.
• You need a wildcard rule to catch a whole keyword pattern.

A 301 line in .htaccess runs before PrestaShop's own routing, so always place your rules above the standard PrestaShop block and keep a backup of the file before editing. A malformed rule can take the storefront down, which is why testing matters. 

Test Before You Go Live

Run each old URL through a redirect checker and confirm you see a single 301, not a chain of two or three hops. Follow the target in an incognito window to check it loads the right page and returns a 200. Then resubmit your sitemap in Search Console and watch the Coverage report over the following days.

A redirect you have not tested is a redirect you have not made.

When 410 Gone Beats A Redirect

A 410 Gone says the opposite of a redirect: this page existed, it is gone, and there is nothing here worth keeping. That signal only makes sense when no honest destination exists.

Three situations justify it. The product had no equivalent or successor and its category has since been removed from your catalogue. The listing was pulled for legal or regulatory reasons, such as a recalled item or a brand you can no longer sell. Or the URL was thin duplicate content that never earned a meaningful backlink. In each case, redirecting to an unrelated product page creates a soft 404 that frustrates shoppers and dilutes crawl signals.

In PrestaShop, the cleanest route is to delete the product from the Catalog > Products list rather than leaving it disabled. A disabled product typically returns a 404, not a 410, so the distinction matters if you want the stronger signal. If your theme or server configuration does not return a 410 automatically, ask your developer to map the specific URL to a 410 response at server level, then confirm it with your browser's network panel.

Before deleting, export the product's data and note any inbound links pointing to it. A 410 is a permanent statement, so treat it like one.

One exception: if the discontinued item could still answer a shopper's question (fabric care, compatibility, warranty details), an archive page built with extra tab content keeps that value alive instead of throwing it away.

Cleaning Up: Sitemaps, Internal Links and Search Console

Redirecting or removing a URL is only half the job. Search engines and shoppers still find dead product pages through sitemaps, old internal links and cached search results, so the leftover signals need tidying too.

Start with your sitemap. In PrestaShop, outdated products typically drop out once their status or association changes, but any that linger should be cleared by regenerating the sitemap under Shop Parameters or via your sitemap module. Confirm the discontinued URL no longer appears before you move on.

Next, hunt down internal links. Old product references hide in CMS pages, category descriptions, blog posts and banners. Use a crawl of your store to list every page still linking to the dead URL, then update each one to point at the redirect target or successor item.

Then set up monitoring. In Google Search Console, the Pages report flags 404s and soft 404s, so you can catch links you missed. Keep an eye on it for a few weeks after the change.

If a dead URL still appears in search results and cannot wait for recrawling, the Removals tool in Search Console lets you request a temporary block. Treat it as a stopgap, not a substitute for a proper redirect.

Give any archive page real substance so it earns its place.

Finally, set a routine. Revisit your sitemap, internal links and Search Console reports each time a product line changes, and dead URLs stop accumulating quietly in the background.

The Discontinued Product Page Checklist

Work through this list for each retired SKU, one at a time, and keep a short note of what you decided. That record saves you from re-litigating the same page six months later.

1. Audit the Traffic. Check the page in Google Search Console for impressions, clicks and any backlinks or ad campaigns pointing at it. A page with zero traffic and no links is safe to remove.
2. Pick Your Action. Choose one of four outcomes: 301 to a successor, 301 to the parent category, 410 Gone, or keep it live as an archive or pre-order page.
3. Decide the Successor First. If a replacement product exists, that URL wins. If not, the parent category is the honest destination.
4. Implement in PrestaShop. Set the redirect through the SEO and URLs tab or your redirect module, then confirm the old URL is gone from your sitemap and internal links.
5. Test the Result. Open the old URL in a private browser window and confirm it lands where you intended, with the correct status code.
6. Monitor for A Few Weeks. Watch Search Console for new 404s and any drop in category impressions before you move on to the next batch.

Batch the work by category rather than by product. Grouping edits keeps it faster, and if you ever want extra context on a live product, the PrestaShop Module Tabs module at $49.00 lets you add specification or care tabs without a second page.

Why Discontinued Product Pages Need A Decision, Not A Default

When a product stops selling, the page behind it does not stop existing. In PrestaShop, disabling or deleting a product leaves its URL in the wild: indexed by Google, saved in customer bookmarks, and linked from old newsletters and blog posts. What you do with that URL is a small decision with a long tail.

The mistake most store owners make is treating every retired SKU the same. Deleting everything strips value from your catalogue. Redirecting everything to the homepage confuses both shoppers and search engines. This guide gives you a traffic-value triage: a clear decision tree for discontinued product pages in PrestaShop, mapped to 301 redirects, category redirects, 410 responses, and archive pages.

Start With the Question That Actually Matters: What Is This URL Worth?

Before you touch anything, decide how much value the dead product page is carrying. A product that sold for years, earned reviews and attracted backlinks is a different asset from a test SKU that went live briefly and never got indexed.

In PrestaShop, you can find this out from the Stats area (page views, visitor origin) and from Google Search Console, which shows clicks, impressions and the queries the URL ranked for. Cross-check your backlink tools too: a handful of referring domains pointing at the product URL is a signal that the page earned real value and deserves a redirect rather than removal.

The triage has four possible outcomes:

• 301 to a successor product when a newer version or direct replacement exists.
• 301 to the parent category when the product has no successor but the category still sells related items.
• 410 Gone when the URL has no value and should be removed cleanly from the index.
• Keep as an archive page when the product attracts steady traffic from people who still own it.

Treat every dead URL as a transaction: either route its traffic somewhere it still converts, or tell search engines it is closed for business.

The Decision Tree in Full

Work through the branches in order. The first one that matches is your answer.

Branch 1: Does A Direct Successor Exist?

If the discontinued item has been replaced by a newer model, an updated version or a close equivalent in your catalogue, that is the cleanest case. Redirect the old product URL to the new product page with a 301. The customer lands on something they can buy, and the SEO value of the old page transfers to a relevant, live page.

In PrestaShop, go to SEO and URLs under Traffic & SEO and use the redirect option in the URL redirects section. Enter the old URL, choose 301 Moved Permanently and set the target. Clear the Shop and Language fields if the redirect should apply everywhere. Use the Definitive option only once you are certain the mapping will not change.

Branch 2: No successor, But The Category Still Sells?

If there is no direct replacement, but the parent category is alive and full of related products, redirect the old URL to that category page. A shopper who followed a link to a discontinued kettle lands on the kettles category and can browse alternatives. Search engines see a relevant destination, not a dead end.

Set this up the same way: in SEO and URLs, add a new redirect, choose 301 and point to the category. Avoid sending the redirect to your homepage. A homepage redirect on a product URL tells Google the old page did not have a substitute, and a shopper looking for a discontinued item has to restart their search.

Branch 3: The URL Has No Worth At All?

Test products, seasonal one-offs with no backlinks, or SKUs that never earned search visibility should not clutter your catalogue or your redirect table. Delete the product in PrestaShop and respond with a 410 Gone for that URL.

410 is a deliberate statement: this page is permanently gone; do not keep checking. Search engines treat it as a faster cleanup signal than a 404. Use it when there is genuinely nothing to point to. 404 is fine for a stale link, but a controlled 410 is cleaner for pages you have consciously retired.

Branch 4: Is The Product Itself The Destination?

Some products stop being sold but keep attracting traffic: earlier models, spare parts, discontinued lines people still own. In those cases, keep the page, but convert it into an archive or reference page. Remove the Add to cart button, add a clear "discontinued" message, and explain what the customer can buy instead.

In PrestaShop, set the product to Disabled rather than deleting it. You keep the URL, the reviews and the SEO. Use the product description to answer the questions those visitors still have: "Is there a replacement?" and "Where can I buy spare parts?" This is where extra product tabs add serious value. With PrestaShop Module Tabs, you can add a "Compatibility" tab, a "Spare parts and accessories" tab, and a "Why was this discontinued?" tab without touching theme files, and backfill the content with the module's built-in AI tab generation feature. 

A Quick Comparison of the Four Options

Conclusion

Every discontinued product page in PrestaShop falls into one of four buckets, and the work is simply picking the right one. Audit the URL's traffic and links, point it at a successor or category with a 301, return a 410 when there is nothing worth keeping, or keep it live as an archive with real content. Then write down what you chose, so the next product line change is a routine job rather than a scramble.

If you take the archive route, the tab work is where most of the value sits. The PrestaShop Module Tabs Module lets you add unlimited custom tabs with multimedia and multilingual content, apply display rules so they only appear where they should, and generate professional tab descriptions with its built-in AI feature. It is the fastest way to turn a retired product page into one that still answers questions and keeps earning its place in your catalogue.

Frequently Asked Questions