Nov 14, 2025
How to plan a website migration without losing SEO rankings
A site migration without lost rankings is not luck, it is process. Audit what you have, map every URL to a 301 redirect, keep the on-page elements intact, test it in staging, update Search Console at launch, watch the numbers daily for a month, and fix what breaks within a day or two. Even a clean migration usually dips a little in the first weeks. A sloppy one, with missed redirects, loses far more than that, and takes far longer to come back. The difference is whether someone did the seven steps below, or skipped them to save a week.
1. Audit current SEO performance first
You cannot tell what broke if you never wrote down what worked. Before anything moves, document what Google currently rewards you for.
Export your top landing pages by organic traffic, and note their rankings for primary keywords, their monthly sessions, and their average position in Search Console. Take a full crawl with Screaming Frog or Sitebulb to capture title tags, meta descriptions, heading structure, and canonical tags. Pull your backlink profile from Ahrefs or Semrush, with attention to links pointing at your strongest pages, since those carry most of your organic value. If a high-authority site links to /old-product-page, that URL has to be in your redirect map.
Picture a SaaS company that migrates 2,400 pages without writing any of this down. Three weeks later traffic is down by a third, and nobody can say which pages or keywords slipped, so nobody knows what to fix. Now picture the same company having baselined everything: when rankings dip, it traces the drop to a specific set of pages with broken canonical tags, fixes them, and recovers within days. Same migration, same problem, completely different outcome, and the only difference is the baseline.
2. Map URLs and set up 301 redirects
Every public-facing URL needs a destination. Miss one and you have created a 404 where a ranking page used to be.
Start from your sitemap and crawl data, and export every URL that is indexed or receiving backlinks. Map each old URL to its exact new equivalent, one to one. The pages people forget are the ones that quietly carry traffic: pagination URLs like /blog/page/2/, filtered views like /products?color=blue, old campaign landing pages, and regional subfolders. A migration that overlooks a set of location-specific landing pages can lose a real share of organic sessions and only notice weeks later, once the crater shows up in the reports.
Every old URL should redirect to one new URL with equivalent content. /old-blog-post goes to /new-blog-post, not to the homepage, because a redirect to the homepage tells Google the original content is gone. Set the redirects at server level, in the Apache or Nginx config or in Cloudflare, rather than through JavaScript or a meta refresh, since search engines process server-side 301s faster and trust them more.
One thing worth correcting, because the old advice still circulates: a 301 redirect does not bleed link equity. Google passes nearly all of a page’s ranking signal through a 301. Redirect chains, where A points to B which points to C, are still worth fixing, but for different reasons, they slow crawling, they cost page speed, and a long enough chain risks Google giving up before the end. The fix is the same either way: point A straight at the final destination. Screaming Frog flags multi-hop redirects automatically, so check staging for them before launch.
3. Preserve on-page SEO elements exactly
A new CMS will have different field names and templates, but Google expects to see the same signals it saw before.
Title tags should stay identical, or very close. If a page ranked with the title “Best coffee grinders for small kitchens” and you relaunch it as “Top coffee machines”, Google reads that as a different topic and treats the page accordingly. Heading structure carries the same weight: keep the H1 a page ranked with, do not let a template quietly rewrite it. Meta descriptions do not move rankings directly, but they move click-through rates, so keep them unless you are fixing something genuinely broken.
If the old site used Product, Review, or FAQ schema, replicate it exactly. Losing a rich result in the search listing drops your click-through rate even when the ranking itself holds steady, so test the structured data in Google’s Rich Results Test before launch. Internal links matter too, they are how PageRank moves around your site. A page that had fifty internal links pointing at it and now has five has just been demoted in Google’s eyes, whether you meant that or not. And keep your alt text, the descriptive kind, rather than letting the new CMS auto-generate “image_1234.jpg” on every image.
4. Test everything in staging first
Launch day is the wrong moment to discover the redirects do not work. Staging exists to catch the disasters before customers do.
Crawl the staging site with Screaming Frog set to follow redirects, and confirm every old URL lands on the correct new URL with a 301 status. Look for 404s, redirect chains, and loops. Check that canonical tags point where they should and have not stayed pinned to the old domain. Run a full audit with Sitebulb or Oncrawl to catch the things manual testing misses: orphaned pages, broken hreflang, missing XML sitemaps, duplicate content, robots.txt rules that block more than they should.
Page speed affects rankings, so if the new platform is slower than the old one, you will see drops even with perfect redirects. Run Core Web Vitals checks on your most important landing pages in staging, and treat a regression as a launch blocker, not a post-launch task. Test the redirects across Chrome, Firefox, Safari, and Edge, and on a real mobile device, because some rules break on a specific browser, and staging is a much better place to find that out than production.
5. Update Search Console and monitor daily
Search Console is your direct line to Google, so use it the moment the new site is live.
Add the new domain as a property within the first day, and submit the new XML sitemap. If you are changing domains entirely, set up both properties and use the Change of Address tool so Google is told officially. Use the URL Inspection tool to request indexing for your highest-priority pages first: the homepage, the top landing pages, anything with significant backlinks.
Then watch. Check the indexing report daily for the first two weeks, looking for 404s, redirect errors, and pages blocked by robots.txt, because the sooner you catch those, the less ranking damage they do. Run a rank tracker on your top keywords daily and watch for sudden drops of ten positions or more, which usually mean a redirect failure or an indexing problem rather than normal movement. Small fluctuations of a few positions are Google re-evaluating the site and are nothing to worry about. Whole pages falling out of the index, or top keywords dropping from page one to page five, are.
6. Fix issues within 48 hours
Migration problems compound. A 404 on day one is a ranking drop by day three and a visible traffic dip by the end of the week, so speed of response matters more than anything else in this phase.
Rank the issues by impact and work top down: revenue-generating pages first, then pages with strong backlinks, then pages ranking in the top three for high-volume terms, then everything else. A 404 on the homepage is a five-alarm fire. A redirect chain on a tag page with three monthly visits can wait. Most of what you find falls into four buckets. A 404 is usually a missed redirect, so add it and request re-indexing. A redirect chain gets fixed by pointing the first URL straight at the final one. Slow pages are usually unoptimised images or heavy JavaScript on the new platform, so compress, lazy-load, and minify. Missing schema gets copied across from the old pages and re-tested.
Go back to that SaaS company from step one. The version that lost a third of its traffic had missed a set of redirects out of its 2,400 URLs. Once someone identified them, adding them back took an afternoon, and traffic started recovering within days. The damage was containable because the team acted fast. That is the whole point of monitoring daily, not weekly.
7. Track recovery for 90 days
Migration effects are not instant. Full ranking stabilisation takes a couple of months as Google re-crawls, re-indexes, and re-evaluates the site.
The rough shape is predictable. The first weeks bring small fluctuations as Google discovers the redirects. By week three or four, most pages settle and the genuine outliers become obvious. By week eight or so, a migration that went well is back to around 90 to 95 percent of its pre-launch traffic, and over the following weeks it recovers fully or improves, as Google rewards the cleaner technical setup. Compare everything against the baseline from step one: organic sessions, rankings for your top terms, indexed page count, crawl errors, and conversion rate from organic traffic.
The cost of getting this wrong is concrete. A site earning €50,000 a month from organic traffic that loses 30 percent for three months during a botched migration has lost €45,000 in revenue. A properly planned migration with professional help sits well inside that figure, which is the real argument for doing the seven steps rather than improvising. Our website migration support covers exactly this, from the pre-launch audit through the 90-day monitoring window.
Final thoughts
A site migration is a high-stakes move. One missed redirect map or forgotten canonical tag can cost months of traffic and a serious amount of revenue. The protocol is not complicated: document everything before you start, map every URL to its destination, keep the on-page elements intact, test in staging until nothing breaks, launch with Search Console ready, monitor closely for thirty days, and track recovery for ninety. The tools are ordinary and the steps are clear. The only real variable is whether someone skips a step to save time. Do not.
FAQ
Q: How long does a website migration take without losing SEO?
Planning and execution run a few weeks to a couple of months depending on site size. The launch itself happens in a day, but full ranking recovery takes roughly two to three months. Rushing the planning to save a fortnight tends to cost far more than that in lost traffic afterwards.
Q: What is the most common cause of traffic loss during site migration?
Missed or incorrect 301 redirects, by a wide margin. When old URLs return 404s or redirect to irrelevant pages, Google treats the content as deleted. A complete redirect map covering every indexed URL, tested in staging, is the single most effective protection.
Q: Do I need to redirect every single URL on my old site?
Every public-facing URL that is indexed or has backlinks, yes. That includes blog posts, product pages, category and tag pages, paginated URLs, and old landing pages. Crawl data and backlink reports are how you build the complete list, so nothing carrying traffic gets missed.
Q: How quickly will Google re-index my site after migration?
High-authority sites are often re-crawled within a day or two. Smaller sites can take a week or more. Submitting the new sitemap immediately and requesting indexing for your top pages speeds it up, and the indexing report shows you the progress.
Q: Can I migrate my site in phases to reduce risk?
Phased migrations make sense for very large sites, where sections move over weeks. For most sites a single cutover is simpler and creates fewer technical complications. A partial migration needs careful subdirectory planning and can confuse Google if it is not executed precisely.
