Migrating PrestaShop without losing your search visibility

A badly prepared PrestaShop migration erases years of search visibility overnight, by breaking the signals Google spent months building: URLs, 301 redirects, tags, structure. One rule covers most of it: nothing Google knows about should disappear without a redirect.

What makes traffic drop after a migration

Four causes, in order of frequency:

1. URLs change with no redirect: every old indexed URL returning a 404 is a lost position.
2. Title and meta tags are reset by the new theme or the new version.
3. Structured data disappears because the theme does not reimplement it.
4. Internal linking breaks: internal links point at dead old URLs.

Before the migration: the inventory

You only migrate well what you have mapped:

• Export every indexed URL. Search Console plus a site crawl give you the reference list everything else depends on.
• Note the high-traffic pages. They deserve a manual check after the switch.
• Save the tags: the title and meta description of every page should survive the migration, not be regenerated at random.
• Record the starting version. Moving from a PrestaShop 1.6 to a modern version does not raise the same questions as a simple theme change. A 1.7 that stays on 1.7 has its own checklist, with no migration involved.

The redirect plan

For every old URL that changes:

• A 301 redirect (permanent) to the equivalent new URL. Never a 302 for a migration.
• Page-to-page mapping: a category to the equivalent category, not to the homepage. Redirecting everything to the home page is the surest way to lose everything.
• No redirect chains. A → B → C leaks SEO value: redirect A straight to C.

Keep PrestaShop on friendly URLs on both sides, and preserve the same slug structure where you can: the fewer URLs you change, the fewer you redirect.

Right after the switch

1. Test a sample of URLs: do the old ones really redirect with a 301?
2. Check sitemap.xml and robots.txt: is the sitemap up to date, and is robots.txt blocking something by mistake?
3. Check the structured data on products and articles.
4. Restore internal linking: links must point to the new URLs, and it is a good moment to check that no content is orphaned.
5. Watch Search Console coverage for 4 to 6 weeks: a spike of 404s signals a forgotten redirect.

Content does not need re-migrating

Your editorial content is portable. If it lives in a module that follows the versions (the blog stays compatible from 1.6.1 to 9), the migration does not threaten it. One more argument for not letting your content depend on a theme.

FAQ

How long to recover the traffic? With clean 301s, a few weeks. Without them, the loss can be permanent.

Should I tell Google? Submit the new sitemap and, if you are changing domain, use the change of address tool in Search Console.