Website Redesign Without Losing SEO: A Step-by-Step Migration Guide
Redesigning your website? Protect your Google rankings with this step-by-step SEO migration plan: URL inventory, 301 redirects, testing and launch checks.

A new website should bring more customers, not fewer. Yet many businesses see their Google traffic drop sharply after a redesign — usually because URLs changed without redirects, content disappeared or the new site was accidentally blocked from indexing.
The good news: these problems are predictable and preventable. This is the migration process I follow so that rankings stay intact — and often improve.
Why redesigns lose rankings
- Changed URLs without 301 redirects — Google and visitors hit 404 errors, and the authority of old pages is lost.
- Removed or thinned content — pages that ranked well are merged, shortened or deleted.
- Lost on-page elements — titles, headings and meta descriptions are rewritten without considering keywords.
- Indexing blocks — the staging site’s
noindextag or robots.txt rule goes live. - Slower performance — a heavier design worsens Core Web Vitals.
- Broken internal links — navigation and links point to old URLs.
Step 1: Benchmark the current site
Before changing anything, record where you stand: organic traffic per page from Google Analytics, clicks and queries from Search Console, current rankings for your main keywords, and Core Web Vitals. Without a baseline, you can’t tell whether the migration went well.
Step 2: Build a complete URL inventory
Crawl the old site with a tool such as Screaming Frog, and combine the list with URLs from your sitemap, Search Console and analytics. Include pages with backlinks — those carry the most authority. This list becomes your redirect map.
Step 3: Decide what happens to every URL
For each old URL choose one action:
| Old page | Action |
|---|---|
| Same content, same URL | Keep the URL |
| Same content, new URL | 301 redirect to the new URL |
| Merged into another page | 301 redirect to the most relevant page |
| Removed, no equivalent | 301 to the closest relevant page, or return 410/404 if nothing fits |
Avoid redirecting everything to the homepage; Google often treats that like a missing page.
Step 4: Preserve what ranks
Carry over the content, headings and title tags of pages that bring traffic, and improve them rather than replacing them. Keep structured data, image alt text and internal links in place.
Step 5: Keep staging private — then open it at launch
Protect the staging site with a password or noindex so Google doesn’t index it — and make removing that protection part of your launch checklist. In WordPress, double-check that “Discourage search engines from indexing this site” is unticked after launch.
Step 6: Test before launch
- Test every redirect from your map, and check for chains and loops.
- Crawl the staging site for broken links, missing titles and accidental noindex tags.
- Compare speed and Core Web Vitals with the old site. See my Core Web Vitals guide.
- Confirm that analytics and conversion tracking work on the new site.
Step 7: Launch and monitor closely
- Deploy the new site and the redirects at the same time.
- Submit the new XML sitemap in Search Console and request indexing for key pages.
- Crawl the live site to confirm redirects and status codes.
- Watch Search Console daily for the first two weeks for 404s, indexing problems and drops in impressions.
- Update important backlinks and your Google Business Profile with new URLs where possible.
If you’re also changing your domain name, use the Change of Address tool in Search Console after setting up redirects.
Example redirect map
A redirect map is simply a spreadsheet with one row per old URL. Here’s what a few rows typically look like:
| Old URL | New URL | Action | Why |
|---|---|---|---|
| /our-services.html | /services/ | 301 | Same content, new URL |
| /seo-vancouver | /services/seo/ | 301 | Merged into the main SEO page |
| /blog/2019/10/post-title | /post-title/ | 301 | Simpler permalink structure |
| /old-promo-2021 | — | 410 | Expired offer with no equivalent page |
| /about-us/ | /about-us/ | Keep | URL unchanged — no redirect needed |
Map every old URL to the most relevant new page. If there’s genuinely no equivalent, a 410 (gone) or 404 is better than redirecting everything to the homepage — Google treats mass homepage redirects as soft 404s anyway.
The most common redesign mistakes
- Redirecting everything to the homepage. Relevance is lost and Google often ignores those redirects.
- Redirect chains. Old URL → older redirect → new URL. Point every old URL straight at its final destination.
- Leaving “noindex” on after launch. Staging sites are often blocked from search; check that the block is removed the moment the new site goes live.
- Changing URLs that didn’t need to change. Every URL change carries some risk. Keep URLs that already rank whenever you can.
- Cutting content that ranked. A “cleaner” page with half the text can lose the very content Google was ranking.
- Forgetting images and PDFs. Files that get traffic from image search or links need redirects too.
- Breaking internal links. Menus, footers and in-content links should point to final URLs, not to redirects.
- Losing tracking. Analytics and conversion tags missing on the new site make it impossible to judge the impact.
Special cases
Moving to a new domain
Everything above applies, plus: redirect every URL on the old domain to its equivalent on the new one, keep the old domain registered and redirecting for years, and use the Change of Address tool in Google Search Console.
Switching platforms (for example, to WordPress)
Platforms produce URLs differently — category paths, trailing slashes, file extensions. Crawl the old site before you switch so you have the full list, then set permalinks on the new platform to match the old structure as closely as possible.
Merging two sites
Decide which site is the primary one, map the content of the secondary site page by page into the primary, and redirect accordingly. Merge overlapping pages instead of keeping two weak versions.
Post-launch checklist
| When | What to check |
|---|---|
| Launch day | Robots.txt and noindex removed, sitemap submitted, redirects tested on a sample of old URLs, analytics firing |
| First week | Search Console coverage and crawl errors, 404 report, forms and phone links, page speed |
| Weeks 2–4 | Rankings and traffic for your top pages compared with the benchmark, fix any missed redirects |
| Months 2–3 | Overall organic traffic and conversions versus the pre-launch baseline |
How long until rankings settle?
Some fluctuation in the first weeks is normal while Google recrawls the site. With complete redirects and preserved content, rankings typically recover within a few weeks — and a faster, better-structured site often climbs higher than before.
Frequently asked questions
How long should I keep 301 redirects?
As long as possible — ideally permanently. Google recommends keeping them for at least a year, but old links on other websites will keep sending visitors for much longer.
Will changing my design alone affect SEO?
Visual changes alone rarely hurt. Problems come from changes to URLs, content, internal links, indexing and speed — which usually happen at the same time.
Should I launch the new site gradually?
For large sites, migrating in phases can reduce risk. For most small business sites, a single well-tested launch is simpler and works well.
Should I redirect pages to the homepage if they have no equivalent?
No. Redirect to the closest relevant page. If nothing is relevant, let the old URL return a 410 or 404. Mass redirects to the homepage are usually treated as soft 404s.
Can a redesign improve SEO?
Yes — a faster site, clearer structure and better content often lift rankings once Google has re-crawled everything. The goal of a careful migration is to keep what you have so those improvements add to it rather than replacing lost ground.
Planning a redesign?
I handle redesigns from design to SEO-safe migration, so your new site launches with its rankings intact. See my web design and SEO services, check the SEO checklist for new websites, or get in touch to plan your migration.


