A website that no longer works for your business does not always need to be replaced. Sometimes clearer content, better navigation and a few carefully chosen improvements will solve the problem. In other cases, the existing structure makes every change difficult, and a rebuild gives you a more practical foundation.
The useful starting point is to identify what is getting in the way. A dated appearance is one issue; an unreliable editing system, confusing services or a broken contact journey are different problems with different solutions.
What is the difference between a redesign and a rebuild?
A redesign changes how a website looks and how people use it. That might include new layouts, clearer page structure, updated typography and more useful navigation, while keeping the existing platform and much of the underlying setup.
A rebuild replaces more of that underlying setup. On a WordPress website, this could mean a new theme, a different content structure or replacing functionality that is difficult to maintain.
The terms overlap. Ask what will actually be retained, changed and tested when you compare proposals.
When focused improvements may be enough
Your website may be a good candidate for smaller changes if you can still edit it comfortably, its main features work and its pages broadly match the business you run today.
Look for specific problems you can describe clearly:
- Visitors struggle to find a particular service.
- Your best work is missing or poorly explained.
- Important information is buried below less useful content.
- Mobile layouts make reading or contacting you awkward.
- Your wording no longer reflects the work you want to attract.
For example, if your services have changed but the website remains straightforward to manage, rewriting and reorganising those pages may be more useful than replacing the whole site.
When a rebuild deserves consideration
A rebuild is worth investigating when the current foundation repeatedly prevents necessary changes. Perhaps routine edits require workarounds, important functionality depends on software that is no longer maintained, or your business needs a substantially different structure.
None of these signs automatically proves you need a new website. A review should establish what causes the problem, what can be repaired and what each route would involve. A slow website, for example, needs investigation before deciding whether a rebuild is the answer.
Check your content before changing the design
Make a list of your existing pages and decide which still serve a purpose. Note what should stay, what needs rewriting and which questions are unanswered.
If you have Search Console and Analytics data, use it to understand which pages attract visitors and what they do next. A page that looks unremarkable may still answer an important customer question. Keep that evidence alongside your design preferences.
This is also the moment to collect project examples, photography and service information. Missing content can delay both a modest redesign and a full rebuild.
Protect useful URLs and contact routes
Changing a website can affect more than its appearance. Record existing URLs before work begins, agree which will remain and plan relevant redirects for any that change.
Check forms, email links, downloads and other important journeys before launch. Agree how enquiries will be measured afterwards. An email-link click can show interest, but it does not confirm that someone sent an enquiry.
If search visibility matters to your business, include SEO review and launch checks in the scope from the start.
Compare the full scope
Ask each proposal to explain what is included in content, design, development, testing and handover. Check who supplies copy and images, which features are included and what happens after launch.
If you need ongoing help, my WordPress hosting, maintenance and support services explain the support available beyond the initial project.
For a rebuild, ask how you will manage the new site. For a redesign, ask whether any existing limitations will remain. The best option should solve the problems you have identified and fit the way you need to use the website.
My guide to choosing between a template and a custom build explores that foundation decision in more detail.
Start with a clear list of problems
Before committing to either route, write down what your website needs to help customers understand, what currently gets in their way and what your team finds difficult to manage.
That gives you a practical basis for deciding whether to improve the existing site or replace more of it.
If you would like help assessing the options, explore my website design and WordPress development services or tell me about your website.