Website Relaunch Without Losing Google Rankings: The Migration Playbook

Most traffic lost in a relaunch is lost in the planning, not on launch day. Here is the step-by-step playbook we use to redesign or replatform a site and keep the rankings, leads and AI citations it has earned.

By · 18.11.2026

Website relaunch and SEO migration

A new website is supposed to bring more business. Too often, the first thing it brings is a phone call that starts with: "Our enquiries dropped by half since the relaunch. What happened?"

What happened is almost never the design. It is the invisible layer underneath: hundreds of old URLs that now return a 404, page titles that were lost when content moved to the new CMS, a staging noindex tag that went live, or a service page that ranked for your most valuable keyword and simply was not rebuilt. Google does not see your new hero animation. It sees addresses, content and signals, and it compares them with what was there before.

The good news: a relaunch that is planned properly usually shows a short, shallow dip and then grows past the old numbers. This article is the playbook we follow at BlackCard when we build or rebuild a website, written so you can judge any relaunch plan, whether we run it or not.

Why relaunches lose traffic in the first place

Search engines have spent years building a picture of your site: which URL answers which question, which pages other sites link to, how fast pages load and how users behave on them. A relaunch can reset parts of that picture overnight. The common causes, roughly in order of how often we find them when we are called in to repair a relaunch:

  1. Missing or wrong redirects. Old URLs return 404, or every old URL is redirected to the homepage. Google treats mass redirects to an unrelated page much like a 404 (a "soft 404"), so the ranking value of the old page is lost either way.
  2. Content that quietly disappeared. During the redesign, someone decided the old FAQ, the long service descriptions or the "boring" blog posts did not fit the new look. Those pages were often the ones ranking for long-tail searches that bring buyers.
  3. Lost on-page signals. Title tags, meta descriptions, headings, alt text and structured data that lived in the old CMS were not migrated. The new pages are prettier but say less.
  4. Indexing blockers. A noindex meta tag or a Disallow: / rule from the staging environment reaches production. This one can wipe out visibility in days.
  5. Performance regressions. The new site ships heavy scripts, unoptimised images and a slower server. Core Web Vitals get worse, and so does the experience for real visitors.
  6. Broken internal linking. Navigation is simplified, important pages fall three or four clicks deep, and internal links in old content still point to dead addresses.
  7. Tracking gaps. Analytics is installed twice or not at all, so nobody can tell whether traffic actually dropped or whether the measurement did.

Notice what is missing from that list: the new design itself. A good redesign is an opportunity. The risk is in the migration.

How big a dip is normal?

Practitioners broadly agree on a few thresholds, and they match what we see in our own projects:

  • A temporary dip of roughly 10–30% in organic traffic during the first two to six weeks is normal, especially if URLs changed. Google needs time to recrawl, process redirects and re-evaluate pages.
  • A drop of 30–50% that does not recover within a few weeks means something is wrong and needs investigation.
  • A drop of 50% or more usually points to a structural mistake such as missing redirects, blocked indexing or deleted content. Without a fix, severe cases can take a year or longer to recover, and some never fully do.

The size of the dip is largely decided before launch. A relaunch that keeps the same URLs and content structure often shows almost no dip at all. A relaunch that changes domain, platform, URL structure and content at the same time stacks four risks on top of each other.

Decide what kind of migration you are actually doing

"Relaunch" covers very different projects, and each carries a different risk profile:

  • Design only (new look, same URLs, same content): low risk.
  • Platform change (WordPress to Next.js, Wix to a custom build): medium risk.
  • URL structure change (/services.php?id=4 to /development): medium to high risk.
  • Content restructure (merging 40 thin pages into 12 strong ones): medium to high risk.
  • Domain change (oldname.com to newname.com): high risk.
  • All of the above at once (rebrand plus replatform plus new domain): the highest risk.

You do not need to avoid the risky changes. Sometimes a domain change or a new URL structure is the right business decision, for example after a rebrand. But you should make each change deliberately, know which risk you are taking on and budget for the work that controls it. If you can stage the changes (for example: replatform first with identical URLs, restructure three months later), the risk drops sharply.

Phase 1: Benchmark everything before you touch anything

