The first step is understanding the current business
A redesign begins by clarifying what has changed and what the website needs to support now. Your audience, services, and day-to-day customer questions help shape that discussion.
The existing website is a starting point, not merely something to replace. Useful content, familiar journeys, and recognizable brand elements can inform the new direction.
The structure and content develop together
The sitemap sets out the pages and their roles. Content planning helps establish what each page needs to explain and where a visitor should go next.
You may be asked for existing copy, service information, practical details, images, and access to the current site. Agree on which materials you provide and which writing, editing, or migration work is in scope.
Design reviews connect the idea to its purpose
The visual direction brings typography, imagery, hierarchy, and interaction into one experience. Feedback is most useful when it describes how the direction supports the business and audience.
Instead of only saying that a section feels wrong, explain whether the message is unclear, an important detail is missing, or the tone does not fit your customers. That context gives a design decision something concrete to answer.
Development makes the experience testable
The approved direction becomes a working website. Layouts, navigation, forms, and agreed functionality can then be reviewed in the context of the real experience.
Use the review stage to try important tasks on different screens. Read the content, follow key links, and submit test enquiries through the agreed testing setup. Distinguish content corrections from new requirements so their effect can be discussed.
Migration deserves its own plan
A redesign can change page addresses, content organization, or the underlying platform. Important existing URLs and functionality should be identified before launch.
Discuss which pages remain, which move, and which need redirects. Review page information and search foundations alongside the new content. No migration can promise unchanged search outcomes, but the transition should be considered rather than accidental.
Launch is a checklist, not a single button
A launch plan brings content readiness, account access, forms, navigation, responsive checks, and the technical transition together. The details depend on the current hosting and website setup.
Agree who makes the final decision and how the live site will be checked after the transition. If any interruption is expected, it should be discussed before the change is made.
Handover makes the next chapter practical
The finished website needs clear responsibilities. Account access, documentation, editing needs, and maintenance should be understood as part of the project.
Further support, search work, content, or optimization can be planned separately. Explore what happens after launch or our website redesign service to see how the pieces fit together.
KEEP EXPLORING
A related perspective.
THE ENQUIRY JOURNEY
Why Your Website Gets Visitors but Not Enquiries
Explore the difference between website traffic and useful enquiries, including audience fit, clear messaging, trust, mobile usability, and form friction.
Read the perspectivePROJECT PLANNING
What Small Businesses Should Know Before Hiring a Web Design Agency
Useful questions about project fit, scope, ownership, content, maintenance, and evidence before choosing a website design partner.
Read the perspectiveYOUR NEXT HORIZON
Have a question about your own website?
Tell us what you want to improve and where you are starting from.