A website migration is any change to your domain, platform, URL structure or design that can affect how search engines find your pages. Done carelessly, it can wipe out years of rankings in a week. Done well, it keeps your traffic and often improves it. The difference is a plan: benchmark before you start, map every old URL to a new one, redirect with permanent 301s, protect the content that ranks, and monitor closely for the first 12 weeks.
Key takeaways
- Benchmark rankings, traffic and every URL before you change anything.
- Map every old URL to its closest new equivalent and redirect it with a permanent 301.
- Keep the content, titles and internal links of the pages that already rank.
- On launch day, test redirects, remove staging noindex tags and submit the new sitemap.
- Monitor Search Console for 12 weeks and keep redirects in place for at least a year.
This checklist covers the three stages of a safe migration: before launch, launch day and after launch. It applies to a simple redesign as much as to a full replatform or domain change.
What counts as a website migration?
Not every migration carries the same risk. The more your URLs, content or domain change, the more carefully you need to plan.
| Type of change | What changes | SEO risk |
|---|---|---|
| Redesign, same URLs | Design, templates, some content | Low to medium |
| Replatform (for example WordPress to Webflow) | CMS, URL patterns, code, speed | Medium to high |
| URL restructure | Paths, folders and slugs | High |
| Domain change or rebrand | The whole domain | High |
| HTTP to HTTPS, or www changes | Protocol or host name | Low when redirected |
Why do rankings drop after a redesign?
Rankings rarely drop because of the new design itself. They drop because something search engines relied on disappeared or changed without a signal. The usual causes:
- Old URLs that now return 404 errors because no redirect was set.
- Redirect chains, loops or temporary 302 redirects where permanent 301s were needed.
- Content that ranked was removed, merged or thinned out.
- Titles, headings and internal links changed on your most valuable pages.
- A noindex tag or robots.txt rule left over from the staging site.
- Slower pages, broken structured data or missing images after launch.
Google has confirmed that permanent redirects pass ranking signals to the new URL, so a clean redirect map is the single most important protection you have.
Before launch: the pre-migration checklist
1. Benchmark everything
- Crawl the current site with a tool such as Screaming Frog or Sitebulb and export every URL, title, meta description, heading and canonical.
- Export your top pages and queries from Google Search Console for the last 12 months.
- Export landing pages from your analytics, and the pages that earn backlinks.
- Record rankings for your priority keywords and your Core Web Vitals.
2. Map every URL
- Build a redirect map: one row per old URL, pointing to the closest equivalent new URL.
- Redirect one to one wherever possible. Never send everything to the homepage; search engines treat that as a soft 404.
- Keep URLs that do not need to change. The safest redirect is the one you never need.
3. Protect the content and on-page SEO
- Keep the content of pages that rank and earn traffic, or improve it; do not cut it for the sake of a cleaner design.
- Carry over titles, meta descriptions and headings for your most valuable pages, then refine them after launch.
- Rebuild internal links to point straight at the new URLs, not through redirects.
- Keep image alt text, structured data and canonical tags.
4. Keep staging out of search
- Protect the staging site with a password, not just robots.txt.
- If staging uses noindex, put a launch-day task in the plan to remove it.
5. Prepare the technical layer
- Server-side 301 redirects for every mapped URL, with no chains.
- Canonical tags that point to the new URLs.
- A fresh XML sitemap that lists only the new, indexable URLs.
- A reviewed robots.txt, and hreflang tags if you run more than one language.
Launch day checklist
- Deploy the redirects and test a sample of your top 100 URLs: each should return a 301 to a page that returns 200.
- Remove staging passwords and noindex tags, and check robots.txt on the live site.
- Submit the new sitemap in Google Search Console and Bing Webmaster Tools. For a domain change, use Google's Change of Address tool.
- Ping Bing and other IndexNow engines so they recrawl the changed URLs quickly.
- Check that analytics, consent and conversion tracking fire on the new templates.
After launch: what to monitor for 12 weeks
| When | What to check | Where |
|---|---|---|
| Day 1 | 404 errors, redirect errors, robots and noindex | A crawler and Search Console |
| Week 1 | New URLs being indexed, coverage errors | Search Console, Pages report |
| Weeks 2 to 4 | Rankings and impressions against your benchmark | Search Console and a rank tracker |
| Weeks 4 to 12 | Traffic, conversions and Core Web Vitals | Analytics and Chrome UX data |
Keep your redirects in place for the long term. Google recommends keeping them for as long as possible, and generally for at least a year.
How long does it take for rankings to recover after a migration?
A well executed redesign that keeps its URLs often sees little or no drop. When URLs change, expect some movement while search engines recrawl and reprocess the site; for most small and medium sites this settles within a few weeks, and larger or more complex moves can take longer. If rankings are still down after a month, recheck redirects, indexing and the content of your most valuable pages against your benchmark.
Use the redesign to improve conversion, not just looks
A migration is the rare moment when everything is on the table. Use it to fix what your data says is broken: slow templates, confusing navigation, weak calls to action. A UX audit before the redesign shows which pages leak the most, our Core Web Vitals playbook covers speed, and why UX design matters for SEO explains how the two work together.
Frequently asked questions
Will a website redesign hurt my SEO?
Not if it is planned. Rankings drop when URLs break, content that ranked is removed or technical signals change without redirects. Keep URLs where you can, redirect every changed URL with a 301 to its closest equivalent, protect your best content and monitor Search Console for the first weeks after launch.
How do I redirect old URLs after a redesign?
Build a redirect map that pairs every old URL with its closest new equivalent, then set permanent 301 redirects on the server. Redirect one to one rather than sending pages to the homepage, avoid chains, and test your most important URLs on launch day.
Should I change my URLs during a redesign?
Only when there is a clear reason, such as a messy structure that hurts navigation. Every changed URL needs a redirect and takes time to be reprocessed, so keeping existing URLs is the lowest risk option.
How long should I keep 301 redirects?
As long as possible. Google recommends keeping redirects for at least a year, and in practice it is safest to keep them permanently because old links and bookmarks keep sending visitors to the old URLs.
What is the difference between a 301 and a 302 redirect?
A 301 tells search engines a page has moved permanently and that the new URL should replace the old one. A 302 signals a temporary move. For a migration or redesign, use 301 redirects.
Do I need to tell Google about a website migration?
Submit your new XML sitemap in Google Search Console and inspect a few key URLs. If you are moving to a new domain, also use the Change of Address tool. For Bing, submit the sitemap in Bing Webmaster Tools and use IndexNow to signal changed URLs.