You cannot protect what you have not measured. At least four weeks before launch, capture:

  • A full crawl of the current site. Every URL, status code, title, meta description, H1, canonical tag and word count. Tools like Screaming Frog or Sitebulb do this in minutes for most small and mid-sized sites.
  • Search Console performance data. Export the last 16 months of queries and pages (the maximum Google Search Console stores). This shows which URLs bring clicks and for which searches.
  • Analytics landing pages. Which pages start sessions, and which of those sessions turn into enquiries, sign-ups or sales.
  • Backlinks. Which URLs other websites link to. A page with few visits but strong external links still carries authority that must be redirected.
  • Rank tracking for your money keywords. Ten to fifty searches that actually bring customers. Track them daily from now until three months after launch.
  • Core Web Vitals and load times for your top templates, so you can prove the new site is not slower.

Then sort every URL into a simple priority list. In a typical B2B site of 300 URLs, we usually find that around 20–40 pages generate the vast majority of organic leads. Those pages get the most care.

Phase 2: Build the URL map — the most important document in the project

The URL map is a spreadsheet with one row per old URL and one column for its new destination. It sounds dull. It decides whether the relaunch keeps its traffic.

Rules we apply to every map:

  1. Every old URL that has traffic, links or rankings gets a destination. No exceptions, including PDFs, images that rank in image search and old campaign landing pages.
  2. Map to the closest equivalent, not the homepage. An old page about "custom CRM development" maps to the new page about custom business software, not to /. If there is genuinely no equivalent, consider keeping or rebuilding the page rather than throwing its value away.
  3. One hop only. Old URL to final URL, directly. If the old site already had redirects, update them so they skip the intermediate step. Chains of three or four redirects waste crawl budget and dilute signals.
  4. Use permanent redirects. 301 or 308 tell search engines the move is permanent. 302 and 307 are temporary and send the wrong signal for a relaunch.
  5. Decide deliberately about pages you remove. If a page has no traffic, no links and no business value, a clean 410 (gone) or 404 is fine. If it has any of the three, redirect it.
  6. Normalise variations. Trailing slashes, uppercase letters, www versus non-www, http versus https. Choose one form and redirect the others.

For a 300-URL site, a well-built map takes one to three days. For an online shop with 20,000 product and category URLs, it takes pattern-based rules (for example, every /product/<id> becomes /shop/<slug>) plus manual work for the top sellers.

Phase 3: Migrate the content and the signals, not just the words

When content moves to a new design, the risk is that it gets shortened, rewritten for aesthetics or split into tabs and sliders that hide it. Before you approve the new templates, check that each important page keeps:

  • The same search intent and substance. If the old service page answered pricing, process and FAQs, the new one must too. Cutting 1,200 words to 300 because "nobody reads" is a common way to lose a ranking.
  • Title tags and meta descriptions. Migrate them explicitly, then improve them. Never let the CMS fall back to a generic "Company Name | Home" title on every page.
  • Heading structure. One clear H1, with H2s that reflect the questions people search for.
  • Structured data. Organization, Article, Product, FAQPage and Breadcrumb markup help search engines and AI assistants understand the page. A relaunch is a good moment to add what was missing.
  • Image alt text and file names, especially for sites that get traffic from image search.
  • Canonical tags that point to the new URL itself, not to the staging domain and not to the old URL.
  • Internal links. Update links inside your content to point directly to new URLs instead of relying on redirects. Keep your most valuable pages within two clicks of the homepage.

This is also where a relaunch can gain ground. Merging five thin, overlapping blog posts into one comprehensive article, adding a proper FAQ section to service pages or improving the structure and usability of key pages can lift rankings above the old baseline once Google has processed the move.

Phase 4: Get the technical foundations right on staging

Test everything on a staging environment that mirrors production, but protect that staging site with a password or IP restriction rather than only a noindex tag. That way there is no noindex tag that could accidentally ship to production.

Our pre-launch technical checklist:

  • Crawl the staging site and compare it with the crawl of the live site. Every important old page should have a counterpart.
  • Test the redirect map by running all old URLs against staging and checking that each returns a single 301 to the expected destination with a 200 at the end.
  • Check rendering. If the new site is built with a JavaScript framework, make sure important content is in the server-rendered HTML. Frameworks like Next.js make this straightforward with server rendering or static generation; client-only rendering makes indexing slower and less reliable, and many AI crawlers do not execute JavaScript at all.
  • Measure performance. Aim for a Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1 on mobile for your key templates.
  • Prepare the XML sitemap with only canonical, indexable, 200-status URLs.
  • Prepare robots.txt for production, and make sure it does not block CSS, JavaScript or important sections. Decide consciously which AI crawlers you allow; blocking all of them also removes you from the answers that AI assistants give your future customers.
  • Check hreflang if you run multiple languages or countries, because language versions are a common source of migration bugs.
  • Verify analytics, conversion tracking and consent so you can compare before and after with confidence.

