Website Relaunch Without Losing Rankings: A Checklist

A website relaunch is meant to make the site more modern, faster and better. Yet traffic from Google often drops afterwards because old addresses lead nowhere or important content has disappeared. With careful planning, this can largely be avoided. This checklist guides you through the phases before, during and after go-live.

Why relaunches can cost rankings

Google has stored and evaluated your existing pages under specific addresses (URLs). If these addresses change without Google learning where the content now lives, signals such as links and user signals are lost. Visitors arriving via old links or bookmarks end up on an error page.

Typical causes of ranking losses include:

• missing or incorrect redirects
• deleted or heavily shortened content that used to rank well
• changed page titles and headings without regard for search terms
• technical errors, such as a site accidentally blocked from search engines
• noticeably slower load times

Some temporary fluctuation is normal even with a clean move. Google itself notes that for medium-sized sites it can take a few weeks or more before the new URLs fully appear in search results.

Phase 1: Take stock before the relaunch

Before changing anything, document the current state.

• Capture all URLs: from the XML sitemap, with a crawler (a program that scans the website the way a search engine does), from server logs, analytics and the CMS. Remember PDFs and images too.
• Identify top pages: Google Search Console shows which pages receive the most clicks and impressions. These pages deserve special attention.
• Save rankings: export the most important queries and positions as a baseline.
• Find linked pages: pages with many external links must not be lost under any circumstances.
• Record technical metrics: load times, Core Web Vitals and indexing status serve as a later comparison.

Phase 2: Planning and URL mapping

The heart of every SEO-safe migration is the URL mapping: a table that assigns each old URL to its matching new URL.

A few ground rules from Google's documentation on site moves apply:

• Redirect each old URL to the matching new page, not wholesale to the home page.
• Avoid redirect chains. Each old URL should point directly to its final destination.
• Keep or improve well-ranking content instead of deleting it.
• Retain proven page titles, meta descriptions and headings where they work well.

If the URLs do not need to change at all, that is the safest route. So check whether the existing structure can be kept.

Phase 3: Build and test before go-live

Ideally, the new website is built on a staging environment. It should be blocked from search engines, for example with password protection, so that no duplicate content ends up in the index.

Before go-live, check:

• Redirects: every entry in the URL mapping is set up as a server-side permanent redirect. Google recommends status code 301 or 308.
• Canonical tags: each page points to itself via a canonical tag (a hint indicating the preferred URL).
• Internal links: menus, footer and in-text links point directly to the new URLs, not to old addresses that redirect.
• hreflang: on multilingual sites, the language annotations are updated to the new URLs.
• Structured data: markup for things like the organisation, articles or FAQs has been carried over.
• Load time and mobile view: the new site is at least as fast as the old one and works well on smartphones.
• Tracking: analytics and the consent banner work.

Phase 4: Go-live

Choose a launch time with low traffic and enough staff available for quick fixes. Immediately after switching over:

1. Remove search engine blocking: robots.txt must no longer block the site, and no "noindex" directives from the test phase may remain.
2. Submit the new XML sitemap in Google Search Console. Keep a list of the old URLs to check the redirects.
3. Spot-check redirects, especially for the top pages.
4. For a domain change, use the Change of Address tool in Search Console. It is only intended for moves to a different domain or subdomain, not for switching from HTTP to HTTPS or changing paths within the same domain.

Phase 5: The weeks after the relaunch

Now monitoring begins. Plan for intensive monitoring during at least the first few weeks.

• Check Search Console daily: watch for rising 404 errors, indexing problems and redirect warnings.
• Compare rankings and clicks: use the data saved in phase 1 as a baseline.
• Add missing redirects: if old URLs turn up that were missing from the mapping, redirect them promptly.
• Update external links: ask partners and directories with important links to update the address, and adjust your own profiles.
• Keep the redirects: Google recommends keeping redirects generally for at least one year, and ideally indefinitely.

The checklist to tick off

Before

• All old URLs captured, including PDFs and images
• Top pages, rankings and backlinks saved
• Technical metrics documented

Planning

• URL mapping complete, each URL with a matching target
• Important content carried over or improved
• Titles and meta descriptions reviewed

Before go-live

• 301 or 308 redirects set up and tested
• Canonicals, internal links, hreflang and structured data checked
• Load time and mobile view tested

Go-live

• Test-phase blocking removed
• New sitemap submitted
• For domain changes, change of address reported in Search Console

After

• Search Console and rankings monitored
• Missing redirects added
• Redirects active for at least one year

Relaunching with Simplify Data

Simplify Data, based in Kiel, Germany, plans and delivers website relaunches with WordPress and Next.js for companies in Schleswig-Holstein, Hamburg and remotely across Germany. If you wish, we start with an SEO audit of the existing site so that valuable content and rankings are preserved during the move. Learn more on our web development page.

Sources

• Google Search Central: Site moves with URL changes
• Google Search Console Help: Change of Address tool