Redesign your website or improve what you have?

A website that generates too few enquiries does not necessarily need rebuilding. The problem may be an unclear offer, a broken form or pages that are hard to find. A redesign becomes useful when the structure or technology prevents the improvements the business needs. Base the decision on the problem, not just the site’s age or appearance.

Start with the action you expect a visitor to take

Choose a primary action: a quote request, booking, order or contact. Walk through the site as a new customer, including on a phone. Can you understand the offer without extra explanation? Can you find the right service? Does the form confirm submission, and does the enquiry reach the person responsible for replying?

Separate traffic problems from page problems. If few relevant visitors arrive, a new design alone is not evidence that enquiries will increase. If people arrive but encounter errors, fixing those errors may be the first useful project.

When improving the existing site makes sense

• The pages and platform support the current offer, but the messaging is unclear.
• Problems are specific: a form, navigation, large images or a few templates.
• The team can edit content and updates can be tested safely.
• Useful pages, photographs, URLs and features are worth keeping.

Define a short list of changes and acceptance criteria. For example: a visitor can find the service in the menu, understand what it includes and send an enquiry without an error. Verify the result before extending the work.

When a redesign may be justified

• The offer or audience has changed and the page structure no longer represents it.
• Templates cannot support the required features or content types.
• Repeated changes create compatibility problems and maintenance becomes difficult to control.
• Almost every routine content update needs technical intervention.

These signs justify an assessment, not an automatic migration. Compare the cost and risk of repair with rebuilding, including content, licences, data integrations and handover. Rebuilding one section may be enough.

What to preserve before building something new

Inventory page addresses, useful content, images, forms, integrations and measurement data. Confirm who controls the domain, hosting and relevant accounts. Do not remove a working site before a restorable copy and launch plan are in place.

If URLs change, map old addresses to their new equivalents and prepare redirects. Update internal links and the sitemap. Google recommends planning and monitoring URL moves; rankings may fluctuate during recrawling. Google’s guide to URL changes.

A decision example

Hypothetical example: a service business has an editable website, but every offer sits on one page and the form is difficult to use on a phone. The first option to assess is separating services and fixing the form, not changing platform. If the current platform cannot support the required page management without fragile workarounds, rebuilding becomes an option to compare.

What to request in the proposal

Separate the work into structure and copy, design, implementation, migration, measurement and maintenance. Agree who approves materials, what will be tested and how to restore the previous state if launch causes problems. A “modern website” is not a sufficient acceptance criterion.

For a rebuild, explore website design and redesign. For targeted changes and ongoing operation, see website management and maintenance. If the issue is turning visits into enquiries, conversion optimisation may be relevant.