Website Migration SEO: When Do You Need Specialist Support?

By Istiak Ahmed Soikot, Founder and CEO, Rank OG

Last reviewed: November 2026

Website migration SEO services protect your rankings when URLs change during a redesign, platform switch, or domain move. The work is unglamorous: a complete redirect map, a clean technical handoff, and close monitoring after launch. Get specialist support when the move is complex.

This guide is for business owners and marketing leads planning a redesign, platform switch, or domain change. You will learn what Google expects during a move, the five safeguards that prevent traffic loss, and how to judge when website migration SEO services are worth the fee.

What actually counts as a website migration?

A website migration is any substantial change that affects how search engines reach, crawl, or index your site. Google splits moves into two families: moves with URL changes, such as domain changes, HTTP to HTTPS switches, and new URL paths, and moves without URL changes, such as switching hosts or adding a CDN.

That distinction decides most of the work, and it is the fork in the road where website migration SEO services either apply or they do not. A hosting move needs no redirects because no user-visible URL changes. Everything else needs a redirect plan, because every old URL Google knows has to find its new home.

Why do migrations lose rankings?

Migrations lose rankings when Google cannot match old pages to new ones. Google’s own troubleshooting list names the usual suspects: leftover noindex or robots.txt blocks from staging, redirects pointing to pages that do not exist, fresh crawl errors, sitemaps that still list old URLs, and servers that buckle under heavier post-launch crawling.

Notice what is not on that list: the redirect itself. Google states plainly that 301 and other permanent redirects do not cause a loss in PageRank. The damage people blame on “the migration” is almost always self-inflicted: a missing redirect map, a staging block nobody removed, or content that changed at the same time as the URLs.

What are the 5 critical safeguards during a website migration?

Google’s migration documentation reads like a checklist, and the five steps below are its backbone. They are also the core of what website migration SEO services deliver. Miss one and the other four cannot save you. Nail all five and even a large move stays boring, which is exactly what you want.

1. Map every old URL to its new home

You cannot redirect a URL you do not know exists, so the redirect map comes first: one row per old URL, one destination, one status code. Building this map is the single most valuable part of website migration SEO services. Google recommends server-side permanent redirects, meaning 301 or 308, with each old page going directly to its closest new equivalent.

A 302 or 307 tells Google the move is temporary, so it keeps the old URL. Googlebot can follow up to 10 hops in a redirect chain, but Google advises pointing straight at the final URL and keeping any chain to three hops or fewer. Pages you are deliberately retiring should return a proper 404 or 410.

2. Record the old site before you touch anything

Crawl the full site, export 12 months of clicks from Search Console, and list every URL that has backlinks. That inventory is both your redirect source and your baseline. Without it, you cannot tell a normal post-launch wobble from a real problem, and you will argue about it for weeks.

Include the forgotten corners: images, PDFs, and old campaign pages that other sites link to. Most website migration SEO services start every engagement with this inventory, because the pattern we see is always the same: the main pages migrate cleanly while a dozen linked PDFs quietly 404, and nobody notices until a backlink audit months later.

3. Keep staging locked down, then remove the blocks on launch day

Build the new site behind noindex rules or password protection so Google never indexes a half-built copy, then remove every block the moment you launch. Google lists forgotten noindex and robots.txt blocks among the most common migration failures, and it is easy to see why: the launch feels done, the site looks right, and search traffic quietly falls off a cliff.

Prepare the production robots.txt before launch day, not after. If your team blocked crawling during development, write down exactly what the file should look like once the move starts.

4. Carry the on-page signals to the new URLs

Titles, meta descriptions, H1s, body copy, and structured data should move with each page. Give every new URL a self-referencing canonical tag, update hreflang annotations to the new URLs, and rewrite internal links to point at final destinations instead of routing visitors through redirects.

Internal links that still point at old URLs force every visitor and crawl through a redirect hop, adding latency and server load. Update navigation, breadcrumbs, and sitemaps in the same pass.

5. Monitor both properties after launch

Watch the old property’s traffic fall and the new one’s rise. In Search Console, the old sitemap’s indexed count should drop toward zero while the new sitemap’s climbs; redirect warnings on the old sitemap are normal. Check server logs for unexpected 404s daily for the first week.

Google says to expect ranking fluctuation for a few weeks on a medium site, longer on large ones, while it recrawls everything. Keep the redirects in place for at least a year so Google can transfer signals fully, and keep watching weekly for two to three months. A drop that deepens after the first weeks points to a specific error worth investigating, not normal settling.

When can you handle a migration yourself?

You can usually handle a hosting or CDN move on your own, because no user-visible URL changes and there is nothing to redirect. Google’s hosting-move guide is short: copy and test the new setup, lower your DNS TTL a week ahead, flip the DNS records, watch the logs on both servers, then shut the old hosting down.

