Moving to a new website without losing search traffic

A redesign is one of the few times a company can lose a large share of its search traffic in a single afternoon. It usually is not the design that causes it. It is the quiet stuff underneath: URLs that change, pages that disappear, titles that get rewritten, and redirects that nobody planned.

The good news is that this risk is very manageable. A careful migration follows a known set of steps, and most of the work happens before launch day.

Why traffic drops after a redesign

Search engines have spent years learning what each of your pages is about and how much to trust it. That knowledge is attached to specific URLs. When a URL changes without a redirect, the old address returns an error, and the new one starts with no history.

Multiply that across dozens or hundreds of pages, add a few rewritten titles and some deleted content, and it is easy to see how a launch can undo a lot of earned visibility. Recovery is possible, but it is slower and more stressful than doing it right the first time.

Start with a complete URL inventory

Before anything else, list every URL your current site has. Not just the ones in the navigation. Pull from several sources, because each one misses something:

• Your XML sitemap.
• A crawl of the live site.
• Search Console's indexed pages and performance reports.
• Your analytics, sorted by landing page.
• Pages that other websites link to.
• Old campaign landing pages, PDFs, and image URLs that still get visits.

Combine these into one spreadsheet. For each URL, note whether it gets meaningful traffic, whether other sites link to it, and what it ranks for. This tells you which pages matter most and deserve the most care.

Map one-to-one 301 redirects

Every old URL that is changing needs a permanent (301) redirect to the most relevant new URL. One to one is the goal: the old pricing page goes to the new pricing page, not to the homepage.

Some practical rules I follow:

• Redirect to the closest equivalent, not the nearest convenient page.
• Avoid chains. An old URL should go straight to its final destination, not through two or three hops.
• If content is genuinely retired with no replacement, it is acceptable for that URL to return a proper "gone" or "not found" response. Mass-redirecting everything to the homepage tends to be treated as an error anyway.
• Keep URLs the same wherever you can. The safest redirect is the one you do not need.

A redirect map is not a technical afterthought. It is the document that decides whether your search history survives the move.

Preserve what is already working

A redesign is a good moment to improve content, but be deliberate about pages that already perform well.

Keep page titles and meta descriptions on high-traffic pages unless you have a clear reason to change them. If you do rewrite them, keep the core topic and wording people search for. Keep headings and body content substantially similar on pages that rank, and do not merge or split them without thinking through where their traffic will go.

Check structured data, canonical tags, image alt text, and language tags too. These are easy to lose when templates are rebuilt from scratch. If you run your site in more than one language, make sure language versions stay correctly linked to each other.

Fix internal links and the sitemap

Redirects catch outside visitors and old bookmarks, but your own site should link directly to the new URLs. Update navigation, footers, in-content links, and any buttons that point to old paths. Internal links that go through redirects work, but they are slower and messier than they need to be.

Generate a new XML sitemap containing only the live, canonical URLs you want indexed. Remove the old sitemap once the redirects are in place, and submit the new one in Search Console.

Launch day and the weeks after

The launch itself should be boring. Before switching over, test the redirect map on a staging copy so you know each old URL lands where it should. On the day:

1. Deploy the new site with redirects active.
2. Spot-check your most important old URLs by hand.
3. Run a crawl of the old URL list and confirm each returns a single 301 to the right page.
4. Confirm the new site is not blocked by robots.txt or noindex tags left over from staging.
5. Submit the new sitemap in Search Console.

Then keep watching. In the following weeks, check Search Console for crawl errors, pages that drop out of the index, and unexpected "not found" reports. Compare landing-page traffic in your analytics against the same pages before launch. Some movement is normal while search engines recrawl; a sustained drop on a specific page usually points to a missed redirect or a changed title.

Common mistakes I see

• Leaving a staging noindex tag in place after launch.
• Redirecting everything to the homepage.
• Forgetting PDFs, images, and old campaign pages.
• Changing URL structure for style reasons alone.
• Launching on a Friday with nobody available to check.
• Deleting the old site before confirming the redirects work.

The short version

Inventory every URL, map each one to its closest new equivalent with a single 301, keep what already ranks, update internal links and the sitemap, and watch Search Console closely after launch. It is careful work, not difficult work. If you are planning a move and want this handled properly, see how search migration fits into a build.