Website Refresh, Redesign Or Rebuild: What’s The Right Choice?

By Neil Kilgallon on Wednesday, 14 October 2026

When a business decides its website needs improving, the first thought is often to commission a completely new one. The current design might look dated, enquiries may have dropped, or the team may struggle to manage content and add new features.

But starting again isn't always necessary. Some websites can improve considerably with better design, content, and navigation while keeping the existing CMS and functionality. Others may look perfectly respectable but be held back by outdated technology that makes further development difficult or expensive.

As a web design agency in London, we regularly help businesses assess their existing websites and decide how much needs to change. In this article, we'll explain the differences between a website refresh, redesign and rebuild, what each approach involves, and how to decide which is right for your business.

What's The Difference Between A Website Refresh, Redesign and Rebuild?

People often mix up these terms, but they represent very different levels of effort. Knowing what each one means can really help when you're talking with a web design agency or comparing different proposals.

Website Refresh

A refresh involves improving an existing website without significantly changing its structure or underlying functionality. This might include updating colours, typography, imagery, content or individual page sections.

The main layout and content management system usually remain in place. It's often the quickest and least expensive option, provided the existing website is well-built and can accommodate the changes.

Website Redesign

A redesign involves a more thorough review of the website's look and how visitors use it. This can include a completely new visual design, revised navigation, improved page layouts and a different approach to presenting content.

A redesign doesn't automatically mean replacing the existing CMS. If the current platform is suitable, you may be able to build the new designs around it, although the front-end templates and components will still need development work.

Website Rebuild

A rebuild focuses on replacing or substantially reworking the website's underlying technology. That might involve moving to a different CMS, replacing outdated code, restructuring the database or developing new functionality and integrations.

A rebuild can also include a complete redesign, but it doesn't have to. A business might be happy with its visual identity and want to retain much of the existing design while replacing a platform that no longer meets its requirements.

The table below summarises the main differences:

These aren't fixed categories. A project might involve a complete redesign alongside a CMS replacement, while another might only require new page templates and several technical improvements.

What matters is defining exactly what work is needed, not relying on how the project is described.

When Is Refreshing Your Existing Website Enough?

If your website is technically sound, easy to manage, and already achieves most of its objectives, you may not need a complete redesign.

For example, a professional services company might have a website with clear navigation, well-structured content and a reliable CMS. However, its photography is outdated, some pages are too text-heavy, and the visual design no longer feels consistent with its brand.

In that situation, improving the presentation of key pages, updating the imagery and reviewing the content could make a noticeable difference without rebuilding the website.

Other improvements might include clearer calls to action, updated service information, improved forms, or better use of existing content modules.

Before recommending this approach, we would want to establish that the underlying website can support the changes. A seemingly straightforward layout adjustment can become complicated if the original templates were poorly developed or the CMS provides very little flexibility.

Updating an individual page differs from addressing a problem that affects the whole website. If visitors struggle with the navigation or the site performs poorly on mobile devices, a few cosmetic changes are unlikely to resolve the issue.

Our article on updating a tired-looking website covers smaller improvements that can extend an existing site's useful life.

When Should You Consider A Complete Website Redesign?

A redesign is often the right approach when the website no longer reflects the business or isn't providing visitors with a good experience.

This is particularly common for organisations that have grown, introduced new services, changed their positioning or expanded into different markets. The website may have worked well when it was first developed, but its original design and structure may no longer suit the organisation.

We would consider several areas when planning a redesign.

Your Brand Has Changed

A business can change considerably over a few years. Its services, audience, positioning and visual identity may all have evolved, while the website still represents an earlier version of the organisation.

In some cases, the existing brand guidelines provide everything needed for a new website design. In others, you may need to review the identity itself before starting the website work.

At ID Studio, our brand strategy and identity team can work alongside the website designers when the brand needs changes. We wouldn't automatically recommend a rebrand simply because a business is commissioning a new website.

Visitors Are Struggling to Find What They Need

A website can look attractive but still be difficult to use.

