SEO equity, conversion, performance, analytics, and content continuity are all at risk. We plan the migration, protect what works, and verify results before and after go-live.
A website relaunch touches every system your site connects to: search rankings, analytics, conversion tracking, CDN configuration, and CMS editorial workflows.
Most relaunch failures are not caused by bad design. They are caused by missing redirect plans, broken analytics, and no performance baseline to compare against.
We treat a relaunch as a system migration. That means planning before building, measuring before launching, and verifying results in the six weeks after go-live.
A relaunch without a redirect plan and crawl verification can destroy organic rankings that took years to build. Google must find the new URLs and transfer equity. Without a mapping, it cannot.
Analytics tracking breaks on relaunches more often than it stays intact. Goal completions stop recording. Funnel data becomes useless. The team operates blind on the most critical measurement period.
A new design that has not been tested against real user behavior often performs worse on conversion in the first weeks. The visual improvement and the business improvement are not the same thing.
Every relaunch engagement begins with a content and URL audit before a single design file opens. We need to know what the current site does well before we decide what changes. Protecting existing performance is as important as building new capability.
Before any URL or structure changes, we audit existing rankings and traffic. Redirect mapping is defined before development starts. Post-launch, we monitor crawl errors, index coverage, and ranking movement for a minimum of six weeks.
Many teams do not need a full rebuild. A content, performance, and UX audit often identifies targeted improvements that deliver faster results than starting from scratch. We scope the minimum viable change that fixes the business problem.
Three things cause most relaunch failures: no redirect plan, no performance baseline, and no analytics continuity. Traffic drops, rankings tank, and the team cannot measure whether the new site is better because tracking was not set up correctly.
Discovery and planning: two to three weeks. Build: six to twelve weeks depending on scope and content volume. Post-launch stabilisation sprint: six weeks minimum. Rushing any phase increases migration risk.
The full Website & Relaunch service is at services/websites, covering discovery and information architecture, UX design, WordPress engineering, and post-launch tuning.
Performance is a core part of every relaunch. See the website performance guide for how we set baselines, measure Core Web Vitals, and verify results against real devices.
If conversion rate is the primary outcome metric for the relaunch, see the conversion optimization guide. we treat CRO as part of the relaunch scope, not a separate workstream.
For WordPress-specific relaunches, including migration from page builders, multisite setups, and WooCommerce rebuilds, see the WordPress agency page.
We are the right fit if you want a team that pushes back when it matters.
Engagements with commercial outcomes on Work. Team bios and operating model on About. Nothing to download. Review it before you commit to a call. Open to review. Commit when ready.