Website Relaunch: Process, Project Plan & SEO Checklist (Without Losing Rankings)

A website relaunch is the fundamental technical and structural overhaul of a website, often involving a new CMS, a new site structure, and new URLs. To avoid losing rankings in the process, Google recommends redirecting every old URL with a server-side permanent redirect to its new destination, following a prepared URL mapping.

What is a website relaunch and how does it differ from a redesign?

A website relaunch is a fundamental overhaul of a website on a technical and structural level, while a redesign only affects the look and feel. A relaunch often changes the content management system, the information architecture, and above all the URLs. This URL change is exactly what makes a relaunch risky from an SEO perspective, because Google has to transfer all previously built-up signals to the new addresses.

With a pure redesign, the URLs, page structure, and content stay the same, only colors, typography, or layout change. Here the ranking risk is low. As soon as URLs or the domain change, we are talking about a site move with URL changes, and the SEO migration rules described in this article apply. Professional implementation is part of our web design service.

How does a website relaunch work step by step?

A website relaunch runs through seven project phases that build on each other, from analysis to monitoring after go-live. Following this sequence significantly reduces the risk of data loss and ranking drops.

1. Analysis and current-state assessment: capture the full URL list, current rankings, traffic data, and technical weaknesses. This before state is your benchmark.
2. Concept and goals: define target audiences, page structure (information architecture), and measurable goals.
3. Design and UX: wireframes and layouts based on the new structure.
4. Development on staging: implementation in a protected test environment that is not publicly indexable.
5. SEO migration: prepare URL mapping, redirects, canonicals, and sitemaps.
6. Go-live: switch over to the new site, activate redirects, remove indexing blocks.
7. Monitoring: observe crawling, indexing, and rankings over several weeks.

Phases 1, 5, and 7 determine SEO success. Design and development are visible, but URL mapping is what protects your rankings.

How do I prevent ranking losses during a relaunch?

You prevent ranking losses by redirecting every old URL with a permanent redirect to the most relevant new URL and actively informing Google about the move through Search Console. According to Google Search Central (as of 2026), creating an old-to-new URL mapping is a central step of every site move; Google places it in its guide right after preparing the new site.

SEO migration consists of five building blocks. First, server-side permanent redirects following the URL mapping. Second, according to Google every new URL gets a self-referencing rel=canonical tag that points to itself. Third, after the move you submit a new XML sitemap in Search Console and remove the old one. Fourth, for a domain or subdomain change you use the change of address tool. Fifth, you keep the redirects in place for a long time. Google recommends keeping redirects in place generally for at least 1 year after a site move so that all signals are transferred to the new URLs (Google Search Central, as of 2026).

For small and medium-sized websites, Google recommends moving all URLs at the same time so the algorithms recognize the move faster. Only very large sites can migrate in sections.

What is URL mapping and how do I set up 301 redirects correctly?

URL mapping is the complete assignment of every old URL to its new destination, and according to Google it is a fundamental step of a site move. Google lists URL mapping in its guide right after preparing the new site. First, create a complete list of all old URLs from a website crawl, Google Search Console, and the server log files. Then assign each old URL to the most contextually relevant new URL, not simply to the homepage.

For redirects the following applies: Google treats status codes 301 and 308 as permanent redirects. The indexing pipeline uses them as a signal that the redirect target should become canonical. Codes 302 and 307 are temporary and do not provide this canonicalization signal (Google Search Central, as of 2026). For a relaunch you therefore need 301 or 308.

Avoid redirect chains and, where possible, redirect directly to the final destination instead of through intermediate stops. For the choice of method, Google names an order of reliability: server-side redirects are the most reliable, followed by meta refresh, then JavaScript redirects, and as the lowest, explicitly discouraged level, so-called crypto redirects. You should only use JavaScript redirects if server-side or meta refresh redirects are not possible (Google Search Central, as of 2026).

How do I make sure Google re-indexes the new site quickly?

You achieve fast re-indexing by keeping the staging environment properly blocked during development and correctly removing that block at go-live. Protect staging with access protection and a meta robots noindex tag, not with a robots.txt disallow.

The reason matters: for a noindex directive to work, the page must not be blocked by robots.txt. Otherwise the crawler never sees the noindex rule, and the page can still appear in search results (Google Search Central, as of 2026).

At go-live, remove noindex and disallow from the live site, submit the new XML sitemap in Search Console, and remove the old one. Use the URL inspection tool to check whether the new URLs are crawlable and indexable. For a domain or subdomain change, use the change of address tool.

What are the most common mistakes in a website relaunch?

The most common relaunch mistakes concern indexing and redirects, not design. Knowing them helps you avoid the most costly ranking drops.

