Do you need a new website, or can you fix the one you have?

Somewhere around the fourth or fifth year of a small business website, a familiar feeling sets in. The site looks a little dated. It is slower than it used to be. Editing it feels harder than it should. A competitor has launched something that makes yours look tired. And the question arrives: do we need a new website?

Ask an agency and the answer is often yes, because building new websites is what agencies are set up to sell. Ask a freelancer who maintains the current one and the answer is often no, because patching it is what they are set up to sell. Neither answer is necessarily wrong. Neither is necessarily based on your business.

This article is the assessment we run when a small business asks us whether to rebuild or repair. It will help you work out which problems your site actually has, which of them can be fixed where they are, which cannot, and how to compare the two routes on cost, risk and results rather than on how the homepage looks.

The short answer

Fix the site you have if its problems are about content, speed, clarity or small pieces of functionality, and the platform underneath is sound, supported and something you can edit. Rebuild if the platform is the problem: if it is obsolete, unsupported, insecure, impossible to edit without a developer, or fundamentally unable to do what the business now needs.

Most sites fall clearly on one side of that line once you look properly. The difficulty is that the symptoms owners notice first, an old fashioned appearance or a drop in enquiries, can come from either side. The rest of this article is about telling them apart.

How long should a small business website last?

There is no fixed lifespan, but patterns are consistent enough to be useful. A well built small business site on a mainstream platform, maintained properly, typically serves for somewhere between four and seven years before a significant rebuild makes sense. Poorly built or unmaintained sites often struggle after two or three.

What ages a website is rarely the design alone. It is the combination of changes around it. Browsers and devices evolve. Search engines raise their expectations for speed and mobile use. Platforms release major versions that older themes and plugins cannot follow. Your business changes its services, prices and customers. And the expectations of visitors rise as they grow used to faster, clearer sites elsewhere.

Regular maintenance and steady improvement extend the life of a site considerably. A site whose content is updated, whose components are kept current and whose weak pages are improved each year can stay effective far longer than one launched and left alone. Conversely, a site that has not been touched since launch may need replacing sooner than its age suggests.

So treat age as a prompt to assess, not a reason to rebuild. A seven year old site that has been cared for may need nothing more than a refresh. A three year old site that was built cheaply and never updated may already be past saving.

Why the question is harder than it looks

Websites fail in ways that are easy to feel and hard to diagnose. A drop in enquiries might be caused by a design that no longer builds trust, a form that has quietly stopped sending, a competitor that now outranks you, a change in how your customers search or a seasonal dip that happens every year. Only one of those is fixed by a new design.

Appearance is also a poor guide. A dated looking site can convert well because it answers questions clearly and loads quickly. A beautiful modern site can convert badly because it hides the phone number behind animation. Owners notice the look first because it is the most visible thing, but it is rarely the most important.

And there is an emotional pull towards starting again. A new site feels like progress. It offers a clean slate, a launch, something to show people. Fixing an old one feels like maintenance. That pull is worth resisting until you know what is actually wrong, because a rebuild that recreates the same underlying problems in a new design costs a great deal and changes very little.

Start with what the website is supposed to do

Before assessing anything, write down what the site is for and how well it does it. Produce enquiries, sell products, take bookings, support existing clients, help you recruit. Then find the numbers: visitors per month, enquiries or sales per month, and how both have moved over the last two years.

This matters because the decision should be driven by the gap between what the site does and what it needs to do. If the site produces a healthy flow of enquiries and your main complaint is that it looks old, the case for a full rebuild is weak, and a careful refresh may be enough. If the site produces almost nothing despite reasonable traffic, something important is wrong and it needs diagnosing before any money is spent. Our guide on why your website gets traffic but no enquiries walks through that diagnosis.

Also note what the business needs next. A website that suits a business selling one service locally may not suit the same business two years later when it sells online, operates in three regions or needs customers to book and pay. Sometimes the site has not got worse. The business has outgrown it.

Signs the site can be fixed

These problems are real and worth solving, but none of them on its own requires starting again.

