Website Migration SEO: How to Redesign Without Losing Rankings

Picture the launch party. The new site looks fantastic. The team is happy, the owner is thrilled, someone orders pizza. Three weeks later the phone is quieter than it's been in years, and nobody can say why.

Here's what usually happened. The old site had a page for every service, and Google had spent years learning them. The new site moved them to different addresses and nobody said so. Visitors who clicked an old link hit "page not found," and Google quietly dropped the pages from its results.

That's avoidable. Website migration SEO is the set of steps that carries your search visibility from the old site to the new one, and it's mostly careful bookkeeping, not magic. Do the bookkeeping and a redesign can be a straight upgrade. Skip it and you can lose years of earned traffic in an afternoon.

This is the checklist we'd hand a friend. You don't need to be technical to follow it.

Website migration SEO: what puts your rankings at risk

A migration is any change that alters how search engines reach your content. A redesign on the same platform counts if the URLs change. So do these:

• Moving from one platform to another, say from a drag-and-drop builder to custom code.
• Changing your domain name.
• Switching from HTTP to HTTPS.
• Restructuring your site so pages live at new addresses.
• Merging two websites into one.

A pure visual refresh with the same URLs and content is low risk. The risk comes from moving things.

Google's guidance on moving a site with URL changes says it plainly: map old URLs to new ones, use permanent server-side redirects and monitor the move. Everything below follows it.

In our experience, migrations lose rankings for a short list of reasons:

1. URLs changed with no redirects. The old address now shows an error, and everything that page earned goes with it.
2. Everything was redirected to the homepage. It feels tidy, but Google treats it as a mismatch and the old page's relevance doesn't carry over.
3. Good content was cut. A page that quietly drove calls got "cleaned up" because it was in the way of the new layout.
4. The new site was left blocked. A setting that hides a development site from search engines stayed switched on after launch. This one is more common than anyone admits.
5. Titles, headings and internal links were rewritten without a plan, so the signals that told Google what each page was about vanished.
6. The new site is slower or harder to crawl than the old one.

Every item is a process failure, not a technology failure, which means a checklist can prevent it.

Still deciding whether a rebuild is right at all? Signs you need a new website will help. And if your rankings were already sliding, read why SEO is not working first, because a migration can't fix a problem it doesn't understand.

Before anything changes: crawl and inventory every URL

You can't protect what you haven't counted. The first job, before design, before code, is a full list of every address on the current site and what each one is doing for you.

Build the master list

Gather URLs from several places, because no single source has them all:

• A crawl of your live site. A crawling tool follows your links the way a search engine does and lists every page, image and file it finds.
• Your sitemap. The sitemap shows what the site says it contains.
• Search Console. The performance report lists pages that actually appear in Google, including old ones your navigation no longer links to.
• Your analytics. Pages that people visit, including ones nobody links to internally.
• Your CMS. Posts, pages and custom content types, including drafts and forgotten leftovers.
• Backlink data. Pages on other sites that link to you point at specific URLs, and those are worth the most to protect.

Google also suggests saving a list of the sites that link to your old URLs, so you can ask for updates later.

Put all of it in one spreadsheet, one row per URL. A small business site with a blog can easily have hundreds of addresses once you count old posts and category pages.

Record what each page is worth

Next to every URL, add columns for the decisions ahead:

• Monthly visits from search, from your analytics.
• Clicks and impressions from Search Console.
• Number of other sites linking to it.
• Whether it produces leads, calls or form submissions.
• The current title tag, meta description and main heading.
• Its status (working, redirecting, or returning an error).

This is your baseline. Three months after launch, when someone asks "did the redesign hurt us?", it's how you answer with facts. Save your overall traffic and lead numbers from before the move, too.

The crawl will turn up odd stuff: test pages, duplicate URLs with tracking tags, landing pages from a campaign long ago. Each odd row gets a decision in the next step.

Decide what to keep, merge or retire

Now comes the part where a redesign can actually improve your SEO. With the inventory in hand, sort every URL into one of four buckets.

Two principles do most of the work here.

Keep what ranks, and keep it recognizable. A page that already earns steady traffic has proven something. If the new design needs it shorter or cleaner, fine, but keep the same topic, the same main heading idea and the words people actually search. The most expensive mistake in a redesign is rewriting a high-performing page into "better" marketing copy that no longer answers the search it ranked for.

