Website migration: how to move platforms without losing rankings.

Migrations lose rankings through carelessness, not through some inherent penalty for moving. Google follows clean signals fine. What it can't forgive is a thousand URLs that used to answer queries suddenly returning 404, or all redirecting to the homepage, which it treats much the same way. The whole discipline of website migration SEO is preserving the map between what ranked and what now exists.

This belongs to the infrastructure cluster and leans on the technical SEO audit. Read the platform comparison first if the migration itself is still a question.

Before: benchmark and map

You can't protect what you haven't inventoried.

1. Crawl the current site and export every URL. Pair it with Search Console's top pages and queries, and a year of organic landing-page data from analytics. This is the asset register.
2. Build the redirect map: one old URL to one new URL. The single document the whole migration depends on. Every product, category, blog post, image-heavy page and ranking oddity gets a destination. The lazy patterns that cause the post-launch drop: blanket redirects to the homepage, redirecting deleted products to the homepage instead of their category, and forgetting URL parameters and pagination.
3. Benchmark everything: rankings for the terms that matter, organic sessions by landing page, Core Web Vitals field data. Post-launch arguments about "is this normal" get settled by these snapshots.
4. Replicate the on-page layer on the new platform: title patterns, meta descriptions, heading structures, internal links and structured data. New design is fine; new everything at once makes diagnosis impossible if traffic dips.

Launch day: verification, not celebration

• 301s, not 302s, on every mapping. Permanent moves get permanent codes.
• Spot-check the top 100 traffic URLs by hand, then crawl the old URL list and confirm every entry resolves with a single hop to the right destination. Redirect chains waste crawl budget and dilute signals.
• Robots.txt isn't blocking the new site, the staging noindex tags came off, and the canonical tags point at the new domain or paths. The most common self-inflicted wound in migrations is shipping the staging block to production.
• Submit the new sitemap in Search Console; if the domain changed, use the change-of-address tool.
• Internal links updated to final URLs, not routed through redirects.

After: the monitoring window

Some turbulence for a few weeks is normal while Google recrawls and reconsolidates; that's not a failure signal. What to watch:

Signal	Where	Healthy pattern
Coverage and 404 reports	Search Console	404 list shrinking, not growing
Organic sessions by landing page	Analytics vs benchmark	Recovering toward baseline within weeks
Top-query rankings	Your benchmark list	Wobble then settle
Crawl of old URLs (re-run monthly)	Crawler	Still redirecting, no decayed mappings

A worked failure pattern, for recognition: traffic holds for two weeks, then slides. Cause, usually: redirects were in place but the new pages are thinner, slower or stripped of the internal links that supported them. The redirect map preserves the address; the page still has to deserve the ranking. That's where the speed and content layers re-enter.

Keep the redirects live for the long term, at minimum a year and ideally indefinitely. Old URLs live on in bookmarks, emails and backlinks long after you've forgotten them.

Frequently asked questions

Will I lose traffic after a website migration?

Some short-term movement is normal. Sustained loss almost always traces to mapping gaps, blocked crawling, or new pages that are weaker than what they replaced. All three are preventable and diagnosable.

How long should 301 redirects stay in place?

At least a year, and ideally permanently. Backlinks and bookmarks to old URLs keep paying you only while the redirects keep answering.

Can I redirect old pages to the homepage?

No. Bulk homepage redirects are treated like soft 404s and forfeit the equity of every page doing it. Map one-to-one, or to the closest relevant category when a page truly has no successor.

What to read next

• How to run a technical SEO audit before you migrate
• Shopify vs WooCommerce: picking the platform you'll move to
• Site speed optimisation, so the new pages keep their rankings

---

How Qwrki fits

Qwrki runs replatforming as part of the operating layer: the crawl and redirect map, the pre-launch benchmarks, launch-day verification, then the monitoring window where most drops are caught and fixed. We treat a migration as one tracked sequence rather than a single risky launch day. Book a call if you have a move coming up and want the redirect map checked before anything ships.