A tiny brochure site with identical URLs on a new platform is also manageable in-house, provided someone understands 301 redirects and checks Search Console afterward. The rule of thumb: if you can list every URL from memory and a week of lost traffic would not hurt the business, you probably do not need website migration SEO services.

When do website migration SEO services earn their fee?

Website migration SEO services earn their fee when the move changes URLs at scale, revenue depends on organic traffic, or the setup is technically tangled. Domain changes, platform switches with new URL structures, and merging several domains into one are the classic cases where specialist support pays for itself.

Picture a 400-page store moving platforms two weeks before its busiest season, with URLs, templates, and hreflang all changing at once. That is several ways to break things in one launch, and Google’s guidance is blunt: change one thing at a time. A specialist sequences the work, builds the redirect map, validates it on staging, and watches the crossover while your team runs the business.

Other signals: thousands of URLs, a purchased domain with an unknown history (Google advises checking it for manual actions left by a previous owner), or a merger of overlapping sites. Our technical SEO services cover migration planning and execution for exactly these situations.

How does each migration type compare on risk?

Not all moves are equal. This table ranks common migration types by what changes and how much specialist help they typically need.

Migration type	Do URLs change?	Biggest SEO risk	Specialist support?
Switching hosts or CDN	No	DNS propagation hiccups, slower server	Usually not needed
HTTP to HTTPS	Yes	Mixed content, missed redirects	Worth it for large sites
CMS or platform change	Often	URL and template changes landing together	Recommended
Redesign with new URL structure	Yes	Broken internal architecture	Recommended
Domain change or rebrand	Yes	Long, uncertain recovery window	Strongly recommended
Merging multiple domains	Yes	Duplicate content, redirect tangles	Strongly recommended

The pattern is simple: no URL changes means low risk, while domain changes and merges carry the most. If your move sits in the bottom three rows, that is when website migration SEO services stop being optional and start being insurance.

How do you know the migration worked?

The migration worked when new URLs replace old ones in Google’s index and clicks cross over to the new property. Google says a medium site can take a few weeks or more for new URLs to largely replace old ones, and larger sites take longer.

Measure it in three places. In Search Console, compare the old and new sitemaps’ indexed counts and watch the queries report for new URLs gaining impressions. In GA4, compare landing page traffic against your pre-launch baseline. In your server logs, confirm Googlebot is crawling the new URLs. This crossover check is also how website migration SEO services prove the job is done.

What to do next

1. Crawl your site and export Search Console and analytics data before anything changes. This baseline is your single source of truth.
2. Decide what is actually changing: URLs, platform, design, or all three. Split the work into steps wherever you can.
3. Build the one-to-one redirect map and test every redirect on staging before launch.
4. Launch during a low-traffic window, remove every staging block, and verify with the URL Inspection tool.
5. Compare Search Console and analytics against your baseline weekly for two to three months.
6. If the move involves a domain change or thousands of URLs, get a free SEO audit first so a specialist can sanity-check the plan before launch day.

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

Google says a medium site can take a few weeks or more before new URLs largely replace old ones, and larger sites take longer. Recovery depends on site size, server speed, and redirect quality. A drop that deepens after the first weeks signals a specific error, not normal fluctuation.

Do 301 redirects lose link value during a migration?

Google states that 301 and other permanent redirects do not cause a loss in PageRank. Migration losses come from missing redirects, redirects to the wrong pages, or long chains. Keep every redirect to one hop, pointed at the final URL, and leave redirects in place for at least a year.

Can I redesign my site and migrate it at the same time?

Google advises changing one thing at a time: move first, then change the platform or layout. Stacking a redesign, a platform switch, and new URLs into one launch gives every lost ranking several plausible causes. Split the work into steps and both risk and diagnosis get simpler.

What is the biggest mistake businesses make during a migration?

Leaving staging protections on the live site. Google lists forgotten noindex tags and robots.txt blocks among the most common migration failures. The new site launches, Google cannot index it, and traffic falls off fast. Prepare the production robots.txt in advance and verify with the URL Inspection tool on launch day.

Should I keep my old domain after migrating?

Yes, keep the old domain registered and its redirects live for at least a year, as Google recommends, so signals transfer fully. From a user perspective Google suggests keeping redirects indefinitely, while updating your own links and asking high-traffic referrers to point at the new URLs.

Sources

Site Moves and Migrations, Google Search Central. Changing Your Web Hosting and SEO, Google Search Central. Sources checked November 2026.

Planning a move? If this is your first migration, website migration SEO services can review your plan before launch day. Get a free SEO audit first, and talk to us if the checklist above feels bigger than your team. We reply within 24 hours.