Navigation may have become complicated as you added new services. Important information may be buried several pages deep, or the content may be organised around internal departments rather than what customers need.

These problems often need more than changes to colours or typography.

Our website design process starts with a review of the website's structure and the journeys visitors need to follow. We develop wireframes to establish how content should be organised and presented before creating the visual designs.

That planning can reveal opportunities to simplify the website instead of adding pages and navigation options.

The Existing CMS Still Works Well

If the CMS is secure, properly maintained and flexible enough to support the new requirements, there may be little reason to replace it.

A redesign could involve creating new front-end templates, introducing different content modules and changing the navigation while retaining the same CMS, user accounts and underlying data.

This can reduce development and migration work compared with replacing the entire platform.

However, it is worth assessing how easily the new designs can integrate. Retaining the CMS is only beneficial if doing so doesn't introduce significant compromises or unnecessary development costs.

When Does Rebuilding A Website Make More Sense?

Sometimes the biggest website problems aren't immediately visible to visitors.

The design might still look reasonably modern, but the underlying technology can make everyday tasks difficult. Adding a new page might require a developer, a simple form change could affect other functionality, or the CMS may no longer receive the updates needed to stay secure.

These issues become more significant as a website grows.

A rebuild may be worth considering when:

• The CMS or underlying framework is outdated, unsupported or increasingly difficult to maintain.
• The website relies on old code that makes improvements expensive or introduces problems elsewhere.
• Content editors have limited control over pages and regularly need development assistance.
• New functionality cannot be accommodated without extensive changes to the existing architecture.
• The website needs to integrate with systems the existing platform cannot reliably support.
• Security, performance or accessibility problems are difficult to address within the current setup.

For example, an organisation might want to introduce customer accounts, online bookings, or CRM integration. If the existing website was originally developed as a straightforward brochure site, accommodating these features could require substantial changes.

In that situation, continuing to extend the old system may cost more over time than developing a platform around the new requirements.

Our web development team works with different CMS platforms and development frameworks, including ProcessWire, WordPress and Laravel. We aren't tied to one system, so we base our recommendation on what the website needs to do, how it will be managed, and how it may develop.

It's also worth remembering that an unfamiliar CMS doesn't necessarily need replacing. Before recommending a rebuild, we would review the quality of the existing development, the platform's capabilities, and whether its limitations cause genuine problems.

What Should You Review Before Deciding?

One of the most common mistakes is deciding that a website needs replacing before properly assessing what is already there.

We would recommend reviewing the existing website from several perspectives before agreeing on the scope of a redesign or rebuild.

Website Design & User Experience

Start by looking at how visitors use the website.

Can they find the information they need? Are the navigation and page layouts clear? Is it obvious what the business offers and what action someone should take next?

A website that receives plenty of relevant traffic but generates very few enquiries may have problems with its messaging, page layouts or conversion process.

However, poor enquiry numbers don't necessarily indicate a design problem. The website might simply be attracting the wrong audience.

Google Analytics, conversion tracking, and user behaviour can help you identify where visitors struggle and what needs attention.

It's also useful to review the website on different devices. A desktop layout might work perfectly, while the mobile experience can make navigation, forms, or important content hard to use.

Content & SEO Performance

Before changing a website's structure, identify which pages perform well in search engines and which are underperforming.

Google Search Console shows the searches generating impressions and clicks, while analytics helps identify which pages visitors use and what actions they complete.

This information is particularly important if you're considering removing pages, reorganising services or changing URLs.

An outdated-looking page might still generate valuable search traffic. Replacing it with a much shorter page or removing it entirely could affect that visibility.

A redesign can also improve weak content, address duplication, and build a clearer structure around your services and target search terms.

At ID Studio, our digital marketing and SEO team reviews these areas alongside website planning where SEO forms part of the project. It means decisions about navigation, content and page structure can account for existing search performance before development begins.

CMS & Website Functionality

Speak to the people who manage the website.

Are they comfortable adding pages and updating content? Can they manage images, forms, navigation and other common tasks without asking a developer?

