Article · Halo
When to refresh your site—and when to rebuild
Not every tired site needs a ground-up rewrite. Here is how we decide with clients.
Start with goals, not aesthetics
A refresh makes sense when the information architecture still matches how buyers choose you, the brand evolved modestly, and the codebase is maintainable. A rebuild makes sense when navigation fights the user, technical debt blocks shipping, or integrations need a cleaner foundation.
We look at analytics, form abandonment, and qualitative feedback from your team. If the site hides your best proof or buries contact paths, that is a structural issue—not something a new font solves.
Signs a refresh is enough
Templates are consistent, CMS workflows work, and performance issues are mostly asset weight or caching. Typography, color, and component polish can lift perceived quality without re-platforming. You keep URLs stable and avoid SEO disruption when changes are disciplined.
Marketing needs new landing pages often? A refresh can include modular sections your team can reuse, as long as the underlying system supports it without hacks.
When rebuild is the honest answer
Multiple conflicting page builders, duplicate URLs, or inaccessible admin experiences slow everyone down. Security rot—unpatched plugins, ancient runtimes—also pushes toward rebuild because band-aids accumulate risk.
Rebuilding is not punishment; it is a chance to simplify hosting, tighten performance budgets, and align content with how you sell today. We scope the smallest viable launch, migrate redirects carefully, and keep search engines informed.
Hybrid paths
Sometimes we phase work: stabilize hosting and performance first, then redesign high-traffic templates, then retire legacy sections. The right sequence limits downtime and spreads investment across quarters.