Redirect on product deletion
The rule is created before the product is removed. The target is configurable: default category, deepest or highest assigned category.
Language:
Cart
0
PrestaShop 1.7, 8, 9 compatible
A deleted product URL should return 301, not 404.
What the shop gets
Automatic 301
and a redirect manager
and a redirect manager
Redirects are created on deletion, and every existing rule is managed from one list.
What is this module for?
A shop catalogue keeps changing: products go out of stock for good, categories are merged. The URLs that disappear live on in Google results, in newsletters and in other sites' links — and they return 404. That hurts more than the visitor: a 404 URL loses the ranking it earned, the value of every inbound link goes nowhere, and the crawler spends part of the shop's crawl budget on dead addresses. A 301 keeps that chain alive — this module writes it at the moment of deletion, before the record is gone, and keeps every existing redirect in one place.
What it does
Redirects where the work used to be manual.
Redirect on category deletion
The deleted category and its subcategories point to the nearest category that stays. Without one, they point to the homepage.
One rule per language
Every active language gets its own rule, and in multistore only the shop the record is removed from.
Redirect management list
Rules are editable in a list: status code, on and off, click counter, filtering by origin.
CSV import for migrations
URLs inherited from a previous system can be uploaded from a CSV file by column order.
Log of every decision
A file log of every automatic decision, one file per month, for the developer.
The real interface
This is the module from the inside
Settings
Redirect list
CSV import
Good to know
Do I need a developer?
No. Upload and install the module as usual, switch on what should be redirected, and pick the target category. From there, deletions need no further work.
Why it pays off
What you gain — for visitors and for search
Versions
What changed in each version?
- Timestamps now keep the time in the rule list
- Unused files removed
- Hungarian back-office translation
- Localized module name and description
- Automatic 301 for deleted products and categories
- Target category: default, deepest or highest
- Subcategories and every language get their own rule
- Direct target instead of a redirect chain
- Origin column and filter in the list
- File log, one per month
Frequent questions
What customers ask most often
What about products that were already deleted?
No rule can be built for those, because the URL is no longer reconstructable. They can be added manually or from CSV.
What is the target when a product loses every category?
The rule points to the homepage, so the visitor does not end up on an error page.
Does the module overwrite manual rules?
No. When a URL already has a rule, the module leaves it alone and writes that to the log.
Does it work with several languages and shops?
Yes. Every active language gets its own rule, and in multistore only the shop the record is removed from.
Do redirects slow the shop down?
No. Matching is an indexed lookup on the rule table and runs before the controller loads.
What happens when the module is removed?
The rules and their statistics stay in the database; only the module settings are removed.
Can it handle URLs inherited from another system?
Yes. CSV import fills the list with the old URLs by source and target column index.
Why does this matter to Google, not just to visitors?
Because search engines treat a removed URL as a 404: the ranking it earned and the value of every link pointing at it are lost, and part of the crawl budget goes to dead addresses. A 301 tells the crawler where the content went, so the value moves to the page that stays and the 404 list in Search Console stops growing.
Support
Where to find help
All modules
Browse our other PrestaShop modules.
PrestaShop courses
Courses and tutorials for PrestaShop.
Documentation
Detailed usage documentation.
Live support
Direct help with installation and setup.
