A dated appearance is not enough evidence to justify rebuilding a website. Start with the problems customers and staff experience, then determine whether focused repairs can solve them. A redesign becomes a stronger investment when its scope addresses structural limits that smaller changes cannot reasonably fix.

This guide covers current-site constraints, focused fixes versus rebuild work, retained content and migration priorities. Discuss the relevant requirements through ITZ’s Website Redesign service.

Customer experience

Review whether visitors can find relevant services and complete contact tasks on supported devices. Identify confusing navigation, unreadable layouts and form problems before deciding the scope of change.

Record observable task failures rather than collecting only preferences about colours. Can visitors find the right service, read important details and send an enquiry? Ask staff what questions arrive because the site is unclear. Prioritise problems by their effect on real journeys and the confidence of the evidence, not how recently a competitor changed its design.

Technical condition

Assess platform support, dependencies, loading performance and access arrangements. Some issues can be resolved through maintenance; others may require replacing components or changing the platform.

Review the platform, dependencies, editing model and support situation. Some issues can be corrected with maintenance or performance work; others may reveal unsupported components or a structure that cannot accommodate required content. Ask for an assessment that distinguishes defects, technical constraints and optional enhancements before agreeing to replace the whole site.

Review Your Website Redesign Priorities to discuss current-site constraints, focused fixes versus rebuild work, retained content and migration priorities.

Content and brand alignment

Check whether the site accurately describes the current business, service areas and offering. A redesign may be appropriate when the structure no longer supports the information customers need.

Map the current business offering against the published content. A company may have changed its services while retaining a site organised around an old model. Fixing that mismatch requires content decisions as well as visual design. Keep useful material and verified evidence, and assign an owner to create missing explanations before the new layouts depend on them.

Transition planning

Preserve useful content and established URLs where practical. Map necessary redirects and define checks for forms, integrations and key pages before release. Use evidence to prioritise work instead of redesigning solely because of the site’s age.

Protect existing URLs, search signals and enquiry operations during transition. Google's site-move guidance explains the need to plan URL changes and redirects. Define launch checks and a rollback route. A visually successful redesign can still damage customer journeys if old links fail or enquiry delivery is not verified after deployment.

A practical example

Illustrative example: a site has reliable service content but an awkward form on mobile. A targeted form and navigation improvement may be sufficient. Another site may need a rebuild because its unsupported platform cannot deliver required branch pages and editing controls. The scope should follow the diagnosed constraint in each case.

Your review checklist

  • List evidenced customer and editing problems.
  • Separate focused fixes from structural platform limitations.
  • Retain useful content and plan missing material.
  • Protect URLs, enquiry delivery and rollback arrangements.

Frequently asked questions

Is a complete rebuild always necessary?

No. A focused assessment can identify whether content updates, performance work or interface changes will address the problem without replacing the entire site.

References and further reading

Related services and guides

Discuss the next step

Review Your Website Redesign Priorities. Use the form below to discuss current-site constraints, focused fixes versus rebuild work, retained content and migration priorities. Share the relevant goals and existing arrangements; do not include passwords, private records or access tokens.

Review Your Website Redesign Priorities ↗

Reviewed and expanded on 15 October 2026. Examples are illustrative; the appropriate approach depends on your business requirements and existing systems.