Should You Repair Your Existing Website or Replace It?

If your website is slow, difficult to update or no longer represents the business, it needs attention. Whether it needs repairs or a replacement depends on what is causing those problems and how much work each option would involve.

When to repair and when to replace

If your website is structurally sound, reasonably fast, easy to maintain and already performs well in search engines, repairing or improving it may be enough.

Replacing the website is usually worth considering when several fundamental problems exist at the same time, such as:

• poor website speed
• outdated design
• difficult mobile navigation
• an old or restrictive content management system
• excessive plugins or third-party scripts
• security or maintenance problems
• confusing website structure
• poor conversion rates
• technical SEO problems
• pages that are difficult for search engines to crawl
• a website that has become expensive to maintain
• technology that prevents further improvements

One problem rarely justifies rebuilding an entire website. When several problems share an underlying cause, replacing the site may be more economical than repeatedly working around it.

Thinking about your own rebuild?

Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.

Tell us about your project↗

What does repairing a website actually mean?

Website repairs can include improvements as well as fixes, while keeping the existing platform, structure or theme.

Typical website improvements might include:

• redesigning individual pages
• improving navigation
• compressing images
• improving website speed
• updating written content
• improving calls to action
• fixing broken links
• making pages mobile-friendly
• improving forms
• simplifying menus
• updating branding
• improving metadata
• adding internal links
• fixing accessibility issues
• removing unnecessary plugins
• correcting technical SEO problems

If the underlying website is healthy, these improvements can make a significant difference without requiring a complete rebuild.

Repairs become less efficient when each change exposes another limitation. For example, image optimisation may leave a slow site with unresolved performance problems, or an old theme may restrict a homepage redesign.

Removing several plugins may help little if another twenty are still needed to keep the site working. Check how much of the remaining work is improving the site and how much is working around its limitations.

What does replacing a website mean?

Replacing your website means rebuilding the site using a new technical foundation rather than continuing to modify the existing one.

Identify what already works and preserve it during the rebuild.

That might include:

• successful pages
• useful written content
• existing search rankings
• important URLs
• backlinks
• branding
• photographs
• customer journeys
• enquiry forms
• analytics data
• useful page titles and descriptions

You can rebuild the code while keeping useful content and structure, using the existing site as a starting point.

10 signs your existing website may need replacing

1. Your website is consistently slow

Visitors expect websites to respond quickly. A slow site can make even a professional business appear dated or unreliable.

Before deciding to replace the site, establish why it is slow.

Common causes include:

• oversized images
• cheap or overloaded hosting
• unnecessary JavaScript
• excessive tracking scripts
• poorly coded themes
• page builders
• large numbers of plugins
• third-party widgets
• unused CSS
• complicated database queries

Many of these problems can be fixed. If the website’s architecture prevents effective repairs, rebuilding with lighter technology may give a better long-term result.

2. Small changes have become surprisingly difficult

Staff should be able to update telephone numbers, photographs, opening hours and service descriptions without needing a developer for each change.

Older websites often accumulate technical complexity over time.

You might have:

• one plugin controlling forms
• another controlling layouts
• another controlling SEO
• another controlling redirects
• several controlling visual elements
• custom code added by previous developers

These additions may each serve a purpose, but together they can make a website difficult to understand and expensive to maintain.

If every small change creates the risk of breaking something else, rebuilding onto a cleaner platform may be worthwhile.

3. Your website looks bad on mobile

On a phone, check whether visitors can comfortably:

• read the text
• use the navigation
• tap buttons
• complete forms
• view photographs
• understand your services
• find your contact details
• move between pages

An old responsive theme may technically work on mobile while still providing a poor experience.

If mobile problems exist throughout the website rather than on one or two pages, a rebuild may be easier than repairing every template individually.

4. The design no longer reflects your business

As services, teams and branding change, your ideal customer may differ from the one you were targeting five years ago. The website can become outdated even when nothing is technically broken.

Ask whether the website accurately represents the company to someone discovering it today.

A visual refresh may be enough. If the content, structure, navigation and technology also need changing, a rebuild may be more efficient.

