Website Relaunch: Cost, Process, and the Priciest SEO Traps

A website relaunch is two projects in one: building a new website – and losing nothing of what the old one earned along the way. The second part gets underestimated regularly, and that is exactly where the most expensive mistakes happen. This article lays out both: what a relaunch costs, how it runs cleanly, and which SEO traps destroy rankings that took years to grow.

When a relaunch is due – and when a refresh is enough

Not every ageing website needs a rebuild. A refresh – new texts, current images, reworked sections – is enough as long as technology and page structure hold. A relaunch is due when the foundation is the problem:

• The technology is so outdated that every update is a risk – or updates stopped coming entirely.
• Load times stay poor despite optimization, because the foundation caps them.
• The design visibly costs trust – the website looks older than the company.
• The structure no longer matches the offering: services are missing, ranking content leads nowhere.

The rule of thumb: when the list of individual fixes grows longer and more expensive than the rebuild, the rebuild is the more honest calculation.

One note from practice, because it saves money: “I don’t like the design any more” is not on its own a reason for a relaunch. Where the technology holds, design can be reworked without touching a single address – and a move nobody needs is pure risk with no return. Check first whether the problem sits in the appearance or in the foundation.

Taking stock: the data that belongs before a relaunch

This is the section most relaunch quotes skip, and it is the most important one. Before anything gets designed, three exports belong on the table:

1. All indexed URLs with impressions and clicks from Google Search Console, twelve-month window. This is the list that decides what the new site must inherit – and it is usually longer than the page structure you carry in your head. Old guide articles, subpages from a former campaign, PDF files.
2. The pageviews from your analytics tool. Combined with point 1, it becomes clear which pages have search traffic and which only get clicked internally.
3. The pages that produced inquiries. Often only sales knows this, and it sits in no tool. A low-traffic page that brings two inquiries a year is worth more than one with a thousand views and no contact.

From these three lists comes one decision per URL: stays at the same address, moves (and needs a redirect), gets merged, or may go. That table later becomes the basis of the redirect mapping – build it at the start and you avoid tedious work under deadline pressure at the end.

What regularly stands out: a substantial share of the pages on a website that grew over years has not had a single impression in twelve months. Those may go, with a clear conscience. A relaunch is the cheapest moment to tidy up, because culling costs nothing extra here – later, every page that came along is maintenance effort.

What a relaunch costs

First the framing that was too brief in our own article for a long time: a relaunch is not the entry price of a new website. The entry range applies to a modest new build without taking over an existing site. As soon as the content and rankings of an existing site come along, the project sits one tier higher.

The full overview with every item is on our pricing page. What a relaunch adds beyond the development itself are two items a greenfield build doesn’t have:

• Content migration: reviewing, carrying over, and culling existing content. Manual work at twenty pages, its own sub-project at two hundred. The effort depends less on page count than on whether content gets carried over or rewritten.
• Redirect mapping: every old URL gets a defined destination. Meticulous work with a direct effect on visibility – and the first item missing from cheap quotes.

What does not drive the price, although it often feels like it: the number of design drafts and the number of images. What does drive it: special logic (configurators, booking, calculations), additional languages, connected systems, and the volume of content that gets rewritten instead of carried over. If you want to save budget, save it on the content nobody reads anyway – not on the redirect mapping.

Every figure here is an entry point, not a fixed price. It becomes a fixed price after the first conversation, once the scope is settled.

What’s in the price – and what comes on top

Because relaunch quotes are hard to compare, here is how we split it. Included with us: concept and page structure, design, implementation, carrying over existing content within the agreed scope, the complete redirect mapping, the technical launch check, and a handover session so you can maintain the site yourself afterwards.

Not included and, depending on the project, its own item: newly written copy, professional photography, translations, licences for fonts or images, integration with third-party systems, demanding data migration out of a shop, and ongoing operation after launch. Hosting runs directly through you – we don’t host client sites ourselves as a matter of principle, so the data and the contract stay with you.

The item most often missing from other quotes is the third from the top: the content. A quote that doesn’t name content migration either hasn’t planned for it or will bill it later.

How to make relaunch quotes comparable

Prices from different providers are hard to compare directly, because the same number hides different scope. Four questions create comparability – and they cost nothing:

1. Is the redirect mapping in the price, and for how many URLs? The answer “of course we’ll do that” without a number usually means nobody looked at Search Console.
2. Is content carried over or rewritten? That is the largest single item and the most common reason for follow-up invoices.
3. What does operation cost in the year after? A cheap rebuild on maintenance-heavy technology can cost more over five years than a pricier one on low-maintenance technology.
4. Who owns the code, the content, and the credentials afterwards? And does hosting run through you or through the agency? The answer decides how free you are later.

