It is the most common fear when rebuilding a website: "what if we lose our rankings?". The fear is legitimate; botched migrations have cost companies dearly. The good news: with method, a migration goes cleanly. Here is our complete method, step by step, the one we apply to every redesign.
Why a redesign can hurt
Your current visibility rests on your page addresses (URLs), accumulated over the years: they are known to Google, linked by other sites, saved in bookmarks. If the new version of the site changes those addresses without telling anyone, search engines hit missing pages, and so do your visitors. That is a failed migration: years of visibility thrown away in days.
Step 1: the inventory
Before touching anything, we map the terrain: every page of the old site, the ones that get traffic, the ones that rank, the ones that receive external links. Useful content is kept or improved in the new version; dead pages are owned as such. Without an inventory, you redirect blindly.
Step 2: the 301 redirect plan
The cornerstone. Every old URL is mapped to its new equivalent in a 301 redirect plan: the permanent redirect that tells search engines "this page has moved here, permanently". Engines understand the move; visitors see nothing.
The classic mistakes we see in failed migrations:
| Mistake | Consequence |
|---|---|
| Redirecting everything to the homepage | Google treats it as deleted pages; visibility melts |
| Temporary redirects (302) instead of 301 | Engines wait for the old page to return instead of transferring |
| Redirect chains (A to B to C) | Diluted signal, slower loading |
| Forgetting images and PDF documents | Dead links and lost traffic, invisible from the pages |
| Testing nothing before the switchover | You find the holes after Google has already seen them |
Step 3: Search Console, the official channel
Transferring your Google Search Console is part of the process: it is the official channel to follow the indexing of the new version, submit the new XML sitemap and spot any errors immediately. The honest goal: keep the variation to a minimum. A redesign always involves some flux while the engines digest; anyone who guarantees zero impact or a landing position is lying to you.
Step 4: the seamless switchover
The new version is fully tested on a pre-production environment: content, redirects, tags, speed. The domain name switchover then happens in a short window, and your business email is checked before the change: no website downtime, no mailbox downtime. The technical foundations of the new version (structure, tags, speed, sitemap, HTTPS) are built in from day one, not bolted on afterwards.
Step 5: post-switchover monitoring
In the following weeks, we watch: the indexing of the new pages, residual 404 errors (there are always a few to fix), loading performance, and the evolution of impressions in Search Console. Fixes happen as we go, while the engines finish digesting.
How long the digestion takes
Let us be precise about what to expect: after a clean switchover, engines recrawl the site, follow the redirects and re-evaluate the pages. This digestion generally takes from a few weeks to a few months depending on the size of the site and the crawl frequency. A temporary variation in positions during this period is normal and expected; it is a lasting variation that signals a problem, and that is exactly what post-switchover monitoring is for.
The special case of changing domain
Rebuilding on the same domain or moving to a new one are not the same job. A domain change adds a layer: redirects from the old domain to the new one (maintained long-term, not six months), the change-of-address notification in Search Console, and updating external profiles (directories, social networks, signatures). When the historical domain carries years of inbound links, you never unplug it brutally.
Who does what
A successful migration is a collaboration; better to say it before starting:
- The supplier: inventory, redirect plan, technical testing, switchover, monitoring and fixes. It is their job; demand the checklist.
- You: the credentials (domain registrar, Search Console, current hosting), approval of carried-over or rewritten content, and flagging the pages that matter to your business, which you know better than anyone.
If your current supplier cannot produce the list of your most visited URLs before the redesign, the migration question is already answered: it will not be under control.
The complete checklist
- Inventory of pages, traffic and inbound links
- Useful content kept or improved
- 301 redirect plan, URL by URL (no mass redirect to the homepage)
- Images and documents included in the plan
- Full pre-production testing, redirects verified
- DNS switchover in a short window, email preserved
- Sitemap submitted, Search Console monitored
- 404 and performance monitoring for several weeks
Considering a redesign but the migration holds you back? That is precisely our job, and this method is applied to every project. Tell us about your site, or start by checking whether it is time to rebuild it.