Website relaunch without losing rankings: the steps before and after launch

Why do websites lose rankings after a relaunch?

Google does not know your website as a whole but as a collection of individual addresses. Each address has its own history: search terms it appears for, links from other websites pointing to it, and signals collected over years. When a new website changes or deletes these addresses without telling Google where the content now lives, each new page effectively starts from zero.

The most common causes are therefore not design questions but technical details: changed URLs without redirects, deleted pages that used to bring in visitors, new page titles that no longer contain the main search term, or a staging environment whose block on search engines was carried over at launch. All of this can be avoided with a clean plan. Short fluctuations in the first few weeks are normal; a lasting drop is not.

Step 1: Crawl and export your old URLs

Before anything is rebuilt, you need a complete list of every address on the existing website. This list is the foundation for everything that follows. Do not rely on a single source, because each shows only part of the picture.

• →A crawl of the old website with an SEO crawler: all reachable pages, images and PDFs with status code, page title, meta description and H1.
• →The existing sitemap.xml: it often contains pages that are barely linked internally any more.
• →Google Search Console, Performance report: export pages with clicks and impressions over the last twelve months. These are the pages you must not lose.
• →Pages with external links: addresses other websites point to, for example from the Links report in Search Console.
• →Your analytics tool: landing pages with significant visits, including from other channels such as newsletters or ads.

Step 2: Keep URLs or map them cleanly

The simplest redirect is the one you do not need. If an old address makes sense, such as /services/bathroom-renovation, just keep it. Only change addresses where there is a real reason: unreadable parameters such as /page?id=12, file extensions such as .html or .php, a new language structure or a different page layout.

For every address that changes, record in a spreadsheet where it will point in future. The rule: to the new page that matches the content most closely, not to the home page across the board. Redirecting an old service page to the home page throws away that page's signals. If an old page genuinely has no successor, an honest 404 or 410 status is better than an unsuitable redirect.

This spreadsheet becomes your redirect list. A 301 redirect tells search engines that the page has moved permanently. In Next.js you set this up in the configuration. With permanent: true, Next.js responds with status code 308, which is also a permanent redirect and is treated by Google like a 301.

// next.config.js
module.exports = {
  async redirects() {
    return [
      {
        source: "/services.html",
        destination: "/services",
        permanent: true,
      },
      {
        source: "/index.php/contact",
        destination: "/contact",
        permanent: true,
      },
    ];
  },
};

Step 3: Carry over content, titles and structured data

A relaunch is often when copy gets shortened and pages get merged. That can make sense, but it carries the greatest risk. Pages that bring in clicks according to Search Console should keep their core: the topic, the main search terms, the answers to your customers' questions. Improve these pages rather than reinventing them.

The same applies to page titles and meta descriptions. Keep titles that work well and adjust them only carefully. Also check the basic structure of every page. In our study “AI visibility of Berlin businesses 2026”, covering 579 Berlin business websites, only 47.8 % had exactly one H1 heading and 66.1 % had a meta description. A relaunch is the best opportunity to get this right on every page.

Do not forget structured data. If the old website had JSON-LD with business name, address, phone and opening hours, the new one needs it too, ideally more complete. According to our study, 57.5 % of the websites checked had no structured data at all, and only 10.4 % included address and phone. Adding it during the relaunch leaves you with a better foundation for Google and AI assistants than before.

Step 4: Internal links, sitemap and technical checks

Shortly before launch, check the new website the way a search engine will see it. Ideally, crawl the staging environment with the same tool you used for the old site and compare the results. These points belong on the list:

• →Internal links point directly to the new addresses, not to old URLs that are then redirected.
• →Important pages can be reached via navigation and in-text links; no page is orphaned.
• →The new sitemap.xml contains only current, reachable addresses with status code 200, no redirects and no error pages.
• →robots.txt does not block the live site. A block from staging must not go live, and neither must a noindex tag in the page head.
• →Canonical tags point to each page's own new address.
• →On multilingual sites, hreflang tags are set and reference each other.
• →Every line of the redirect list has been tested: open the old address, check target and status code, no chains of multiple redirects.

Step 5: After launch, monitor Search Console, 404 errors and load time

On launch day, submit the new sitemap in Google Search Console and check a few important pages with the URL Inspection tool. If you have also changed domains, use the Change of Address tool in Search Console as well. Then the real work begins: over the following weeks, check the indexing and performance reports regularly.

New 404 errors are the most important warning sign. They reveal addresses missing from the redirect list, such as old PDFs, image paths or pages that were only reached via external links. Add missing redirects promptly. Keep the redirects in place permanently, or at least until Google has fully picked up the new addresses and the old ones no longer receive meaningful traffic.

Keep an eye on load time too. A new website with large images, videos in the header or many scripts can be noticeably slower than the old one. Check the Core Web Vitals for your most important page types on mobile, both with PageSpeed Insights and in the corresponding Search Console report once enough data is available.

Checklist for your relaunch

A relaunch is a chance to improve structure, content and technology at the same time. This order keeps you in control: secure what you have, plan redirects, carry over what works, check the technical side, monitor after launch. If you take these steps seriously, your new website does not start from zero but from where you were, with better foundations.

If you want to know where your current website stands before a relaunch, for example on page titles, headings, structured data and load time, the free website check at Website check shows the key points within a few minutes.