Updated on
There’s no single “correct” way to manage 301 redirects in PrestaShop: it depends on how much your catalog changes and how much hassle you want. Here are the three approaches side by side, with their downsides, and a rule for choosing. A note on transparency: Zeyvro sells a module of the third kind, so we also tell you when you don’t need it.
- You almost never change URLs: the .htaccess or a manual manager is plenty.
- You change URLs often, withdraw products or are about to migrate: you want the 301 to be created on its own and CSV import.
- PrestaShop 8, out of the box, only redirects disabled products: for everything else you need one of these three methods.
What ways are there to manage 301 redirects in PrestaShop?
Three: rules written by hand in the server’s .htaccess, a manual manager in the back office where you create each redirect yourself, or a module that also detects URL changes and creates the 301 on its own. The difference is who remembers to create the redirect: you or the system.
A · Manual .htaccess
Nothing to install. You edit a critical server file, which PrestaShop regenerates, and slug changes go undetected.
B · Manual manager
From the back office, no file editing. But you create every redirect: change a slug and forget, and the 404 stays.
C · Automatic detection + CSV
When a product or category slug changes, the 301 is created on its own. And you load many at once by CSV.
What C costs
It’s a paid module feature. If your catalog barely changes, it won’t pay for itself.
When is the .htaccess enough?
When you have few redirects, you can edit the file without breaking it and you almost never change URLs. Pros: nothing to install and full control. Cons: one mistake in the file can stop the site from loading, it gets awkward with many rules, it doesn’t notice when you change a product URL, and PrestaShop regenerates that file, so you have to keep an eye on your rules still being there.
When does a manual back-office manager make sense?
When you want to create and edit redirects without touching the server, and your URL changes are occasional and you remember them. Pros: convenient and safe. Cons: it depends on your memory. Every time you rename a product or move a category, you have to remember to create the redirect; otherwise the old URL stays a 404.
When is automatic detection worth it?
When you change URLs with some regularity, withdraw products or are about to migrate the store. That’s what Zeyvro SEO Redirect 301 does:
- Automatic 301: when you save the new slug of a product or a category, it creates the redirect from the old URL to the new one, in every language.
- CSV import and export: one redirect per line, no row limit, and it reports the skipped lines.
- Chains resolved: with A→B and B→C, when C becomes D it updates A→D.
- Product removals: it lists disabled products or products that deny orders whose URL is still live, and redirects them to a category, a manufacturer or another product, one by one or in bulk.
- Slug suggestions: if you rename a product or a category and its URL still carries the old text, it proposes the new one and applies it with its 301 in one click (or on save, if you switch it on).
What it doesn’t do: it doesn’t measure the effect on traffic or rankings (that’s in Search Console or Analytics), and CMS pages aren’t part of the automatic creation; their redirects are created by hand or by CSV.
So which method should I choose?
Ask yourself three questions. How many URLs do you change a month? Do you withdraw products often? Is a migration or a redesign coming up? If the answers are “hardly any” and “no”, A or B is plenty: don’t pay to automate something you won’t use. If any answer is “yes”, method C saves you the 404s that manual management lets slip.
💡 Already chosen and want to create them? The step-by-step is in how to set up 301 redirects in PrestaShop 8.
Does the automatic method replace the manual one?
No, they complement each other: automatic detection covers product and category slug changes, and every other redirect is still created by hand or by CSV. Zeyvro SEO Redirect 301 does all three.
What is CSV import for?
For migrations, redesigns or catalog cleanups where many URLs change at once: you load every redirect in one go instead of creating them one by one.
Can I start with the .htaccess and switch later?
Yes, but moving .htaccess rules into a manager takes work. If you expect your catalog to change, start with a manager now.
Does PrestaShop include a redirect manager?
No. Out of the box it only redirects disabled products; to redirect any other URL you need server rules or a module.
What should I do with products I withdraw?
Redirect their URL to the category, the manufacturer or a similar product so you don’t leave a 404. Zeyvro SEO Redirect 301 lists disabled products or products that deny orders whose URL is still live and redirects them in bulk.
If yours is method C: automatic 301, CSV and product removals, no .htaccess.
See Zeyvro SEO Redirect 301 →Zeyvro builds PrestaShop modules from a real store in production. Unobfuscated code.