How often should you redesign your website?

The answer you will find most often is "every two to three years". It is a description of what companies do, not a recommendation. Most of those redesigns redo work that did not need redoing, because the site was built as a set of fixed pages that nobody could change safely. So how often should you redesign your website? We think the better question is what should trigger a rebuild, and how to make everything else a monthly improvement instead. That is the idea behind our website retainers, and this article explains the reasoning.

01Why sites get redesigned every few years

In our experience the trigger is rarely the design itself. It is everything around it:

• The CMS fights the team. Every new page needs a developer, so marketing stops asking and works around the site.
• The code has one owner. The freelancer or agency who built it has moved on, and nobody else dares to touch it.
• Small changes pile up. Three years of one off landing pages, plugins and quick fixes make each change slower and riskier than the last.
• The brand moved on. The company changed its positioning, and the site cannot follow without being rebuilt.

None of these is solved by a new look. A redesign that rebuilds the same fixed templates on the same terms resets the clock, and the cycle starts again.

02Signs you need a rebuild

These are structural problems. Fixing them inside the current site usually costs more than starting again on better foundations.

• Your team cannot publish or change a page without a developer, and that is slowing down campaigns
• The platform, theme or framework is out of support, or updates keep breaking the site
• Core Web Vitals fail across most templates and fixes do not hold, because the problem is the theme or the architecture. The HTTP Archive's 2025 Web Almanac found that self hosted platforms, where themes and plugins pile up, vary far more in speed than tightly managed ones
• The site cannot support something the business now needs, such as new markets, languages or product lines
• Accessibility problems are built into the templates rather than being one off mistakes

If two or more of these are true, a rebuild is probably cheaper over the next three years than patching.

03Signs you only need a refresh

These feel big but rarely justify a full rebuild:

• The visual style feels dated, but the structure and CMS work
• Conversion is low on specific pages; that is usually copy, offer and layout on those pages
• You need new pages for a launch or a campaign
• Rankings dropped for some pages; that is a content and technical SEO problem first

A refresh changes the surface: copy, imagery, colour, type and a handful of templates. On a site built from components, a refresh can roll through the whole site in weeks, because the components update everywhere they are used.

04What a rebuild costs you beyond the budget

The invoice is the visible part. The hidden costs are time and search visibility.

A rebuild takes your marketing team's attention for months, and the site is usually frozen while it happens. If URLs change, rankings are at risk. Google's guide to moving a site is clear that you should map every old URL to its new one with permanent redirects, and still expect ranking fluctuations while the site is recrawled, for a few weeks or longer on bigger sites. Plan for it: keep the URLs that earn traffic, carry over titles and content that rank, and watch Search Console closely after launch. We keep the full list in our website migration SEO checklist, and if you do go ahead, start with a clear design brief.

05How to stop redesigning every few years

The goal is a site that changes continuously, so there is never a big relaunch to fund. Four things make that possible:

1. Build from components, not pages. A documented component system lets your team assemble new pages from tested pieces, and lets a brand update flow through every page at once. This is what we mean by a fluid website.
2. Choose a CMS your team will actually use. The right platform depends on who edits the site; we compare two common options in Webflow vs WordPress.
3. Keep performance part of the routine. Speed decays as scripts and content pile up. A monthly check stops it becoming a reason to rebuild; our Core Web Vitals checklist is the one we use, and it sits inside a wider maintenance schedule of weekly, monthly and yearly tasks.
4. Budget for improvement every month. A small amount of design and engineering time each month costs less than a large project every three years, and the site gets better instead of slowly going out of date.

06So, how often should you redesign your website?

Rebuild when the foundations fail: the platform, the code, the content model or the CMS experience. On a well built site that should be rare. Refresh the design whenever the brand or the market moves. Improve something every month.

If you are not sure which situation you are in, that is exactly what our discovery phase is for. You can read how we work from first call to the months after launch, or send us your site and we will tell you honestly whether it needs a rebuild at all.