• The words are out of date or unclear. Services have changed, prices are wrong, the homepage does not say plainly what you do. Rewriting content is far cheaper than rebuilding the site that holds it.
• Pages are missing. You offer services that have no page of their own, or you serve areas the site never mentions. New pages can be added to most sites without touching the rest.
• The site is slow, but the platform is sound. Oversized images, too many plugins, poor hosting and unnecessary scripts are the usual causes. All can be fixed where they are.
• The enquiry form or checkout is awkward. Too many fields, a confusing layout, no confirmation message. These are small changes with large effects.
• The photographs are poor. Replacing stock photography with real pictures of your team and work transforms a site and requires no development at all.
• The design looks a little dated, but it works. A refresh of typography, colours, spacing and imagery within the existing templates can modernise a site considerably at a fraction of the cost of a new one.
• Tracking is missing or broken. Setting up measurement is a configuration job, not a rebuild.
• The mobile experience has specific problems. Small tap targets, unreadable text or a phone number that cannot be tapped can usually be corrected without redesigning the site.

If most of your list looks like this, fix the site. Put the money you would have spent on a rebuild into content, photography, speed and measurement, and you will probably get a better result sooner.

Signs you genuinely need a new website

These problems sit in the foundations. Fixing the surface leaves them in place, and repeated patching usually costs more over time than rebuilding once.

• The platform is obsolete or unsupported. The software your site runs on no longer receives security updates, or the theme or page builder it depends on has been abandoned by its developer. Every month it stays online, the risk grows.
• Nobody can safely update it. Updating one component breaks another, so updates have simply stopped. This is a common and dangerous state, and it is usually the point at which rebuilding becomes cheaper than repairing.
• You cannot edit it yourself. Changing a sentence requires a developer, because the site was built in a way that does not allow editing, or the person who understood it has gone.
• It is not genuinely usable on a phone. Some older sites were designed only for desktop screens and adapted awkwardly later. If the mobile experience is fundamentally broken rather than slightly awkward, the structure needs replacing.
• It cannot do what the business now needs. Online sales, bookings, customer accounts, multiple languages or integration with your other systems, where the current platform either cannot support them or would need so much custom work that a new build is simpler.
• Performance cannot be fixed. The site remains slow after images, plugins and hosting have been addressed, because the theme or builder itself generates too much code. We cover the measurement side in the Core Web Vitals work that actually moves rankings.
• The structure no longer fits the business. The navigation, page types and content model were designed for a different business. Adding pages to a structure that does not suit them produces a site that becomes harder to use with every addition.
• You do not own or control it. The site sits on a platform owned by a former supplier, or you cannot get access to the code, the hosting or the domain. Sometimes the only practical route to control is a new build on something you own.
• It has been hacked more than once. Repeated compromises usually point to underlying weaknesses that cleaning up the damage does not remove.

One of these on its own may justify a rebuild. Two or three almost always do.

The platform question

Most of the decision comes down to whether the platform your site runs on is still fit for purpose. It is worth assessing this directly rather than inferring it from symptoms.

Is it supported?

Find out what the site is built on and whether that software, and every major component it depends on, is still maintained. For a WordPress site, that means the core software, the theme and each plugin. For a hosted platform such as Squarespace, Wix or Shopify, the platform itself is maintained for you, but older templates may not be. For a custom built site, ask whether anybody still understands and maintains the code.

Is it up to date?

A supported platform that has not been updated for two years is nearly as risky as an unsupported one, and bringing it up to date can itself be a significant job if updates have been skipped for a long time. Ask whoever maintains it how far behind it is and what it would take to catch up.

Can it do what you need next?

Think about the next three years, not just today. If you expect to start selling online, the choice of platform for a shop has long term consequences, which we compare in Shopify or WooCommerce: choosing without the sales pitch. If you expect to add bookings, memberships or integrations, check whether the current platform can support them sensibly.

Can someone else work on it?

Sites built on widely used platforms with standard methods can be maintained by many developers. Sites built on obscure systems, heavily customised themes or proprietary platforms controlled by one supplier cannot. If only one person or company can work on your site, you are carrying a risk that a rebuild on a standard platform would remove.

Problems that look like design problems but are not

Many owners commission a new design to solve problems that design cannot touch. Before deciding, rule these out.

Falling enquiries caused by search

If traffic from search has dropped, the cause may be a competitor improving, a change in how search results are displayed, lost rankings for particular pages or technical problems preventing pages from being indexed. A new design does not solve any of these, and a careless rebuild can make them considerably worse.

Falling enquiries caused by the market

Demand moves with seasons, the economy and changes in your industry. Compare your figures with the same period last year and, if you can, with what peers are experiencing before blaming the website.

Lost enquiries caused by broken plumbing

Contact forms that stop sending, notification emails landing in spam and phone numbers that have changed are surprisingly common. Test every form and every contact route before concluding that the site is not persuading people.