Phase 5: Launch day

Pick a launch window with low traffic and no major campaign running, and make sure the developer who built the redirects is available for the following 48 hours. Then:

  1. Deploy the new site and activate the redirects at the same moment.
  2. Remove any staging password and confirm that no noindex tag or blocking robots.txt rule is live.
  3. Crawl the old URL list against production. Fix any 404s or chains immediately.
  4. Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools. Keep a sitemap of the old URLs submitted for a few weeks as well, so search engines recrawl them sooner and discover the redirects faster.
  5. If you changed domain, use Google's Change of Address tool in Search Console and keep both domains verified.
  6. Request indexing for your ten most important pages through URL Inspection.
  7. Test the conversion paths yourself: contact forms, booking links, checkout, confirmation emails. A relaunch that keeps its rankings but breaks the form still loses the business.
  8. Update the links you control: Google Business Profile, social profiles, email signatures, directory listings and paid campaigns.

Phase 6: Monitor for at least three months

The first weeks after launch decide whether a dip stays temporary. Our monitoring rhythm:

  • Daily for the first two weeks: Search Console coverage and crawl errors, 404 logs, rankings for money keywords, conversion numbers.
  • Weekly until month three: Organic clicks by page compared with the same pages before launch, indexed page count, Core Web Vitals field data, server logs for crawler activity.
  • At month three: A formal before-and-after report. Which pages gained, which lost, and why.

When a specific page loses rankings, check the obvious first: does the old URL redirect correctly, is the new page indexed, did its content or title change, and did internal links to it disappear? Nine times out of ten the cause is one of those four.

Keep the redirects in place for as long as possible. Google's guidance is at least a year; in practice we keep them indefinitely, because old links on other websites, bookmarks and printed material keep sending people to the old addresses for years.

A realistic relaunch timeline

For a typical company website with 100–500 pages, a relaunch that protects rankings looks like this:

  • Weeks 1–2: benchmark crawl, Search Console and analytics exports, keyword priorities.
  • Weeks 2–4: information architecture, URL map, content inventory and content decisions.
  • Weeks 3–8: design and development, content migration, structured data.
  • Weeks 7–9: staging QA — crawl comparison, redirect testing, performance, tracking.
  • Week 9: launch and 48-hour hypercare.
  • Weeks 10–21: monitoring, fixes and a three-month report.

SEO work does not need to make a relaunch slower. It needs to start on day one instead of the week before launch, which is when most teams remember it.

What the migration work costs compared with what it protects

Here is the calculation we encourage every client to run. Suppose your site brings 2,000 organic visitors a month and 1.5% of them become qualified enquiries. That is 30 enquiries a month. If you close one in five and an average customer is worth €8,000, organic search is worth around €48,000 in new business per month.

A relaunch that loses 40% of that traffic for six months costs roughly 72 enquiries, or around €115,000 in potential revenue. The migration work described in this article typically adds a few days to a week of specialist effort to the project. It is one of the highest-return line items in any website budget, and the one that is most often cut.

Relaunching in the age of AI search

In 2026, rankings are not the only thing at stake. Google's AI Overviews, ChatGPT search, Perplexity and other assistants increasingly answer questions directly and cite a small number of sources. Those citations depend on many of the same signals: crawlable HTML, clear structure, consistent facts and pages that have been trusted for a long time.

A relaunch should therefore also:

  • Keep server-rendered, readable content, because many AI crawlers fetch raw HTML.
  • Preserve the pages that are already cited. Check which of your pages appear in AI answers for your core topics before you change them.
  • Make facts easy to extract: prices or price ranges, processes, locations, service areas and FAQs in plain text rather than inside images or carousels.
  • Keep author, company and contact information consistent across the site, so assistants can attribute your expertise correctly.

Signs your relaunch plan needs a second opinion

