Migrate without losing rankings by planning SEO from the start: crawl and inventory every existing URL, map each old URL to its new equivalent with 301 redirects, preserve titles, content, and internal links, keep the staging site noindexed until launch, then launch, submit a fresh sitemap, and monitor Search Console closely. Done methodically, a migration preserves — sometimes improves — your search traffic.
- The non-negotiable step is a complete 301 redirect map: every old URL pointed to its closest new equivalent before launch.
- Inventory every existing URL first — from a crawl, Search Console, and analytics — so nothing that ranks is forgotten.
- Preserve titles, meta descriptions, headings, body content, and internal links; lost signals cause lost rankings.
- Keep the new/staging site noindexed during build, and remove that block at launch — forgetting either side causes major problems.
- Migrations are highest-risk when they change URLs, CMS, domain, or structure all at once; isolate changes and monitor Search Console daily after launch.
What a 'Migration' Actually Is — and Why It's Risky
A migration is any change significant enough that URLs, structure, or the platform underneath them moves. That includes a redesign with new URLs, switching CMS (say WordPress to a custom or headless build), changing domain (rebrand, or finally moving to HTTPS or a non-www version), consolidating multiple sites, or restructuring your navigation and URL hierarchy.
The risk comes from the fact that Google's rankings, and the backlinks others have given you, are attached to specific URLs. When those URLs change without a clear, permanent path from old to new, the signals that earned your rankings get severed. The site can look better and still lose half its organic traffic overnight.
The encouraging part is that this risk is almost entirely controllable. Traffic loss in migrations comes from preventable mistakes, not from migrating itself. A migration executed with SEO planned in from day one routinely preserves rankings — and because it's often paired with a faster, better-structured site, it can come out ahead. The difference between a smooth migration and a disaster is preparation, and specifically the redirect map.
Before Launch: Inventory, Map, and Preserve
The work that protects your rankings happens before anything goes live.
First, inventory every URL. Crawl your current site, then cross-reference Google Search Console (which URLs get impressions and clicks) and analytics (which pages get traffic) and your backlink data (which URLs have earned links). The goal is a complete list of every page that has value, so nothing important is silently dropped.
Second, build the redirect map. For each old URL, decide its new equivalent and record a 301 (permanent) redirect from old to new. Pages with no direct equivalent should redirect to the most relevant new page, not the homepage. This map is the single most important migration artifact — prioritize your highest-traffic and most-linked pages, and have it ready to deploy at launch.
Third, preserve the signals on the pages themselves. Carry over title tags, meta descriptions, heading structure, and — critically — the body content that was ranking. Resist the urge to thin pages for visual cleanliness; if a page ranked because it was thorough, keep it thorough. Re-create internal links between related pages so authority keeps flowing. And keep the new or staging site noindexed throughout the build so Google doesn't index a half-finished version — while remembering to remove that block at launch.
Launch Day: Deploy, Open the Gates, Tell Google
Launch is where preparation pays off, executed in a deliberate sequence.
Deploy the new site with the 301 redirects live from the moment it goes public — not added later. Then remove the noindex/robots block that kept the staging site private, so Google can finally index the new site. Forgetting this step is one of the most common ways a launch tanks: a perfect new site that's still telling Google to stay away.
Next, update and submit a fresh XML sitemap in Search Console reflecting the new URLs, and (if a domain change) use the Change of Address tool. Spot-check redirects by visiting a sample of important old URLs and confirming they land on the right new pages with a 301, not a 404 or a redirect chain. Verify a handful of key pages are indexable using URL Inspection. Confirm analytics and conversion tracking are firing on the new site — migrations frequently break tracking, which means you'd be flying blind exactly when you most need data.
If you can, launch at a low-traffic time and avoid stacking unrelated changes on the same day. The cleaner and more isolated the migration, the easier it is to diagnose anything that goes wrong.
After Launch: Monitor, Diagnose, Recover
A migration isn't finished at launch — the first few weeks of monitoring are part of the job.
Watch Google Search Console closely: indexing/coverage for de-indexed pages or new errors, crawl stats, and the performance report for queries or pages that lost ground. Keep an eye on analytics for traffic drops isolated to specific sections. A small, temporary dip in the first week or two is normal as Google reprocesses the site; a sustained drop points to a specific problem to fix.
When you see a drop, diagnose against the checklist: are the affected URLs redirecting correctly, or 404ing? Are they indexable, or did a block slip through? Did they keep their content and titles, or get thinned? Are they still internally linked? Most post-migration losses trace to a redirect that was missed, a page that lost content, or an indexability flag — all recoverable once found.
Handled this way, a migration preserves your hard-won rankings and often improves them, because you've usually also improved speed and structure. If a migration feels risky to run alone — and the stakes are real — this is core to our web development work: we redesign and migrate sites with the redirect mapping and monitoring built into the project, so search traffic carries through the move. Our guide on why rankings drop after a redesign covers the recovery side in more depth.
Related questions
The 301 redirect map — pointing every old URL to its closest new equivalent, deployed live at launch. Skipping or botching redirects is the leading cause of lost traffic in migrations, because rankings and backlinks are attached to specific URLs. Get this right and you've prevented most of the damage; get it wrong and little else matters.
Usually only a small, temporary dip in the first week or two as Google re-crawls and reprocesses the new site. Done methodically — redirects, preserved content and metadata, intact internal links, clean indexing — rankings typically hold and recover quickly, and often improve if the new site is faster and better structured. Sustained losses indicate a specific, fixable mistake.
Expect a few weeks for the bulk of re-crawling and a month or two for things to fully settle, depending on site size and crawl frequency. Larger sites take longer. Monitor Search Console throughout; a brief early dip is normal, but anything still down after several weeks should be diagnosed against the redirect, indexability, and content checklist.
You can, but it raises the risk because more signals move at once and problems are harder to isolate. If possible, separate big changes — migrate the domain, let it settle, then redesign, or vice versa. If they must happen together, be especially rigorous with redirects, use the Change of Address tool, and monitor daily after launch.
You don't need it identical, but preserve the substance that was ranking — depth, topics, titles, and headings. You can improve and modernize content; just don't thin a page that ranked because it was thorough. If you consolidate pages, redirect the old URLs to the merged page and make sure the combined page covers what both originals did.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get Free Proposal →