A CMS might be technically capable but poorly configured for the way your team works. In some cases, improving the editing tools or introducing flexible content modules could resolve the problem without replacing the entire platform.

Other organisations may need more fundamental changes.

For example, a website that has gradually accumulated different plugins, integrations and custom modifications can become difficult to maintain. If making one change repeatedly causes problems elsewhere, it is worth investigating the underlying architecture.

We would also review software support, security updates, hosting, and overall code quality before deciding what to retain.

Future Business Requirements

A website should accommodate more than today's requirements.

If you expect to introduce new products, additional languages, customer portals or connections to business systems, these should form part of the initial assessment.

That doesn't mean developing every possible feature immediately. It means ensuring the chosen approach doesn't create an obstacle to already planned work.

For example, a business might not need an integrated booking system today, but if one is likely to be introduced next year, that should influence the decision about the CMS and technical architecture.

It is much easier to make these decisions during planning than discover halfway through development that the proposed platform cannot support an important requirement.

Could A Phased Approach Be More Practical?

Not every website improvement needs to happen within one large project.

For some organisations, a phased approach makes sense, especially when the existing website has a solid technical foundation but several areas need attention.

The first stage might focus on the navigation and most important service pages. Further work could involve updating supporting content, introducing new page modules or developing additional functionality.

This can spread the investment over a longer period and allow the business to assess the results of individual improvements.

There are limitations, however.

If the website is being completely restructured, repeatedly changing the same templates or navigation across stages can add development costs. Technical dependencies may also need to be resolved before other work can begin.

Phasing works best when you have a clear plan for the finished website, even if you deliver it over time.

Our ID Support service gives existing clients ongoing access to our designers and developers for website improvements, maintenance, and new requirements. This can be an alternative to commissioning a major redesign when the existing platform remains suitable.

How Do The Costs Of A Redesign And Rebuild Compare?

A website refresh will generally involve less work than a complete redesign, while replacing the underlying platform can add significant development time.

However, the cost depends on what already exists and what needs to change.

A well-developed CMS with flexible content modules may make it relatively straightforward to introduce a new design. By comparison, an older website with rigid templates and heavily customised code could require considerable development effort to achieve the same result.

A rebuild can add costs for database development, CMS configuration, integrations, content migration, and testing.

You may also need to recreate functionality even if visitors won't notice any difference. For example, a form that sends information to several internal systems might require substantial work to reproduce and test on a new platform.

The cheapest initial option isn't necessarily the most economical over several years.

If an agency recommends retaining the existing platform, ask how much development work will be needed to accommodate future changes and whether any technical limitations will remain.

If a rebuild is recommended, ask which existing components can be retained and why replacing the others is justified.

We've covered the wider factors affecting website project budgets in our article, Why Do Website Costs Vary So Much Between Web Design Agencies?. It explains how differences in planning, design, functionality, content, and technical requirements can lead to very different proposals.

The same principle applies here. Two agencies could describe their proposals as a website redesign while including substantially different amounts of development work.

Before choosing between them, make sure you understand what each intends to retain, replace or improve.

What Happens To SEO When You Redesign Or Rebuild A Website?

A redesign doesn't automatically mean losing your Google rankings. But changes to a website's content, structure, and technical setup can affect its search visibility if they aren't planned properly.

The level of risk depends on what is changing.

If you're updating a few page layouts while retaining the existing URLs and content, the SEO implications may be relatively limited.

A complete rebuild can be more involved, particularly if you're moving to a new CMS, changing the URL structure or consolidating existing pages.

Before starting, we recommend identifying the pages that currently attract search traffic and deciding what content to keep, improve, or redirect.

If URLs are changing, we need to plan redirects so visitors and search engines can find the relevant replacement pages. Existing metadata, headings, internal links and important technical settings should also be reviewed.

The new website then needs testing before launch, followed by monitoring to identify indexing or ranking issues.

A rebuild may also provide opportunities to improve technical performance, website structure and content management. Those improvements can benefit SEO, but you shouldn't assume they'll automatically produce higher rankings.