With those four answers in writing, two quotes with different totals suddenly become comparable – and sometimes the more expensive one turns out to be the cheaper one.

The five-year calculation

Deciding on a relaunch purely on build cost distorts the decision. Build and operating costs belong in one calculation – and operation is the item where a technology switch pays off.

A maintenance-heavy website needs ongoing updates, security care, and backups; with us that runs through WordPress maintenance from 99 € a month, depending on the package. A static Astro site doesn’t have that attack surface: no plugin zoo, no database, no weekly security updates – the care package starts at 40 € a month.

The difference sounds small and reaches four figures over five years. On top comes the part that appears in no calculation: time nobody spends on update aftercare, and outages that don’t happen. That is why we always raise the technology question in a relaunch – not out of preference, but because it is the one moment when switching costs nothing extra.

Said honestly: this calculation doesn’t work out for everyone. If you publish content daily, have several editors, or need features that have existed as a WordPress plugin for years, WordPress is cheaper – over five years too. The calculation pays off for sites that rarely change.

The process in six steps

1. Inventory. Which pages rank, which bring inquiries, which does nobody read? Search Console and analytics data decide what the new site must inherit – before anything gets designed.
2. Goals and structure. What should the new website deliver, for whom, with which pages? This is also where the technology decision falls – we’ve documented the decision path separately.
3. Content first. Texts and images get settled before development, not during it. Missing content is the most common reason relaunches take twice as long as planned.
4. Design and development. Built on a development environment – with feedback in fixed loops instead of permanent back-and-forth.
5. Redirect mapping and launch check. Every old URL gets its 301 redirect; the technical checklist runs: indexability, load times, forms, structured data.
6. Launch and observation. After going live, Search Console gets watched for weeks: crawl errors, 404 hits, ranking movement. A relaunch is only finished once the curves are stable.

Four to eight weeks from the final briefing is realistic. And the step that sets the pace is almost always the same one: step 3. Technology and design can be planned; content can’t – because it needs decisions that often involve several people.

What sits on your side and sets the tempo: sign-off on the content, one person with authority to decide on interim questions, and the credentials – hosting, domain management, Search Console, the existing CMS. Missing credentials are the least spectacular project blocker there is, and they hit a surprising number of relaunches shortly before launch.

Redirect mapping: the mandatory exercise

Because this is the item with the greatest damage potential, here is what it actually involves. The rule is simple and inconvenient: every indexed URL gets a 301 redirect to its closest content equivalent – not wholesale to the homepage. A blanket redirect to / is, for Google, practically the same as a 404, only harder to diagnose.

Our generator takes the tedious part off your hands – paste the old-new list, copy the finished .htaccess rules:

# Enter redirects above …

Also available as a standalone page with all guides: redirect generator.

Three details that checklists usually miss and that still matter:

Where the redirect technically lives is not irrelevant. A real 301 comes from the server – from .htaccess on Apache, from the server configuration on nginx. Some systems and frameworks offer their own redirect settings that internally only produce a meta-refresh or a JavaScript redirect. That looks identical in the browser and does not pass the signals reliably. We therefore handle moves at server level on principle and use framework redirects only in addition. If in doubt, check the status code of an old URL – it has to come back as a literal 301.

Resolve redirect chains. If a website already has two moves behind it, URL A points to B and B points to C. After the relaunch, D arrives, and the chain becomes a cascade. Every old address should point directly at the final destination, not via intermediate stops.

What often gets forgotten: addresses with parameters, paginated lists (/blog/page/3/), files such as PDFs, image URLs that are linked externally, and the paths in the old sitemap. The http-to-https and www-to-non-www redirects deserve one pass as well, because a hosting change likes to drop one variant.

After launch, the mapping table gets measured once in full: call every old URL and check the status code. It is boring and it finds something every time.

The priciest SEO traps in a relaunch

Almost every relaunch damage we see in audits traces back to one of these mistakes:

1. Forgotten redirects. Old URLs die with 404s, and with them the rankings and every external link that ever pointed at them. See above – this is the mistake with the biggest lever.
2. Changing URLs without need. Every changed URL is a move with friction loss. Where the structure doesn’t get decisively better, addresses stay as they are.
3. Deleting ranking content. “The old guide page doesn’t fit the new design” is not a reason to delete a page that brings monthly visitors. Only the check against search data decides what may go.
4. Taking noindex live. The development environment is blocked for Google – and that block travels to the live site alarmingly often. A classic with total-loss potential that costs two minutes in the launch check.
5. Launching slower than before. If the new site loads heavier than the old one, the relaunch wastes its biggest lever. Load time is a design decision in a rebuild, not an afterthought.
6. Reinventing titles and meta descriptions. Pages that rank well often have a title that hits the search term precisely. In the relaunch it gets reworded for tone – and the click-through rate falls. On ranking pages the title stays, even when it doesn’t match the new wording.
7. Losing structured data. Review stars, opening hours, FAQ markup, product data: whatever sat in the old site as schema markup and was visible in search results has to be present again in the new one. Otherwise the rich results disappear and the click-through rate drops at an unchanged position.
8. Leaving the old sitemap in place. A sitemap that keeps reporting the old addresses systematically sends Google to redirects. Submit the new sitemap, remove the old one.

