How long does a website relaunch take? Timeline from analysis to go-live
Realistic relaunch timelines: from a compact redesign in 6–10 weeks to a relaunch with CMS switch and multi-language support in 4–7 months.
Website Relaunch Duration
The short answer
Compact relaunch (design refresh, CMS stays): 6–10 weeks. Mid-size project (new design, content): 3–5 months. Large relaunch (CMS switch, migration, multi-language): 4–7 months.
The short answer: a compact relaunch with a design refresh on the existing CMS takes 6–10 weeks; mid-size projects with a new design and content rework take 3–5 months. Add a CMS switch, extensive content migration and multi-language support, and 4–7 months are realistic. The underestimated time factor is rarely the technology – it is content, approvals and the SEO migration.
As a development partner – made in Germany, based in Leer, East Frisia – we plan relaunch projects backwards from the desired go-live date, ideally outside your peak season. For budgets, see the website relaunch cost calculator; for ongoing operations afterwards, the website maintenance calculator helps.
The phases of a website relaunch on the timeline
| Phase | Duration | Scope |
|---|---|---|
| Analysis & concept | 2–4 weeks | Inventory, goals, information architecture, wireframes and the CMS decision. The most important fork in the road: keep or switch. |
| Design | 2–5 weeks | Design system, page types and responsive layouts. A refresh of existing brand elements is much faster than a completely new look. |
| Implementation & CMS setup | 4–10 weeks | Templates, components, features and CMS configuration. With a CMS switch, features from the old system must additionally be rebuilt. |
| Content & SEO migration | 2–6 weeks | Migrating and reworking content, redirect mapping (301), meta data and structured data. The most important protection against traffic loss after go-live. |
| Testing & go-live | 1–3 weeks | Device tests, forms, performance, accessibility and the final switchover – with ranking monitoring in the weeks after. |
What really influences website relaunch duration
These factors decide whether your relaunch lands at the lower or upper end of the range:
- CMS strategy: a switch (e.g. to a modern or headless CMS) extends the project by 4–8 weeks compared with keeping it.
- Content volume: hundreds of pages needing rework are the most common cause of delays – prioritise content early.
- Approval processes: the more departments sign off texts and designs, the more generous the buffer should be.
- SEO requirements: clean redirect mapping and meta migration take time but prevent 30–60% traffic loss.
- Multi-language support: every additional language adds translation, review and QA effort.
Plan timeline and budget together
In a free initial consultation we clarify scope, milestones and realistic dates for your project – made in Germany, from Leer in East Frisia.
FAQ
FAQ: Website Relaunch Duration
How long does a small website relaunch take?
A design refresh on the existing CMS with largely migrated content is realistic in 6–10 weeks – including concept, implementation and testing. Prerequisites are fast approvals and a clear page scope.
How long does a relaunch with a CMS switch take?
With a CMS switch, 4–7 months are realistic: features of the old system must be rebuilt, content migrated and editors trained. The switch still pays off when the old CMS has reached security or feature limits.
What delays website relaunches most often?
Underestimated content work and long approval loops. Texts, images and translations should be produced in parallel with development – not only once the templates are finished.
When is the best time for go-live?
Outside your strongest sales season and never right before weekends or holidays. Plan two weeks of monitoring after go-live to check redirects, rankings and forms.
Can a relaunch be accelerated?
Yes: start content migration early, bundle approvals, prioritise the page scope for go-live (add further pages later) and only switch the CMS if truly necessary. An experienced partner with relaunch checklists saves additional loops.