5. You are paying to maintain problems instead of improving the website

Maintenance is a normal cost. Review the last year or two of spending to see how much went towards recurring faults and workarounds.

If most of it has been spent on:

• plugin conflicts
• compatibility problems
• security issues
• broken layouts
• hosting problems
• software updates
• emergency fixes

consider whether those costs are keeping a restrictive platform running. A replacement can sometimes reduce the amount of work required.

6. Your website relies on too many plugins

Plugins are useful, particularly on WordPress. The number alone tells you little about a site’s quality; check how many dependencies they create and whether each is needed.

If your website requires many extensions to provide functionality that could otherwise be straightforward, you have more software to:

• update
• monitor
• secure
• troubleshoot
• keep compatible

Over time, this can increase maintenance requirements and create unnecessary complexity.

Before rebuilding, check which functions the business needs and whether they can be provided more simply.

Many business websites need far less technology than their existing setup suggests.

7. Your website is difficult for search engines to understand

Technical structure can cause SEO problems as well as content. Look for:

• large numbers of duplicate pages
• broken internal links
• confusing URL structures
• incorrect canonical tags
• pages accidentally blocked from indexing
• important pages buried deep within the site
• duplicate title tags
• unnecessary archive pages
• redirect chains
• outdated XML sitemaps
• poor internal linking

Individual SEO problems can often be repaired. A rebuild may help when the overall structure is difficult to untangle, but keep successful URLs wherever possible to reduce migration risk.

8. Your website is not generating enquiries

Visitors may arrive at a website that looks respectable and still leave without enquiring. Check whether it explains:

• what you do
• who you help
• where you operate
• why customers should choose you
• what they should do next

Check whether people reach the website, which pages they visit and where enquiries currently come from.

A lack of leads does not automatically call for a new website. Better content, clearer calls to action or stronger service pages may help. Restructuring may be worthwhile if the whole site makes it difficult for customers to find what they need.

9. Your current platform is restricting what you can do

A heavy theme or unnecessary generated code can limit performance improvements. The platform may also restrict technical SEO and structured data, or make simple changes depend on complicated workarounds.

When the platform itself becomes the obstacle, replacing the website becomes much easier to justify.

10. You are afraid to update it

If your team avoids updating plugins, themes or the CMS because doing so might break the website, the system has become fragile.

Likewise, if nobody knows how the site was built because the original developer disappeared years ago, maintaining it can become increasingly risky.

When repairing your existing website makes more sense

Repair is often the better option when the foundations remain sound.

For example, consider improving the existing website if:

• it already loads quickly
• it works well on mobile
• search engines crawl it successfully
• important pages rank well
• the CMS is still supported
• editing content is straightforward
• there are no major security concerns
• the structure makes sense
• the main problems are visual or content-related

Replacing a site in this condition can add unnecessary cost and risk. A focused update to service pages, the homepage and calls to action may give better value while leaving the underlying system in place.

Repair vs replace: a simple website checklist

Question	Repair may be enough	Replacement may be better
Is the site fast?	Yes	Consistently slow
Does it work well on mobile?	Mostly	Problems across many pages
Is the CMS supported?	Yes	Old or unsupported
Is it easy to update?	Yes	Simple changes are difficult
Does it rank in Google?	Yes	Major technical SEO issues
Is the structure logical?	Yes	Confusing or bloated
Are maintenance costs reasonable?	Yes	Frequent developer fixes
Does the design represent the business?	Minor refresh needed	Completely outdated
Is the codebase manageable?	Yes	Fragile or unnecessarily complex
Can the current platform meet future needs?	Yes	No

If most of your answers fall into the left-hand column, improving your existing website may make sense.

If several fall into the right-hand column, investigating a replacement is worthwhile.

Will replacing your website damage your SEO?

Your current website may already contain years of accumulated SEO value.

Pages may:

• rank for valuable searches
• attract backlinks
• appear in local search results
• generate organic traffic
• have established URLs that Google understands

A poorly managed replacement can disrupt search visibility. Begin by checking what the current website has achieved and how to protect it.

Do not delete successful pages without checking them

Before rebuilding a website, identify:

