Decide what the redesign must improve
A website redesign checklist should begin with the problems you want to solve. An outdated appearance may be one issue, but it does not explain why customers abandon an enquiry or why staff cannot update a service description. Record those problems separately so design decisions have something concrete to answer.
Choose a small set of outcomes before discussing layouts. These might be clearer service information, fewer failed form submissions or a simpler editing process. Record the present position and how you will compare it after launch. Treat an improvement as something to verify, rather than a promised result of a new design.
Name the decision-maker, content owner and technical contact. Agree which decisions need wider review and when feedback must arrive. A short decision log helps everyone understand why an earlier option was rejected without reopening the same conversation.
Inventory what exists before removing it
Make a list of current pages, documents, forms, integrations and important media. Include material that is not linked from the main menu. Record each item's purpose, owner, accuracy and proposed action: retain, improve, combine or retire. Check that any photographs, logos and testimonials have permission for their intended use.
Ask colleagues which pages they send to customers. Review available enquiry and search data alongside that feedback. A page with few visits can still answer an important question or support an existing customer. Avoid treating low traffic alone as a reason to delete it.
Keep a copy of approved content and export the information your team needs before changing platforms. Confirm who holds domain and hosting access, and whether a previous supplier must help with the transfer. Do not put passwords in the content inventory.
Plan the structure and URL changes
Sketch the proposed navigation around customer tasks. Give each page a clear job and remove competing versions of the same explanation. Review the plan with someone who did not create it: can they find what is included, what happens next and how to contact you?
If addresses will change, create an old-to-new URL map. Google's migration guidance recommends testing the new site, mapping URLs, implementing redirects and monitoring the move. Where a page has a genuine replacement, send visitors to that relevant destination rather than automatically sending everything to the homepage.
Treat a domain move, platform change and visual redesign as separate decisions. Google advises changing one thing at a time where possible. Your technical lead should explain which changes can be separated and what makes any combined release necessary.
Agree content and design acceptance checks
Approve real copy before judging whether a layout works. Long service names, actual contact details and realistic form errors reveal problems that placeholder text hides. Identify who checks claims, pricing and policies, and keep a record of the version they approved.
Test representative pages with a keyboard, enlarged text and a narrow screen. Review headings, form labels and image alternatives. W3C's Easy Checks provides a starting point, but passing a quick review does not establish complete accessibility. Arrange a fuller assessment appropriate to the site and its users.
Set practical acceptance criteria for the editing experience too. Ask the person who will maintain the site to change a paragraph, replace an image and preview a page. Record any training or documentation needed before they take ownership.
Prepare the handover and release decision
List what must be true before launch: approved content, completed critical journeys, an agreed redirect map, account access and a recovery plan. Give each check an owner and evidence location. Mark unresolved issues by their effect on users, rather than by how easy they are to fix.
Plan how enquiries and transactions will be handled during the change. Agree who can stop the launch and what would trigger a rollback. The detailed release checks belong in a separate launch plan; this planning checklist should ensure that plan exists and has an owner.
After launch, compare the agreed outcomes with the baseline and review customer feedback. Keep a named person responsible for content accuracy, technical issues and improvement decisions. A redesign is ready to hand over when the team can operate it, not simply when the new homepage looks finished.
Website redesign checklist: copyable planning record
Copy these fields into your project document. Use one page record for each existing URL and one decision record for each unresolved choice. Leave a field marked unknown when it still needs investigation.
Project: [name]. Decision-maker: [name]. Content owner: [name]. Technical contact: [name]. Main problem: [observed issue]. Desired outcome: [observable change]. Baseline and evidence: [measurement or feedback]. Review date: [date].
Page record: [current URL]. Purpose and audience: [details]. Content owner: [name]. Decision: [retain / improve / combine / retire]. Reason: [evidence]. Replacement URL if applicable: [destination]. Content approval: [owner and status]. Migration check: [owner and evidence].
Decision record: [question]. Options: [choices]. Dependency: [what is needed]. Owner: [name]. Due date: [date]. Decision and reason: [result]. Effect on scope or launch: [details].
Planning completion: [ ] Outcomes and baseline recorded. [ ] Content inventory reviewed. [ ] New page structure agreed. [ ] URL changes assigned. [ ] Content and design acceptance checks agreed. [ ] Release and recovery plan assigned. [ ] Operating owner and handover requirements agreed.