Moving a website without losing rankings.

What counts as a migration (and why it's risky)

"Migration" sounds like a purely technical, once-in-a-decade event, but it covers more than people realise: moving to a new domain, switching platform or CMS, redesigning a site in a way that changes URLs, restructuring your pages, moving from HTTP to HTTPS, or merging sites. Any of these can put your hard-won search visibility at risk.

The risk is specific and it's about rankings. Over months or years, your pages earn authority and rankings tied to their specific URLs. When you change or move those URLs without telling search engines where everything went, that accumulated value can evaporate — Google finds broken links where valuable pages used to be, drops them from results, and treats the new pages as unknown newcomers starting from scratch. The traffic you built disappears not because the new site is worse, but because the connection to what you earned was severed. This is the single most avoidable disaster in web projects, and it's covered from the redesign angle in the redesign guide too.

The golden rule: map and redirect every URL

If you remember one thing, remember this: every valuable URL on the old site must redirect to its equivalent on the new one, using a 301 (permanent) redirect. That single discipline prevents the great majority of migration disasters.

The process is methodical: first, list every URL on your existing site (a crawl tool or your analytics and Search Console data gives you this). Second, decide the new URL for each — ideally keep them identical, but where they must change, map old to new explicitly. Third, implement a 301 redirect from each old URL to its new home, so anyone (and any search engine) arriving at the old address is sent seamlessly to the right new page, carrying the earned authority with them.

The mechanics of 301s, redirect chains and the difference from 302s are covered in the technical SEO guide.

Preserving what makes pages rank

Redirects get people to the right page, but the page also needs to keep the things that made it rank. Before migrating, capture and preserve:

• On-page content — the actual text that ranks. A redesign that quietly cuts content often cuts rankings with it; if a page ranks well, respect what's there.
• Title tags and meta descriptions — these tell search engines what a page is about; losing or mangling them in a migration confuses rankings.
• Heading structure — the H1s and H2s that signal what the page covers.
• Structured data — carry over the schema markup, or you lose rich results and machine-readability (the AI-era point).
• Internal links — the linking structure that distributes authority; rebuild it deliberately, don't let it vanish.
• Images and their alt text — including anything ranking in image search.

The principle: a migration should preserve and improve, not silently discard. Know what's working before you change anything — which is exactly what the audit stage of the discovery process is for. Export your Search Console data first; those ranking pages are your must-protect list.

The pre-launch migration checklist

That "not blocking search engines" line deserves emphasis — new sites are often built with a noindex tag or a robots.txt block to keep them hidden during development, and forgetting to remove it at launch hides the entire live site from Google. It's one of the most common and most damaging migration mistakes, and it's covered in why a website isn't showing on Google.

Launch day and immediately after

At launch: put the redirects live with the new site, submit the updated sitemap in Search Console, and verify that a sample of old URLs correctly redirect to their new homes (test a good spread, not just one). Confirm the site is crawlable and indexable — no leftover blocks. Then watch closely.

The first days and weeks after a migration are when problems surface, and catching them fast is the difference between a wobble and a disaster. Some short-term ranking fluctuation is normal as Google re-crawls and re-processes the moved site — don't panic at day-two noise. But a sustained drop signals a real problem (usually a redirect gap, a blocking tag, or lost content) that needs immediate attention. Speed of response matters: a redirect mistake fixed within days causes a blip; the same mistake left for weeks can cause lasting damage.

Post-launch monitoring: what to watch

For at least the first month or two, monitor:

• Search Console coverage and errors — is the new site being indexed? Are there crawl errors, or old URLs reporting problems? This is your primary early-warning system.
• Rankings for your key terms — track the important searches; a temporary dip that recovers is normal, a sustained drop is not.
• Organic traffic — compare against the pre-migration baseline, expecting some short-term movement but watching the trend.
• Redirects still working — spot-check that redirects haven't broken, especially after any further changes.
• Core Web Vitals and errors — make sure the new site is technically healthy, not just present.

A properly executed migration, closely monitored, typically sees rankings hold steady or recover quickly. The horror stories almost always trace back to skipped redirects, lost content, or blocking tags left in place — all preventable with the preparation above.

When to get help with a migration

For a small, simple site, a careful owner following the steps above can migrate successfully. But the stakes rise sharply with the value of your existing traffic: if your site drives real revenue through search, a botched migration is an expensive mistake, and the redirect mapping in particular is fiddly and unforgiving at scale.

This is exactly the kind of work where experience earns its cost — knowing the traps, mapping redirects correctly, preserving what ranks, and monitoring properly afterward. If you're moving a site that matters, or replacing one as part of a redesign, it's worth having someone handle the migration who's done it before and treats "preserve the rankings" as the non-negotiable it is. Getting it wrong is far more expensive than getting it done right.

Frequently asked questions

What is a website migration?

Any significant change to a site's location, platform or structure — a new domain, a new CMS, a redesign with changed URLs, a move to HTTPS, or merging sites. The main risk is losing the search rankings the old site earned, which makes careful planning essential.

Will I lose my Google rankings if I migrate my website?

Only if it's done carelessly. Rankings are lost when URLs change without proper redirects, when ranking content is discarded, or when a blocking tag is left on the new site. Done properly — with a full redirect map and preserved content — rankings typically hold steady or recover quickly.

What is the most important part of a website migration?

Mapping every valuable old URL to its new equivalent and setting up a 301 (permanent) redirect for each. This single discipline prevents the great majority of migration disasters by carrying earned authority from old pages to their new locations.

What is a 301 redirect and why does it matter for migration?

A 301 is a permanent redirect that sends visitors and search engines from an old URL to a new one while passing the page's earned authority. In a migration, redirecting every old URL to its new equivalent with a 301 is what preserves your rankings through the move.

Why shouldn't I just redirect everything to my new homepage?

Because a visitor or search engine looking for a specific page — say 'boiler repair Chelmsford' — doesn't want your homepage, and a blanket redirect to it loses nearly all that page's specific ranking value. You must map each old URL to its equivalent new page, not funnel everything to the homepage.

What should I preserve when migrating a website?

The things that make pages rank: on-page content, title tags and meta descriptions, heading structure, structured data, internal links, and images with their alt text. A migration should preserve and improve these, not silently discard them along with the rankings they support.

How do I avoid hiding my new site from Google after launch?

Remove any 'noindex' tag or robots.txt block that was added to keep the site hidden during development. Forgetting to remove it at launch hides the entire live site from Google — one of the most common and damaging migration mistakes. Verify indexability immediately after going live.

How long does it take for rankings to recover after a migration?

With a properly executed migration, rankings often hold steady with only brief fluctuation as Google re-crawls the moved site. Some movement over the first days to weeks is normal; a sustained drop signals a real problem to fix. Full stabilisation typically occurs within a few weeks to a couple of months.

What should I monitor after a website migration?

Search Console coverage and crawl errors (your main early warning), rankings for key terms, organic traffic against the pre-migration baseline, that redirects still work, and Core Web Vitals. Watch closely for the first month or two, since fast response to a problem is what prevents lasting damage.

Is some ranking fluctuation normal after migrating?

Yes — short-term movement is normal as Google re-crawls and re-processes the moved site, so don't panic at day-two noise. What matters is the trend: a temporary dip that recovers is expected, while a sustained drop indicates a genuine issue like a redirect gap or blocking tag.

Should I migrate my website myself or get help?

A small, simple site can be migrated by a careful owner following the right steps. But if your site drives real revenue through search, the stakes are high and redirect mapping is fiddly, so experienced help is worth the cost — a botched migration is far more expensive than doing it properly.

Can I improve my site during a migration?

Yes, but carefully — preserve what's working (ranking content, URLs, metadata) while improving the rest. The danger is a redesign that quietly discards ranking content or changes URLs without redirects. Know what's performing before you change anything, then enhance around it rather than replacing it blindly.

Related: Website redesign · Technical SEO · Not showing on Google? · Discovery process