Website Refresh or Rebuild: How to Tell Which One Your Site Needs

Most conversations we have with a business owner start in the same place. The website is not doing its job, everybody agrees something needs to change, and nobody is sure whether that means tidying up what is there or starting again.

It is an expensive question to get wrong in either direction. Rebuild a site that only needed a refresh and you have spent a sizeable sum replacing something that was working. Refresh a site whose foundations have gone and you have spent good money on a new coat of paint over a problem that is still lurking.

This is how we work out which one a business needs, including the part of the decision that almost nobody mentions.

What is the difference between a refresh and a rebuild?

The two words get used loosely, so it is worth being precise about what each one involves.

A refresh keeps the existing website and improves it. The platform stays, the page structure mostly stays, and the web addresses stay exactly as they are. What changes is what sits on top: the design, the photography, the words, the calls to action, and often the speed. It is closer to redecorating than rebuilding.

A rebuild replaces the site. New foundations, new structure, usually a new platform, and often a new set of web addresses. Everything is reconsidered, including the things nobody could change before because the old setup would not allow it.

The distinction matters because they solve completely different problems. A refresh fixes how a website presents itself. A rebuild fixes what a website can do.

Which one does your website need?

Rather than working from how old the site feels, work from the symptoms. This is the triage we run before quoting anything.

The pattern is consistent. If your frustrations are about how the site looks and reads, you are describing a refresh. If your frustrations are about what the site will not let you do, you are describing a rebuild.

One qualifier worth adding. Speed sits in the middle, because a slow website can be either an easily fixed problem with oversized images or a symptom of foundations that cannot be saved. The HTTP Archive's Web Almanac 2025 found that only 48% of mobile websites pass all three of Google's Core Web Vitals, so a site being slow is common rather than damning. It needs a proper look before anyone decides what it means.

What a refresh can realistically fix

A good refresh does more than most owners expect, and it is usually the better commercial decision when the foundations are sound.

• Clarity. Rewriting the first screen of a homepage so a visitor understands what you do within seconds is often the single highest-return change on a website.
• Credibility. Better photography, real reviews with names attached, and case studies with outcomes in them will shift how a business is judged before anyone reads a word.
• Conversion. Giving every page one obvious next step, and making that step small enough that people take it, changes enquiry numbers without touching the underlying build.
• Speed. Compressing images properly and removing plugins that nobody has reviewed in three years frequently takes seconds off a page.
• Search visibility. Improving titles, headings and page structure works with the authority the site has already built rather than starting from zero.

That last point is the commercial argument for a refresh, and it is worth sitting with. An older website has been accumulating credibility with search engines for years. A refresh keeps all of it.

When is a rebuild the honest answer?

There are situations where a refresh is the wrong recommendation and we will say so.

The clearest is when the platform itself is the constraint. If your team cannot publish a news post without raising a support ticket, or every new page needs a developer, the website is costing you time every week and no amount of visual improvement will change it.

The second is when the site was built on something that is no longer supported. Unsupported software stops receiving security updates, which turns a website into a growing liability rather than an asset.

The third is when the business has changed and the website has not. Companies that have added a service line, moved into a new market, or repositioned entirely often find the old structure simply has nowhere to put the new business. You can force it, and the result reads exactly as forced.

And there is a fourth, less technical case. Some websites have been patched by so many different hands over so many years that nobody can safely change anything. When the cost of working around the existing build starts to approach the cost of replacing it, replacing it is the better investment.

What does a rebuild risk that nobody tells you about?

Here is the part that gets left out of almost every guide on this subject, and it is the part that matters most to an established business.

Your current website has spent years earning its place in search results. Every page that ranks, every link pointing at you from elsewhere, and every bit of trust Google has built up about your domain sits attached to specific web addresses. A rebuild that changes those addresses without careful planning can lose a meaningful share of it, and that traffic is not something you can simply buy back.

Google's own documentation on site moves is unambiguous about what is required: use permanent redirects, map each important old address to its closest new equivalent, and do not funnel large groups of old pages to the homepage. Google also notes that a medium-sized site can take several weeks to be fully recrawled and reindexed after a move.

In practice this means a rebuild has an extra workstream that a refresh does not: a complete inventory of the existing pages, a redirect map for every one that matters, and monitoring after launch to catch what slipped. When an agency quotes for a rebuild and there is no mention of redirects or migration anywhere in the proposal, that is worth asking about before you sign.

None of this is an argument against rebuilding. It is an argument for rebuilding deliberately, with the search work planned in from the start rather than discovered afterwards. Handled properly, a rebuild can improve search performance rather than damage it. Handled carelessly, it is the most expensive way to lose customers we see.

How old is too old for a website?

There is no fixed answer, and the industry's habit of quoting an average lifespan is less helpful than it sounds.

Orbit Media's research into website lifespan is instructive here. Looking at 50 top marketing brands, they found an average lifespan of just over two years. Looking at their own client sites, the average was more than six years. The same study, two very different numbers, and the difference is not age but how well the site was built and how consistently it has been maintained.

That matches what we see. A well-built site that has been looked after can go five or six years and only need periodic refreshing. A site built cheaply on the wrong foundations can be holding a business back after eighteen months. Age on its own tells you very little.

The more useful question is not how old the website is, but whether it is still doing the job the business needs. If you are unsure how to answer that, the numbers worth watching will tell you more than the launch date will.

How to make the decision with confidence

If you are weighing this up, three things will get you to a clear answer.

Start with the symptoms, not the solution. Write down what is frustrating you about the website, in your own words. The list will usually point clearly at either presentation or capability, and that is the whole decision in miniature.

Get the foundations assessed before anyone quotes. Whether the platform is supported, how the site performs, how the pages are structured for search, and whether your team can manage it. An agency that recommends a rebuild without looking at any of that is guessing, and guessing in the direction of the larger invoice.

Ask what happens to your existing search visibility. This is the single most revealing question you can put to anyone quoting for a rebuild. A good answer covers redirects, the migration plan and what monitoring happens after launch. A vague answer tells you what you need to know.

For a fuller picture of what the work itself involves once you have decided, what a website redesign involves walks through every stage, and our guide to website costs in the UK sets out realistic ranges for both routes.

Not sure which one you need?

We are happy to give you a straight answer, including when that answer is that your website does not need replacing. If you would like a second opinion on where your site stands, get in touch and we will take a proper look, or see how we approach web design.