Website redesign checklist: plan a website that works for your business

What should a website redesign actually change?

A website redesign is the process of improving a website’s content, structure, interface, and technical delivery. Its value comes from helping visitors understand your business and complete useful actions, while making the site easier for your team to maintain. A new visual identity can be part of that work, but the project also needs clear decisions about navigation, editing, performance, and ownership.

For a US or Canadian business, the first question is often practical: can a prospective customer understand the offer, assess whether it fits, and contact the right person? Write down where that journey currently breaks. A visitor may struggle to find a service, a salesperson may receive enquiries without enough context, or staff may need a developer for every content change. Those observations give the redesign a purpose.

1. Define the audience, outcome, and baseline

Choose one primary outcome and a few supporting measures. A business website might aim to increase qualified enquiries, help buyers compare services, or reduce repeated support questions. Distinguish a useful enquiry from a form submission that does not match your offer. Review existing analytics, search queries, customer questions, and feedback from the people who answer calls.

Create a baseline before work begins. Record current enquiry quality, popular entry pages, frequent navigation problems, and how long routine content updates take. If analytics are incomplete, say so and establish a measurement plan. Avoid promising a percentage improvement without evidence. A redesign can improve the conditions for a better experience, while sales outcomes also depend on the offer, demand, and follow-up.

• Name the primary audience and their main task.
• Define the action that counts as a useful outcome.
• Record available evidence and important unknowns.

2. Audit the pages and content you already have

List the existing pages, their URLs, owners, and intended audiences. Decide which pages to keep, improve, combine, or retire. Check whether important claims are supported, service descriptions answer real questions, and contact details are current. An inventory prevents a visually polished site from launching with outdated or contradictory information.

Assign an owner and deadline to each new piece of content. Product photography, staff biographies, pricing explanations, and approval of technical claims can become dependencies. Plan those responsibilities alongside design. For businesses serving both the USA and Canada, explain genuine service coverage and relevant delivery arrangements. Separate country pages are useful when the information actually differs; duplicating a page with only a country name changed adds little value.

3. Build the navigation around visitor decisions

Group pages by the questions visitors are trying to answer. A person comparing providers needs to understand capabilities, relevant experience, delivery approach, and the next step. Use familiar labels and make the important paths easy to find on a phone. Internal department names do not always make useful navigation labels.

Review a simple sitemap and a few page outlines before designing every screen. Each page should have a clear purpose, a descriptive heading, enough context to support a decision, and an appropriate call to action. A service page may invite a project discussion; a guide may point to a related capability. Repeating the same sales prompt everywhere can interrupt the reading experience.

4. Protect search visibility when URLs change

Keep useful existing URLs when there is no strong reason to change them. Where a page moves, map its old URL to the most relevant new destination and test the redirect. Update internal links, canonical URLs, and the sitemap. Avoid sending every retired page to the homepage when a more appropriate destination exists.

Google’s site-move guidance recommends preparing a URL mapping and checking the new site before switching. Search visibility can fluctuate while changed URLs are processed, so a redesign should include monitoring rather than a guarantee that rankings will stay identical. Review important landing pages, indexing, and broken links after launch.

Reference: Google Search Central: site moves with URL changes

5. Design and test the actual content

Use realistic headings, long service names, real images, and representative testimonials in the design. Placeholder copy can conceal problems with line length, navigation, and page height. Review the experience on narrow screens and with a keyboard, including menus, form labels, focus indicators, validation messages, and confirmation states.

Treat performance as part of the page design. Large imagery, embedded video, fonts, and animation all affect delivery. Plan image sizes and loading behavior around their role on the page. A hero needs enough resolution to look clear, while below-the-fold images can load later. Test important pages on ordinary devices and connections instead of relying on a single desktop preview.

6. Confirm editing, integrations, and ownership

Ask your team to perform common editing tasks in the proposed content management system. Can they change a service description, replace an image, and add a new article without breaking the layout? Define which changes they can make and which require technical help. Permissions should reflect the responsibilities of the people using the system.

List every connection: enquiry routing, CRM, analytics, scheduling, newsletter tools, and payment services if applicable. Test the complete flow, including what happens when a connection fails. Agree who owns domains, hosting, repositories, licenses, and support. Those decisions affect the website’s running costs and how easily another team can maintain it.

7. Use a release checklist and review after launch

Before going live, check forms, links, redirects, responsive layouts, analytics events, metadata, and access to the production accounts. Confirm that test-only restrictions are removed from the public site and that a recovery plan exists. Have the person responsible for content approve the final copy and the technical owner approve the release steps.

After launch, review enquiry quality, user feedback, indexing, and important failures. Compare results with the baseline using a sensible observation period. Agree which improvements belong in support and which require a new scope. The first live version is a working starting point; a short, prioritized improvement list is more useful than reacting to every request at once.

• Content and URLs approved
• Visitor tasks and forms tested
• Production access and recovery steps documented
• Measurement and support owners assigned

How to prepare for your first redesign conversation

Bring your current website URL, the main audience, the problems you want to solve, and any fixed deadlines. Share existing analytics and a few examples of websites you find clear, explaining what works about them. You do not need to arrive with a finished specification.

A useful first discussion should clarify the scope, dependencies, content responsibilities, and next decision. Valley of Digital can help connect content planning, responsive design, development, and handover around your business’s priorities. The right starting point may be a focused review or prototype before a full rebuild.