Site Migration SEO: How to Move Your Website Without Losing Rankings

You can migrate a website without losing your rankings, but only if you treat the move as an SEO project and not just a design job. The basics are simple to say and easy to skip: record where you stand today, map every old URL to its new home, redirect properly, change as little as possible at once, and watch Google Search Console closely afterwards. This guide walks through each step in plain English, whether you are changing domain, moving platform or rebuilding the whole site.

TTOY Digital

Plan a Website Move That Protects Visibility

TTOY Digital builds mobile-first websites and targeted local SEO strategies for small businesses strengthening their online presence.

Explore TTOY Digital

TL;DR

A migration is any big change to your domain, URLs, hosting, platform or design. Any of them can move your rankings.
Before launch, record your baseline and build a complete old-to-new URL map. Never skip the map.
Use permanent server-side redirects straight to the closest matching page, not to the homepage.
Change one major thing at a time where you can, so a drop is easier to diagnose.
After launch, check Search Console daily at first. Settling can take weeks, and keep redirects live for at least a year.

What counts as a site migration?
Why migrations hurt rankings
Before the move: groundwork
Launch day
After launch: the first 90 days
A migration checklist on one page
Our perspective
How we can help
FAQ
Sources

What counts as a site migration?

Most owners think “migration” means changing domain. It is wider than that. Google’s own guidance on site moves and migrations covers anything that changes your existing page URLs: moving from HTTP to HTTPS, changing domain or hostname, or restructuring URL paths. Google also says rankings can fluctuate for a while as it recrawls and reindexes the new addresses.

Ahrefs takes a broader view, describing a migration as a significant change to your domain, URLs, hosting, platform or design. That matters for small businesses, because the changes most of us actually make fall into a few familiar groups:

Domain change: rebranding, or swapping a clunky name for a cleaner one.
Platform change: moving from a site builder to WordPress, or the other way round.
Redesign: new look and new page structure, often with new URLs.
Hosting move: same site, different server.
HTTPS move: switching from HTTP to HTTPS.
Restructure: merging pages, renaming sections, changing the menu.

The trap is the quiet one. A redesign that “only” changes how things look often changes URLs, headings and internal links along the way. We cover that in more detail in our piece on whether a website redesign affects SEO.

Why migrations hurt rankings

Google has spent years learning your old pages. It knows what each URL is about, which other sites link to it and how people behave on it. When the address changes, none of that follows automatically. It only transfers if you tell Google, clearly and page by page, where each old page now lives.

Most losses come from a handful of avoidable slips:

Old URLs that now show an error page.
Hundreds of old pages redirected to the homepage.
Titles, headings and copy rewritten at the same moment as the platform changed.
A “noindex” tag or robots.txt block left over from the test site.
Internal links and sitemaps still pointing at the old addresses.

None of these is exotic. All of them are things a careful checklist catches, which is why the next sections are ordered the way they are.

Before the move: groundwork

Change one big thing at a time

Google recommends changing only one major factor at a time where possible, for example keeping a domain move separate from a CMS or layout change. The reason is practical. If rankings dip after a combined move, you cannot tell which change caused it. Webnode’s migration guide makes a related point: avoid changing content at the same time as the platform, and keep existing URLs where practical.

For a small business that might mean: move to the new platform first with the same URLs and copy, let things settle, then refresh the content. It feels slower, but it is far easier to fix if something goes wrong.

Record your baseline

You cannot say whether the move worked unless you know where you started. Search Engine Land’s guidance on migration checks suggests recording organic sessions, rankings, top landing pages, indexed pages, conversions and site speed before the transition. Pantheon goes further, listing Search Console clicks, impressions and queries, indexed and excluded URLs, sitemaps, canonicals, titles, descriptions, crawl errors and performance metrics.

For a ten to fifty page business site, a sensible baseline is a spreadsheet with:

Every live URL, taken from a crawl and from your sitemap.
Clicks, impressions and average position per page from Search Console.
Your top ten landing pages and what they earn you in enquiries or calls.
Current titles, meta descriptions and H1s.
Page speed figures for your main pages.
A note of which pages have outside links pointing to them.

Save it somewhere safe before anything changes. If you have Google Business Profile listings and local rankings, screenshot those too.

Build the URL map

Google recommends preparing and thoroughly testing the new site, then creating a mapping from every current URL to its corresponding new URL. This is the single most important document in the project.

It looks like this:

Old URL	New URL	Notes
/services/web-design-derby	/services/web-design	Merged two pages, keep the stronger copy
/about-us	/about	Same content
/blog/old-post	/blog/old-post	No change
/old-offer-page	/services	No close match, nearest relevant section

Where a new page genuinely replaces an old one, point to it. Where an old page has no equivalent, choose the nearest relevant page. Do not send everything to the homepage: Google warns that sending many unrelated URLs there can confuse users and may be treated as a soft 404.

Test on a staging site

Build and check the new site somewhere search engines cannot find it, such as a password-protected staging copy. Check that:

Every page in your map exists and loads.
Titles, headings and copy have carried over.
Forms, phone links and any booking tools work on mobile.
Pages load quickly. Our note on page speed and Core Web Vitals explains why this affects enquiries as well as rankings.
Nothing on the staging site tells search engines to stay away that might be copied across by accident when it goes live.

Launch day

Pick a quiet moment

Google suggests launching during a lower-traffic period if possible. For many local firms that is a weekday evening or a quiet week, not the week before your busiest season. Make sure someone who can fix things is available for the next day or two.

Weekly planner marking a quiet launch window

Move everything together

