You have spent months on the new website. New design, sharper messaging, a faster framework, and a CMS your team actually enjoys using. It goes live - and three weeks later organic traffic is down 35 percent and the inbound leads have gone quiet. This is the most common way B2B companies lose their hard-won search visibility, and almost all of it is preventable.
A website relaunch is not just a design project. To Google, it is a migration: URLs change, internal links shift, and the signals that ranked your pages get reshuffled overnight. Done with an SEO plan, a relaunch is roughly neutral and can even lift rankings. Done without one, it quietly erases years of progress. For the wider strategy your relaunch needs to protect, see our complete B2B SEO guide. This checklist covers the steps that keep your rankings intact through the move.
A widely cited study of 892 domain migrations found the average site took roughly 523 days to recover its pre-migration organic traffic, and 17% never recovered even after 1,000 days. (Source: Digital Applied, 2026)
Why a Relaunch Puts Your Rankings at Risk
Search engines rank specific URLs, not "your website" in the abstract. When you relaunch, those URLs often change: a page that lived at /solutions/reporting becomes /platform/analytics, the old blog structure gets flattened, and dozens of pages get merged or quietly dropped. Every one of those changes breaks the link between an existing ranking and the content behind it. If Google cannot follow the path from the old URL to the new one, the ranking has nothing to point to.
The damage is rarely a clean dip. Most website migrations quietly lose between 20% and 40% of their SEO value, and the worst cases lose far more. The reason it hurts so much in B2B is the sales cycle: your highest-intent pages - pricing, comparison, and bottom-of-funnel solution pages - are usually the ones that get restructured most aggressively in a redesign. Lose their rankings and you lose the traffic that was actually converting.
The good news is that a clean relaunch is close to neutral. The traffic loss is not caused by the new design or the new platform. It is caused by missing redirects, removed pages, and technical mistakes at go-live. Fix those, and the move becomes an upgrade rather than a setback.
Before You Relaunch: Inventory and Benchmark
You cannot protect what you have not measured. Before a single page goes live, build a complete picture of the current site so you have something to redirect to and something to compare against.
Start with a full crawl using Screaming Frog or Ahrefs Site Audit and export every indexed URL. Then pull your Search Console data: the top pages by clicks and impressions over the last 12 months, and the queries that drive them. Sort that list by traffic value. The pages at the top are your priority - they are the ones that must survive the move with a one-to-one redirect to an equivalent page.
Record a baseline while you are at it: current organic sessions, keyword rankings for your money terms, and the number of indexed pages. After launch, this baseline is the only way to tell a normal re-indexing wobble from a real problem. It is also worth running a full SEO audit before the relaunch, so you fix existing issues rather than carrying them into the new site. Do not skip pages that get few visits but earn backlinks - a forgotten resource page can hold a large share of your domain authority.
Build a 1:1 Redirect Map
The redirect map is the single most important deliverable of any relaunch. Every old URL needs a defined destination on the new site, mapped before launch and tested after. This is where most migrations succeed or fail.
Use permanent 301 redirects, not temporary ones. A 301 redirect tells search engines that a resource has permanently moved and that its existing SEO authority should transfer to the new URL; pages with no equivalent should serve a 410 status code so search engines know they are gone for good. Map each old URL directly to its closest match. Where a page is being consolidated, point it to the page that replaces it, not to the homepage - bulk redirects to the homepage are treated as soft 404s and pass almost no value.
Two rules prevent most redirect disasters. First, avoid chains: if A moves to B and later B moves to C, update the original rule so A points straight to C. Long chains leak authority and slow crawling. Second, keep your URL structure wherever you reasonably can. Every URL you do not change is one you do not have to redirect, monitor, or risk.
Launch Day and the First 30 Days
The most catastrophic relaunch mistake is also the simplest: shipping the staging site's "noindex" tag or robots block to production. A staging environment is usually closed to search engines on purpose. If that block survives go-live, you are telling Google to remove your entire site. Make "remove the noindex and robots disallow" the first item on your launch-day checklist, and confirm it on the live domain, not just in the codebase.
Immediately after launch, submit the new XML sitemap in Search Console and keep the old sitemap available for a few weeks so Google rediscovers the old URLs and follows your redirects. Spot-check the top 50 pages by traffic to confirm each redirect resolves in one hop to a live, indexable page. Then watch Search Console daily for two to four weeks. A re-indexing dip of 5 to 10 percent for the first couple of weeks is normal and recovers on its own. A sharp, sustained drop is a signal to investigate redirects and crawl errors right away.
Once the dust settles, run a complete post-launch review covering crawlability, indexation, and Core Web Vitals - the same ground as a technical SEO check. Treat the first month as active monitoring, not a finish line.
Conclusion
A website relaunch is a migration wearing a design brief. The new look is rarely what costs you traffic - missing redirects, dropped pages, and a stray noindex are. Inventory the old site, map every URL to a destination with clean 301s, remove the staging block at go-live, and monitor Search Console closely for the first month. Do that, and your relaunch protects your rankings instead of resetting them. For the full picture beyond the move, read our complete B2B SEO guide, or talk to us about managed B2B SEO if you want a second set of eyes on the migration plan.
Frequently Asked Questions
Will my rankings drop after a website relaunch?
A small, temporary dip is normal. When redirects are clean and the technical setup is sound, expect a re-indexing wobble of roughly 5 to 10 percent for about two weeks, followed by recovery. A large, sustained drop is not normal and almost always points to a redirect gap, a removed page, or a noindex tag that survived go-live.
How long does it take to recover traffic after a relaunch?
A well-executed relaunch recovers within a few weeks. A botched one can take far longer: a study of 892 domain migrations put the average recovery at around 523 days, with a meaningful share of sites never fully recovering. The difference is almost entirely down to redirect quality and technical execution, not time.
Do I need to keep my old URLs?
Keep your URL structure wherever you reasonably can - every URL you do not change is one you do not have to redirect or monitor. When URLs must change, redirect each old URL one-to-one with a 301 to its closest equivalent on the new site. Avoid bulk redirects to the homepage, which search engines treat as soft 404s.