How to Migrate Your Website Without Losing Your Google Rankings: An SEO Migration Guide

Somebody has told you the website is being rebuilt, and somebody else has told you that rebuilds tank your Google rankings. Both are half right. An SEO migration is the work of carrying your existing search visibility across to a new site, and rankings survive it when three things get done properly: a full inventory of every URL you have, a one-to-one redirect map, and monitoring for the first 90 days. Traffic falls when those get skipped, which happens more often than anyone admits.

What follows is written to be handed to whoever builds your site. Not sure the rebuild is the right call? Read whether a redesign makes sense first. This piece assumes the decision is made.

---

What is an SEO migration, and which changes actually count as one?

An SEO migration is any change big enough that Google has to re-learn your site: a new address, a new structure, or a substantially new set of pages. It isn't a synonym for redesign. A visual refresh that leaves every URL and every page of content where it was carries almost none of this risk, and that distinction spares a lot of people unnecessary anxiety.

Five change types trigger real migration risk.

---

Why rankings drop after a redesign, and how far they usually fall

Four causes account for nearly everything. URLs changed and nothing redirects them. Content was trimmed, taking the words that were ranking with it. Internal links were rebuilt from the new navigation and never restored to deeper pages. And technical signals were lost: titles, structured data, canonical tags, replaced by templates that don't carry them.

A short dip while Google reindexes is normal. A sustained drop is not, and the difference matters. Google's own site move documentation says to expect temporary fluctuation, and that for medium-sized sites it can take a few weeks or more before Google starts showing the new URLs instead of the old ones, longer for larger sites. That's the expected shape. Two months of decline with no recovery is a different animal.

We won't put a number on typical traffic loss, because there isn't a credible one. The figures circulating on this topic are mostly invented, and a percentage that doesn't apply to your site is worse than none. What we can say from our own work: a bit more than half the rebuilds we inherit mid-flight arrive with no redirect map at all . That's where the risk sits.

“301 and other permanent redirects don't cause a loss in PageRank”

Google Search Central, Site Moves and Migrations documentation

Worth quoting because the opposite belief is stubbornly common, and it leads people to avoid redirects out of a fear that redirecting costs something. It doesn't. Not redirecting does.

---

The website migration checklist: what to do before you launch

Nine items. Each one has a way to tell it's genuinely done, which is the part that lets a non-technical owner check somebody else's work rather than taking their word for it.

1. Inventory every URL on the current site. What it is: one combined list from a crawler, your analytics and Search Console. How you know it's done: you're handed a spreadsheet, and its row count is higher than the page count anyone quoted you.
2. Find out which pages earn your traffic and links. What it is: the subset that actually matters. How you know it's done: someone can name your top ten pages by organic traffic without looking them up twice.
3. Record the baseline before anything changes. What it is: current rankings, traffic, indexed page count and top queries, saved somewhere permanent. How you know it's done: you have dated exports, not screenshots.
4. Build the redirect map, one to one. What it is: every old URL paired with its new destination. How you know it's done: the map has as many rows as the inventory, and no column of repeated homepage links.
5. Carry the content across, not just the design. What it is: keeping the text that was ranking. How you know it's done: you can point at the old page and the new one and see the same substance.
6. Rebuild internal links to the new URLs. What it is: links pointing directly at new addresses rather than relying on redirects. How you know it's done: a crawl of staging returns no internal links that redirect.
7. Carry titles, meta descriptions and structured data across. What it is: the invisible half of every page. How you know it's done: spot-check five pages and compare old against new, field by field. Our guide to SEO basics before you launch covers the general version of this.
8. Keep the staging site out of the index. What it is: password protection or a noindex rule while you build. How you know it's done: searching for a distinctive phrase from staging returns nothing.
9. Prepare the new sitemap and keep the old one. What it is: two files, one of new URLs and one of old, both ready to submit. How you know it's done: both exist as files before launch day, not after.

Take a full inventory of every URL on the current site

Three sources, because none is complete alone. A crawler finds what's linked. Analytics finds what gets visited, including orphan pages. Search Console finds what Google indexed, including things you forgot existed. Merge and de-duplicate. Include images and PDFs, which get traffic and links and which nobody ever remembers.

Find out which pages actually earn your traffic and links

A small handful of pages usually carry most of the organic traffic, and they're rarely the ones anyone talks about in the redesign meeting. Find them, then argue for keeping their URLs unchanged. The cheapest migration is the one where your best pages don't move.

Record the current baseline before you touch anything

The step people skip and then desperately wish they hadn't. Without a dated record of where you started, you can't tell in March whether something broke in January or whether traffic was always seasonal. Export Search Console performance, top landing pages and indexed page count. Twenty minutes, and it's the difference between diagnosing a problem and guessing at one.

Keep the staging site out of the index

Two mirror-image disasters live here. A staging site that gets crawled, so Google indexes a half-built copy that competes with your real pages. And the more common one: a live site launching still carrying staging's noindex tag, which quietly removes the whole site from Google over the following fortnight. That second one accounts for roughly one in five of the post-launch emergencies we get called into . It's a single line of code, documented plainly in Google's noindex guidance, and it's completely silent until the traffic goes.

---

Redirect mapping, the step everyone underestimates

A 301 redirect is a permanent instruction that says "this page has moved here", and it passes both visitors and search engines to the new address. That's the whole concept, and Google's redirects documentation is the reference worth bookmarking. Everything else is discipline.

