Website decisions
Website redesign or a new website: which do you need?
A website that feels dated does not automatically need to be replaced. Start with the problem you want to solve, then decide how much of the existing site needs to change.
The short answer
Improve the existing site when the foundations work and the problems are specific. Redesign when the structure or presentation needs attention. Consider a rebuild when the underlying platform or implementation prevents the changes you need.
1. Separate an improvement, a redesign and a rebuild
Providers use these terms differently, so ask what will actually change.
- An improvement fixes specific issues, such as confusing service copy, a broken form or oversized images.
- A redesign changes the layout, visual presentation or page structure. It may keep the existing platform.
- A rebuild replaces a substantial part of the underlying website implementation, sometimes including its content management system.
These options can overlap. A redesign may include some technical rebuilding, while a rebuild may keep familiar content and branding. A proposal should describe the scope clearly instead of relying on a label.
2. Diagnose the problem before choosing the solution
List the symptoms and the evidence for each. “The website is not working” is too broad to guide a useful decision.
| What you notice | What to check first |
|---|---|
| Visitors arrive but do not enquire | Whether the visitors are relevant, services are clear and the contact process works. |
| The website is slow | Image sizes, scripts, embedded tools and hosting before assuming every page needs replacing. |
| Updating content is difficult | Whether the editing process, permissions or platform is the obstacle. |
| The business has changed | Whether the page structure still reflects your services and customers. |
| The site looks dated | Whether a focused visual refresh would solve the problem while retaining useful content. |
Check the enquiry form yourself. Confirm that a successful submission reaches the right inbox. If tracking is available, compare visits with genuine enquiries and ask which pages those customers used. These checks can reveal a smaller and more useful first step.
3. Match the scope to the evidence
If the content is clear, the platform is maintainable and the site works on a phone, targeted improvements may be enough. Changing a confusing contact section is a different job from replacing the entire site.
A redesign becomes more useful when visitors repeatedly struggle to understand the services or find information, or when the business has outgrown its original structure. A rebuild is worth considering when the existing setup makes necessary changes impractical or leaves you dependent on components you cannot reasonably maintain.
The Inspectra project describes a rebuild that addressed an inspection business's website, a booking embed and suburb information. The important lesson is to connect the proposed work to specific problems, rather than assuming the same approach suits every business.
4. Identify what is already worth keeping
Before changing the site, make a list of the pages, content and features that serve customers well. Include pages that receive relevant search visits, useful project photography, service explanations, booking links and contact details.
Save a copy of the current website and record who has access to the domain, DNS, hosting, email and analytics accounts. Make sure you understand which services depend on those settings. Moving a website and moving business email are separate decisions.
Ask the designer to explain what will be retained and why. Starting from a new template should not mean discarding the information your customers rely on.
5. Treat launch as part of the project
If page URLs change, map each old address to its appropriate replacement and set up permanent redirects. Update internal links and the sitemap to use the intended addresses. Google's site-move guidance explains URL mapping, redirects and post-launch monitoring.
A redesign cannot guarantee unchanged search rankings. Google advises that significant site moves can cause temporary fluctuations as pages are recrawled and reindexed. Preserve useful content and plan the change carefully rather than promising a risk-free move.
Before launch, test forms, mobile navigation, booking links and the pages most likely to be visited. After launch, check them again on the live domain. Confirm that analytics is working and monitor Search Console for unexpected indexing or URL problems.
6. Write a brief that makes proposals comparable
A useful brief includes the business goal, current problems, pages to retain, required features and who will manage the finished site. Ask providers to separate essential launch work from optional later improvements.
- What evidence supports a rebuild rather than a smaller improvement?
- Which URLs and content will remain?
- Who prepares and tests any redirects?
- What happens to booking, email and analytics connections?
- What access and files will you receive?
- What support is available after launch?
You do not need to decide on a platform before having that conversation. First establish the outcome and the constraints. Our web design service covers new and redesigned sites, while website support may suit businesses that need targeted changes.