Website migration SEO: move your site without losing rankings
A migration succeeds or fails on the details: every old URL, every redirect and the first weeks in Search Console.
Key takeaways
- An SEO migration is any major change to domain, URLs, platform, hosting or language set-up that search engines need to pick up.
- The foundation is a complete URL inventory and a redirect map in which every old URL goes to the best matching new URL with a single 301.
- Test everything on a protected staging environment and work through a fixed checklist on launch day.
- After launch, Search Console temporarily shows messages that often prove your redirects and canonicals are working; judge trends, not snapshots.
- Google advises keeping redirects in place for as long as possible, generally at least one year.
An SEO migration means moving a website to a different domain, platform, URL structure, host or language set-up without search engines losing track of it. It works when every old URL points to the best matching new URL with a single 301 redirect, the content stays at least as good, and you check in Search Console after launch that Google is picking up the move.
I am writing this shortly after my own migration. In October 2026 I moved seomotion.nl and racemotion.nl from WordPress to static HTML websites, and seomotion.nl became multilingual at the same time. So this is not theory: it is the approach I learned at agencies and have now applied to my own sites, including what I ran into in Search Console afterwards.
What types of website migration are there, and how risky are they?
Not every migration carries the same risk: the risk grows with the number of URLs that change. A hosting move with identical URLs is manageable; a domain change or new URL structure needs a full redirect plan.
| Type of migration | What changes | Risk | Main focus |
|---|---|---|---|
| Hosting move | Server, URLs stay the same | Low | Uptime, speed, no robots.txt block |
| http to https or www change | Protocol or host name | Low to medium | Site-wide 301s, update canonicals and internal links |
| Platform or CMS change | Templates, often URLs too | Medium to high | URL mapping, titles, structured data, speed |
| New URL structure | Page paths | High | One-to-one redirects, no chains |
| Domain change | The entire domain | High | All redirects plus the Change of Address tool |
| Merging or splitting sites | Content and URLs | High | Content mapping: which page replaces which |
| Internationalisation | New language versions | Medium | hreflang, phased release |
My own migration was a combination: a CMS change (WordPress to static HTML), a hosting move (shared hosting to Netlify), changed URLs and an expansion to four languages. The domain stayed the same and remained with the registrar. That helps: a domain change adds an extra layer of risk.
What goes wrong in practice is almost always the same: forgotten URLs that end in a 404, redirect chains, a noindex or robots.txt block carried over from the test environment, canonicals pointing to staging, and internal links that still go to old URLs.
How do you prepare for an SEO migration?
Preparation revolves around two documents: a complete inventory of every existing URL and a redirect map that records where each URL will go. The more complete the inventory, the smaller the chance of losing traffic and links.
A crawl of your current site alone is not enough. A crawler only finds pages that are linked internally, while old pages often still have traffic or backlinks. So combine:
- a full crawl of the current site;
- the XML sitemap(s);
- an export of pages from the Search Console Performance report (ideally 16 months);
- landing pages from your analytics;
- URLs with backlinks from a link tool;
- server logs, where available.
Then record a baseline: clicks, impressions and positions per page, the number of indexed pages and your Core Web Vitals. Without a baseline you cannot tell after launch whether a dip is normal or a problem.
Next, the redirect map. The rule is one-to-one: every old URL gets a single 301 redirect to the best matching new URL, with no intermediate hops. Do not send everything to the homepage; Google tends to treat that kind of redirect as a ‘soft 404’. Pages with no successor, traffic or links can return a 404 or 410.
Example redirect map. The URLs below are fictitious and purely illustrative.
| Old URL (example) | New URL (example) | Status | Note |
|---|---|---|---|
| http://example.com/?p=123 | https://www.example.com/services/seo-audit/ | 301 | WordPress ID URL, protocol and www in one step |
| /2019/05/ten-seo-tips/ | /blog/seo-tips/ | 301 | Date removed from the path |
| /category/news/ | /blog/ | 301 | Archive page to blog overview |
| /home/ | / | 301 | Duplicate homepage |
| /contact-2/ | /contact/ | 301 | Leftover from an old version |
| /tag/seo/ | none | 410 | Thin tag page with no traffic or links |
Note the first row: redirecting http to https first and non-www to www second creates a two-step chain. Send the redirect straight to the final URL.
What should you test before launch?
Test the new site on a password-protected staging environment and check everything there that you cannot calmly fix once it is live. A password is safer than a robots.txt block or noindex alone, because those settings sometimes go live by accident.
- Crawl the staging site and compare titles, meta descriptions, H1s and canonicals with the old site.
- Check that all important content is in the HTML and not loaded only through JavaScript.
- Test the full redirect list with a script or crawler: status 301, one hop, correct destination.
- Check structured data, hreflang and the XML sitemap.
- Check that internal links point directly to the new URLs, not through redirects.
- Measure load times and Core Web Vitals for the main templates.
- Test analytics, consent and forms.
What do you do on launch day?
On launch day you follow a fixed sequence and verify each step on the live site, not on the basis of what ought to work. Pick a quiet moment, not just before a busy period.
- Put the new site live and remove the password, noindex and robots.txt blocks from staging.
- Check robots.txt, a few pages for noindex and the canonicals in the live HTML.
- Test a sample of redirects, including http, non-www and the old URLs with the most clicks and links.
- Submit the new XML sitemap to Google Search Console and Bing Webmaster Tools.
- For a domain change, use the Change of Address tool in Search Console.
- Inspect your key pages with the URL Inspection tool and request indexing.
- Check that analytics is receiving data.
What did I see in Search Console after my own migration?
In the first days after my migration, Search Console showed a series of messages that look like errors but mainly showed that the redirects and canonicals were doing their job. That is normal, and worth knowing before you panic.
First, the context. In October 2026 seomotion.nl and racemotion.nl moved from WordPress on shared hosting to static HTML on Netlify, with zero JavaScript. Old WordPress URLs got a 301, both sites have an XML sitemap and an llms.txt, and I set up a Domain property in Search Console and Bing Webmaster Tools. seomotion.nl became multilingual (Dutch, English, German and Belgian French) with hreflang. The German and French versions went live in phases: first with noindex, then released on 5 October 2026.
| Search Console message | Cause on my site | A problem? |
|---|---|---|
| Excluded by ‘noindex’ tag | German and French pages crawled while still on noindex | No, clears after a recrawl |
| Page with redirect | http to https and non-www to www | No, this is correct behaviour |
| Alternate page with proper canonical tag | Non-www version during the transition | No, the canonical works |
| Old URL /home/ flagged as a duplicate | WordPress leftover of the homepage | No, now a 301 to / |
| Crawled – currently not indexed | New pages Google still had to assess | Not yet, but keep watching |
| Sitemap: Couldn’t fetch | First attempt just after submission | No, a few days later ‘Success’ with all 99 URLs |
The lesson I take from it: during a migration you temporarily see ‘errors’ that actually show the system is working. Judge trends, not snapshots, and check every message by testing the URL live. A ‘Page with redirect’ message for an http URL is exactly what you want to see.
The Page indexing report also lags behind reality: it reflects the situation when Google last crawled each URL. The URL Inspection tool with ‘Test live URL’ shows how things are now.
And the result? racemotion.nl went from 71 to 100 on mobile in PageSpeed Insights, with Largest Contentful Paint dropping from 6.2 to 1.4 seconds. seomotion.nl scores 100 on both mobile and desktop. Why I left WordPress, and when WordPress is still a good choice, is covered in my article on WordPress SEO.
What should you monitor in the weeks after launch?
After launch, track a few fixed signals every week: 404 errors, indexing, clicks per page and the status of your sitemap. Look at the trend over weeks, not at a single day.
- Performance report: compare clicks and impressions per page with your baseline.
- Page indexing: is the number of indexed new URLs rising?
- Not found (404): is there an old URL you forgot? Add the redirect.
- Recrawl the old URL list: do all URLs still return a single-hop 301?
- Ask sites with important backlinks to update their link to the new URL.
- For a multilingual site, check the hreflang relationships against Google’s documentation on localised versions.
How long does recovery take, and how long should redirects stay?
According to Google, rankings can fluctuate temporarily; a medium-sized site can take a few weeks and a large site longer. Google says to keep redirects ‘as long as possible, generally at least 1 year’; my advice is to never remove them in principle.
That guidance is in Google’s documentation on site moves with URL changes. Redirects remain necessary for visitors arriving through old links, bookmarks or emails, and for backlinks that are never updated. On most servers and static hosts they cost next to nothing. In its documentation on redirects, Google recommends a permanent redirect, such as a 301, for a permanent move.
If a drop lasts longer than a few weeks, go back to your redirect map and your 404 report. In almost every migration that disappoints, the cause is technical, not ‘Google needing time to adjust’.
My advice: how should you approach your own migration?
Plan a migration as a project with its own timeline: inventory and redirect map first, staging tests next, and time reserved for monitoring after launch. Do not combine more changes than necessary; the less that changes at once, the easier it is to trace a problem. I deliberately chose to release the German and French versions in phases.
If it is an online shop, pay extra attention to filters, product variants and out-of-stock items; I cover those in my article on ecommerce SEO. If you want a second pair of eyes on your migration plan, that falls under technical SEO, and for multilingual sites under international SEO. And if you would rather learn it yourself, I cover migrations in my technical SEO training.
Sources
Frequently asked questions
Do you always lose rankings during a website migration?
Not always, but temporary fluctuations are normal, as Google itself says. Lasting losses are usually caused by missing redirects, lost content or technical blocks. With a complete redirect map and proper testing, a migration without lasting losses is very achievable, although nobody can guarantee it.
Should I use a 301 or a 302 redirect for a migration?
For a permanent move, use a 301 (or 308). A 302 is meant for temporary situations, such as a short-term campaign page. Google may eventually treat a long-standing 302 as permanent, but a 301 sends the right signal straight away.
Can I migrate and rewrite all my content at the same time?
You can, but it makes analysis harder: if a page drops, you will not know whether the redirect or the new copy is to blame. I recommend phasing major content changes, or at least logging them per page so you can trace them later.
When is it better not to schedule a migration?
Avoid your busiest period of the year, such as the weeks before the holidays for an online shop, and any time when nobody is available to fix problems. Also leave room after launch for monitoring and small corrections.
Do I always need the Change of Address tool?
No, only when you move to a different domain. For a migration within the same domain, such as a new CMS, different hosting or a new URL structure, the tool is not needed. My own domains stayed the same, so I did not use it.
Curious what SEO and GEO could do for your business?
Tell me where your business stands today and where you want to take it. In a short, no-obligation call we will work out which steps will make the biggest difference.