• pages receiving organic traffic
• pages ranking for useful keywords
• pages with external links
• pages generating enquiries
• important service and location pages

Use evidence to decide whether to retain, update, merge or remove each page. A simpler navigation menu is not enough reason to delete a page that brings useful traffic or enquiries.

Keep existing URLs where it makes sense

If a page currently lives at:

/commercial-cleaning/

and the equivalent page on the new website still covers commercial cleaning, there may be no good reason to change the URL.

Keeping valuable existing URLs reduces unnecessary migration work.

Redirect URLs that do change

Sometimes changing URLs is unavoidable.

Pages may be consolidated or the existing structure may be genuinely poor.

When an old URL is replaced, it should normally redirect permanently to the most relevant new page.

For example:

/our-services/web-design-services/

might become:

/web-design/

Visitors following the old link should automatically reach the appropriate new page rather than seeing an error.

This also helps search engines understand where the old page has moved.

Avoid simply redirecting every deleted URL to the homepage. A redirect should point to the closest relevant replacement wherever one exists.

Rebuilding a website does not mean changing your domain

If your existing domain is established and appropriate for your business, you can usually keep it.

For example:

yourbusiness.co.uk

can continue to be your domain even though every line of code behind the website has been replaced.

The domain, website design, hosting, CMS and underlying technology are separate things.

Should you replace WordPress with something else?

WordPress powers a huge number of websites and remains suitable for many businesses.

Check whether the business still needs the publishing tools and functions its WordPress setup provides.

WordPress can make sense when a website needs extensive CMS functionality, frequent editorial publishing or particular integrations.

But many small and medium-sized business websites are fundamentally quite simple.

They consist of:

• a homepage
• service pages
• location pages
• an about page
• case studies
• articles
• contact information
• enquiry forms

If a relatively simple website requires a large CMS, page builder and numerous plugins to operate, there may be an opportunity to simplify the technology.

What about static websites and Astro?

One option for replacing a traditional CMS-based business website is a modern framework such as Astro.

Astro is particularly suited to content-focused websites where performance matters.

Instead of requiring a database and server-side CMS to assemble every page each time somebody visits, much of the website can be generated ahead of time as lightweight HTML.

For the right project, this can result in:

• very fast pages
• less unnecessary browser-side JavaScript
• fewer moving parts
• reduced plugin dependency
• greater control over page structure
• strong technical foundations for SEO

Ecommerce, complex memberships, customer dashboards and highly dynamic applications may need a different approach. Choose technology according to the website’s tasks.

For a straightforward business website, a lighter setup can remove unnecessary complexity.

Can you keep the good parts of your existing website?

Use the existing website and its performance data to understand:

• which pages people visit
• what Google has indexed
• which content ranks
• what services matter most
• what links other websites have created
• how the business currently presents itself
• what information customers expect to find

Use those findings to decide what works, what needs changing and what the replacement should do.

Plan the replacement

Start by auditing the existing website before commissioning a new design.

Step 1: understand the existing site

Review:

• page structure
• website speed
• mobile performance
• search visibility
• indexing
• backlinks
• content
• conversions
• technical issues
• analytics

Step 2: identify what is worth keeping

Look for:

• useful content
• high-performing URLs
• established search rankings
• successful calls to action
• good photographs
• valuable backlinks
• well-written service information

Step 3: identify what is holding the website back

This might include:

• performance
• design
• navigation
• technology
• accessibility
• SEO structure
• content quality
• maintainability

This creates the brief for the replacement.

Step 4: build the replacement before removing the existing site

Build the replacement separately while the current site stays available. Compare the two before switching.

That makes it possible to assess:

• page speed
• design
• content
• navigation
• mobile usability
• page structure
• technical SEO

before making the final switch.

A working replacement lets you assess these things directly before approving the switch.

Step 5: map the existing pages

Every important URL on the old website should have a destination on the replacement.

It might:

• remain exactly the same
• move to a new URL
• merge with another page
• be removed because it no longer serves a purpose

Recording these decisions before launch helps prevent valuable pages being accidentally lost.

Step 6: test before launch

