PIPELINE
EN
DeutschEnglishFrançaisItalianoEspañol中文
INQUIRY

Guide

Implement a website relaunch: step by step

The path from decision to live operation — in the order that has proven effective in small businesses, including the points where projects typically get stuck.

Request assessment ↗Website relaunch
Quote upon request5 to 10 weeksAs of 2026
In short

A website relaunch is implemented by first identifying the bottleneck, then narrowing it down, and only then implementing it. The implementation itself takes 5 to 10 weeks; a project is almost never delayed by technology, but by missing content, access, and decisions.

01 — Getting started

Where to begin

  1. Name the bottleneck

    Not the most interesting thing, but what takes the most time. A week of tracking what repeats delivers a more realistic list than any workshop.

  2. Define a small scope

    One process, one measurable goal. What works gets expanded — what doesn't costs little.

  3. Survey the starting situation

    Which content, data, and access is available. For a website relaunch, this is the factor that most strongly influences effort and duration.

  4. Decide who is responsible

    For the implementation and for operations afterward. Without this definition, every system becomes outdated.

  5. Only then request proposals

    With a clear scope, proposals become comparable. Without it, you get numbers that have nothing to do with each other.

02 — Process

The steps in detail

  1. Analysis

    Which pages bring visitors, which search terms, which inbound links.

  2. Plan structure

    New structure with mapping of every old URL. That's the core, not the design.

  3. Build

    New site is built in parallel, the old one stays online until the end.

  4. Switch and monitor

    Migration with redirects, followed by four weeks of close monitoring.

03 — Participation

What we need from you

  • A contact person who can make decisions — not just forward them.
  • Access to the affected systems, in time and not on launch day.
  • Real examples from daily business — the messier, the more useful for testing.
  • Two to four hours for coordination, distributed over the project duration.
  • An answer to the question of what success means. Without it, nothing can be assessed afterward.

04 — Bottlenecks

What typically causes delays

  • Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
  • Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
  • Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
  • Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.

05 — Questions

Frequently asked questions

Is a relaunch worth it if we're renaming soon anyway?

Not in that order. Clarify the renaming first, then relaunch — otherwise you build a site that needs adjustment again shortly after.

Do we have to go offline during the relaunch?

No, the old site stays online until the switchover day. The change happens on a set date, usually outside business hours, and typically takes only a few minutes.

Should we carry over all content?

No. Pages that bring neither visitors nor serve a purpose are removed — that makes the site clearer and the remaining pages stronger. What brings visitors is carried over and improved.

When is a relaunch overdue?

When the site doesn't work on mobile, the content management system no longer receives security updates, or you can't change content yourself. A merely outdated appearance is the weakest reason of all.

What happens to our email addresses?

They remain untouched as long as the domain stays the same. We still check the settings before the move, because an incorrectly set record can stop mail delivery.

Will we lose Google rankings with a relaunch?

Only if you do it wrong. Short-term fluctuation over two to four weeks is normal, a lasting drop is not. The cause is almost always the same: missing or incorrect redirects. We create the list before the move and check it afterward.

Can we switch over gradually?

For larger sites, yes — section by section. It takes longer but spreads the risk and cost.

06 — Next

Related pages

Website relaunch by region

Next step

Send us a few sentences about your project.

We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.

Send inquiry ↗ office@pipeline-solutions.at OR +43 681 207 64 203