Changing your domain, redesigning your look, or switching to a new CMS can send your traffic tumbling overnight if the migration isn't properly prepared. A significant share of the visibility drops we see at small and mid-sized businesses come from a botched migration, not a Google penalty. The good news: these losses are avoidable. Here's the method we apply at TC Automation to migrate a website without losing its SEO rankings, with a concrete checklist, real-world examples, and the watch-outs that make all the difference.
Why a migration causes rankings to drop
Google ties your rankings to specific URLs. When you migrate, those URLs often change: a new domain name, a new folder structure, moving from `/blog/my-article.html` to `/articles/my-article`. If Google hits a 404 error where the page it knew used to be, it eventually deindexes that page, and you lose the associated ranking along with the visitors who landed there.
The other classic causes of a drop are the loss of SEO tags (title, meta description, structured data) during the redesign, misconfigured redirects, or a staging site left indexable that creates duplicate content. We also regularly see internal links still pointing to the old addresses, or an entirely rethought site structure that breaks the site's topical logic. The good news: each of these risks can be managed with a bit of method.
Migration doesn't mean just one thing
A simple switch to HTTPS, a CMS change with constant URLs, a visual redesign, or a full domain change don't carry the same risks. The more elements you change at once (domain + structure + design), the tighter your monitoring must be. When possible, avoid changing everything in one go.
Migration types and their risk levels
Before you start, clearly identify what you're changing. It determines the scope of your redirect plan and how intensive your monitoring needs to be. If you're still unsure about the scope, our article on website redesign: when and how to go about it will help you frame the project up front.
| Type of migration | What changes | SEO risk level |
|---|---|---|
| HTTP to HTTPS switch | The protocol only | Low with clean redirects |
| Visual redesign | Design, URLs unchanged | Low to moderate |
| CMS change | Technical, often URLs too | Moderate to high |
| New site structure | URL structure | High |
| Domain change | Full domain name | High |
Step 1: map the existing site before touching anything
You can only migrate well what you actually know. Before making a single change, build a complete inventory of your current URLs and their performance. This document becomes the reference for building your redirect plan and for checking, afterward, that nothing was left out. For a small business with around thirty pages, a spreadsheet is enough; for a site with several hundred URLs, a crawler becomes essential.
- Export the list of all your indexed URLs (Google Search Console, a crawler like Screaming Frog, or your existing sitemap).
- For each page, note the ranking keywords and the traffic it receives, so you can identify the strategic pages to protect first.
- Save the title, meta description, and Hn tags of every important page.
- Log your strongest backlinks: these are the pages linked to by other sites and they deserve special attention.
- Pinpoint your most-visited pages and your conversion pages (contact, quote requests): these are your absolute priorities.
This mapping work often overlaps with a full SEO audit: take the opportunity to spot weak or outdated pages that the migration lets you clean up rather than carry over as-is.
Never migrate without a backup
Make a full backup of the site and its database before the operation. If something goes wrong, being able to roll back in minutes prevents a multi-day disaster. Also test that the backup is genuinely restorable: a backup you can't actually restore is worthless.
Step 2: build the redirect plan
This is the heart of a successful migration. Every old URL must point to its equivalent new version via a 301 redirect (a permanent redirect). The 301 passes most of the SEO value the old page accumulated on to the new one. A 302 redirect (temporary), by contrast, tells Google the change isn't permanent and doesn't pass that value the same way: keep it for genuinely temporary cases.
Create a mapping table that pairs each old URL with its destination. The goal is the most precise mapping possible: redirect to the page with the closest content, never lazily to the homepage. Mass-redirecting dozens of URLs to the homepage is read by Google as pages that no longer exist, which wipes out the benefit of the 301.
| Old URL | New URL | Type |
|---|---|---|
| /services/brochure-site.html | /services/web | 301 |
| /blog/2023/my-article | /articles/my-article | 301 |
| /contact-us | /contact | 301 |
| /deleted-page | (closest matching page) | 301 |
One redirect = a single hop
Avoid redirect chains (A to B to C). They slow down crawling and dilute the signal. Always point the old URL directly to the final destination. A crawl tool easily surfaces these chains so you can fix them before going live.
Real-world case: a business changing its domain
Take a services company moving from `old-name.com` to `new-name.com` during a rebrand. Without a redirect plan, all its ranking pages turn into 404s on the old domain, and the new domain starts almost from scratch. With a page-by-page 301 redirect, it keeps the old domain for at least a year, redirects every URL to its equivalent, then declares the address change in Search Console. The result: a temporary dip of a few days, then a return to the original level, instead of a lasting collapse.
Step 3: preserve your content and SEO tags
A redesign shouldn't be an excuse to lose content. Pages that rank do so thanks to their text, headings, and structure. Carry those elements over as-is to the new version, and improve them later once the migration has stabilized. A common mistake is starting over with a clean design that has half as much text: Google sees a thinned-out page and the ranking slips.
- Keep your optimized title and meta description tags, or improve them without gutting them.
- Maintain a consistent Hn hierarchy: a single H1 per page, with structuring H2s.
- Carry over the structured data (Schema.org) present on the old site.
- Check that images keep their alt attributes and descriptive file names.
- Don't remove your existing internal linking: rebuild the links between your pages using the new URLs.
If you take the chance to rework your tags, lean on the best practices for title and meta description tags rather than starting from scratch on copy that was already working.
Use the migration to lighten your media: lighter images improve load speed, a factor that weighs on both SEO and user experience. We walk through the process in our guide on how to optimize your images for the web. Compress your visuals before putting them back online.
Lighten your images before going live
Reduce the file size of your visuals with no visible loss of quality to speed up your new site and sharpen your technical SEO.
Step 4: going live and the technical checks
On launch day, a handful of technical settings determine whether Google understands your new site correctly. Handle them in order and verify each point rather than assuming it works. Ideally, schedule the go-live during a low-traffic window, so you have room to fix issues before the rush.
- 1Remove the staging site's indexing block: check the robots.txt file and make sure there's no `noindex` tag on the pages you want ranked.
- 2Enable HTTPS and force the redirect from http to https, along with your choice between the `www` and non-`www` version.
- 3Generate and submit a fresh, up-to-date sitemap.xml.
- 4Test a sample of old URLs in the browser to confirm the 301s actually work.
- 5Check your internal links: they should point to the new URLs, not route through redirects.
- 6Review your canonical tags: each page should declare itself as canonical, without mistakenly pointing to the old domain.
The test that reassures
Take your ten most important pages, open their old URL one by one, and check that each lands directly on its new version in a single redirect. If those ten are perfect, you've secured the bulk of your traffic.
Step 5: post-migration monitoring
A migration doesn't end at go-live. The first few weeks are decisive: this is when Google recrawls your site and updates its index. Close monitoring lets you fix issues before they hurt your traffic for the long term. Expect several weeks before full stabilization, sometimes longer for a large site.
- In Search Console, submit the new sitemap and watch the coverage report to spot 404 errors.
- If you're changing domains, use Search Console's change of address tool.
- Watch your organic traffic in your analytics tool: a slight temporary dip is normal, but a sharp and lasting drop signals a problem.
- Regularly check the 404s being generated and add the missing redirects.
- Track the rankings of the strategic pages you identified in Step 1.
Also remember to update your pages: after a migration is the right time to check the length and depth of your copy. Content that's too short rarely ranks well.
The common mistakes that cost you dearly
Most traffic drops after a migration come down to a handful of recurring mistakes. Knowing them in advance keeps you from making them.
- Redirecting everything to the homepage instead of page-by-page mapping: this is the most destructive mistake.
- Forgetting to deindex the staging site or, conversely, leaving a `noindex` in production after going live.
- Letting the old domain expire too soon during an address change, which cuts off the redirects.
- Neglecting backlinks: notifying the sites that link to you, when possible, protects your authority.
- Migrating mid-campaign or in peak season, with no room to make corrections.
A successful migration doesn't show up in the traffic charts: that's precisely where all the work lies.
Frequently asked questions
How long does it take to recover traffic after a migration?
Expect anywhere from a few weeks to a few months depending on the size of the site and the scale of the changes. A slight dip in the first few days is normal while Google recrawls and reindexes. If traffic hasn't recovered after several weeks, look for a technical cause: broken redirects, pages set to noindex, or unhandled 404s.
How do you migrate a website without losing your SEO rankings?
The golden rule is to map all your URLs, then set up page-by-page 301 redirects to the new addresses. Preserve the content and SEO tags that were working, verify the technical setup on launch day, and monitor Search Console in the following weeks. It's the rigor of the redirect plan that protects your traffic.
Why did my traffic drop after my redesign?
The most common causes are URLs changed without 301 redirects, a loss of content or tags during the redesign, a site left on noindex, or internal links still pointing to the old addresses. A quick review of the coverage report in Search Console usually reveals the source of the problem.
Which type of redirect should I use for a migration?
Always use the 301 redirect, known as permanent. It tells Google the change is definitive and passes almost all of the SEO value to the new page. Reserve the 302 for genuinely temporary cases, since it doesn't transfer that value the same way.
Should I notify Google of a domain change?
Yes. On top of the 301 redirects, declare the change through Google Search Console's change of address tool, once both the old and new domains are verified. This speeds up how quickly the migration is taken into account and shortens the transition period.
In summary
Migrating a site without losing your SEO rankings isn't magic: it's a matter of preparation and rigor. Map the existing site, identify the type of migration and its risk level, build a precise 301 redirect plan, preserve your content and tags, verify the technical setup on launch day, then keep a close watch in the following weeks while avoiding the classic mistakes.
This is exactly the approach we apply for our clients as part of our website design and redesign services. If you're preparing a redesign or a domain change and want to secure your traffic, let's talk about your project: our team can support you from the initial audit through post-migration monitoring.
