Start with the Constraint, Not the Preference
Businesses often choose redesign or rebuild based on opinion. Better decisions come from diagnosing constraints: technical debt, content architecture limits, and conversion bottlenecks.
When Redesign Is Usually Better
- Core platform remains stable and maintainable
- URL structure and content equity can be preserved
- Conversion issues are primarily UX/message-related
- Timeline or budget favors iterative improvement
When Rebuild Is Usually Better
- Platform limitations block required functionality
- Technical debt makes changes expensive or risky
- Information architecture is fundamentally broken
- Major repositioning requires full content/system rethink
Risk-Control Checklist
- Preserve and map high-value URLs
- Validate tracking and analytics parity
- Run launch-readiness QA before cutover
- Schedule post-launch stabilization windows
Practical Recommendation
If incremental improvements can achieve your business goals with lower risk, redesign first. If structural constraints keep recurring, rebuild with a long-term architecture plan.
Need help applying this strategy to your business website?
Book a Website Strategy Consultation