Website relaunch with SEO support: protect your visibility

  • Requirements catalogue for agency, developers and editors
  • Redirect plan for every URL with rankings and traffic
  • Implementation by our team, often faster and more affordable with AI
Relaunch support enquiry
4.9
Based on 32 reviews
Google Premier Partner 2026 badge
Microsoft Partner Badge
SISTRIX-zertifizierte Agentur

SEO belongs in the planning

In many projects it is unclear who is responsible for SEO. The developers see it as an editorial topic, the editors as a technical task. We bring the requirements in early, while they can still be implemented at no extra cost.

Fixing it later costs far more

Our rule of thumb from many projects: an SEO requirement that is retrofitted after go-live costs around three times as much. Some decisions, such as URL structure or rendering, can only be corrected later with a great deal of time and effort.

SEO is the foundation for GEO

AI systems such as ChatGPT, Gemini and Claude draw on search indexes and on your website. What search engines can no longer find after the relaunch is usually missing from AI answers as well. That is why we check both together, classic search and GEO.

Baseline

We record what your website delivers today: rankings, traffic, backlinks and conversions per URL. It is based on an SEO analysis of the current state and makes clear which pages must survive the relaunch.

Requirements catalogue

A binding document for development, design, concept and editorial teams. Every requirement is explained and prioritised in five levels, from essential to optional. The catalogue covers hosting, indexing, rendering, site structure, structured data and editorial guidelines.

URL mapping and redirects

Every old URL gets a suitable destination. To do this we combine all sources: a crawl of the old website, Google Search Console, web analytics, SISTRIX and backlink data. The result is a redirect table your developers can import directly.

Staging check

Before go-live we check the new website in the test environment: status codes, canonicals, hreflang, internal linking, page titles, structured data, loading times and rendering. We separate what is normal on a staging environment, such as password protection or noindex, from real errors.

Go-live support

On the day of go-live we test the redirects, robots.txt, the XML sitemap and indexability. In addition to the new XML sitemap, we submit a second sitemap with the old URLs in Google Search Console. This way Google fetches the changed addresses sooner, follows the redirects and updates its index quickly. We watch crawling from the start.

Monitoring after the relaunch

In the first weeks we check visibility, index coverage, error pages and loading times at short intervals. We report deviations to your developers with specific corrections, where possible before they affect rankings.

We implement it for you

Where a rebuild by developers does not pay off, we carry out the relaunch ourselves: reviewing and merging content, structured data, redirects, technical clean-up and a contemporary design. You receive a checked result: every change is made in a test environment, with a backup and a log entry, and only what you have approved goes live. For websites with a lot of existing content this can be faster and more affordable than a conventional rebuild, because AI agents do the routine work. Coordination, approvals and review stay in human hands. Results are checked in several stages: automatically, by a second review pass with another AI agent and by our team, in full for important changes and by spot checks otherwise.

1

Kick-off

We clarify goals, timeline, people involved and the scope of the relaunch: design, CMS, domain, structure, languages.

2

Setting the baseline

We crawl the old website, analyse rankings, traffic and backlinks and define the baseline values against which we later measure the relaunch.

3

Handing over the catalogue

We hand over the catalogue and go through it with everyone involved. We answer open questions from the developers during implementation.

4

Assigning URLs

As soon as the new structure is in place, we assign every old URL to a new one: ideally through rules (regex) for whole directories and URL patterns, the rest individually in a mapping table. For important pages without an equivalent, we recommend carrying the content over to the new website.

5

Implementation by us (optional)

If we implement the work ourselves, we work on a copy of your website, as described under ‘We implement it for you’. Only what you have approved goes live.

6

Checking the test environment

We check the test environment and deliver a prioritised list of errors with links to the affected pages. After the corrections we check again.

7

Go-live and monitoring

We support the go-live, test all redirects and watch the website in the weeks that follow. At the end we compare the results with the baseline values.



 Your relaunch is coming up 

Do you know which of your pages bring the traffic?

We show you which URLs, rankings and links you need to protect during the relaunch.


Relaunch support enquiry
 SEO and GEO in a relaunch 

