Website migration without losing traffic

A website migration without losing traffic comes down to one rule: every page that Google and customers know today must lead somewhere sensible tomorrow, with content at least as good as before. Most traffic drops after a redesign happen because old page addresses vanished without redirects, important content was cut to make the design look cleaner, or the new site launched with a "don't index" setting still switched on.

A well-planned move often holds its traffic, sometimes with a short dip of a few weeks. A careless one can lose a large share of organic visits for months. The difference is a few days of preparation. Here is the process I follow when I rebuild a site and keep its domain.

What counts as a migration

Any of these changes can affect rankings:

• Redesign on the same domain, with new page addresses or a new structure.
• Platform change, for example from a page builder or an old WordPress theme to a hand-coded site or a custom CMS.
• Domain change, such as moving from a .com to a .ca, or rebranding to a new name.
• Protocol or subdomain change, like http to https or www to non-www.
• Merging sites, such as combining two location sites into one.

The more of these you do at once, the higher the risk. When possible, change one thing at a time. If you must rebrand and redesign together, plan for a bigger dip.

Before: record what you have

You can't protect what you haven't measured. Before anyone touches the design:

1. Export all current URLs. From the sitemap, a crawl of the site and the Pages report in Google Search Console. Include PDFs and images that get traffic.
2. Find the pages that matter. In Search Console's Performance report, sort pages by clicks for the last 12 months. In most small business sites, a small group of pages brings most of the organic traffic.
3. Note the searches each page ranks for. Again from Search Console. These are the pages whose content must survive.
4. List external links. Search Console's Links report shows which of your pages other sites link to. Those pages need redirects even if they get little traffic.
5. Save a benchmark. Organic clicks, enquiries from organic search, and positions for your main keywords. You'll compare against this after launch.

The redirect map

This is the heart of the job: a spreadsheet with every old URL in one column and its new destination in the other.

Rules:

• Use 301 (permanent) redirects, one hop from old to new. Avoid chains like A to B to C.
• Redirect to the closest matching page, not everything to the homepage. Mass homepage redirects are treated by Google much like missing pages.
• Pages with no equivalent and no traffic or links can return a 404. That's fine.
• Keep the map after launch. You'll need it when something odd shows up in Search Console months later.

Content parity

A new design often looks cleaner because text was removed. Sometimes that's an improvement; often it deletes the very paragraphs that ranked. For every important page, check that the new version keeps the main topic, the key information, the headings that matched searches, and the internal links. Improve it if you can, but don't shrink a 900-word service page that ranks to a 150-word one with a big photo.

Also carry over title tags, meta descriptions, image alt text and structured data, or improve them deliberately.

Launch day checklist

• Remove the "noindex" or password protection used on the staging site.
• Check robots.txt doesn't block the new site.
• Test a sample of redirects from the map, including the top 20 pages.
• Submit the new XML sitemap in Search Console.
• For a domain change, verify the new domain in Search Console and use the Change of Address tool.
• Update the website link in your Google Business Profile, Apple Business Connect, Bing Places and main directories.
• Check analytics and conversion tracking fire on the new site: forms, calls, bookings. See the GA4 guide for small businesses.
• Make sure the canonical tags point to the new URLs, not the old or the staging domain.

The first eight weeks

Expect some movement. Google needs time to recrawl and process the redirects.

• Week 1: check Search Console daily for spikes in 404 errors or "excluded" pages. Fix missing redirects as you find them.
• Weeks 2–4: compare clicks and positions for your top pages against the benchmark. A small dip is normal.
• Weeks 4–8: most well-handled migrations settle back by now. If key pages are still down, compare old and new content side by side, and check that internal links point to new URLs directly rather than through redirects.

If a page that used to bring enquiries is still missing after two months, look at it with fresh eyes: was a section cut, a heading changed, a link from the menu removed? Small changes add up.

Keep the old domain registered and its redirects running for at least a year after a domain change, ideally permanently. Links from other sites will keep pointing to old addresses for a long time.

Mistakes I see most often

• The designer launched the new site and nobody created redirects.
• Blog posts were "cleaned up" and deleted, including the three that brought the most visitors.
• The old domain was allowed to expire after a rebrand.
• Tracking broke at launch, so nobody noticed enquiries dropping.
• A domain change, redesign, new structure and new content all went live on the same day.

How I handle it

I don't patch existing sites. When a business needs a new one, I build it from scratch, keep the domain and move the content that matters, with the redirect map and checks above built into the project. If you're working with another designer and want someone to own the SEO side of the move, that's my SEO migration service. And if the move is mostly technical, such as changing hosts or platforms, see website migration.