In short: A relaunch is a move. Rankings disappear because of missing redirects, deleted content and a noindex left behind in staging, almost never because of the new design. This website relaunch guide walks through the order that protects visibility: build a content inventory first, map every old URL to a new one, then work a fixed checklist on launch day. At Okapi Digital in Frankfurt we plan every relaunch backwards, starting with the URL map and ending with the design.
Most relaunch projects start on instinct. The site looks dated, the CMS is painful to use, a competitor has just published something better looking. Three months later the new site is live, and the enquiries stop. The new site is rarely the problem. The connection to Google was cut somewhere along the way.
This article sets out the process that prevents that: whether a relaunch is justified at all, the phases, the URL mapping, the launch-day checklist and what to measure in the four weeks that follow.
When Is a Relaunch Justified, and When Is a Refresh Enough?
A relaunch replaces technology, structure and design. A refresh swaps the surface and the content while the foundation stays. Choosing wrong costs you either money or patience.
The arguments for a relaunch are technical. The CMS no longer gets updates. The site is barely usable on a phone. Load time cannot be improved because the theme is in the way. A structure that cannot absorb new service pages is a clear signal too, as is a merger, a rebrand or a repositioned offer.
The argument against is when the complaints are purely cosmetic. Dated photos, weak copy, a call to action nobody notices: those are jobs for an afternoon or a week, not a quarter. We covered what a conversion-focused rework actually changes in web design that converts.
| Situation | Refresh is enough | Relaunch needed |
|---|---|---|
| Design looks dated, technology is fine | ✓ | |
| Copy and images are old | ✓ | |
| Site is unusable on mobile | ✓ | |
| CMS no longer receives security updates | ✓ | |
| Load time stays above 3 seconds despite tuning | ✓ | |
| New services do not fit the structure | ✓ | |
| Brand, name or positioning is changing | ✓ |
Website Relaunch Guide: What Happens in Each Phase?
A relaunch has eight phases. The order matters more than the pace: start with design and you will be making decisions about content nobody has counted yet.
The website relaunch process in eight phases
| Phase | What happens | Typical duration |
|---|---|---|
| 1. Analysis and goals | Capture current Analytics and Search Console data, agree on goals | 3–5 days |
| 2. Content inventory | List every URL, score it, decide what happens to it | 3–5 days |
| 3. Structure and URL map | New site structure, old URL mapped to new URL | 3–5 days |
| 4. Concept and design | Wireframes, design drafts, sign-off | 1–2 weeks |
| 5. Build on staging | New site built in a shielded test environment | 2–4 weeks |
| 6. Content and testing | Load content, test forms, tracking and redirects | 1 week |
| 7. Launch | Go live against a fixed checklist, on a weekday morning | 1 day |
| 8. Monitoring | Watch indexing, rankings and conversions, fix what breaks | 4–8 weeks |
That puts the total at three to four weeks for a compact business site and six to eight weeks for a larger one with ten pages or more. Phase 8 keeps running after the project feels finished.
Why Is the Content Inventory the Most Important Step?
The content inventory is a spreadsheet listing every single URL on your current website. It comes from three sources: the XML sitemap, a crawl with a tool such as Screaming Frog, and the Google Search Console performance report for the last twelve months.
For each URL you record the title, clicks and impressions from Search Console, inbound links, the date it was last updated, and a decision. There are only four decisions available: keep, rewrite, merge or delete.
That spreadsheet answers the questions relaunches usually fail on. Which ten pages bring the most traffic? Which subpage ranks for a keyword the new concept has dropped? Which old blog post carries backlinks you should not throw away? Without an inventory, pages like these get deleted quietly and the loss only surfaces weeks later.
Every page that disappears needs a successor. A deleted article about a service you still offer gets redirected to the new service page. Only content with no value and no links can vanish without a replacement.
What Does Website Relaunch SEO Actually Involve?
Website relaunch SEO is mostly one job: making sure every address Google knows about still lands somewhere sensible after the move.
Keep URLs where you can. Every unchanged URL is one redirect fewer and one failure point fewer. Change URLs only when the old structure causes real problems, such as parameters like ?id=447 or a language setup you are replacing.
Use 301 redirects for everything else. A 301 status code tells Google the address has moved permanently and passes the old page's signals along. A few rules:
- Every old URL gets exactly one target: the new page that matches it most closely.
- Redirecting all old pages to the homepage is treated like a 404 by Google. It is the single most common mistake.
- Resolve redirect chains: old → new, not old → interim → new.
- The redirect list is not a one-off. It stays in place permanently, years later included.
Carry titles, meta descriptions and headings across. Pages that rank well rank partly because of their wording. If a redesign replaces every H1 with a brand slogan, the terms the page was found for disappear with it.
Finally, check structured data and internal links. FAQ markup, opening hours and reviews should reappear on the new site. Internal links point at the new targets instead of routing through redirects. There is more on the technical foundation on our SEO services page.
What Kills Traffic After Launch?
After go-live there is a short list of mistakes that reliably destroy visibility. All of them are avoidable, and all of them happen regularly.
| Mistake | Effect | How to check |
|---|---|---|
| noindex left over from staging | Pages drop out of the index one by one | Source code plus URL inspection in Search Console |
| robots.txt blocks the whole domain | Google stops crawling entirely | Open yourdomain.com/robots.txt |
| Missing or blanket redirects | 404 errors, lost backlinks | Run the old URL list through a crawler |
| Canonical tags still point at staging | Google indexes the wrong address | Spot-check the source code |
| Sitemap still lists old URLs | Crawl budget is wasted | Submit the new sitemap |
| Tracking not carried over | You cannot see the damage | Send a test enquiry through the form |
| Content trimmed instead of migrated | Pages rank for fewer terms | Compare word counts on your top pages |
The first item is by far the most expensive. A staging environment belongs on noindex, otherwise it competes with the live site. That is exactly why the setting is so easy to miss during the move.
How Do You Test on Staging Without Confusing Google?
A staging environment is a complete copy of the new website on its own address. You shield it three ways: password protection at server level, noindex in the source code, and a robots.txt that excludes all crawlers.
Password protection is the most reliable of the three, because it also stops someone sharing the test version by link and polluting your analytics data. Relying on robots.txt alone risks the address showing up in search results anyway.
Before go-live, crawl the staging version once in full. That crawl finds broken links, missing alt text, duplicate titles and pages without meta descriptions while fixing them still costs nothing. After launch, run the same crawl against the live site.
Where Do Core Web Vitals Fit In?
Core Web Vitals are Google's user-experience metrics: LCP for how fast the largest visible element renders, INP for how quickly the page responds to input, and CLS for visual stability while loading. They feed into rankings, and a relaunch makes them unusually easy to damage.
The reason is mundane. New designs arrive with large hero images, video, web fonts, animation libraries and chat widgets. Each element is defensible on its own, and together they make the new site slower than the old one. So measure the existing site's numbers before you start and treat them as the minimum the new site has to beat.
In practice that means serving images in modern formats, hosting fonts locally, limiting third-party scripts to what you actually need, and setting fixed dimensions for images and embeds so nothing jumps while the page loads.
The Website Relaunch Checklist for Launch Day
Launch day runs on a list. Schedule it for a weekday morning when everyone involved is reachable, and work through the items in this order.
Before you switch over
- Full backup of the old site and its database
- Redirect list imported and spot-checked
- Every form submitted, receipt of the emails confirmed
- Legal notice, privacy policy and cookie banner reviewed
- SSL certificate active on the live domain
Immediately after you switch over
- noindex removed, verified in the live page source
- robots.txt allows crawling
- Canonical tags point at the live domain
- New XML sitemap submitted in Google Search Console
- Redirects tested against your twenty most important old URLs
- Analytics and conversion tracking are recording data
- Homepage and three subpages submitted through URL inspection
- Whole site clicked through on phone and tablet
- Google Business Profile, social profiles and email signatures updated
Print the list or turn it into a task where each line gets ticked off. A website relaunch checklist only works if someone actually runs it on the day you switch.
What Do You Watch in the First Four Weeks?
A relaunch is not finished at go-live. The first four weeks tell you whether the move worked.
Week 1: Check the page indexing report in Search Console daily. Rising 301 counts and some new 404s are expected. Every 404 gets a redirect. Check daily that form enquiries are arriving, too.
Week 2: Compare rankings for your twenty most important keywords. Mild movement is normal while Google re-evaluates the new pages. A drop across every keyword at once points at a technical problem instead, usually at indexing level.
Week 3: Look at the Core Web Vitals report in Search Console. It runs on real user data, so it only fills up after a few weeks. Review the pages with the highest bounce rates alongside it.
Week 4: Compare clicks and impressions with the period before the relaunch and, more importantly, count enquiries. A new site with ten percent fewer visitors but twice as many enquiries was a success.
What Does a Website Redesign Cost?
Website redesign cost follows scope, not looks. The drivers are page count, custom design, special features and how much content has to be migrated and rewritten.
For orientation: our website development starts at €999 for a compact site with a handful of pages. The most popular package for growing businesses with four to six pages, a CMS and full on-page SEO sits at €3,490. Projects with ten pages or more and custom functionality start at €8,490. After launch, ongoing care starts at €49 per month for hosting, backups and security updates.
There is a full breakdown, including the running costs, in how much a professional website costs.
Conclusion
A relaunch is a controlled move. The value of a website sits in its content, its addresses and the trust Google has built up over years. Secure those three things before the first design draft and you can replace the surface freely without losing the foundation.
The work that pays off most is invisible: the content inventory, the redirect list and the checklist on launch day. Design decides whether visitors stay. Those three documents decide whether any arrive.
Planning a relaunch and want to know which pages you absolutely have to keep? Book a free intro call. We will look at your current site, name the risks specifically, and tell you honestly whether a relaunch or a refresh is the right call.