For small and medium sites, Google recommends moving all URLs at the same time. Larger sites may move in sections so they are easier to monitor, but most small business sites are well under that threshold, so a single clean switch is usually the simpler answer.

Set up redirects properly

From Google’s guidance on redirects and URL mapping, the rules are:

Use server-side permanent redirects (301 or 308).
Send each old URL directly to the closest relevant final URL.
Avoid chains, where A goes to B goes to C.
Do not bulk redirect everything to the homepage.
Keep the redirects in place for at least one year.

Then tidy the rest: update internal links so they point at the new URLs rather than relying on redirects, and update canonical tags, hreflang if you use it, and your XML sitemap.

If the domain is changing

A domain change adds a few extra steps. Verify every variant of the old domain in Search Console (with and without www, HTTP and HTTPS), then use the Change of Address tool once redirects are working. Keep the old domain registered and renewed for as long as the redirects need to run, which is one more reason to keep your domain names and DNS in good order rather than letting the old one lapse.

If you also run email on the old domain, plan that move separately so messages do not stop arriving on the day of launch.

After launch: the first 90 days

The first week

Open Search Console and check the basics. Google’s guidance points to the old and new sitemaps and indexing data, query impressions and clicks, crawl errors and the URL Inspection tool. Then test a sample of old URLs by hand and confirm each lands on the right page with a single redirect.

What to look for, drawing on Pantheon’s list of post-launch problems:

Important new URLs that are not getting indexed.
Old URLs that still return a normal page instead of redirecting.
Unexpected 404, 5xx or soft-404 responses.
Wrong canonicals being selected by Google.
Accidental noindex tags or robots.txt blocks.

Google’s Search Console help adds that after a restructure, domain move or HTTPS move, ranking problems should prompt checks of 301 redirects, page indexing, robots.txt, manual actions, security issues and URL Inspection. Search Engine Journal also reported that John Mueller suggests starting any post-migration deindexing investigation in Search Console, where 404s or robots.txt blocks tend to show up.

Weeks two to twelve

Do not panic at a wobble. Google says medium-sized sites can take a few weeks or more for new URLs to replace old ones, and larger sites can take longer. Keep watching both old and new sitemaps, crawl errors, queries, clicks and traffic.

Compare against your baseline each week. Pantheon recommends looking at clicks, impressions, average positions, high-value landing pages, branded versus non-branded searches and differences by device or country. Branded searches (people typing your name) usually recover first, so a dip there is a stronger warning than a dip on broad terms.

If a key page falls and stays down, work through this order:

Is the old URL redirecting to the right place in one step?
Is the new page indexable, with no noindex tag or robots block?
Did the title, heading or copy change from the old version?
Is the page slower than before?
Is the canonical pointing where you expect?

Fix the cause, then use URL Inspection to request reindexing of the affected page.

A migration checklist on one page

Stage	Do this
Before	Choose one major change, record baseline, crawl the site, build the URL map, test on staging
Launch	Pick a quiet time, move all URLs together, add 301 or 308 redirects, update internal links, canonicals and sitemap
Domain change	Verify all old variants, submit Change of Address, keep old domain renewed
After	Check Search Console, test redirects, fix noindex or robots issues, compare with baseline weekly
Long term	Keep redirects for at least a year, keep old backlinks pointing somewhere useful

Our own write-up on SEO best practices during website migration goes through the same ground from a project-management angle.

Our perspective

We have seen the same story many times. A business owner pays for a lovely new site, it launches on a Friday, and by the following month the phone has gone quiet. Nobody did anything wrong on purpose. The designer designed, the developer built, and nobody was holding the list of old URLs.

That is why we treat SEO as part of the build, not an add-on. Because we are a small team based in Derbyshire, we can talk to you in person about which pages actually bring you work, protect those first, and keep the rest tidy. Our approach is ongoing optimisation rather than a one-off handover, so we are still watching Search Console in the weeks after launch, when it matters most.

We also think it is worth keeping the moving parts few. If you are changing platform, we would rather keep your URLs and wording steady, then improve things once the dust settles. It is less exciting on launch day and a lot kinder to your enquiries.

Chris

How we can help

If you are planning a rebuild or a platform move, our web design plans start from £120 per month on the Starter plan, with Growth at £170 and Smart at £560 per month. Pair it with our local SEO service, which starts from £150 per month, and the migration is planned and monitored by the same people. Once the site is live, WordPress maintenance is £30 per month per site, and UK web hosting starts from £15 per month.

FAQ

How long does SEO take to recover after a site migration?

Google says medium-sized sites can take a few weeks or more for new URLs to replace the old ones, and larger sites can take longer. Keep comparing Search Console clicks and impressions with your pre-move baseline rather than judging by a single day.

Does changing my domain name hurt SEO?

It can cause a temporary dip, because Google has to recrawl and reindex everything under the new address. Permanent redirects from each old URL to its closest new page, a verified old domain in Search Console and the Change of Address tool all help it understand the move.

How long should I keep 301 redirects in place?

Google recommends keeping them for at least one year. In practice, if old pages still have links pointing to them or still get visits, leaving the redirects in place longer costs you nothing.

Should I redirect all my old pages to the homepage?

No. Google warns that sending many unrelated URLs to the homepage can confuse visitors and may be treated as a soft 404. Redirect each old page to the closest relevant new one.

What should I record before migrating?

At minimum: organic sessions, Search Console clicks and impressions, top landing pages, indexed pages, conversions and page speed. Add your titles, descriptions, canonicals and sitemap, so you can compare after launch.