Switching websites is the highest-risk moment for anyone who already has organic traffic. A post-migration drop is almost never the new design's fault: it is missing redirects, URLs changed without criteria, and lost tracking. This is the playbook for migrating without losing rankings.
Before touching anything: the inventory
No migration should begin without a complete map of the current website. Without this document, it is impossible to tell afterward what broke.
- A list of every indexed URL, with each one's traffic and ranking position.
- Pages that receive external links.
- Current metadata: title, description, and canonical.
- Configured events and conversions.
- Forms, integrations, and lead destinations.
The 301 redirect map
Every old URL needs a destination: its new equivalent, or, failing that, the closest page in content. Redirecting everything to the homepage is the most common and most expensive mistake: Google treats it as a soft 404 and discards the history.
| Old URL situation | Correct destination | Code |
|---|---|---|
| A new equivalent exists | the matching new URL | 301 |
| Content merged into another page | the consolidated page | 301 |
| Content discontinued with a substitute | the relevant replacement page | 301 |
| Content discontinued with no substitute | keep 404 or 410 | 404 / 410 |
| URL temporarily down | an informational page | 302 |
What needs to be fully preserved
- The title structure and content of pages that already rank well.
- Metadata, when it already performs: rewriting everything is betting against the history.
- Existing structured data.
- Conversion events and tracking integrations, following the guide to GA4 events.
- Images that drive search traffic, along with their file names.
Launch day
Before publishing
- The staging environment blocked from indexing.
- Redirects tested in bulk, including variants with and without a trailing slash.
- robots.txt and the new site's sitemap reviewed.
- A full backup of the old environment.
Right after publishing
- Remove any indexing block from the new environment.
- Submit the new sitemap in Search Console.
- Crawl the entire site looking for 404 errors and redirect chains.
- Validate that conversions fire in production, not just in preview.
The following four weeks
A 10% to 20% fluctuation in the first two weeks is expected while Google reprocesses the URLs. What is not normal: a continuous drop, pages disappearing from the index, and growing crawl errors. Compare position by URL against the frozen inventory and address exceptions one by one.
If the new site also changed visually, isolate the variables: performance may have changed too. It is worth measuring Core Web Vitals and comparing the conversion rate before concluding the problem is SEO.
Website migration checklist
- URL inventory exported with traffic and ranking position.
- 1-to-1 301 redirect map approved.
- Staging environment blocked from indexing.
- New site's sitemap and robots.txt reviewed.
- Conversions and integrations tested in production.
- Search Console monitored daily for the first two weeks.
- Position-by-URL comparison done at 30 days.
Conclusion
A well-done migration is spreadsheet work before it is design work. With an inventory, a redirect map, and disciplined monitoring, it is entirely possible to switch websites and come out of the transition with more traffic than before.
Frequently asked questions about website migration without losing traffic
Is it normal to lose traffic when migrating a website?
A few weeks of fluctuation is expected while the search engine reprocesses the URLs. A deep, prolonged drop points to a redirect failure, an indexing block, or lost content.
Should every redirect be a 301?
For a permanent migration, yes: a 301 transfers the authority signal. A 302 is temporary and should not be used when the old URL is not coming back.
Can I redirect everything to the homepage?
No. Mass redirecting to the homepage is treated as a soft 404 and discards the history of every URL. Each old address should point to its closest equivalent.
How long until full recovery?
In well-executed migrations, four to eight weeks to stabilize, depending on the site's size and crawl frequency.
About the author
Yara Iencius
Partner and Head of Design & UX, KCLOCK
Conversion designer. Responsible for UX/UI, interfaces, landing pages, and e-commerce sites that turn strategy into a high-converting experience.
- #seo
- #website
- #migration
Want to apply this to your funnel with people who do it every day?
KCLOCK builds high-converting funnels, landing pages, websites, and e-commerce stores. We diagnose your current funnel and show you where the revenue you're leaving on the table is hiding.
