Structure & usability review
A review of the existing pages, navigation, visitor journeys, and the issues the redesign should address.

A redesign is a chance to make your website more useful—not simply to change the colours. I help reshape outdated websites around the people, content, and business they need to support.
Discuss website redesignThe process starts by understanding what works today and what causes friction. Navigation, page hierarchy, mobile layouts, forms, content management, and loading behaviour can all be reviewed before a new design is developed.
Existing content and URLs deserve attention during a redesign. Useful pages should have a clear destination in the new structure, and necessary URL changes should be planned with redirects. Depending on the condition of the current site, the project may retain the existing platform or move to a more suitable one. That decision is made from the requirements and maintenance needs rather than appearance alone.
The final deliverables are agreed around your project. Here are the areas this service can cover.
A review of the existing pages, navigation, visitor journeys, and the issues the redesign should address.
Updated visual direction and page layouts, with development of the agreed functionality for desktop and mobile.
Planning for existing content, important page addresses, and redirects where the new structure requires a change.
We review the current website, identify important content and URLs, and agree the main problems to solve.
I create the new structure and interface, then develop and test the features included in the project.
We check content, links, forms, redirects, and hosting requirements before replacing the existing site.
Where the content and structure allow it, yes. Important URLs are identified early. Any necessary changes should be mapped to relevant new destinations with redirects.
Not necessarily. Sometimes improving the existing platform is enough. A migration is considered when functionality, maintainability, or technical limitations justify it.
Development can usually take place in a separate environment so the current website remains available until the agreed launch. The exact setup depends on hosting and access.
We agree a content inventory and decide what to retain, improve, or remove. The migration scope should be confirmed rather than assuming every old page is still needed.