Website relaunch is a comprehensive overhaul of an existing website, often with new design language, new technology stack, new CMS, or new content. Unlike website migration (URL change), the domain typically does not change, but almost everything else can. A relaunch is a great opportunity to optimize but also carries major SEO risks if not done correctly.
What is a website relaunch?
A website relaunch is not the same as a website redesign. A redesign might only change the visual appearance. A relaunch is a more comprehensive overhaul:
- New design language and aesthetics
- New or revised URL structure
- Switch to new CMS (WordPress to Webflow, etc.)
- Revised information architecture and navigation
- Modernized technology stack
- Revised or new content
- New functionality or features
A relaunch is a large project - typically 3-6 months of planning and development and hundreds of thousands of euros for a mid-size website.
The reasons for a relaunch vary:
- Outdated website: Current website is 5+ years old, feels outdated
- Performance issues: Website loads slowly, does not work on mobile
- CMS switch: Switch to better or simpler CMS
- Brand refresh: Company is rebranding, website should reflect new brand
- Growth: Website cannot grow with the company anymore
- Market changes: New market position requires new website messaging
Website relaunch vs. Website migration
These are often mixed up but are different:
| Aspect | Relaunch | Migration |
|---|---|---|
| Domain | Same domain typically | Often domain change |
| URL structure | Can change completely | Often 1:1 mapping |
| Design | New design essential | Design can stay the same |
| Content | Often revised/reorganized | Often same, structurally moved |
| CMS | Can lead to new CMS | Can lead to new CMS |
| Complexity | Very complex | Complex but more structured |
Relaunch planning and preparation
Step 1: Discovery and audit (week 1-2)
- Audit current website. Which pages work well?
- Analyze traffic and keyword rankings
- Gather user feedback. What works, what does not?
- Catalog all URLs
- Analyze backlinks and referrers
Step 2: Strategic planning (week 3-6)
- Plan new URL structure
- Define new information architecture
- Work out redirect strategy
- Content audit. Which pages to keep, update, or delete?
- Specify design requirements
- Choose CMS if needed
Step 3: Design and development (week 7-16)
- Create wireframes and design mockups
- Build staging environment
- Perform development
- Migrate/revise content
- Perform testing (functionality, performance, browser compatibility)
Step 4: Finalization (week 17-18)
- Final QA and testing
- Implement 301 redirects
- Final SEO element review
- Performance optimization
- Launch planning and communication
SEO during a relaunch
The most important thing at a relaunch is that SEO is not added at the end as an afterthought. SEO should be part of planning from the beginning.
SEO during relaunch:
- Preserve well-performing URLs: If a page ranks well, try to keep the URL similar or at least redirect to the new URL
- Optimize your CMS for SEO: Make sure the new CMS supports meta tags, XML sitemaps, schema markup
- Create a redirect map: Each old URL should redirect to a thematically relevant new URL
- Check core web vitals: New website should load fast and be responsive
- Implement schema markup: Use structured data for better SEO
- Plan for featured snippets: Optimize content for position 0
- Mobile-first indexing: New website must be mobile-optimized
Content strategy during relaunch
A common mistake is deleting massive amounts of content during a relaunch. That is SEO-harmful.
Content audit matrix:
| Page status | Traffic/ranking | Action |
|---|---|---|
| High performer | High | Keep and polish, keep URL similar |
| Mid performer | Medium | Keep but improve and optimize |
| Low performer (relevant) | Low but thematically relevant | Keep and optimize to improve performance |
| Low performer (not relevant) | Low, outdated or off-topic | Delete with 301 redirect to relevant new page |
| Outdated content | Variable | Update or delete |
The rule: Never delete a page without a 301 redirect. Redirect to a similar new page.
Post-relaunch monitoring and optimization
Week 1 (critical):
- Check Google search console daily for crawl errors
- Test website functionality (forms, links, etc.)
- Start user analytics
- Monitor user feedback
- Monitor performance
Month 1 (recovery phase):
- Monitor traffic movements vs. pre-relaunch
- Track rankings for important keywords
- Observe crawl statistics in search console
- Ensure sitemap coverage is 100% ideally
- Check mobile usability errors
Month 2-6 (optimization phase):
- Rankings should rebuild or improve
- Optimize low-performing pages based on data
- Build backlinks for new top pages
- Optimize internal link structure
Relaunch risk mitigation
1. Staging environment before launch: Build the completely new website in a staging environment and test everything before going live. Never go live on Friday or before weekend.
2. Backup old website: Keep old website archived 12+ months for emergency fallback.
3. Gradual rollout if possible: Instead of changing everything at once, you could (if architecture allows) roll out section-by-section.
4. Communication to stakeholders: Sales, customer success, support should know a relaunch is coming. New page structure, new lead generation pages, etc.
5. Quality assurance plan: Perform extensive testing. Feature testing, regression testing, performance testing.
Common relaunch mistakes
1. Change too much at once: If you change domain, URL structure, content, design, and CMS all at the same time, it becomes impossible to debug if something goes wrong.
2. Completely delete old website: Even if 301 redirects are set, give the old website time to die (6-12 months).
3. SEO as afterthought: SEO should be part of planning from the beginning, not at the end.
4. No redirects or wrong redirects: This is the #1 relaunch mistake. Give old URLs new homes. Never to homepage or generic 404.
5. Not monitoring after launch: The first weeks after launch are critical. You must monitor daily for errors.
A website relaunch is a great opportunity to modernize and optimize. But it requires planning, testing and post-launch monitoring. The best relaunches are where users notice minimal difference. Everything works better, but the structure stays similar.