Many requirements apply equally to classic search and to AI systems. Some are added for GEO. The most important points:

  • Redirects: every old URL is redirected permanently with a 301 to its new destination, without chains and not simply to the homepage. This protects rankings and backlinks. AI systems also cite your old URLs and should still land on the right content.
  • Indexing: robots.txt, XML sitemap, canonicals and noindex must not contradict each other. Typical errors are a canonical pointing to a redirected URL or a blocked page in the sitemap.
  • Access for AI crawlers: new firewalls, bot protection and robots.txt rules often block crawlers such as GPTBot or ClaudeBot without anyone noticing. We check whether the crawlers you want can reach the new website, on request with a log file analysis.
  • Rendering: content that is only loaded via JavaScript is seen by Google with a delay. Most AI crawlers, including those from OpenAI, Anthropic and Perplexity, did not execute JavaScript in a measurement by Vercel and MERJ in late 2024 and did not see this content. Important text therefore belongs in the HTML that is delivered. For JavaScript applications that load content via Ajax, we recommend server-side rendering.
  • Content and facts: in a relaunch, texts are often unintentionally shortened, merged or moved into PDFs. If details about services, prices or locations are missing afterwards, AI systems answer imprecisely or wrongly. We compare the content before and after the relaunch.
  • Structured data: markup for the organisation, products and articles is often lost when the system changes, or is poorly maintained afterwards. It is rebuilt in the new template and validated before go-live.
  • Loading time and stability: hosting, caching and image formats determine the Core Web Vitals. Slow or faulty server responses slow down every crawler.
  • Measurement: tracking and consent are migrated and tested as well. In addition, before the relaunch we record how often AI systems mention your brand, for example with a GEO audit, and measure again afterwards.
 From practice 

Typical errors around go-live

The following points come from relaunch projects we have supported, anonymised here.

  • Gaps in the redirect plan: in a staging check in 2026, 92 old URLs had no destination. After go-live these pages would have returned a 404 error. The gap was closed before go-live. On the day of go-live, all 392 redirects tested led to a suitable destination.
  • Settings from the test environment: a noindex or a blocking robots.txt moves from staging to the live website. Exactly this happened at a go-live in 2026 and was corrected straight afterwards. That is why we check indexability again on the day of go-live.
  • Googlebot locked out: on one website, an IP blocklist at the hosting provider locked out Googlebot. Visibility fell by around two thirds within a week. After the correction it was back at its previous level two weeks later. Whether crawlers can reach the website therefore belongs on the checklist for every change of hosting.
  • Launch without server-side rendering: an online shop was due to go live without server-side rendering. Search engines and AI crawlers would have seen a largely empty page instead of the products. We were able to prevent this shortly before go-live.
  • Missing content: pages with good rankings have no equivalent in the new structure, or their text has been cut heavily. We then recommend carrying the content over to the new website and redirecting the old URL to the page that now holds it.
  • Internal links to old addresses: menus and body text still point to old URLs and run through redirects. This costs loading time and crawl budget. Canonicals pointing to old URLs contradict the redirects.
  • Language versions: hreflang annotations point to pages that no longer exist, or the language versions do not reference each other.
 Results from practice 

How relaunches we have supported have developed

Five examples from our work: we name Beta Klinik and gekonntgekocht.de and have anonymised the other three. The visibility figures come from SISTRIX.

  • Medium-sized company, go-live in December 2024: the SISTRIX Visibility Index has multiplied since go-live (as of the end of September 2026). Google Search brings considerably more visits than in the previous year.
  • Beta Klinik, go-live on 15 December 2025: it was important that specialist content, expert profiles and author details survived the relaunch completely. The Visibility Index rose from 0.70 in the week of go-live to 1.81 at the end of September 2026, the highest value since measurement began (SISTRIX). Beta Klinik case study (in German)
  • Online shop changing its shop system, go-live in summer 2026: in the first weeks, rankings in Google Search were a few positions lower on average. After six to seven weeks they were back at the starting value, and the Visibility Index remained stable. Such fluctuations are normal as long as redirects and content are right.
  • Specialist clinic, go-live in September 2026: in the first week after go-live, Google Search brought more visits than in the week before.
  • gekonntgekocht.de, the recipe website of our founder’s family with more than 5,000 recipes, pilot project for a relaunch with AI agents in 2026: the AI agents’ work included 4,050 corrections in 2,346 recipes. Goals, subject-matter rules and every go-live step stayed with us. From 4 to 17 October 2026, Google Search brought 35 per cent more clicks than in the two weeks before the first go-live step, and recipe results with images rose from 34 to 31,682 impressions (Search Console). Read the case study

Read more in our article Typical errors in a website relaunch.

 Request relaunch support 

Let us talk about your relaunch

Tell us what you are planning and when the new website is due to go live. We will get back to you with a proposal for scope and process.

Microsoft Partner Badge
SISTRIX-zertifizierte Agentur
4.9
Based on 32 reviews

Reviews from our Google Business Profile. We check every review against our client projects.

Relaunch support enquiry
Monique Schumacher
Monique SchumacherTeam Lead Content ManagementCall: +49 228 433 994 14

* Required

Please enter your name.

Please enter a valid email address, e.g. name@company.com.

For a call back.

Please enter your number with area code, e.g. +49 228 243 313 53.

Please tell us briefly what it is about.

Free and without obligation. We usually reply on the same working day.

Information on how we process your data: Privacy policy