Don't redirect for the sake of redirecting. Google's guidance says to retire content you aren't carrying over by returning a 404 or 410 response, not by funneling it all to a single irrelevant page. A retired page with no value can simply end. A page that has a close successor should point to it.

This is also the time to be honest about thin content. Years of short blog posts nobody reads are weight, not an asset. Merging five weak articles into one useful one often performs better than all five did apart. For what makes an article worth keeping, see content marketing for SEO.

Map every old URL to a new one

This is the heart of website migration SEO. A redirect map is a plain table: old address on the left, new address on the right. It's boring to build and it's the single biggest factor in whether the move goes well.

How to build it

Start with your inventory. For each URL marked keep, improve or merge, write down the exact new address. Then check the following:

• One-to-one wherever possible. The old service page goes to the new service page, the old post to the new post. Relevance is what transfers value.
• Closest match when there is no equal. If a page is gone but a parent section exists, the parent is a reasonable target. The homepage almost never is.
• No chains. If page A redirects to B and B redirects to C, point A directly at C. Google says it can follow a chain, but it also recommends keeping hops few and redirecting straight to the final destination. Chains slow visitors and waste crawling.
• Account for variations. The www and non-www versions, http and https, trailing slashes and capital letters can all be separate addresses to a search engine. Decide on one standard form and redirect the rest to it.

Use the right kind of redirect

You want a permanent, server-side redirect, the kind commonly called a 301 redirect (a 308 does the same job). It tells browsers and search engines "this page has moved for good, go there instead." Google specifically recommends server-side redirects and treats client-side tricks, like a script or meta refresh, as a last resort.

Temporary redirects (302 and 307) say "this is a short detour," which isn't what a migration is.

A sample of what the map looks like:

(Made-up addresses, for illustration.)

Whoever builds the site should treat the redirect map as a deliverable on par with the design files. If you're hiring, ask about it up front; our list of questions to ask a web designer is a good start.

Test before you launch

Run the whole map against the staging copy. A developer can script it: feed in every old URL and confirm each lands in the right place. Nobody should click through 300 links by hand.

Rebuild the on-page signals

Redirects get the visitor to the right place. The new page then has to tell search engines what it's about, as clearly as the old one did. This is where redesigns quietly bleed rankings, because it's invisible on screen.

Go back to the baseline spreadsheet and make sure each important page keeps:

• Its title tag and meta description. Carry them over, then improve them deliberately. Don't let a new template overwrite them with the site name. See the glossary entries for title tag and meta description if those terms are new.
• Its main heading. One clear H1 that matches the topic the page ranks for.
• Its body content. Especially the text that matches the search. If you cut the page down, don't cut out the words the page ranks for.
• Its canonical tag. Each page should point to itself as the preferred version, which Google's guidance also recommends on the new site.
• Its structured data. If your old pages had review stars, business details or FAQ markup, the new ones should too. Check the schema markup carries over.
• Its image alt text and file names, so image search traffic doesn't disappear.

Internal links deserve more attention than they get

Your own links between pages tell Google which ones matter. In a rebuild, the navigation and footer change and in-text links to old addresses break or point at redirects.

Update every internal link to point straight to the final new URL. Redirects are a safety net, not a plan. Then confirm your most important pages are still linked from the main menu, the homepage and related pages.

Also make sure you haven't buried your best pages. A service page that moved from one click off the homepage to four will often slip, even with perfect redirects.

Don't let the new site get slower

Big videos, heavy scripts and unoptimized photos can undo your SEO work on their own. Test your key templates against the Core Web Vitals measures before launch, not after. The free website check gives a quick read on speed, SEO basics and security.

Staging, launch day and the first 48 hours

While the new site is still in staging

Build and test the new site on a private staging site. Keep it hidden from search engines and from the public so Google doesn't index a half-finished duplicate. Password protection is the safest method, since a simple "noindex" setting is easy to forget.

Then, the pre-launch checks:

1. Crawl the staging site and compare it to your inventory. Every page you meant to keep should exist.
2. Test the full redirect map and fix anything that lands in the wrong place or on an error.
3. Review the technical files: robots.txt, the XML sitemap and canonical tags.
4. Check forms, phone links and tracking. A migration that keeps rankings but breaks the contact form has still cost you leads.
5. Confirm analytics and conversion tracking work, so before and after can be compared.
6. Make sure Search Console is ready, with the right properties verified, including every version of your address (with and without www, http and https). Keep the verification method in the new site's code, or access can be lost at the worst moment.
7. Confirm the server can handle extra crawling, which Google notes often rises after a move.

