Gruppe Digital

GuidesWebsite

Website relaunch without losing rankings: the most common mistakes and how to avoid them

A new website should bring more inquiries, not fewer. Yet after many relaunches, traffic and rankings collapse because basic steps are missed during the move. The good news: most mistakes are well known and can be avoided with careful planning.

Berke, founder · updated Oct 20, 2026 · 5 min read

Key points at a glance

  • Before the relaunch, record all existing URLs and assign a new address to each one.
  • Use server-side, permanent redirects (301 or 308) directly to the matching target.
  • Don't remove content that brings visitors and inquiries today without an equivalent replacement.
  • Remove test environment blocks such as noindex before go-live.
  • Watch Search Console and web analytics particularly closely in the weeks after launch.

Why relaunches so often cost rankings

For Google, a new website is initially a collection of new addresses. Everything the old pages have built up over the years in terms of trust, links and rankings is tied to their URLs. If these change without a redirect, the new site practically starts from zero.

Then there are content changes. During a relaunch, texts are shortened, pages merged or subpages removed because they no longer fit the new design. If exactly these pages have brought visitors so far, they are missing afterwards.

A relaunch is therefore not just a design and technology project. It is also a move, and moves need an inventory list.

That doesn't mean you can't change anything during a relaunch. New structures, better texts and more modern technology can even improve visibility in the long term. What matters is that you plan changes deliberately and don't accidentally lose what exists.

Mistake 1: no complete URL mapping

The most important step happens before go-live: a list of all existing URLs and their new counterparts. Google recommends compiling this list from several sources, such as sitemaps, server logs or web analytics, Search Console's links report and the content management system. Images, PDFs and downloads belong in it too.

Assign each old address to the new page that matches its content best. If several old pages are merged into one new page, that's fine. However, redirecting many old URLs wholesale to the homepage is problematic. Google generally doesn't treat such redirects as an equivalent replacement.

Especially on older SME websites, there are often product data sheets, job ads or expert articles that nobody remembers anymore. But they often have external links, which you keep with a clean mapping.

Example: excerpt from a URL mapping
/products/turned-parts.html/services/cnc-turning/
/products/milled-parts.html/services/cnc-milling/
/downloads/datenblatt-a.pdf/downloads/datasheet-a.pdf (unchanged)
/news/trade-fair-2019.html/news/ (archive, matching content)

Illustrative example. In practice, the mapping is usually maintained as a table and fully tested before go-live.

Mistake 2: wrong or cumbersome redirects

For permanently changed addresses, server-side redirects with status code 301 or 308 are the recommended route. They signal to Google that the new URL is the canonical one from now on. Temporary redirects such as 302 tend to make Google keep the old address in the index.

According to Google, JavaScript redirects are only a stopgap, because Google only recognizes them after rendering. Also make sure that every old URL points directly to its final destination. Chains of several redirects easily arise when earlier relaunches have already left redirects behind.

Keep the redirects in place for a long time. Google recommends at least one year, preferably as long as possible. After all, external links to your old addresses don't disappear after a few months either.

Test the redirects before go-live, if technically possible, and immediately afterwards on the live site. A crawling tool that retrieves the complete list of old URLs shows within minutes which addresses redirect correctly and which return an error.

Mistake 3: content gets lost during the rebuild

A new design tempts you to shorten texts drastically. Short, image-heavy pages look modern, but often no longer answer the questions visitors came via Google for. So check before the relaunch which pages have brought visitors and inquiries in the last twelve months.

These pages should remain at least equivalent in content. Of course you may revise them, for example updating outdated information or improving the structure. The core, i.e. the topic and the relevant information, should be preserved.

Also pay attention to page titles, meta descriptions and headings. During a relaunch, they are often replaced by placeholders or automatically generated variants. That is only noticed when the search results suddenly look different.

The same applies to downloads. In B2B, technical data sheets, certificates and catalogs are often found directly via search. If after the relaunch they are at a new address without a redirect or missing altogether, you lose these visits and annoy customers who have bookmarked the documents.

Mistake 4: test environment settings go live

New websites are usually developed on a test environment that is blocked for search engines. That's right, because half-finished pages shouldn't end up in the index. It becomes dangerous when these blocks are carried over at go-live.

Typical cases are a noindex tag on all pages or a robots.txt that blocks the entire directory. Both can mean that Google no longer includes your new website. Important to know: if robots.txt prohibits crawling, Google won't see a noindex tag either.

Ideally also protect the test environment with a password. And make removing all blocks a fixed item on the go-live checklist.

  • Check meta robots and X-Robots-Tag for noindex
  • Check the live site's robots.txt
  • Canonical tags must not point to the test environment
  • Switch internal links to the new URLs, not old addresses
  • Test forms, tracking and the consent banner on the live site

Mistake 5: Search Console isn't used

Google Search Console is your most important tool during a relaunch. Make sure the property is verified, and after go-live submit a current XML sitemap with the new URLs. Google recommends temporarily keeping the old sitemap in parallel to monitor the transition.

If you also change the domain, for example after a change of company name, verify the old and new domains in Search Console and use the Change of Address tool there. With URL Inspection, you can spot-check whether redirects and indexing work as intended.

Before the relaunch, save an export of the most important data from the performance report. That gives you a basis for comparison when you want to assess after launch whether anything has got worse.

Also look at Search Console's links report. It shows which of your pages are most frequently linked to from other websites. These pages deserve special care in the mapping.

Monitoring after go-live

The work isn't done at go-live. Google points out that rankings can fluctuate temporarily after a move. For medium-sized websites, it can take a few weeks or longer until the new URLs are fully processed.

In the first days check daily, later weekly, the indexing reports, crawl errors and clicks in Search Console. A crawl of the old URL list quickly shows whether all redirects work or whether error pages are appearing somewhere.

Also keep an eye on inquiries, not just visitor numbers. If forms no longer arrive or phone numbers are linked incorrectly, you otherwise only notice when sales asks why it has become so quiet.

A realistic schedule

Plan the SEO tasks from the start, not just shortly before go-live. The inventory and mapping belong in the concept phase, because they influence the new page structure. Testing the redirects belongs in the phase before launch.

Choose a quiet time for go-live when the people involved are available. Launching on a Friday afternoon before a long weekend is rarely a good idea. Also plan time for corrections in the first weeks, because minor problems crop up in almost every relaunch.

Document all decisions on URLs, redirects and removed content. If questions arise months later, for example why a certain page can no longer be found, this documentation helps a great deal. It is also a good basis for the next relaunch.

Frequently asked questions

How long should I keep 301 redirects in place?

Google recommends at least one year and ideally as long as possible. In practice, there is little reason not to keep redirects permanently.

Is a temporary drop after the relaunch normal?

According to Google, short-term fluctuations are common during moves until all URLs have been recrawled. A significant and persistent drop over several weeks, on the other hand, usually points to technical errors or lost content.

Do I need to watch out for anything if URLs stay the same?

Yes. Even without URL changes, new templates, shortened texts, missing page titles or a forgotten noindex can cost rankings. So check the content and technical settings just as carefully.

Should I delete old, rarely visited pages?

That can make sense. But first check whether the pages have external links. If so, redirect them to a page with matching content instead of simply removing them.

Free initial consultation

Where are you losing customers today?

In 30 minutes we show you the three biggest levers for more inquiries, without obligation, and even if we don't end up working together.

Berke, your contact person+49 761 5572 1816 · Reply within 24 hours on business days

Let’s talk

We will get back to you within 24 hours on working days.

Inquiry received!

Thank you for your trust. We will get back to you shortly, within 24 hours at the latest. A confirmation is on its way to your inbox.