Website redesign checklist: rebuild vs refresh
Signals that a visual refresh will not fix conversion—and when a full rebuild pays off
Not every tired website needs a full rebuild. Some need clearer hierarchy, faster pages, and honest messaging on the same foundation. Others are fighting the CMS, the information architecture, or a stack that cannot carry the next offer. This checklist separates a refresh from a rebuild.
When a refresh is enough
A refresh works when the site’s structure still matches how you sell, content is mostly reusable, and the tech can still ship performance and accessibility without heroic workarounds.
Refresh signals
- Offer and audience are stable; only the look feels dated
- Page inventory still maps to real journeys
- Core templates are salvageable with better type, space, and CTA clarity
- Hosting and CMS can meet modern speed and security needs
- You mainly need visual consistency and cleaner conversion paths
When a rebuild pays off
Rebuild when the site fights every new page, every campaign, or every integration. Cosmetic paint on a broken IA usually costs twice: once for the refresh, again for the inevitable redo.
Rebuild signals
- Navigation reflects org charts, not customer jobs
- Templates cannot express the current product or pricing model
- Performance and SEO debt are structural, not content-level
- Editors cannot publish without developer babysitting
- You need new surfaces (portal, quoting, booking) the old stack cannot hold
A practical decision path
Decide with evidence, not taste. Look at conversion paths, content reuse, and technical constraints before you open a mood board.
- 1
Audit the jobs
List the three actions the site must drive. If those paths are buried, structure—not color—is the problem.
- 2
Inventory what transfers
Mark pages and assets that still earn their keep. High reuse favors refresh; low reuse favors rebuild.
- 3
Stress-test the stack
Can you ship Core Web Vitals, accessible forms, and the next integration without fighting the CMS?
- 4
Price both options honestly
A cheap refresh that blocks growth is more expensive than a scoped rebuild with a clear cutover.
Rebuild vs refresh decision
What “finished” looks like either way
Whether you refresh or rebuild, success is measurable: clearer journeys, faster loads, editors who can publish, and a maintenance plan. Pretty screenshots without those outcomes are decoration.
Final thoughts
Refresh when the bones are sound. Rebuild when structure, stack, or editorial reality cannot carry the next chapter. Use a checklist, not a vibe—and scope the work against outcomes you can measure after launch.
Related Articles
Designing flows instead of static pages
Treat the scroll as a timeline and choreograph what the user discovers next
Website SEO that actually moves leads (not just rankings)
Structure, speed, intent pages, and tracking—SEO as a growth system, not a checklist theater
Ready to build something this considered?