Platform Migration: How to Protect Your Rankings

A platform migration is the process of moving your online store from one eCommerce platform to another. That might mean leaving a dated system for Adobe Commerce, moving from a custom build to Shopify, or upgrading between major versions of the same platform. Whatever the route, you are rebuilding the store on new foundations and pointing your domain at it.

Stores migrate for sound reasons: better performance, lower running costs, features the old platform cannot support, or an end to constant maintenance headaches. The business case is usually clear. What catches teams out is that a migration is not just a technical rebuild, it is a search engine event. Every URL, redirect, and piece of on-page content affects whether the rankings you have built survive the move.

That is why SEO has to be part of the migration plan from day one, not a task bolted on at the end. The platforms and agencies that treat replatforming as purely a development project are the ones whose clients lose traffic. For a real-world example of how complex this gets at scale, our case study on Magento migration for large catalogues walks through the technical decisions that make or break a big move.

Even a well-run migration involves a short period of uncertainty, and knowing what is normal stops you from panicking and making things worse. After you go live, search engines need to recrawl your site, discover the new URLs, and process your redirects. During that window, it is normal to see rankings and organic traffic fluctuate.

Google itself advises that a medium-sized site can take a few weeks for most pages to move across in the index, and larger sites longer. Some temporary visibility wobble during this period is expected and usually settles as the move is fully processed. The mistake is to react to week-one data by ripping things out; the right response is to make sure your redirects and tracking are sound, then give it time.

What you should not expect is a permanent drop. A migration handled with full URL mapping and correct redirects typically recovers to its previous levels, and often improves once the new platform’s better performance and user experience start to help. Lasting ranking loss is a symptom of mistakes, not an inevitable cost of moving.

Your search rankings are tied to specific URLs. Over years, those URLs accumulate authority from backlinks, internal links, and Google’s understanding of what each page is about. When you migrate, new platforms almost always generate different URL structures, and that is where the danger lies. If the old URLs disappear without being redirected, the authority attached to them is lost.

The most common ways migrations damage rankings are entirely avoidable:

• Missing redirects. Old URLs that return a 404 error lose all their accumulated authority and drop out of the index.
• Redirecting everything to the homepage. A lazy shortcut that tells search engines the old pages no longer exist in any meaningful form, destroying their rankings.
• Wrong redirect type. Temporary 302 redirects do not pass authority the way permanent 301s do, so using them by mistake leaks rankings.
• Lost content and metadata. Page titles, headings, and body content that change or vanish in the rebuild change how Google sees the page.
• Blocking crawlers. Leaving a staging site’s no-index rule or robots.txt block in place after launch hides the whole site from search.

Every one of these is a planning failure, not a technical inevitability. The next section covers exactly how to avoid them.

Protecting rankings comes down to a handful of disciplines applied rigorously. None of them are complicated, but they have to be complete. Google’s own site move documentation sets out the core principles, and the following checklist puts them into practice for an eCommerce migration:

• Crawl and map every URL first. Before anything is built, crawl the existing site and create a complete map of old URLs to their new equivalents. This map is the backbone of the whole migration.
• Use 301 permanent redirects. Point each old URL at its closest matching new page. Permanent 301 and 308 redirects pass authority across; never redirect everything to the homepage.
• Preserve URL structure where you can. The fewer URLs that change, the lower the risk. If the new platform allows it, keep your existing URL patterns.
• Avoid redirect chains. Send each old URL straight to its final destination rather than through several hops, which slows crawling and dilutes the signal.
• Keep content and metadata intact. Carry over page titles, meta descriptions, headings, body copy, and image alt text so each page stays recognisable to search engines.
• Test every redirect before launch. Validate the full redirect map on staging, checking that each old URL resolves with a single 301 to the right new page.
• Submit a fresh sitemap and use Change of Address. Help search engines find the new URLs quickly by submitting an updated sitemap, and use the Change of Address tool if the domain is changing.
• Update internal links. Repoint internal links to the new URLs directly rather than relying on redirects, which improves crawl efficiency and speed.
• Keep redirects live for at least 180 days. Leave them in place well beyond launch, and longer if search traffic is still arriving on the old URLs.

A safe migration follows a clear sequence, with SEO running through every stage rather than appearing at the end.

The work does not end at launch. The first few weeks are when problems surface, and catching them early is the difference between a brief wobble and a lasting loss. Keep a close eye on the signals that reveal whether the move is settling cleanly.

• Crawl errors and 404s in Search Console, which expose old URLs that were missed or redirects that broke.
• Indexing status, confirming the new URLs are being indexed and the old ones are being replaced rather than lingering.
• Rankings and organic traffic against your pre-migration baseline, so you can tell normal fluctuation from a genuine problem.
• Core Web Vitals and page speed, since a faster new platform should improve these, and regressions signal a build issue.
• Conversion rate, because protecting rankings is pointless if the new store converts worse than the old one.

A migration is also the ideal moment to improve, not just preserve. With a faster platform and a clean rebuild, pairing the move with focused conversion rate optimisation can turn a defensive project into a growth one. If you are planning a move and want it handled without losing rankings, our eCommerce development team manages migrations end to end.

• Platform migration is a search engine event, not just a development project, so SEO must be planned from day one.
• Ranking loss during migration is almost entirely preventable with complete URL mapping and correct redirects.
• Map every old URL to a new equivalent and use 301 permanent redirects, never a blanket redirect to the homepage.
• Preserve content and metadata, avoid redirect chains, and keep redirects live for at least 180 days.
• Expect a temporary fluctuation of a few weeks while search engines recrawl, then a recovery to previous levels.
• Monitor crawl errors, indexing, rankings and conversion after launch, and fix issues immediately.

Common questions about platform migration. Get in touch if yours is not here.