Poor results caused by the wrong traffic

A site attracting visitors who were never going to buy will convert poorly whatever it looks like. Check which search terms and channels bring your visitors before assuming the site is failing them.

Slow response caused by the business

If enquiries arrive but few become customers, look at what happens after the enquiry. How quickly are they answered, and by whom? A new website cannot fix a two day response time.

What fixing actually involves

Fixing a website covers a wide range of work. It helps to think of it in three levels of effort.

Quick fixes, in days

Testing and repairing forms, correcting contact details, updating prices and service descriptions, compressing images, removing unused plugins, making phone numbers tappable, adding clear calls to action, setting up tracking and completing your Google Business Profile. Individually small, collectively often the most valuable work a site can receive.

Substantial fixes, in weeks

Rewriting key pages, adding a proper page for each service and area, replacing stock photography, improving hosting, bringing the platform and plugins fully up to date, refreshing the visual design within existing templates, and fixing the most significant speed and mobile problems. This level of work can transform how a site performs without the cost and risk of a rebuild.

Structural fixes, as a project

Replacing the theme while keeping the platform and content, reorganising navigation and page structure, or rebuilding specific sections such as the shop or booking system. At this level, the work begins to approach a rebuild in cost, and it is worth comparing the two carefully.

Ongoing care is part of fixing too. A site that is repaired and then left alone drifts back into the same condition. A maintenance arrangement covering updates, backups, security and small changes keeps the improvements in place.

What rebuilding actually involves

A rebuild is more than a new design. Understanding the full scope helps you compare it fairly with fixing.

1. Discovery. Understanding the business, its customers and what the site needs to achieve, and auditing the current site, including which pages bring in search traffic.
2. Structure and content. Planning the pages, navigation and content, and writing or rewriting the words.
3. Design. Creating the visual design for each type of page, on mobile and desktop.
4. Build. Developing the site on the chosen platform, including any integrations.
5. Migration. Moving content, products, customers and data from the old site, and mapping every old page address to its new equivalent.
6. Testing. Checking forms, speed, mobile behaviour, accessibility, tracking and every integration.
7. Launch and aftercare. Switching over, redirecting old addresses, monitoring search console and fixing problems that appear in the first weeks.

Each stage takes time and needs input from you, particularly content and decisions. Small business rebuilds commonly take between six weeks and several months depending on size and how quickly content is ready. Our guide on what a web design agency should cost explains what drives the price.

Comparing the cost over three years

The build price alone is a misleading comparison. Compare the total cost of each route over three years, including everything that follows.

The cost of fixing

Add the initial repair work, ongoing maintenance, likely further fixes as older components continue to age, and any workarounds the business uses because the site cannot do something properly. Include the cost of staff time spent on awkward updates or manual processes. For a sound site, this total is usually well below a rebuild. For a site on a failing platform, it can creep above it, because each year brings new repairs.

The cost of rebuilding

Add the build, content and photography, migration, redirects, any new licences or subscriptions, hosting and maintenance. Include the cost of your own time during the project, which is substantial, and allow for a possible temporary dip in search traffic after launch even when the migration is handled well.

The cost of the gap

Finally, estimate what each route produces. If a rebuild would double the enquiry rate and a fix would improve it by a fifth, the rebuild may be cheaper per enquiry even though it costs more. If both would produce similar results, the cheaper route is usually right. This is where knowing your current numbers pays off, because it turns a question of taste into a question of return.

The middle route: rebuilding in stages

Fixing and rebuilding are not the only options. For many small businesses, a staged approach offers much of the benefit of a rebuild with less cost and risk at any one time.

Rebuild the pages that matter most first

Most sites have a handful of pages that do most of the work: the homepage, the main service pages, the contact page and perhaps a pricing page. Redesigning and rebuilding those first, while leaving the blog and minor pages in their current form for a while, produces most of the improvement in a fraction of the time.

Replace the theme, keep the platform

If the platform is sound but the theme or page builder is the problem, it is often possible to replace the theme while keeping the content, users and settings. This is a substantial project, but it avoids the full migration a platform change requires. Our WordPress development work frequently takes this form.

Rebuild one section

If the main site works and one part does not, such as an outdated shop or a booking system that frustrates customers, rebuilding that part alone may be enough.

The staged route has a drawback: for a period, parts of the site look and behave differently. It works best when the stages are planned together from the start, with a single design system that each stage follows, rather than improvised one piece at a time.

The risks of rebuilding