• Staging stays indexable: the test environment was never blocked, or was only blocked via robots.txt, so the noindex tag never takes effect.
• Live site stays on noindex: the development block was forgotten at go-live, and the new site gets completely deindexed.
• Missing or chained redirects: old URLs lead nowhere (404) or run through long chains instead of going directly to the destination.
• Blanket redirect to the homepage: instead of redirecting each URL to its content counterpart.
• Forgotten assets: images, PDFs, and hreflang links are not migrated.
• No before benchmark: without a current-state assessment, success cannot be measured.
• Go-live on a Friday without monitoring: errors go unnoticed over the weekend.

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

Recovery depends on the size of the website. According to Google, a medium-sized website can take a few weeks until most pages in the index have moved to the new URLs, and larger sites can take longer (Google Search Central, as of 2026).

Fluctuations during this phase are normal. What matters is not removing the redirects too early. Google recommends keeping them in place for at least 1 year in general. Over this period, watch crawl stats, index coverage, and rankings in Search Console. A closer diagnosis is needed if, after several weeks, entire sections of the site remain unindexed, many 404 errors appear, or rankings drop permanently rather than just briefly.

Website relaunch checklist: before, during, and after go-live

This checklist summarizes the SEO-critical steps of a website relaunch by phase. All recommendations follow the guidance of Google Search Central (as of 2026).

Phase	Task	Goal
Before go-live	Create a complete list of old URLs from crawl, GSC, and log files	Basis for URL mapping
Before go-live	Secure a before benchmark (rankings, traffic)	Make success measurable
Before go-live	Old-to-new URL mapping, each URL to its most relevant destination	Signal transfer
Before go-live	Prepare 301/308 redirects, avoid redirect chains, and redirect directly to the final destination	Permanent canonicalization signal
Before go-live	Block staging with access protection and noindex, not with a robots.txt disallow	noindex stays effective
At go-live	For small/medium sites, switch all URLs at the same time	Faster move detection
At go-live	Remove noindex and disallow from the live site	Indexing of the new site
At go-live	Set a self-referencing rel=canonical for each new URL	Clear canonicalization
At go-live	Submit the new sitemap in GSC, remove the old one	Faster crawling
At go-live	Change of address only for a domain/subdomain change	Report the move officially
After go-live	Check URL inspection and index coverage	Catch errors early
After go-live	Keep redirects in place for at least 1 year	Complete signal transfer

FAQ about website relaunches

Do I automatically lose rankings during a relaunch?

No, not automatically. If you redirect every old URL to the most relevant new URL with a permanent 301/308 redirect and keep the redirects in place for at least 1 year, Google transfers the signals to the new URLs (Google Search Central, as of 2026). Short-term fluctuations during processing are normal.

Do I need new URLs for a relaunch?

No. If only the look and layout change, the URLs stay the same, and it is a redesign without site-move risk. New URLs only appear once the structure, CMS, or domain changes. In that case you need a complete URL mapping with redirects.

When do I need to use the change of address tool?

Only for a domain or subdomain change. According to Google Search Console Help (as of 2026), it is not intended for a switch from HTTP to HTTPS, from www to non-www, or for path changes within the same domain. It requires ownership of both properties in the same Google account and a 301 redirect set up from the old to the new homepage.

How long do I need to keep 301 redirects?

Google recommends keeping the redirects in place as long as possible after a site move, generally at least 1 year, so that all signals are transferred to the new URLs (Google Search Central, as of 2026). Many operators leave them active permanently.

Why doesn't noindex work on my staging site?

The page is probably also blocked by robots.txt. For a noindex directive to work, the page must not be blocked by robots.txt, otherwise the crawler never sees the rule and the page can still appear in search results (Google Search Central, as of 2026). Use access protection plus noindex on crawlable pages instead.

Should I switch all pages at once or gradually?

For small and medium-sized websites, Google recommends moving all URLs at the same time so the algorithms recognize the move faster. Only very large sites can migrate in sections (Google Search Central, as of 2026).

Roughly how much does a website relaunch cost?

Binding market prices cannot be stated across the board, the effort depends heavily on scope, CMS, data migration, and SEO depth. This is a market observation, not a price commitment. You can only get a reliable estimate through a specific quote based on your page inventory.

Sources

• Google Search Central - Site moves with URL changes: developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes (as of 2026)
• Google Search Central - Redirects and Google Search: developers.google.com/search/docs/crawling-indexing/301-redirects (as of 2026)
• Google Search Central - Block Search indexing with noindex: developers.google.com/search/docs/crawling-indexing/block-indexing (as of 2026)
• Google Search Console Help - Change of Address tool: support.google.com/webmasters/answer/9370220 (as of 2026)

Note: This article provides general technical information and does not replace individual SEO or legal advice. Any effort or cost statements mentioned are non-binding market observations, not a quote or price commitment.

Author: Alexander Weipprecht. As of: June 2026.