Our guide to redesigning your website without losing SEO rankings explains the checks and precautions involved in more detail.

How We Approach Redesigns And Rebuilds At ID Studio

Different projects require different approaches, and the distinction between redesigning and rebuilding isn't always straightforward.

We've worked with organisations that need a new visual identity, others whose main challenge is their CMS, and clients who require ongoing improvements to existing websites.

The following projects show how those requirements can shape the scope of work.

Studio Spicer: Redesigning The Brand And Website

Studio Spicer is an architecture practice working across residential and commercial projects. Its existing brand and website no longer reflected the quality of its work, and the website wasn't presenting its portfolio as effectively as it could.

The CMS also had limitations that made content management more time-consuming than necessary.

Our work included reviewing the brand, developing a new visual identity and creating a website with clearer navigation and a more considered approach to displaying architectural projects.

We also evaluated suitable content management platforms and developed the website using ProcessWire, giving the team a straightforward way to manage projects and content internally.

For Studio Spicer, the requirements went beyond updating the existing website's appearance. Both the visual experience and the content management system needed attention.

You can read more about the project in our Studio Spicer website design case study.

Stats Perform: Combining Design With A More Flexible CMS

Stats Perform provides sports data, AI and technology to broadcasters, publishers, sportsbooks and professional sports organisations.

Its website needed to present a broad range of products to several different audiences, while giving its marketing team the flexibility to manage content and respond to changing requirements.

We worked closely with the Stats Perform team to review how to organise the products and services, develop a new visual direction, and improve navigation and page layouts.

The project also included custom 3D animation and a flexible CMS with reusable content modules.

The design and development requirements were closely connected. Improving the website's presentation mattered, but so did ensuring the marketing team had the tools to manage and expand it.

Our Stats Perform case study explains the design, development and ongoing SEO work in more detail.

Meta: Improving Existing Websites Over Time

Our relationship with Meta offers another example.

We've been retained for several years to provide design, front-end development, back-end development and ongoing support across four websites, including TTC Labs and Open Loop.

Rather than treating every new requirement as a separate website project, we work alongside Meta's teams to introduce new pages, designs and functionality as the websites develop.

Some changes involve extending existing features. Others require more substantial technical work.

For TTC Labs, for example, we migrated the website from Contentful to ProcessWire, introducing a CMS that lets the team create pages by combining designed content modules.

Our ongoing work also includes maintenance, updates and further development across the websites.

This shows how an established website can evolve over several years, with individual design and technical requirements addressed as they arise.

You can find more information in our Meta website design, development and support case study.

How Do You Decide Which Approach Is Right for Your Business?

Before asking agencies to quote for a new website, try to establish which parts of the existing site are preventing you from achieving your objectives.

A useful starting point is to work through the following questions:

• Is the existing CMS suitable? Can your team manage content easily, and does the platform support the functionality you need?
• Are the main problems related to design or technology? Poor navigation and dated layouts require a different solution from unsupported software or unreliable integrations.
• What is already working well? Identify useful content, existing functionality and pages that attract valuable search traffic before deciding what to replace.
• What will the website need to do in the future? Consider planned services, integrations, user accounts and other requirements that could influence the technical approach.
• Would retaining the existing website create unnecessary costs? Ask whether the proposed improvements can be developed efficiently or whether working around the current platform will become increasingly expensive.

The answers should help establish whether you need a refresh, redesign, rebuild or a combination of approaches.

At ID Studio, we start by understanding the existing website and what the organisation wants to achieve. Our designers and developers can then review the options, explain the implications and recommend an appropriate scope of work.

Sometimes that means creating a completely new website. In other cases, keeping the existing CMS or improving individual sections offers a more practical, cost-effective solution.

The important thing is making that decision before committing to a project, rather than discovering halfway through that you are replacing something that worked perfectly well.

Not Sure What Your Website Needs?

If you're considering a website redesign but aren't sure whether to keep the existing platform, we can help you work through the options.

Our team can review your existing website, discuss its limitations and future requirements, and explain what we would recommend improving, redesigning or rebuilding.