A rebuild solves foundational problems, but it introduces risks of its own that need managing.

• Losing search traffic. Changing page addresses without redirects, removing content that ranks or launching with pages blocked from search engines can wipe out years of rankings. This is the most common and most damaging rebuild failure, and it is almost entirely preventable. We set out the process in how to redesign a website without losing your rankings.
• Losing content. Pages, blog posts, reviews, product descriptions and downloads that exist on the old site but are forgotten in the new one.
• Breaking integrations. Booking systems, payment providers, email platforms and internal tools that were connected to the old site.
• Losing tracking history. New tracking set up differently from the old makes before and after comparisons unreliable.
• Disruption to the business. A long project absorbs time and attention, and a problematic launch can interrupt enquiries or sales.
• Recreating the old problems. A new site built without understanding why the old one underperformed can simply repeat its mistakes more attractively.

Each of these risks can be managed with a careful process. Before committing to a rebuild, ask the agency how it handles every one of them. Our list of questions to ask a web design agency covers the specifics.

The risks of patching

Fixing has risks too, though they tend to be quieter and slower.

• Accumulating fragility. Each fix added to an ageing site adds complexity. Eventually, changes in one place break things in another, and every update becomes a gamble.
• Security exposure. A site running outdated components remains vulnerable however good it looks. Patching the surface while the foundations age is the pattern behind most small business website compromises.
• Spending on something with a limited life. Money put into a platform that will need replacing within a year or two is partly wasted, because much of it will not carry over.
• Delaying the inevitable. If a rebuild is genuinely needed, repeated patching postpones it while the cost of repairs mounts and the business keeps working around a site that holds it back.
• Dependence on one person. Heavily patched sites are often understood by only one developer. If they become unavailable, even small changes become difficult.

A useful test is to ask whoever maintains the site how confident they are about the next two years. If the honest answer is that it will probably be fine with care, fix it. If the answer involves a long pause and several caveats, start planning a rebuild.

Considerations for online shops

For businesses selling online, the question carries extra weight, because the website is not only a marketing tool but the till.

The checkout decides

If customers struggle to pay, abandon baskets or contact you because the checkout is confusing, that is lost revenue every day. A checkout problem on a sound platform can usually be fixed. A checkout limited by an outdated platform or payment integration often cannot, and that alone can justify a rebuild.

Migration is more complex

Moving a shop means moving products, variants, images, customer accounts, order history, reviews and discount codes, as well as page addresses for every product and category. It needs careful planning, testing and timing, ideally avoiding your busiest trading periods.

Platform limits appear as the shop grows

A platform that suited fifty products may struggle with two thousand. One that suited a single country may not handle several currencies, tax rules or delivery zones. If growth plans are running into the platform's limits, patching rarely helps for long. Moving to a platform built for the scale you need, such as a well configured Shopify build, is often the better investment.

Security and compliance matter more

Shops handle customer data and payments, which raises the stakes of running outdated software. If your shop platform is no longer supported or updated, treat a rebuild as urgent rather than optional.

What a refresh can realistically achieve

Owners often underestimate how much can change without a rebuild. A refresh keeps the platform, the page addresses and most of the content, and changes how the site looks and reads. Done well, it can make a site feel new to visitors while avoiding almost all of the risk associated with migration.

A typical refresh updates the typography, colour palette and spacing so the site looks current, replaces stock imagery with real photography, rewrites the homepage and main service pages so they say clearly what you do, tightens the navigation so visitors find the important pages faster, improves the enquiry form and calls to action, and addresses the worst speed and mobile problems.

What a refresh cannot do is change the foundations. If the theme generates bloated code, the platform is unsupported or the structure cannot accommodate what the business needs, refreshing the surface will leave those problems in place. That is why the platform assessment comes first. On sound foundations, a refresh is often the best value work a small business can commission. On failing ones, it is money spent decorating a building that needs underpinning.

A refresh also makes a sensible test. If refreshing the key pages produces a clear improvement in enquiries, you have learned that clarity and presentation were the problem, and you can continue improving the site where it is. If it produces nothing, the problem lies elsewhere, and you have ruled out an expensive rebuild aimed at the wrong target.

How to audit your own site in an hour

You can gather most of the evidence for this decision yourself. Work through these checks and note what you find.

