A website redesign should solve specific problems in an existing site: confusing content, difficult editing, poor mobile use or journeys that do not reach the right team. Zoha reviews the current website before proposing a replacement. Useful content, addresses and account ownership need a transition plan as well as a new design.
Updated
On this page
Name the problem before changing the appearance
Ask staff which questions visitors repeatedly call about and which pages they struggle to update. Review the actions that matter, such as finding a program, requesting an appointment or sending a business enquiry. Those answers give the redesign a purpose.
Visual consistency may be part of the work, but it is not the only consideration. A modern-looking homepage will not fix missing service information or enquiries sent to the wrong inbox. Turn each problem into a check that the replacement should pass.
Decide what to keep, rewrite and remove
| Content category | Decision |
|---|---|
| Still accurate and useful | Retain it and give it a clear place |
| Useful but outdated | Assign an owner to update it |
| Duplicated or confusing | Combine it into one useful destination |
| No longer needed | Decide how old visitors and links will be handled |
An old site can contain years of documents and articles. Count the material that needs review instead of assuming a new layout will make it all suitable. Agree who approves factual changes and who supplies missing images, translations or documents.
Test a representative journey early
Use a page outline and clickable prototype to check the new structure. For a hypothetical training business, a visitor should be able to identify an appropriate course, check eligibility and send an enquiry to the right department. Test the wording and navigation before filling every course page.
Invite staff who handle those enquiries to review the journey. Record the questions that remain unanswered. A clear route and complete information can matter more than an additional animation or another block of introductory text.
Treat the switch as a separate job
- Keep an inventory of old addresses and map changed pages to suitable destinations.
- Transfer approved content and check important images and documents.
- Test forms, analytics where used, search settings and staff access.
- Agree the launch window, final approval and rollback responsibility.
A redesign may involve a platform or hosting change, but that should be stated separately. If the design can be improved without moving everything, compare that option too. The migration scope should reflect what is actually changing.
Measure the agreed improvements
Choose a small set of checks before work starts. They might include finding a service without help, completing an enquiry on a phone or allowing an editor to publish a news item. Use the same tasks to review the replacement.
After launch, watch for broken addresses, failed submissions and staff editing problems. Search visibility and user behavior can change for several reasons, so avoid attributing every movement to the design. Record observations and fix specific issues rather than promising a guaranteed traffic increase.