Most relaunch inquiries that reach us begin with a sentence about looks: the site feels old. That is rarely the real reason — and when it is the only one, we often advise against a relaunch.
A relaunch is worth it when the existing system has become a growth problem. This text helps you recognise that, choose the right scope, and avoid the mistakes that make a relaunch expensive.
How to tell the system is holding you back
The signals are rarely dramatic. They are friction in daily work that everyone has got used to:
- Every new page is a special case. A landing page for a campaign takes a week and a person who "knows the template".
- Content is maintained twice. The same service sits on three pages, and when something changes one gets forgotten.
- The site is slow and nobody knows why. Plugins, themes, scripts from three generations of owners.
- Tracking is guesswork. Nobody can say which channel produced the last inquiries.
- Integrations break at every update. The form that writes to the CRM has only done so sometimes since the last plugin update.
- The team works around the website. Proposals go out as PDF, content via social media, because the site is too cumbersome.
Two of those are everyday life. Four of them are a reason for a relaunch — regardless of how the site looks.
The three scopes
Relaunch is not a fixed term. There are three sensible sizes, and the choice decides budget and risk:
Redesign. Same structure, same content, same URLs, new design. Sensible when the system holds and only the surface no longer fits. Low SEO risk, because nothing changes about addresses and content.
Restructuring. New page structure, revised content, partly new URLs, on the existing or a new system. Sensible when the site no longer leads visitors where they want to go. Medium risk — the redirects have to be right.
Rebuild. New system, new structure, new content. Sensible when the old system itself is the problem. Highest risk and highest benefit — here the migration plan decides between success and lost rankings.
The most common mistake is doing a rebuild where a restructuring would have done. The second most common is the opposite: a redesign on a system that has the same problems again in two years.
What a new system has to do
If it comes down to a rebuild, these are the requirements we set for the target system — regardless of the specific tool:
- server-rendered HTML so search engines and AI crawlers see the site in full without JavaScript
- load time as architecture, not as an afterthought — measured against what Google sees from real user data
- content that exists once and is displayed in several places, instead of being copied
- page types instead of individual pages, so the twentieth landing page appears as fast as the first
- forms with a clean handoff to CRM and analytics, including source
- multilingual considered from the start, even if the second language comes later
- maintainability — someone who is not the original team can continue
Which tool delivers that depends on the project. For marketing sites with little structured content often Framer; for content- and product-driven sites usually Nuxt. The trade-off is in Framer vs. Webflow and Migrating from Framer to Nuxt.
The mistake that ruins relaunches
A relaunch without a migration plan loses visibility. Not sometimes — almost always. The cause is banal: old URLs disappear, new ones appear, and nobody documented the connection. Google sees hundreds of dead addresses and a new site without history.
The plan is unspectacular: a full crawl of the old site before starting, a URL concept that changes as few addresses as possible, a redirect list without chains, sitemap resubmitted, four weeks of observation. That costs days and saves months.
The second mistake: content last
Design and technology are finished, and then the copy is missing. Launch slips by weeks, and what finally goes live is the old copy in a new layout.
Content belongs at the beginning. Who says what on which page is a structural decision, not busywork after the design. With us the copy framework stands before the first draft — not as finished text, but as one statement per page.
How long it takes and what it costs
A redesign on the existing system: four to six weeks. A restructuring: six to ten. A rebuild with migration: eight to fourteen, depending on scope and the pace of feedback.
On budget, everything hangs on scope; the orders of magnitude are in What does a website cost?. What we do before every proposal: an inventory that says which of the three scopes is the right one. Sometimes the result is that a relaunch is not the best investment right now — then we say so.
When you should still wait
If the site loads fast, converts cleanly and the team can maintain it without detours, a relaunch is too early. Then smaller steps bring more: improve conversion where people drop off, set tracking up cleanly, deepen the three most important pages.
If you are unsure which situation your site is in, write to us briefly — an inventory is the fastest route to a reliable answer.
