Migrating your website without losing search traffic⁠

A redesign is a good moment to fix structure, content and speed. It is also the moment when many companies lose a large part of their search traffic, sometimes for months. The cause is rarely one big mistake. It is usually a set of small details that nobody owned.

Here is the checklist we work through on every migration, whether the site is moving to a new platform, a new domain or just a new structure.

Why migrations lose traffic

Search engines have spent years learning what your pages are about and how much to trust them. A migration changes addresses, content, internal links and sometimes the domain itself. If those changes are not mapped carefully, search engines have to relearn everything, and some pages simply disappear.

The most common causes we see:

• Missing redirects. Old URLs return errors instead of pointing to their new equivalents.
• Redirects to the homepage. Hundreds of old pages sent to one place, which search engines treat almost like an error.
• Lost content. Pages that ranked well are merged, shortened or rewritten without checking why they ranked.
• Changed metadata. Titles and descriptions replaced with generic ones.
• Staging settings on the live site. A “do not index” setting copied from the test environment.

Before you build

1. Export every URL. From the old site, the sitemap, analytics and search console. Include PDFs, old campaign pages and anything that has backlinks.
2. Find the pages that matter. Sort by organic traffic, leads and backlinks. These pages need special care and a named owner.
3. Decide what happens to each URL. Keep it, merge it into another page, or retire it on purpose. Write the decision down in a redirect map.
4. Benchmark. Save current rankings, traffic and conversions for your key pages, so you can compare after launch.

While you build

• Keep what works. Page titles, headings and content that rank well should not be rewritten without a clear reason.
• Plan redirects one to one. Every old URL that changes gets a permanent redirect to its closest new equivalent.
• Avoid redirect chains. Old URL to new URL in one step, not through older redirects left from previous redesigns.
• Match metadata. Titles, descriptions and social images for every important page, reviewed before launch.
• Keep internal links clean. Links inside the new site should point directly to new URLs, not rely on redirects.
• Protect speed. A new design with heavy images and scripts can undo the gains of a better structure.

On launch day

• Put redirects live at the same moment as the new site.
• Check that the live site can be indexed and the staging site cannot.
• Submit the new sitemap in search console.
• Test your top pages, forms, tracking and consent on the live domain, not only on staging.
• Crawl the old URL list and confirm that every one of them lands where it should.

After launch

Watch search console closely for the first weeks: crawl errors, pages dropping out of the index, unexpected spikes in not-found errors. Fix broken links as they appear.

Compare your key pages against the benchmark after two, four and eight weeks. A small dip right after launch is normal while search engines process the changes. A dip that does not recover means something was missed, and the redirect map is the first place to look.

The best migration is the one your visitors do not notice.

Who should own it

Migrations fail in the gaps between roles. Design assumes development handles redirects. Development assumes marketing has the URL list. Marketing assumes the agency has it covered.

Give the migration one owner with a checklist and the authority to delay launch if something important is not ready. That single decision protects more traffic than any tool.