Should you redesign, rebuild or replatform your website?

Web Development, Front End Development, Tip and Tricks, Web Design, Web Support
19 November 2026

A difficult website can make a complete replacement feel inevitable. Every campaign takes too long to launch. Customers keep asking questions the site should answer. Another repair lands on the development backlog.

 

But replacing the website only helps if the project addresses what is causing those problems. Otherwise, you risk moving the same confusing content, restrictive workflows and unresolved customer journeys onto a new platform.

 

The distinction is straightforward: optimise specific weaknesses, redesign the experience, rebuild an inadequate implementation or replatform when the underlying technology cannot support your requirements. These approaches can overlap. The investment should follow the evidence.

 

Website redesign vs rebuild: which change do you need?

 

Optimise when the problem is contained

 

Optimisation improves specific content, forms, components or performance issues while retaining the broader website.

 

Consider a site where relevant visitors reach a service page but rarely complete its enquiry form. Investigate the proposition, supporting evidence and form experience first. That pattern alone does not establish a need for new technology.

 

Targeted changes can have commercial value. In a Vodafone landing-page experiment, performance improvements increased sales while the tested versions remained visually and functionally identical. It demonstrates the value of isolating a problem before expanding the scope.

 

Redesign when the experience no longer serves customers

 

A redesign changes how people understand, navigate and use the website, including its visual expression.

 

For example, a business may have expanded its services while its navigation still reflects an older offering. Customers struggle to understand where to start. If the platform can support a better structure, the priority is the content and experience.

 

A redesign can require substantial development. Its defining purpose is to improve the experience; it does not automatically require replacing the CMS.

 

Rebuild when the implementation obstructs improvement

 

A rebuild replaces or substantially reworks the code, templates, components or architecture.

 

A warning sign is that routine changes repeatedly break unrelated parts of the site, making even modest improvements costly to test and release. A technical assessment should establish whether those problems are localised or spread through the implementation.

 

The CMS may remain suitable. Rebuilding on the same platform can address how the website was constructed while preserving familiar publishing tools.

 

Replatform when the platform cannot meet the requirement

 

Replatforming changes the CMS or another core platform. It becomes relevant when required publishing workflows, integrations or support arrangements cannot be delivered sustainably within the existing solution.

 

Ask the agency to identify the specific limitation, explain the alternatives and demonstrate how the proposed platform resolves it. “More modern” is an insufficient business case.

 

Establish what the redevelopment needs to achieve

 

Before choosing an approach, distinguish between the frustration people report and the cause you can act on.

 

“Marketing cannot launch pages quickly” could mean missing reusable components, restricted permissions, unclear approvals or a CMS that genuinely cannot support the workflow. Watch someone complete the task. The point where they become blocked is more useful than a general complaint about the platform.

 

For customer-facing problems, combine analytics with research into what people are trying to do. Falling enquiries warrant checking traffic quality and measurement as well as the website itself.

 

At JTB, digital strategy and discovery bring these perspectives together to define the project.

 

For ANZSOG, growth across programs, research and communities created a need for clearer audience pathways and easier access to information. JTB’s stakeholder and alumni consultation, navigation testing and structural analysis informed a discovery and solution definition document that ANZSOG used for its redevelopment RFP.

 

That sequence matters: investigation established requirements before the delivery tender. The resulting project addressed structure, content discovery and a flexible component framework alongside brand and design.

 

Test the platform before deciding to replace it

 

A platform recommendation should distinguish what the software supports from what the existing build makes available.

 

Take campaign publishing. If the CMS supports reusable components but the website has only rigid templates, rebuilding those templates may solve the problem. If the required permissions or approval workflows cannot be supported without extensive custom development, replatforming deserves consideration.

 

Neither finding settles the decision alone. Compare implementation effort, support, training and ongoing operation.

 

The same scrutiny applies to headless CMS architecture. Separating content management from presentation can support specific requirements, but it also introduces development and maintenance responsibilities. Ask which business capability makes that trade-off worthwhile.

A useful recommendation identifies what to retain, what to replace and the evidence behind each choice.

 

Does AI create a reason to rebuild?

 

AI should influence requirements where there is a useful application. It should also prompt scrutiny of vague promises about an “AI-ready website”.

 

For discoverability, Google’s AI search guidance emphasises useful content and established SEO foundations. Review whether important information is accessible, clear and maintained. A CMS replacement does not follow automatically from that assessment.

 

For new functionality, work backwards from the task. AI-assisted publishing might integrate with existing editorial tools. Personalised recommendations may require better content classification, reliable data and new integrations. Assess those dependencies before deciding how much must change.

 

JTB’s work with Westbourne Grammar illustrates the preparation involved. Different audiences needed relevant pathways and content. Analytics, content auditing and user-needs mapping informed the content structure supporting personalisation. We chose a headless architecture to separate content management from the website experience, providing flexibility to develop audience-specific journeys as the school’s needs evolved.

 

The transferable lesson is that useful personalisation depends on understanding audiences and organising content. That case does not make AI a universal reason to rebuild; it shows why the groundwork belongs in the investment decision.

 

When does continued repair become poor value?

 

Small improvements remain worthwhile while they resolve problems without making subsequent changes harder.

 

Reconsider that approach when the same faults return, each new requirement needs another workaround or essential updates become difficult to apply safely. Estimate the effort to deliver the next set of known requirements on the current website, then compare it with rebuilding or replatforming.

 

Include ongoing maintenance and internal time on both sides. Replacement also requires content preparation, migration, integration testing and training.

 

Protect what already performs. Identify valuable search landing pages, useful content and successful enquiry journeys before changing them. Google’s migration guidance recommends mapping changed URLs, testing and monitoring, and separating major changes where practical.

 

Before committing, ask:

  • What measurable customer or business problem will this investment address?
  • What evidence shows the current website cannot resolve it economically?
  • Which existing content, technology and journeys should we retain?
  • What will the transition and ongoing operation require from our team?

 

Start with a decision you can defend

 

A worthwhile assessment should leave you with a recommended scope, the reasons behind it and the implications of retaining or replacing the existing site.

 

JTB combines strategy, experience design and website development to help establish that direction. Bring the recurring problems, upcoming business requirements and evidence you already have. Together, we can identify what needs to change and what is worth preserving before committing to delivery.

Blog

You made it this far
Let's chat
Let's chat
1300 66 99 58
333 Drummond Street Carlton 3053 Melbourne, Australia

    Hi, my name is

    I'm from

    You can call me on

    and email me at

    I would like to chat about...

    (optional)
    (optional - 10mb max)

    Wow, so nice of you  
    We’ll be in touch shortly to learn more about your project.

    Projects

    4

    St Leonard's College

    Education

    Industry Beans

    Food & Drink Hospitality & Leisure

    Small Wonder

    Hospitality & Leisure Retail

    Sushi Sushi

    Food & Drink Technology