1. Find out what the site is built on. Ask whoever built or maintains it, or check the login page and page source. Note the platform, the theme and whether each is still supported.
2. Check when it was last updated. Log in and look for pending updates to the core software, theme and plugins. Many pending updates is a warning sign.
3. Test it on your phone. Open the homepage and two main service pages on mobile data. Note how long they take to appear, whether the text is readable, and whether you can call or enquire easily.
4. Run a speed test. Use a free performance tool on your homepage and main service page, and note whether the results are poor for mobile.
5. Test every form. Submit each one from a personal email address and check that the message arrives and the confirmation appears.
6. Try to edit a page. Change a sentence and a photograph. Note whether it was easy, awkward or impossible without help.
7. Look at your numbers. Compare visitors and enquiries this year with last year, by month.
8. Check search console. Look for indexing errors, security warnings and mobile usability problems, and note which pages bring in most search traffic.
9. Read the homepage as a stranger. Could somebody tell within five seconds what you do, who for and where?
10. List what the business needs next. New services, online sales, bookings, integrations, new areas. Note whether the current site could support each one.

At the end, sort your findings into two groups: problems with content, clarity, speed and small pieces of functionality, and problems with the platform, structure, editing, security or capability. The balance between the two groups is your answer.

Questions to ask whoever maintains your current site

The person or company that looks after your current site holds much of the information you need, even if they have an interest in the answer. Ask them directly, and ask for the answers in writing.

• What is the site built on, and is every part of it still supported? Platform, theme, page builder and each plugin or extension.
• How far behind on updates is it, and why? If updates have been held back because they break things, you need to know what breaks and what it would take to fix.
• What are the biggest risks to the site over the next two years? Security, compatibility, performance or dependence on specific components.
• What would you change if you were starting again? An honest maintainer usually has a clear answer, and it tells you a great deal about the foundations.
• Who has access, and who owns the accounts? Hosting, domain, platform, analytics and search console. You should hold all of them.
• Could another developer take over easily? If not, why not, and what would make it possible?
• When was the last full backup, and has a restore ever been tested?

Vague answers, reluctance to share access or an admission that nobody fully understands the site are all significant findings. They do not automatically mean you need a rebuild, but they mean your current position carries more risk than it appears.

Timing a rebuild well

If you do decide to rebuild, when you do it matters almost as much as how.

Avoid your busiest trading period. Launching a new site, and especially a new shop, in the weeks when the business most depends on it leaves no margin for the problems that every launch brings. Plan to launch in a quieter period, with enough time afterwards to fix issues before demand rises.

Allow for content. The most common cause of delay in any rebuild is waiting for words, photographs and decisions. If your team is stretched, start gathering content before the project begins rather than during it.

Do not leave it until the old site fails. A rebuild started because the current site has been hacked or has stopped working is rushed, stressful and more expensive. The best time to rebuild is while the old site still works, so the new one can be planned properly and launched when it is ready rather than when it is desperately needed.

And keep the old site running and maintained until the new one launches. Neglecting it during a project, on the grounds that it is about to be replaced, is how businesses end up with months of lost enquiries if the project runs late.

Making the decision

With the audit done, the decision usually falls into one of four outcomes.

Fix it

The platform is sound, supported and editable. The problems are content, clarity, speed, photography and small functional issues. Put the budget into those, set up proper measurement and maintenance, and review in six months.

Refresh it

The platform is sound, but the design is holding the business back and several pages need rethinking. Replace the theme or refresh the design, rewrite the key pages and keep the platform, content and page addresses. This captures much of the benefit of a rebuild with less risk.

Rebuild in stages

Some foundations need replacing, but the budget or the business cannot absorb a full rebuild at once. Plan the whole site, then rebuild the most important sections first, following one design system throughout.

Rebuild it

The platform is obsolete, insecure, uneditable, unable to support what the business needs, or controlled by somebody else. Plan a full rebuild on a platform you own, with a careful migration that protects your search traffic and content. For businesses whose needs go beyond what standard platforms handle well, a custom coded website may be the right foundation.

Review it every year

Whichever route you choose, put a date in the diary twelve months from now to run the same audit again. Platforms change, businesses change and a site that was sound this year may not be next year. An annual review turns a stressful, occasional decision into a routine check, and makes it far less likely that you will ever face an emergency rebuild.

Whichever outcome applies, decide based on evidence rather than on how tired the homepage looks. The right choice is the one that closes the gap between what your site does and what your business needs, at the lowest total cost and risk over the next few years. If you would like a second opinion, we are happy to review your site and tell you honestly which of these four applies, including when the answer is that you do not need us to rebuild anything. Our prices for both routes are published.