Check:

• internal links
• contact forms
• navigation
• page titles
• meta descriptions
• canonical URLs
• structured data
• redirects
• sitemap
• robots directives
• mobile layouts
• page speed
• analytics
• tracking

Complete the pre-launch tests before switching to the replacement.

Step 7: monitor the website afterwards

Once the replacement is live, monitor:

• search indexing
• organic traffic
• rankings
• crawl errors
• broken links
• redirects
• conversions
• website performance

Keep monitoring after the DNS changes. The first few weeks show how visitors and search engines interact with the new site.

How much of your existing website should be reused?

There is no fixed percentage to reuse. A site with strong content and a poor platform may keep much of its material while changing the technology completely. A fast, technically healthy site with weak content may need substantial rewriting and little technical work.

Think of a website as several separate layers:

1. Domain
2. URLs
3. Content
4. Design
5. Website structure
6. Technology
7. Hosting

You do not automatically need to replace every layer just because one of them is causing problems.

Is a website redesign the same as a website rebuild?

A website redesign usually changes how the site looks and how visitors interact with it. A rebuild changes some or all of the technology underneath. A replacement may involve both.

For example, you could redesign a WordPress site while keeping WordPress, or keep its visual design and rebuild it with different technology.

Changing the appearance alone may leave performance or maintenance problems unresolved. Diagnose the current site before choosing the work.

How often should a business replace its website?

There is no fixed replacement schedule, such as every three or five years. Judge the site’s performance and condition.

A five-year-old website that is:

• fast
• secure
• accessible
• easy to maintain
• useful to customers
• generating leads
• ranking successfully

may have no reason to be replaced.

A two-year-old website that is slow, difficult to edit and failing to generate enquiries may already need substantial changes.

Questions to ask before replacing your website

Before committing to a rebuild, ask:

What problem are we actually trying to solve?

Name the problems you want to solve. Age alone is not enough reason for a rebuild. Which of these need improvement?

• speed?
• enquiries?
• search visibility?
• appearance?
• reliability?
• usability?
• maintenance costs?

Could the existing website solve those problems?

If yes, repairing it may be more economical.

Are the problems caused by the underlying platform?

If the technology itself is the obstacle, replacement becomes much more compelling.

What is currently working well?

Make a list before changing anything.

Which pages currently attract search traffic?

These should receive particular attention during a rebuild.

Can successful URLs remain unchanged?

Often they can.

How will redirects be handled?

There should be a clear plan before launch.

How will we measure whether the new website is better?

Useful measures might include:

• faster page loads
• better Core Web Vitals
• increased enquiries
• improved organic visibility
• improved conversion rate
• fewer maintenance problems
• simpler content management

Without measurable objectives, “new” can easily be mistaken for “better”.

The cost of doing nothing

Include the cost of leaving the website as it is when comparing repairs and replacement.

A poor website can cost the business through:

• lost enquiries
• lower conversion rates
• poor search visibility
• high maintenance costs
• wasted advertising traffic
• frustrated customers
• slow employee workflows
• damaged first impressions

These costs rarely appear on an invoice, which makes them easy to overlook.

If a website receives hundreds or thousands of visitors, even a modest improvement in the percentage of people who contact the business can have a significant commercial impact.

Compare repair and replacement costs over the same period, including recurring work and operational disruption, before committing.

Compare the options before deciding

Repair a sound website when focused changes will address the problems. If performance, technology, mobile usability, SEO and maintenance problems keep recurring together, compare the cost of further repairs with a rebuild that simplifies the setup.

Compare the current site with a realistic replacement: speed, technical structure, content, mobile use and search visibility. Identify the pages and rankings to protect, then agree what a replacement would improve and how you would check it.

Before you decide, read the complete guide to upgrading an outdated business website, compare a focused refresh with a redesign and review the signs that a business website is outdated.

Then work through our five questions to ask before rebuilding your website and review how our rebuild process works.

For budgeting, compare why redesign prices vary with the likely ongoing website costs after launch.

• website redesign
• website replacement
• website upgrade
• website rebuild
• website performance
• website speed
• SEO
• business websites