Map one to one. Every old URL gets its own destination, chosen as the closest equivalent. Google specifically warns against bulk-redirecting old URLs to the homepage, which confuses visitors and may be treated as a soft 404, meaning the redirect achieves nothing. Merged five pages into one? Redirecting all five there is correct. Five unrelated pages to the homepage is not.

Use 301, not 302. A 302 says "temporarily", and Google treats it accordingly. Flatten chains: if A redirects to B and B to C, point A straight at C. Googlebot follows up to 10 hops, but Google advises no more than three and fewer than five, and every hop adds delay for someone waiting on a phone. That last table row matters: a page that genuinely no longer exists should return a 410 or 404 rather than a misleading redirect.

Keep redirects in place at least a year. Google is explicit about that, and from a visitor's point of view indefinitely is better. Redirect maps aren't glamorous: the largest we've built ran to just over 4,000 URLs and took longer than the homepage design.

---

Launch day: the sequence that keeps you out of trouble

In order, with rough timings. And do not launch on a Friday. That's the single most useful line in this article: if something breaks at 4pm on a Friday, it stays broken until Monday, and Googlebot doesn't take weekends off.

1. Content freeze on the old site, 24 hours out. Any page added after the inventory has no redirect.
2. Full crawl of staging, the day before. An hour. Look for broken internal links, missing titles and anything still carrying noindex.
3. Go live, mid-morning, early in the week. Then everyone stays available.
4. Test a sample of redirects immediately. Twenty minutes. Fifty URLs from the map, weighted to your highest-traffic pages, each checked to land where it should.
5. Check robots.txt and the noindex tags. Five minutes, and the most valuable five minutes of the day.
6. Submit the new sitemap in Search Console. Ten minutes. Keep the old one submitted a while so you can watch old URLs drop out as new ones come in.
7. File a Change of Address, if and only if the domain changed. You don't need it for HTTP to HTTPS, for www changes, or for path changes on the same domain.
8. Confirm analytics and Search Console are still recording. Half an hour. Tracking code vanishes during rebuilds more often than anyone expects.
9. Validate structured data. Twenty minutes with Google's Rich Results Test across your page types.

Still planning the timeline rather than executing it? How long a website build takes sets expectations for the whole project.

---

The first 90 days after a site migration, and what normal looks like

Week one: indexed pages on the new URLs climb while old ones fall, and impressions wobble. Fine. Weeks two to six: the curve should visibly head the right way, new URLs appearing in Search Console and old ones fading. Weeks six to twelve: things settle, and you compare against your saved baseline.

Watch three things weekly in Search Console: coverage for a spike in errors, performance for which URLs earn impressions, and sitemaps for indexing progress. Worry if indexed pages are still falling at week six, if a high-value page never reappears, or if impressions stay flat.

Three fixes resolve most post-launch drops: a missing redirect for a page nobody inventoried, a noindex left in place, and content cut during the redesign that needs restoring. Most sites migrated properly are back to baseline inside four to eight weeks , though larger sites take longer and Google is clear that reindexing time scales with URL count. If monitoring and recovery is more than you want to take on internally, that's the territory of our SEO and AI visibility service. And if a meaningful share of your traffic is local, a migration puts those signals at risk too, so local search signals is worth a read alongside this.

---

Platform-specific traps: Webflow, WordPress and Shopify moves

No platform bashing. Each of these is a fine choice, and each has one thing that reliably goes wrong.

• Webflow. Redirects live in project settings and are straightforward, but CMS collection URLs come from a slug field, and changing a slug silently changes the live URL with no automatic redirect. Editors do this without realising. Lock slugs before launch, audit after. We work in Webflow daily as a Webflow agency, and this is the one that catches people.
• WordPress. Permalink structure. Switching from the default date-based format to a cleaner one changes every post URL at once, and while plugins can generate the redirects, they add a lookup on every request and get disabled during "performance cleanups" months later. Put the rules at server level if you can.
• Shopify. Product and collection URLs carry fixed prefixes you can't remove, so moving onto Shopify almost always means a full URL restructure whether you wanted one or not. It also generates multiple paths to the same product, so canonical tags need care. Plan around the prefixes rather than fighting them.

If you're still choosing where to land rather than moving, choosing between Webflow and WordPress covers the selection question properly.

---

Do it yourself or bring in a studio?

An owner can genuinely handle items one, two, three and nine. Pulling exports, identifying your best pages, saving a baseline and generating a sitemap are button-pressing tasks with a clear finish line. Do them yourself and you'll understand your own site better than you did.

Items four through eight need a developer, particularly the redirect map and the staging index controls, because getting them slightly wrong stays invisible for weeks. If you're commissioning the work, ask for the redirect map as a dated deliverable, not a line item that surfaces in the final week.

Inside a rebuild, we treat the map as part of the build rather than a task for the last afternoon. That's what our website redesign service is set up for, and the same approach runs through our web design in Burnaby and affordable web design in Vancouver work. On cost we won't restate figures: website redesign cost in 2026 and the redesign cost guide handle that.

---

Frequently Asked Questions

---

Three things protect your rankings: a complete URL inventory, a one-to-one redirect map, and 90 days of monitoring against a baseline saved before anything moved. The nine-item checklist above is the working version, written so you can hand it over and check the answers yourself. Migrations that go wrong go wrong quietly, in the boring steps, under deadline pressure.