The first weeks after launch

A relaunch doesn’t end on launch day. What gets watched in the weeks afterwards – and what of it is normal:

Day 1 to 3. Spot-check status codes of old URLs, submit the new sitemap in Search Console, test forms (including whether the emails actually arrive), verify tracking. Positions fluctuating in these days is expected: Google has to crawl and reassign the new addresses first.

Week 1 to 2. Look at the indexing report in Search Console. Two numbers matter: is the count of indexed new pages rising, and are 404 errors appearing on addresses that previously had impressions? The latter is the clear signal for a missing redirect and belongs fixed the same day.

Week 3 to 8. Now visibility becomes meaningful. A dip that closes again is normal. A permanently falling count of indexed pages, or a drop that hasn’t recovered after four weeks, is not – then something structural is wrong, and it needs finding rather than waiting out.

In this phase we deliberately resist the reflex to adjust immediately. Every change in the first week extends the time until you can tell what the move actually did. The exception is errors with a clear cause – a missing redirect or a stray noindex gets fixed at once, not observed.

Accessibility: a relaunch is the cheapest moment

Since 28 June 2025 the European Accessibility Act has applied to services for consumers – simplified: anywhere private customers order, book, or conclude a contract online. Purely informational sites and micro-enterprises are generally exempt. We are developers, not lawyers; whether your site is covered in your specific case belongs with a lawyer. The details are in Accessible websites: what the EAA requires.

For relaunch planning, one practical point matters most: keyboard operability, sufficient contrast, a sensible focus order, and forms whose error messages a screen reader also picks up cost almost nothing in a new design – they are a question of the decisions made while drafting it. Retrofitting the same things into a finished site means touching colours, components, and templates all over again. If you’re rebuilding anyway, don’t leave it on the table, even where there is no obligation.

Carrying AI visibility into the relaunch

Search traffic no longer arrives only from classic result lists, but also from AI answers that cite sources. A relaunch is the moment when the groundwork for that can be built in at no extra cost: clean, machine-readable structure, structured data, clear statements instead of marketing fog, and content that actually answers a question rather than circling it.

That is not a separate project and not a product you buy – it is largely the same set of measures that make a site better for people too. What sits behind it and which levers genuinely exist is summarised in Website visibility in AI search.

The technology switch as a relaunch opportunity

If you are rebuilding anyway, don’t skip the technology question: a relaunch is the one moment where switching from a maintenance-heavy setup to a static architecture costs no extra migration. Whether that pays off for your case is weighed honestly in Astro vs. WordPress – and when a move to a headless system makes sense, in the replatforming article.

In-house or with an agency

A fair question, and the answer isn’t automatically “agency”. In-house works when three things come together: someone genuinely has the time and not just on paper, the website is modest in size, and the redirect mapping gets taken seriously. For a small site with ten subpages and no meaningful search traffic, rebuilding with a website builder is a sensible decision.

The part where in-house regularly fails is not the design. It is the move: assembling the complete URL list, pointing every address at its content equivalent, working through the launch check, and then watching Search Console for weeks. That is unspectacular work, easy to postpone – and its consequences only show up weeks later, when the cause is hard to attribute.

The trade-off in one sentence: if your website measurably brings in inquiries, the risk of a lost ranking usually outweighs the fee. If it doesn’t, the real question isn’t the technology anyway, but what the new site should do better in substance.

An honest conclusion

A good relaunch is unspectacular: visitors see a faster, clearer website – and Google sees the same content under cleanly redirected addresses. The costs are plannable when migration and redirects are priced in from the start instead of arriving as a surprise. And the biggest mistake isn’t a technical one: it is the relaunch without a look at your own data – replacing a website without knowing what worked about it.

If you take one order of operations from this, take this one: export the data first, then decide whether it needs to be a relaunch at all, then build the mapping table – and only after that, talk about design. The relaunches that go wrong do it the other way round.

Thinking about a relaunch? Send us your website – we’ll look at technology, load times, and search data and tell you honestly whether it has to be a rebuild or whether a refresh will do: drop us a line. Fixed price and process: have a website built.