Skip to content
All guides

Website strategy / Decisions

Should you redesign your website or improve what you have?

A dated website doesn't always need rebuilding. Learn what to inspect before spending money on a replacement.

4-minute read · Businesses with an existing website
01

Start with the problem, not the redesign

A site can feel old because of its colour scheme, but the real problem may be a confusing menu, missing service information, hard-to-use mobile layout or a contact process that doesn't work. Those are different kinds of problems, with different fixes.

Try navigating your website as a new customer. Can you understand what the business offers in a few seconds? Can you find pricing or contact information? Does the site work on the phone your customers use?

02

When improving the existing site can make sense

If your core content, infrastructure and customer journeys still work, focused improvements may offer a practical route forward. Examples include rewriting a confusing homepage, reorganising services, improving navigation or checking accessibility and mobile layouts.

  • The current hosting and code are maintainable.
  • Your content and page structure are mostly suitable.
  • The main problems are limited to a handful of screens or journeys.
  • Existing integrations work and can remain in place safely.
03

When a broader rebuild may be justified

Sometimes a website's limitations are structural. Its technology may no longer suit the business, editing simple content may be difficult, pages may not adapt properly to phones, or new features may be hard to add without breaking others.

A rebuild is not automatically safer. Before changing platforms or hosting, document critical pages, login methods, payments, customer records and domain ownership. Arrange a preview and a tested way to recover if something goes wrong.

04

What to ask before migrating

A domain name, website files, email service and database may be managed in completely different places. Moving one does not necessarily move the others. Know which provider controls each part and who has access before making DNS or hosting changes.

  • Which pages and URLs must remain accessible?
  • Will existing search links redirect correctly?
  • How will contact forms, logins and payments be tested?
  • Who controls DNS, hosting and business email?
  • What is the rollback plan if the new version fails?
05

Choose the smallest safe change that solves the issue

A careful audit can identify which problems are urgent and which are purely aesthetic. The best outcome is not necessarily the newest technology; it's a site your customers can use and your business can maintain.

If you're unsure, start by describing what currently frustrates visitors or your team. A public-facing website review is a reasonable first step before committing to a larger project.

Before you start

Your preparation checklist.

  • Test your website on your own phone as a new visitor.
  • List broken features separately from visual preferences.
  • Identify domain, email, hosting and content ownership.
  • Document critical customer and staff workflows.
  • Get a written improvement or migration scope before making changes.

From reading to doing

Ready to discuss
your own project?

Talk through website improvements