Guides and Articles
Website Redesign: Existing Content, Navigation and a Controlled Transition
Plan a website redesign through user problems, content and working systems. Preserve useful addresses and data while improving the experience and launch transition.
Website redesign changes an existing site's structure, appearance or behaviour. It should begin with what needs improvement and what already works. Rebuilding every page without understanding those relationships can replace useful functions with a more attractive but less effective site.
Define the Problem Before the New Look
Visitors may struggle to find services, complete forms or understand the offer. Staff may have difficulty maintaining content. Those are different problems and can require different changes.
Existing evidence, support questions and direct task checks can help identify priorities. The redesign should connect its decisions with those needs rather than assume a fashionable visual style resolves them.
Inventory Content and Addresses
Pages, downloadable files and media can have relationships with navigation, external links and internal tools. The project needs to decide what stays, changes, combines or is removed.
Existing addresses should be handled deliberately when content moves. A new menu does not automatically preserve a visitor's saved link. The transition plan should map useful old destinations to their new counterparts where appropriate.
Improve Structure and Page Templates
Design work can reorganize navigation and create clearer page patterns. Real titles and content should be used to test those patterns, especially across large collections.
Mobile layouts and forms need practical checks. A redesign can look complete in a desktop presentation while leaving narrow-screen tasks awkward or hiding information required to make a decision.
Working Systems Need Migration Planning
Forms, stores, booking tools and account functions connect with data and external services. The new site needs to preserve or intentionally replace those connections. A visual recreation alone does not move the underlying system.
E-commerce can involve product, customer and order data with different migration needs. The responsible team should identify what transfers and how the result is verified.
Test the Transition
The project should check representative visitor journeys, content and technical connections before release. Accessibility review examines barriers that can remain behind a cleaner visual design.
Deployment planning needs a recovery approach and clear responsibility. The business should know how changes are released and how a problem is handled rather than discover those arrangements during launch.
After the Redesign
Maintenance keeps continuing operation distinct from the redesign project. Updated editing guidance and access should reflect the new site. A handover based on the old system can leave staff unable to maintain the improvement.
Redesign Questions
Must every existing page be rewritten?
No. Assess usefulness and quality rather than replace automatically.
Does a new design preserve old links by itself?
No. Address changes need an intentional transition.
Is changing appearance the same as migrating a store?
No. Data and functions need separate planning and checks.
Improve Without Losing What Works
Use the provider guide to compare the new experience and the transition from the existing one.