Website relaunch without losing rankings: what matters in the migration
Relaunch without SEO losses: inventory, 301 plan, content, technical checks and monitoring after go-live. With a checklist.
By Editorial team

A relaunch is meant to make a website faster, more modern and better at selling. In practice, it initially costs many companies visibility: rankings drop, organic traffic falls, leads dry up. This is rarely down to the new design. It happens because search engines treat the new website like an unknown one when the link to the old one is missing.
Relaunch SEO means creating that link: transferring every assessed address of the old website to the new one so that Google keeps its existing assessment. The steps below apply to corporate websites as well as to online stores, where a platform change often affects thousands of product and category URLs.
Why do relaunches so often cost rankings?
Google does not assess a website as a whole, but individual URLs. Each address has collected signals over the years: rankings for specific search terms, clicks, internal and external links. If the address changes, that history starts from scratch, unless someone tells Google where the page has moved.
On top of that come changes that often happen along the way:
- New URL structure:
/services/seo-consulting.htmlbecomes/seo/consulting/. Without redirects, hundreds of error pages appear. - Shortened content: The new design calls for short copy. The very passages a page ranked for disappear.
- Changed internal linking: Navigation and footer get leaner. Important pages lose internal links and with them, weight.
- New technology: A different CMS or a JavaScript framework delivers content differently. What looks good in the browser may be hard for crawlers to read.
Each of these changes is manageable on its own. It gets risky when several happen at once and nobody keeps track of the consequences for search.
Before the relaunch: inventory of URLs, rankings, traffic and backlinks
The most important work happens before the first line of code is written. You need a complete picture of what the old website delivers today. Only then can you make sure none of it gets lost.
Capture at least four data sets:
- All URLs: A full crawl of the existing website, supplemented with the URLs from the XML sitemap and from Google Search Console. Crawlers do not find every page, while Search Console also knows old addresses that still generate impressions.
- Rankings and impressions: The queries and pages of the past twelve months from Search Console. This list shows which pages are actually found.
- Traffic and conversions: The pages with the most organic visitors from your analytics tool and, more importantly, the pages that generate leads or orders.
- Backlinks: The pages other websites link to, from Search Console and a backlink tool. External links are hard to replace and must not lead nowhere after the relaunch.
Combine this data in one spreadsheet, one row per URL. The redirect plan is built from this spreadsheet in the next step. Also keep a copy of the old website, for example as a full crawl including HTML. If questions arise after go-live about what a page said, you will have an answer.
URL structure and redirects: the 301 plan
The best redirect is the one you do not need. So check first whether existing URLs can be kept. A new structure is only worth it if it brings a clear advantage for users and search engines, for example because the old structure has grown unwieldy.
Where URLs change, every relevant old address needs a permanent redirect with status code 301 to the matching new page. Three rules apply to the plan:
- One to one where possible: Each old page points to its direct successor. The category “Garden furniture” redirects to the new category “Garden furniture”, not to “Outdoor”.
- Closest topic where necessary: If a page is dropped, redirect to the page that covers the topic best. If there is no matching page, a 410 status code is more honest than a redirect to the home page.
- No chains: An old URL redirects straight to its target, not via intermediate steps. Existing redirects from earlier relaunches are updated accordingly.
Test the plan on the staging environment before go-live. A crawl of the old URL list against the new website shows whether every address leads via 301 to a page with status code 200.
Carry over content instead of reinventing it
A relaunch is a good occasion to improve content. It is not a good occasion to replace content that works. Pages that rank today do so because of their content: terms, answers, structure. Shortening these texts for a new layout or rewriting them entirely gives up the basis of the rankings.
A simple approach has proven itself:
- Pages with rankings: Carry over the content, keep headings and key statements. Improvements are welcome as long as the page still answers the previous search queries.
- Pages without rankings: Here you have room for something new. Merge, revise or remove.
- Duplicate content: Combine several weak pages on the same topic into one strong page and redirect the old addresses there with a 301.
Carry over page titles and meta descriptions deliberately as well. In many projects they are forgotten and then generated automatically by the new system, often much worse than before.
Technical check before go-live
The staging environment should be checked before go-live as if it were already online. This check is the core of technical SEO. Four areas are decisive.
Indexing: The staging environment is rightly blocked for search engines, usually via noindex or password protection. This block must be removed at go-live. Also check robots.txt, canonical tags and, for multilingual websites, hreflang. A wrong canonical on every page can make a website just as invisible as a forgotten noindex.
Internal links: All internal links point directly to the new URLs, not to old addresses that are then redirected. Important pages should be linked at least as well through navigation and content as before.
Structured data: Product data, reviews, FAQ, breadcrumbs, organization details. Check whether the new system carries over this markup. If it is missing, stars, prices or breadcrumbs disappear from the search results.
Page speed: New designs often bring large images, videos and scripts. Measure the Core Web Vitals of the most important page types before go-live. A page that is slower than the old one gives away part of what the relaunch is supposed to deliver.
The first four weeks after go-live: monitoring in Search Console
Go-live marks the start of the second half of the work. Google gradually crawls the new website, maps the redirects and evaluates the new pages. During this time, errors can still be fixed quickly before they take hold.
A proven routine for the first weeks:
- Day 1: Submit the new XML sitemap in Search Console. Keep the old sitemap with the previous URLs available for a few weeks so that Google finds the redirects faster. Spot-check the most important pages with the URL Inspection tool.
- Week 1: Check the page indexing report daily. New 404 errors, server errors and pages marked “Crawled, currently not indexed” are the most important warning signs.
- Weeks 2 to 4: Filter the performance report by page and compare it with the inventory. Where clicks and impressions drop sharply, check the redirect, content and internal linking of the affected page.
Expect fluctuations. Slight losses in the first weeks are normal as long as the trend recovers afterwards. What matters is that you spot deviations early and can attribute them to a cause.
What are the most common mistakes in practice?
Most relaunch problems we see in projects have little to do with technology in the narrow sense. They arise because SEO is brought in too late and decisions have already been made.
- Redirects as the last step: The 301 plan is put together in the week before go-live, under time pressure and without a complete URL list. Pages with backlinks or rankings slip through the cracks.
- Content cut to fit the design: Detailed category texts or service descriptions are removed for a tidy layout. The page looks better and ranks worse.
noindexcarried over from staging: The block stays active after go-live. This mistake is trivial and surprisingly common, because nobody is explicitly responsible for checking it.- No baseline: Without an inventory, nobody can say after go-live what was lost. The analysis then starts with guesses instead of data.
- Too many changes at once: New domain, new CMS, new structure and new content in one step. If rankings drop afterwards, the cause can hardly be isolated.
All of these have one thing in common: they can be avoided with planning, but are hard to repair afterwards. That is why SEO consulting pays off in the concept phase, not just before go-live.
Checklist to tick off
You can tick the boxes directly on this page. To print, use your browser’s print function.
Before the relaunch
- Full crawl of the old website created and saved
- URLs from sitemap and Search Console added
- Rankings, impressions and clicks of the past twelve months exported
- Pages with conversions and backlinks flagged
- Decision made on which URLs are kept
Redirects and content
- 301 plan created for all relevant old URLs
- No redirect chains, no blanket redirects to the home page
- Content of ranking pages carried over
- Page titles and meta descriptions transferred
Technical check on staging
- Redirects tested against the old URL list
- Canonicals, hreflang and robots.txt checked
- Internal links point to new URLs
- Structured data carried over and validated
- Page speed of the most important page types measured
Go-live and monitoring
-
noindexand password protection removed - New sitemap submitted, old sitemap temporarily still available
- Indexing report checked daily in week 1
- Performance by page compared with the inventory
- Noticeable pages analyzed and corrected
A relaunch without ranking losses is not luck, but the result of a complete inventory, a clean redirect plan and consistent monitoring after go-live. The earlier this work is planned into the project, the less it costs. To use the relaunch to become more visible in AI answers as well, see AI SEO: how ChatGPT, Perplexity and Google AI Overviews choose their sources.
Related services