If any of these are true, pause before launch:

  • Nobody can show you a URL map.
  • The plan says "we will set up redirects after launch".
  • The new site has noticeably fewer pages than the old one and no one has checked what those pages ranked for.
  • Search Console access is not part of the project.
  • Performance has not been measured on a real mobile device.
  • Launch is scheduled for the day before a holiday or a major campaign.

FAQ

Will a website redesign hurt my SEO? A redesign that keeps URLs, content and technical signals intact usually causes little or no lasting impact, and often improves rankings through better speed, structure and usability. Losses come from migration mistakes: missing redirects, deleted content, lost metadata and indexing blockers. With a proper URL map and pre-launch testing, most of that risk is controlled.

How long does it take to recover rankings after a website migration? For a well-executed migration, expect a temporary fluctuation of a few weeks while Google recrawls and processes redirects, with traffic usually back at or above baseline within one to three months. Migrations with structural mistakes can take six to twelve months or longer to recover, which is why prevention is far cheaper than repair.

Should I use 301 or 302 redirects for a relaunch? Use permanent redirects: 301 or 308. Google treats both as permanent moves. Temporary redirects (302 or 307) signal that the old URL will come back, which is not what a relaunch means.

How long should I keep redirects after a migration? Google recommends keeping redirects for at least one year. We recommend keeping them indefinitely, because external links, bookmarks and old marketing material continue to send visitors to the old URLs for years, and redirects cost almost nothing to maintain.

Can I redirect all old pages to the homepage? No. Redirecting many unrelated URLs to the homepage is treated much like a 404 (a soft 404), so the value of those old pages is lost. Each old URL should redirect to the most relevant new page, and genuinely obsolete pages with no traffic or links can return a 410 or 404.

Is it safe to change my domain name during a relaunch? It is possible, but it is the highest-risk type of migration. If you can, separate the domain change from the redesign by a few months. If both must happen at once, use a complete URL map, keep both domains verified in Search Console, use the Change of Address tool and monitor closely for at least three months.

Do I need an SEO specialist for a website relaunch? For a small brochure site with identical URLs, a careful developer can handle it. As soon as URLs, platform, content structure or domain change, or organic search brings a meaningful share of your leads, you want someone who has run migrations before. The cost of that expertise is small compared with the revenue a failed migration can lose.

Does moving to a new platform like Next.js help SEO? A modern platform can improve speed, rendering and structure, which helps both search engines and AI crawlers. But the platform alone does not protect rankings; the migration process does. A fast new site with missing redirects will still lose traffic.

Relaunch with a team that protects what you have built

Your current website may look dated, but it has earned something valuable: years of rankings, links and trust that bring in customers every month. A relaunch should keep all of that and add a better experience on top.

That is how we run website projects at BlackCard. We benchmark before we design, build the URL map alongside the information architecture, develop on modern, fast, server-rendered web technology, and stay with you through the three months after launch until the numbers prove the move worked. If you are also rethinking your positioning, we bring branding and UI/UX into the same plan, so you do not have to coordinate three agencies through one high-stakes launch. If you are unsure whether to hire an agency at all, our comparison of agency vs. freelancer vs. in-house lays out the trade-offs.

Planning a relaunch, or already seeing a drop after one? Book a free call and we will review your current site, your relaunch plan and the pages that matter most, and tell you exactly where the risks are.

Satisfaction is what we strive

Don't hear it from us

  • Martin Peters
    "The BlackCard team was very transparent throughout the entire project, so that we were always up to date on the budget and were able to quickly clear costly issues on our side."

    Martin Peters

    DropFriends
  • Hassan Elammar
    "After working together we were able to solve tracking issues for some of our clients and also implemented fixes on their websites and online stores. This lead to conversion increases."

    Hassan Elammar

    growthartig
  • Marco Pöppel
    "Working with Osamah and Marvin was always thought-provoking and helped us figure out our future strategy much better."

    Marco Pöppel

    CryptoZquad

Your success story could be next

Get a free IT assessment now

The satisfaction and growth of our clients is our utmost priority, and we never end a partnership without making sure our clients are happy.

  • Homelike
  • Growthartig
  • NeuesHandeln
  • Milecrew
  • Avenga
  • Foodist
  • BI
  • Novoferm
  • Homelike
  • Growthartig
  • NeuesHandeln
  • Milecrew
  • Avenga
  • Foodist
  • BI
  • Novoferm