Keep your rankings through a migration by mapping every old URL to its closest new equivalent, using server-side 301 or 308 redirects, changing one major thing at a time, and monitoring both sites afterward. Google says to keep redirects for at least a year and warns that rankings may fluctuate for weeks.
A website migration is the one SEO project where you can lose years of work in an afternoon. A redesign, a new domain, a move to a different platform or even a clean-up of old URLs can all change the addresses Google has learned, and every address that changes without a proper redirect is a page whose rankings and links are left behind.
The mechanics are well documented, and Google publishes them. The reason migrations still go wrong is almost never a mystery. It is a missing URL map, too many changes at once, or a launch that nobody tested.
1. What counts as a migration, and why the type matters
Google separates site moves into two families. A site move with URL changes covers a new domain, a switch from HTTP to HTTPS, and any change to the paths your pages live at, such as moving from /services.php?id=4 to /services/roofing/. A move with no URL changes is a new host or CDN where every address stays exactly the same. The second is far lower risk and has its own, shorter guidance.
Most “redesigns” quietly belong in the first family. A new theme usually arrives with new permalinks, a new blog structure and a different set of category pages, even if the domain never changes. If any address changes, treat the project as a migration.
2. The rule that prevents most disasters: change one thing at a time
Google’s guidance on moves is brief on redesigns, but it is explicit on one point: change only one thing at a time. Its example is to move to a new domain first and change the layout afterward, and the same advice applies to changing your CMS.
The reason is diagnostic, not superstitious. If you change the domain, the URL structure, the page templates, the copy and the navigation on the same weekend, and rankings fall, you cannot tell which change did it. Staged changes let you attribute any drop to a single cause and reverse it. Agencies that bundle everything into one launch are optimizing for their own schedule, not for your traffic.
3. The URL map is the whole project
Google’s sequence puts URL mapping before anything else is switched on, and it asks you to build the list from several sources: your sitemaps, server logs, analytics and CMS, including images and other embedded files. A sitemap alone is not enough, because it lists the pages you want indexed and usually omits old URLs that still carry backlinks and traffic.
For each old URL you need a destination. Where a page has a direct equivalent, point to it. Where several thin pages are being merged into one better page, point them all to the merged page, which Google treats as acceptable. Where there is genuinely no equivalent, a clean 404 or 410 is more honest than a redirect to the homepage, which Google may treat as a soft 404 and which sends users somewhere they did not ask to go.
Use server-side permanent redirects, 301 or 308, and keep every redirect to a single hop. Google says permanent redirects do not cost you link credit, which removes the best excuse for sloppy mapping: the technique works, so any loss is in the execution.
4. Launch day: the checks that catch real problems
Before launch, test the redirects against a sample of real old URLs, not just a handful of top pages. After launch, confirm that canonical tags, robots rules and the new sitemap all point at the new URLs.
Two failures account for most of the preventable damage we see. The first is a staging noindex tag or a robots.txt block that travels to the live site with the rest of the code. The second is analytics, forms and tracking that stopped working at launch, so nobody notices the lead drop until the monthly report. Both take minutes to check and months to repair. We cite our own experience here rather than a published statistic, because we are not aware of a study that ranks migration failure causes.
Use the Change of Address tool in Search Console only when the domain or subdomain changes, for example from example.com to example.net. Google says it is not needed for an HTTP to HTTPS move, a www versus non-www change on the same domain, or a change of paths. For a domain move, submit it for every verified variant of the old domain.
5. What to expect afterward
Be wary of anyone who promises no dip. Google states plainly that rankings may fluctuate while it recrawls and reindexes, and that for medium-sized sites it can take a few weeks or more for new URLs to appear in place of old ones, with larger sites taking longer. Googlebot has to visit every old and new URL at least once, and the move happens URL by URL rather than all at once.
Two knock-on effects are worth knowing. Google crawl activity on the new site rises after a move, so confirm your server can handle it; our guide to whether crawl budget matters for your site explains why a move temporarily raises crawl demand. And performance regressions are common in rebuilds, so run the checks in our Core Web Vitals guide on the new site before launch, not after.
6. Keep the redirects longer than feels reasonable
The most common late mistake is tidying the redirect file after a few months. Google’s guidance is to keep redirects for at least one year, because that is how long its systems need to transfer signals and recrawl links that still point to the old URLs. Keeping them indefinitely is also suggested, with the trade-off that redirects add a small delay for users, so update your own links and the highest-traffic external ones where you can.
Keep the old domain registered too. If it lapses, someone else can acquire it and the links still pointing there are gone or, worse, working for a stranger.
A migration done well still loses some visibility for a while. A migration done badly can lose it for good. The difference is the URL map, the testing and the discipline to change one thing at a time. If a quote for your redesign does not mention redirects, ask where they are, because they are usually not in the price.
If you are planning a rebuild, insist that the URL mapping, redirect build and post-launch monitoring described above are written into the scope of your website design and development project, so rankings are protected as part of the build rather than repaired afterward. And since Google indexes the mobile version of your site, run the mobile-first indexing checklist on the new build too.
Protect your rankings before you rebuild
Send us your current site and we will tell you which URLs carry your traffic and links, so the redirect plan protects the pages that matter.
Plan a safe migrationFrequently asked questions
Will I lose rankings when I redesign my website?
Possibly for a short time, and permanently only if the move is mishandled. Google says rankings may fluctuate while it recrawls and reindexes, and that medium-sized sites can take a few weeks or more for new URLs to replace old ones. A complete URL map, one-to-one 301 redirects and one change at a time keep the loss temporary.
How long should I keep 301 redirects after a site move?
Google recommends at least one year, because that gives its systems time to transfer signals and recrawl links that still point to the old URLs. It also suggests keeping them indefinitely if you can, since users and links may keep arriving at the old addresses for years.
Do I need the Change of Address tool?
Only when the domain or subdomain changes, for example from example.com to example.net. Google says it is not needed for an HTTP to HTTPS move, a www to non-www change on the same domain, or a change of URL paths.
Should I redirect all my old pages to the homepage?
No. Google warns that sending many pages to an unrelated page such as the homepage can confuse users and be treated as a soft 404. Redirect each old URL to its closest equivalent, consolidate similar pages into one, and let pages with no equivalent return a proper 404 or 410.
Can I redesign my site and change my domain at the same time?
You can, but Google advises changing only one thing at a time, such as moving domains first and changing the layout afterward. Combining changes makes it impossible to tell which one caused a ranking drop, and harder to reverse.
Does a migration need a separate plan if only my hosting changes?
A move that changes hosting but keeps every URL the same is covered by separate, shorter Google guidance. It carries less risk, but you still need to test the new server, keep the old one live while DNS changes spread, and check that robots.txt and redirects carried over.
Sources
- Google Search Central: “Site moves with URL changes.” Steps, redirect guidance (301 or 308, no chains, no mass redirect to the homepage), one year minimum redirect retention, Change of Address tool scope, expected fluctuation and the one-change-at-a-time advice.
- Google Search Central: “Optimize your crawl budget.” Statement that site moves can temporarily raise crawl demand.
- Google Search Console Help: Change of Address tool (scope: domain and subdomain moves, not HTTP to HTTPS).
Note: the launch checklist and monitoring schedule are our working method, not a published standard. The failure patterns we describe (a staging noindex carried live, tracking broken at launch) come from our own project experience; we are not aware of a published study ranking migration failure causes, so we have not quoted a percentage.
Reference: Read the original research or documentation.

Muhammad Asjad Khan is a seasoned digital marketer and the Chief Operating Officer at Digital Age, where he leads strategy, innovation, and client success. With years of experience in SEO, content marketing, and performance-driven digital campaigns, Asjad is passionate about helping brands grow their online presence and achieve measurable results. When he’s not optimizing websites or scaling marketing strategies, he’s exploring the latest trends in tech and digital media