How to Migrate Your Website Without Losing Google Rankings

A website migration is a change of domain, URLs, protocol, or platform on a site that already ranks. It is the moment when a project can lose in one week the traffic it took years to build, and almost always because of avoidable mistakes.

Google documents the process, but it is split across three documents and never says the uncomfortable part out loud: there is no zero-risk migration. What exists is a method that keeps the loss to a minimum. Here it is, in order: what to prepare, what to redirect, when to use Change of Address, and what to watch afterwards.

What a Website Migration Is and Why It Risks Your SEO

To Google, migrating means the URLs it knows stop responding and your site becomes a set of new pages it must discover, crawl, and re-associate with their historical signals: links, clicks, and topical context. All of that can be transferred, but you have to build the path.

Types of Migrations: Domain, URLs, HTTPS, and Platform

• Domain change: a new brand or extension. The only case where Change of Address applies.
• URL structure change: same domain, new paths.
• Move to HTTPS: every URL changes.
• Platform or CMS change: almost always drags path changes with it.

Each type is handled differently: only a domain or subdomain change justifies Change of Address, and only when URLs move to a new site.

What Google Says: Visibility May Fluctuate, and That Is Normal

The official guide on moving a site with URL changes puts it plainly: during the move, visibility in Search may fluctuate temporarily, this is normal, and rankings settle over time. Expect odd movements in the first days without assuming you broke something. What is not normal: the new site failing to climb while the old one drops.

The Most Expensive Mistake: Changing URLs, Content, and Design at Once

The Change of Address help page warns: if you combine the move with a redesign of content and URL structure in the new location, you will probably see some traffic loss, because Google has to reassess every page. The fix is not skipping the redesign, it is sequencing: migrate, wait for traffic to settle, then redesign.

Before You Migrate: The Preparation Phase

Most of the outcome is decided before the switch-over day, across four fronts.

Inventory Your Important URLs

You need the URLs that receive traffic and links, not all of them. Cross four sources: your sitemaps, the pages report in Search Console for the last twelve months, server log analysis, and your inbound links report. Prioritize by traffic and links: a guide with forty incoming links deserves a perfect redirect; a tag page with zero clicks can die without drama.

Build the Old-to-New Redirect Map

One two-column table, reviewed twice, then turned into server rules:

• One redirect per URL, to the closest content equivalent, never to the homepage for convenience.
• Include images, JavaScript, and CSS if their paths change.
• If two pages are consolidated into one, both point to the new page and it absorbs their content.

Prepare the New Site: Canonicals, Hreflang, and Internal Links

Every new URL needs a self-referencing rel="canonical", hreflang annotations updated to the new URLs on multilingual sites, and internal links fixed. Two oversights that wreck launches: shipping with the staging noindex still in place and never checking the robots.txt of the test environment.

Save the Lists: New Sitemap and Sites Linking to You

Generate the new sitemap before the move and keep a list of the sites linking to your old URLs: a link updated by a third party is worth more than any redirect, because it points straight at the final destination.

The Golden Rule: Change One Thing at a Time

Why Not Combine a Migration With a Redesign

Google phrases it as "change only one thing at a time": separate the domain change, the design, the content, and the URL structure on your calendar. If you do it all at once and drop thirty percent, you will have four suspects and no way to isolate them.

Test With One Section on Large Sites

On large sites, start with a section that changes little, measure redirects, indexing, and traffic there, and then roll out the rest with your own data in hand.

Redirects: The Heart of the Migration

The official redirects guide ranks the options by preference, and that order matters.

301 and 308: Permanent Server-Side Redirects

They signal that a page moved permanently and that the destination should be shown in results. They resolve on the server, before any HTML is downloaded, with nothing depending on the browser:

Redirect 301 /old-page/ /new-page/

The 308 keeps the HTTP method (a POST stays a POST); for a content site, 301 remains the standard.

Redirect Chains: Under Five, Ideally Three or Fewer

Googlebot will follow up to ten hops, but every hop costs crawl time and adds a failure point. Redirect straight to the final destination; if you cannot, keep the chain to three hops or fewer and always under five. Audit chains after applying the map, not before.

The "Everything to the Homepage" Mistake: Irrelevant Redirects and Soft 404s

Sending hundreds of old URLs to the homepage looks tidy, and Google treats it as an irrelevant redirect with a real risk of soft 404. The legitimate exception is consolidation: several similar pages merged into one new page that covers all of that content.

302, Meta Refresh, and JavaScript: When Not to Use Them

A 302 is temporary and keeps the source in results, so it is useless for a move. Meta refresh and JavaScript redirects are acceptable only without server access, and an on-screen notice is not a redirect: users see it, Google does not read it as a change of address.

Domain Changes: The Change of Address Tool

When to Use It and When Not To

It migrates results from the old domain to the new one, but it only applies to domain or subdomain changes. It does not apply to HTTP to HTTPS, to www to non-www, to moving pages within a site, or to a hosting change without URL changes.

How to Run It

Move and redirect first; submit the change afterwards. Verify every variant of the old domain, with and without www and including subdomains, and redirect each one. Submit it from the old property and keep the new one verified so you can follow both sides.

Official Warnings

Do not chain migrations (A to B and then straight to C) and do not merge several sites into one at once: migrate one, wait for traffic to stabilize, then do the next. Keeping the same architecture at the destination helps signals transfer more directly.

During and After the Migration: Monitoring

How Long Google Takes to Process the Move

A small or medium site takes a few weeks for most pages to move; larger sites take longer. Plan in weeks, not days.

What to Watch in Search Console

• Sitemaps: the old one drops to zero indexed pages, the new one climbs.
• Pages: every new 404 or soft 404 is a missing redirect.
• Queries: compare clicks per query, not just the aggregate.
• URL Inspection: on your top ten URLs, confirm the final destination with no chain.
• Logs and analytics: crawling and completed tasks on the new domain.

Warnings about the old sitemap listing redirecting URLs are expected and can be ignored.

Keep Redirects for at Least a Year

Google recommends at least a year so every signal transfers, including recrawling and the reassignment of external links. In practice, keep them indefinitely: they cost little and prevent 404s on old links.

Warning Signs

A sustained drop in indexed pages, new crawl errors on the new domain, or queries that have not recovered after six weeks. On any of these, check the redirect map before touching content.

Final Checklist for a Website Migration Without Losing Rankings

1. Inventory of URLs with traffic and links.
2. Old-to-new redirect map, one per URL.
3. New site with self-referencing canonicals, hreflang, and no noindex.
4. One change at a time.
5. 301 or 308 on the server, straight to the final destination.
6. No long chains and nothing sent to the homepage.
7. Change of Address only if the domain changes.
8. New sitemap submitted and the old one removed.
9. Weekly monitoring for four to six weeks.
10. Redirects live for a year and a heads-up to sites linking to you.

A migration is not won on switch-over day, it is won in preparation: with the inventory, the map, and the redirects done properly, Google only has to change address. If traffic has already dropped, the next step is the guide on diagnosing a search traffic drop.