Pick the day carefully

Launch in your quietest period, not your busiest, and never on a Friday afternoon, when a problem can sit unnoticed all weekend. Make sure someone is free to watch things for a day or two.

The launch-day checklist

Once the new site goes live, work down this list right away:

• Remove any block on search engines. Check that the "discourage search engines" setting, noindex tags and a restrictive robots.txt are all off. This is the single most common launch-day mistake, and it's a catastrophic one. Check it first, then check it again.
• Switch the redirects on and test them live. Spot-check your top 20 pages by hand, and run the full list through a script.
• Submit the new sitemap in Search Console, and remove the old sitemap if the address changed.
• Inspect key pages with the URL Inspection tool.
• Test the forms and phone links one more time, in production, with a real submission.

If your domain is changing, there's one extra step: Search Console has a Change of Address tool for moves to a new domain or subdomain. Per Google's guidance, you don't need it for HTTP to HTTPS, for www changes or for moves within the same domain.

Update the places outside your site

Your Google Business Profile, social profiles, email signatures, directory listings and ad campaigns all carry old addresses. Update the important ones. Redirects cover the gap, but direct links are cleaner and faster.

The next 90 days: what normal looks like and what doesn't

Even a well-run migration usually causes some movement. Knowing what's expected keeps you from panicking or, worse, tinkering.

Expect some wobble

Google says rankings can shift temporarily during a move. For a medium-sized site, it can take a few weeks or more for new URLs to replace old ones in the results, and bigger sites take longer. Google also has to revisit every old and new URL at least once, and there is no published schedule for when it will.

In practice, that means:

• Traffic to the old addresses falls while traffic to the new ones rises. If you're looking at page-level reports, this will look like chaos for a while.
• Some pages dip, then recover. Some come back a bit higher, especially if you improved them.
• Search Console may show warnings that your old sitemap contains redirected URLs. Google lists that as expected.

What you want is a modest dip that then recovers.

What's a red flag

Some patterns mean something is actually broken, and the earlier you catch them the cheaper they are to fix:

• Whole sections vanish from Google's index and stay gone. Check for stray noindex tags or blocked folders.
• Search Console shows a spike in "not found" errors for URLs you meant to redirect. Your map has gaps.
• Leads fall but traffic doesn't. The forms, phone numbers or tracking broke.
• Your most valuable pages drop out and stay out. Compare their titles, headings and content with the old versions.

What to check, and when

A simple rhythm works:

1. Day 1 and 2: Re-check that the site is indexable, redirects work and forms submit. Watch for server errors.
2. Week 1: Open the Search Console reports for sitemaps, indexing and errors. Fix every broken redirect you find.
3. Weeks 2 to 4: Compare organic traffic and lead counts with your pre-launch baseline. Look at the top 20 pages individually.
4. Months 2 and 3: Review rankings for your most important searches and confirm the new URLs have replaced the old ones in the results.

Then keep the redirects. Google recommends leaving them in place for at least a year, and leaving them indefinitely is also fine. They cost almost nothing to keep, and old links on other sites don't expire just because your launch checklist did.

One more piece of discipline: resist changing ten more things during recovery. If you rewrite titles and restructure the menu while Google is still re-learning the site, you won't know which change helped or hurt. Let it settle, then improve one thing at a time.

Who should do this, and when it's not worth the worry

If your site gets little organic traffic, a migration is far less risky because there's little to lose. If search drives real calls and revenue, treat the SEO plan as a core part of the project, and ask any agency how they handle redirects and pages you already rank for. A vague answer is a warning sign.

You can run the inventory and the keep-or-cut decisions yourself. The redirect build and technical launch checks are where an experienced developer earns the fee. That's how we run our website redesign work: inventory and redirect map come before the design, not after.

Protect the equity you've built

A website that's been around a few years has earned something: links from other sites, a history with Google, pages people trust. A redesign doesn't have to spend any of that. It just has to move it carefully.

So here's the short version to take with you. Count every URL before you start. Decide what stays. Map every old address to a new one with a permanent redirect. Carry the titles, headings and content that already work. Check the launch like it's a flight, with a list. Then watch calmly, and be patient with Google.

If you're planning a redesign and want someone to pressure-test the plan before it costs you traffic, bring it to a discovery call. We'll tell you plainly where we think the risk is, even if the answer is that you're in better shape than you thought.