Website relaunch without losing SEO: how to protect your rankings

Ask any SaaS marketing team about their biggest fear before a website relaunch and you'll hear the same answer: losing rankings. It's a fair fear. Organic search often drives a large share of demo requests, and a relaunch can quietly undo years of work.

But most of the horror stories have one thing in common. The SEO loss wasn't caused by the new design or the new CMS. It was caused by decisions nobody connected to SEO: URLs that changed without a redirect, copy that got trimmed to fit a new layout, a page structure that kept changing after the redirect mapping was done.

This article is about exactly that. Not the full relaunch process (that's in our website relaunch guide for SaaS), but the one question that matters most for organic growth: how do your rankings, traffic and AI visibility survive the move? It's based on relaunches and migrations for more than 120 software companies, from TYPO3, WordPress and other systems to Webflow.

Key takeaways

• The relaunch type determines the SEO risk. A platform migration with unchanged content and URLs rarely costs rankings. A domain change is the opposite.
• The best redirect is no redirect. Every URL you don't change is a risk you don't take.
• Keep what ranks. Pages that perform today get migrated 1:1 first. Optimize them after launch, when you can measure the effect.
• Order matters: approved page structure first, then redirect mapping, then schema markup.
• Stable rankings in week one mean nothing. Google reprocesses changed URLs gradually, so monitor for at least 12 weeks.

Do you really lose traffic in a relaunch?

The honest answer: it depends almost entirely on what you change. "Relaunch" covers everything from swapping the CMS to rebuilding the entire site on a new domain, and the SEO risk is completely different for each.

Platform and design relaunches rarely cost rankings, because Google sees the same content under the same URLs. In our projects, a short dip after a clean migration is usually gone within one to two weeks. Older platforms often have technical gaps, such as missing schema markup or slow templates, so many migrations even end with more visibility than before.

Full relaunches are where it gets tricky. When technology, design, content and URLs all change at once, you can't tell afterwards which change caused a drop, and you can't roll it back selectively. With bigger changes, it can take up to twelve weeks for rankings to settle.

Domain changes are in a different league. All the authority you've built sits on your domain, and moving it takes time. One large study of domain migrations found it took an average of 523 days for organic traffic to recover to its previous level, and 17% of sites hadn't recovered after 1,000 days. If you need a domain change, bring in a specialized SEO agency.

That's also why most "relaunches lose X% of traffic" statistics are misleading. They usually come from domain changes or uncontrolled full relaunches, not from clean platform migrations.

Why rankings drop after a relaunch

When rankings fall after a relaunch, the cause is almost never "Google doesn't like the new site". It's usually one of a handful of very concrete problems:

1. URLs changed without a redirect. Old URLs return a 404, and the rankings and backlinks attached to them are gone. This happens more often by accident than on purpose, for example when the new CMS handles slugs, hyphens or trailing slashes differently.
2. The old platform's redirects were forgotten. Most websites already have redirects of their own, some pointing to important pages. If they aren't carried over, those paths break too.
3. Content got lost in the new templates. Copy was shortened to fit the layout, an H1 disappeared, FAQ sections were dropped, internal links were removed. The URL is the same, but Google sees a weaker page.
4. Pages were merged or deleted too aggressively. Even pages with little traffic contribute to your topical authority. Deleting a large block of them at once can pull down related pages.
5. Two pages now compete for the same topic. A new feature page and a new use-case page target the same keyword and cannibalize each other.
6. Technical leftovers from staging. A forgotten noindex tag, a robots.txt that blocks everything, canonicals pointing to the staging domain. These are the most common mistakes right after launch.
7. Internal links point to old URLs. Every internal link now runs through a redirect, or worse, into a 404.

Notice what's missing from that list: the design itself. A new design rarely hurts rankings unless it changes one of the things above. That's good news, because every cause on this list can be prevented with planning.

Before you start: secure your SEO baseline

You can only protect what you've measured. Before anything changes, capture the current state. This baseline is what you'll compare against after launch, and it's the input for every SEO decision in the project.

First, check whether your tracking can be trusted. In many relaunches we find tracking that was never set up properly: conversions counted twice, forms not captured at all, events that stopped firing years ago. If that's the case, you have no reliable way to tell which pages matter, and no baseline to compare against later. Fix it first, for example with a clean tracking setup using GA4 and Google Tag Manager.

Then export:

• Search Console data per URL for at least twelve months: clicks, impressions, average position, top queries.
• Conversions per page, especially demo requests and trial sign-ups, with the period and conversion definition you used.
• A full crawl of the old site with every URL, status code, title, meta description, H1 and canonical.
• Backlinks per URL, including PDFs and images that other sites link to.
• All existing redirects on the old platform.
• AI visibility: how often you're named for 10 to 20 relevant prompts in ChatGPT, Perplexity and Google AI Mode.

From this data, mark your protected pages: every URL with meaningful traffic, rankings, conversions or backlinks. These pages get special treatment for the rest of the project.

One word of caution: data needs context. We've seen a content audit recommend deleting a page because it had barely any traffic in three months. It had only been live for three weeks. Have someone who knows the content review the data before decisions are made.

Redirects: plan, map and test

Redirects are the centerpiece of every SEO migration. A 301 redirect tells Google that a URL has moved permanently and that the signals of the old page should transfer to the new one. Get them wrong and no amount of good content will save the rankings.

Get the order right

The biggest redirect problems don't happen in the redirect list. They happen before it:

1. Approve the page structure first. Every page, its new URL, title and index status, in one sheet. You can use our page structure sheet as a template.
2. Then build the redirect mapping from the old crawl to the new structure.
3. Then add schema markup, which also depends on final URLs.

Changing URLs after the mapping is done means doing the work twice or creating gaps. In one project, the blog was renamed to "Resources" shortly before launch. Nobody thought about the redirects, and every old blog URL led nowhere.

The rules

• The best redirect is no redirect. Keep URLs unchanged wherever there's no strong reason to change them. Watch out for accidental changes from the new CMS: different slug logic, hyphens, trailing slashes, uppercase letters.
• Map every URL with value to the most relevant page. Not the closest category, not the homepage. Google treats mass redirects to the homepage like missing pages.
• Use 404 or 410 for pages without a real replacement. That's better than a redirect to something unrelated.
• Point directly to the final destination. No chains: every old URL should reach its target in one hop.
• Carry over the old platform's redirects and update them to point to the new final URLs.
• Use patterns where you can. Wildcard rules for entire folders, for example everything under /blog/, keep the list lean.
• Don't forget files. PDFs, images and other assets with backlinks need redirects too.
• Keep redirects permanently. Google recommends at least a year. We recommend never removing them, because external links and bookmarks point to old URLs for years.

Who decides where a page goes

For pages that stay, mapping is mechanical. For pages that are merged or removed, it's a content decision: which new page actually answers the same question? Have someone from your content team review those destinations. AI can speed up the mapping considerably, for example by matching old and new URLs or checking whether a redirect already exists, but the final mapping should always be reviewed by a person.

Temporary redirects before the switch

Sometimes you need redirects before the new site is live, for example when parts of the old site are already being consolidated. Use temporary redirects (302 or 307) for these transition phases. Browsers cache a 301 aggressively, so a 301 you set too early is hard to undo. Once the new site is live, the final redirects are always 301.

Test before and after

Test the full redirect list on staging before launch. After the switch, check the most important URLs individually and the rest in bulk with a redirect checker. Every redirect should return a 301 and land on a page with status 200.

Content parity: keep what ranks

A redirect transfers signals from the old URL to the new one. But if the new page is weaker than the old one, the rankings will follow the content, not the redirect. That's why content parity matters as much as the redirect list.

Migrate protected pages 1:1 first

This is the principle we call foundation first, and it runs through our entire website relaunch guide. Pages that rank or convert well today move into the new design with their content unchanged. New design, new tech, yes. New copy, no. Only rewrite what's weak anyway or strictly necessary for your new positioning, such as the homepage.

It sounds conservative, but it's the only way to keep effects measurable. If you change design, content and URLs at the same time and rankings drop, you'll never know which change caused it. Once the new site is stable, you optimize protected pages one by one and can attribute every change to its result.

What "the same content" means

For every protected page, check that the new version keeps:

• the same main keyword focus and the same H1,
• at least as much body copy, including FAQs and supporting sections,
• the existing title tag and meta description,
• the internal links that pointed to and from the page,
• images with alt text, tables and embedded content.

The most common trap is the template. A beautiful layout that has no room for the existing copy of a well-ranking page is an SEO risk. Test every template with the longest real content of its type, not with placeholder text.

Migration pitfalls that cost content

Content often gets lost in migration without anyone noticing. Three things to check early:

• Static instead of structured content. Glossaries, guides or knowledge articles were often built as individual static pages in the old system. Moving them into a CMS template means manual rework, and things get dropped.
• Exports that don't capture everything. Page builders like Elementor in WordPress embed elements that don't export as structured data.
• Templates built from one example page. A single example rarely contains every element that actually exists: tables, embeds, downloads, accordions, info boxes. Crawl all pages of a type to find them.

Don't delete too much

Relaunches are often seen as a chance to clean up. That's fine for individual pages. But deleting large blocks of content at once, for example 100 old blog posts, can weaken your topical authority even if each post gets little traffic on its own. Merge first where it makes sense, delete carefully, and do it after launch rather than during.

Technical SEO on staging

Everything you can check before launch, you should check before launch. On staging, go through:

• Staging is locked. Password protection or noindex, so Google doesn't index the test version and create duplicate content.
• Titles and meta descriptions are carried over for every protected page and present on every indexable page.
• Canonicals point to the final live URLs, not to staging. One domain variant (with or without www) is canonical, the other redirects.
• Internal links point directly to the new URLs. No internal link should run through a redirect.
• Hard-coded links in migrated content are replaced. Crawl staging for links to the old domain or old URL patterns.
• hreflang is set correctly for every language version.
• Schema markup: global markup such as Organization is in place and validated. Content markup like FAQ or pricing is only added where someone will maintain it. Since 2026, Google no longer shows FAQ rich results, but FAQ markup still helps machines understand your content.
• XML sitemap contains only final, indexable URLs.
• robots.txt for live is prepared and doesn't block important areas or AI crawlers.
• Images are compressed (AVIF or WebP) and have alt text.
• Page speed of core templates is checked. Expect lab scores to drop slightly once your marketing tags are live, and judge Core Web Vitals on real user data after launch.

Webflow-specific SEO points

If you're moving to Webflow or relaunching on Webflow, a few platform details matter for SEO. This is where we see the most avoidable mistakes:

1. Webflow only supports 301 redirects. For permanent moves, that's exactly right. If you need temporary redirects for a transition phase, set them up at the DNS level, for example through Cloudflare.
2. A CSV import replaces all existing redirects. If you upload only the new entries, you delete the old ones. Always maintain one complete list and upload all of it.
3. Wildcards are supported. Use pattern rules for whole folders instead of hundreds of single entries.
4. The automatic sitemap is usually enough. For most sites, Webflow's generated sitemap works well. A custom sitemap only pays off for very large sites.
5. Localization needs extra checks. With Webflow Localization, test how redirects behave on translated slugs. A locale only appears in the automatic sitemap once its subdirectory is published.
6. SEO fields live in the CMS. For CMS templates, map meta title, meta description and OG image to CMS fields during migration, so they don't fall back to a generic default.

We've migrated many SaaS sites to Webflow as a Webflow Enterprise Partner. For all of these checks in one place, with owners and timing, use our website relaunch checklist.

Launch day: the SEO checks

The launch itself is mostly a technical switch. From an SEO perspective, these are the checks that matter, in this order:

1. Upload and activate the complete redirect list. Then test the most important URLs individually and spot-check the rest.
2. Remove noindex and check robots.txt. A noindex tag left over from staging is the single most common mistake after a relaunch, and nobody notices until traffic drops.
3. Check canonicals on live URLs. They should point to the live domain, not to staging.
4. Submit the XML sitemap in Search Console. This helps Google discover the new URLs faster.
5. Run a quick crawl of the live site. Look for 404s, redirect chains and pages accidentally set to noindex.
6. Check tracking. Make sure analytics and conversion events fire, so your comparison with the baseline starts on day one.
7. Record the exact go-live time. You'll need it later to attribute changes in the data correctly.

The next morning, check Search Console for crawl errors and indexing issues, and look at the first conversions. Most launch problems show up within 24 hours. The full launch-day list, including the non-SEO items and who owns each one, is in phase 7 of our relaunch checklist.

The first 90 days: what's normal and what isn't

Here's the part most teams get wrong: rankings often look stable in the first days after launch, even if something went wrong. Google reprocesses changed URLs gradually, so problems can take two to three weeks to show up. Stopping your monitoring after a calm first week is a mistake.

Compare against your baseline with comparable periods, and account for seasonality. When URLs have changed, look at the old and new URL together: the old URL's clicks should move to the new one.

Also keep two things separate: SEO metrics and pipeline. More impressions don't automatically mean more clicks, and more traffic doesn't automatically mean more qualified leads. If analytics conversions drop but demo requests in the CRM are stable, check your tracking before you touch the content.

After two to three months, you have enough data from the new site to start optimizing the protected pages you deliberately left untouched. This is where the relaunch starts paying off, and where our Growth Plan picks up.

Rankings dropped? Find the cause in this order

If traffic drops after the first weeks and doesn't recover, don't start rewriting content. Work through the possible causes systematically, from the most likely to the least likely:

1. Are the pages indexed? Check the affected URLs in Search Console. A leftover noindex, a wrong canonical or a robots.txt rule is the fastest explanation and the fastest fix.
2. Are the redirects working? Test the old URLs of the affected pages. Do they return a 301, land on the right page in one hop, and does that page return a 200?
3. Is the new page weaker than the old one? Compare the old crawl with the new page: H1, title, word count, FAQs, internal links. Often a section got lost in the new template.
4. Did internal linking change? If a page used to be linked from the navigation or many articles and now isn't, it loses weight.
5. Are two pages competing? Check whether a new page now ranks for the same queries and splits the signals.
6. Did demand change? Look at impressions, not just clicks. If impressions fell across the whole market or in a seasonal pattern, the relaunch may not be the cause at all.

In our experience, the first three explain the vast majority of real drops after a relaunch. Fix the cause, request reindexing for the affected URLs, and give Google a few weeks to process the change.

AI search and the relaunch

SEO today isn't only about Google's blue links. AI Overviews appear on a large share of searches, and more and more B2B buyers ask ChatGPT, Perplexity or Google AI Mode for a shortlist before they ever visit a website. A relaunch affects that visibility too, in both directions.

The good news: you don't need a separate "GEO schema" or a special AI file. What helps AI search is the same foundation that helps classic SEO, done properly:

• Measure it before and after. Track how often you're named for the same set of prompts before the relaunch and again within 30 days after.
• Don't block AI crawlers in the new robots.txt unless you've decided to on purpose.
• Serve content as text. Information hidden in images, sliders or checkmark tables can't be read or cited. On comparison pages, write one or two sentences per cell instead of a checkmark.
• Structure content around questions. Clear questions as subheadings and direct answers underneath make your pages easy to cite.
• Keep entities consistent. Company name, product names and categories should be the same everywhere, supported by Organization schema.

A relaunch is a good moment to fix these things, because you're touching every template anyway. Just keep the foundation first principle in mind: for protected pages, improve structure without changing what already works.

The most common SEO mistakes in relaunches

• Bringing SEO in too late. If SEO joins after the page structure and wireframes are set, it can only react. In one project, SEO came in eight weeks late, and by then most structural decisions were already fixed.
• Changing URLs that didn't need to change.
• Changing the page structure after the redirect mapping.
• Forgetting the old platform's redirects.
• Redirecting everything to the homepage.
• Rewriting all content at once, so no change can be attributed to its effect.
• Testing templates with placeholder text and losing copy on protected pages.
• Deleting large content blocks during the relaunch instead of after it.
• Leaving noindex on after launch.
• Uploading only new redirects in Webflow and wiping the existing ones.
• Stopping monitoring after a stable first week.
• Measuring success by impressions instead of leads and pipeline.

Most of these have one root cause: SEO is treated as a launch-day task instead of a project-long responsibility. Make one person on your side the SEO owner from the first week, and most of this list disappears.

FAQ: website relaunch and SEO

Will a website relaunch hurt my SEO?

Not necessarily. A platform migration or design relaunch with unchanged content and URLs rarely costs rankings, and often improves them through better technical SEO. The risk grows when content, page structure and URLs change at the same time, and it's highest with a domain change.

How long does it take for rankings to recover after a relaunch?

After a clean migration, a possible dip is usually gone within one to two weeks. With bigger structural changes, it can take up to twelve weeks for rankings to settle. A domain change can take much longer.

Do I need 301 redirects if my URLs don't change?

No. A URL that stays the same needs no redirect. That's why the best redirect strategy starts with keeping URLs unchanged wherever possible.

How long should I keep redirects after a relaunch?

Google recommends at least a year. We recommend keeping them permanently, because external links and bookmarks often point to old URLs for years.

Should I redirect deleted pages to the homepage?

No. Google treats mass redirects to the homepage like missing pages. Redirect to the most relevant replacement, or return a 404 or 410 if there isn't one.

Can I rewrite all my content during the relaunch?

You can, but it's risky. If rankings drop, you won't know whether the cause was the new content, the design or the URLs. Migrate well-ranking pages 1:1 first and optimize them after launch.

Why did my rankings drop a few weeks after launch, not right away?

Google reprocesses changed URLs gradually. Problems with redirects, missing content or indexing often only show up after two to three weeks. That's why monitoring should run for at least twelve weeks.

Does a relaunch affect visibility in ChatGPT and AI Overviews?

Yes. AI search relies on the same foundation as classic SEO: crawlable text, clear structure and consistent entities. Measure your AI visibility before and after the relaunch to see the effect.

Planning a relaunch and want to keep your rankings? See how we approach a website relaunch for B2B SaaS, or book a free strategy call and we'll look at your current setup together.