Website Redesign Checklist: Complete 2026 Step-by-Step Guide

A website redesign usually starts with a familiar observation: “Our website needs an update.”

Then the questions arrive. Which pages should stay? Who is rewriting the content? Will changing the navigation affect search traffic? And why is everyone reviewing a different version of the homepage?

The design work is only one part of the project. A successful redesign also needs clear goals, a content plan, technical decisions and a reliable way to review changes.

This website redesign checklist takes you through the process, from auditing your current site to checking the new one after launch. Use it to organise responsibilities, protect what already works and keep decisions moving.

What Is a Website Redesign?

A website redesign changes how a website looks, works or communicates. Depending on the project, it may include a new visual identity, revised navigation, rewritten content, a different CMS or rebuilt page templates.

The scope matters. Updating colours and typography is a smaller undertaking than moving hundreds of pages to a new platform.

Before committing to a full rebuild, identify the problem you need to solve. If visitors struggle with one form, improving that journey may be enough. If the site’s structure, content and technology all limit the business, a broader redesign may be justified.

Website Redesign Checklist at a Glance

Use these steps to organise your project:

1. Define your goals and success measures.
2. Audit the existing website.
3. Set the scope, budget and responsibilities.
4. Create a redesign planning sheet.
5. Plan the sitemap and user journeys.
6. Review and prepare content.
7. Plan SEO and URL changes.
8. Create and validate the design.
9. Build and review the website.
10. Complete testing and launch preparation.
11. Launch and verify production.
12. Measure results and improve.

Each stage should end with a clear decision or deliverable. That gives the next person enough information to move forward.

Step 1: Define What the Redesign Must Achieve

“Make it look modern” leaves too much room for interpretation.

Start with the business problem and the user problem. Perhaps potential customers cannot understand your services, mobile visitors abandon the enquiry form or editors struggle to update basic content.

Translate those problems into measurable goals.

Checklist:

• Identify the main business reasons for the redesign.
• Define the audiences the website needs to serve.
• List the most important actions visitors should complete.
• Record current performance before making changes.
• Agree on success measures and a review period.
• Identify who will approve the project’s direction.

For example, a service business might focus on qualified enquiry submissions. An online store might prioritise checkout completion. A support website might measure whether visitors can find useful answers.

Choose targets based on your own baseline and constraints. Avoid setting an improvement percentage simply because it sounds ambitious.

Step 2: Complete a Website Audit Checklist

Your existing website contains useful evidence. Review it before deciding what to replace.

A website audit checklist should cover content, user experience, technical health and the systems behind the site.

Content and Page Inventory

• List existing URLs and page templates.
• Identify pages that attract traffic, enquiries or sales.
• Flag outdated, duplicated or inaccurate content.
• Record important downloads, images and embedded media.
• Identify pages to keep, update, merge or remove.
• Note the owner responsible for each content decision.

User Experience Review

• Check whether navigation labels are understandable.
• Review the main journeys on mobile and desktop.
• Identify confusing forms and unnecessary steps.
• Look for unclear calls to action.
• Review available customer feedback and support questions.
• Observe representative users completing important tasks where possible.

Technical and Operational Review

• Identify broken links and unexpected error pages.
• Review performance and accessibility issues.
• Document the CMS, hosting and publishing workflow.
• List forms, payment systems, CRM connections and other integrations.
• Check analytics and conversion tracking.
• Record maintenance problems and known security issues.

Turn audit findings into specific actions. “Improve usability” is difficult to assign. “Reduce the enquiry form from three steps to one, subject to validation” gives the team a concrete proposal to assess.

Step 3: Agree on Scope, Budget and Responsibilities

A redesign can expand quickly when every review introduces another page, feature or integration.

Define the scope before detailed design begins.

Checklist:

• Confirm which pages and templates are included.
• List required features and integrations.
• Decide whether the CMS, hosting or domain will change.
• Separate launch requirements from later improvements.
• Estimate design, content, development, testing and migration costs.
• Allow time for reviews, revisions and dependencies.
• Assign an owner for each workstream.
• Define how changes to scope will be approved.

Name a final decision-maker. Teams can collect input from several people, but conflicting feedback needs someone who can resolve it.

Also agree on review deadlines. A project plan becomes unreliable when approval time is treated as unlimited.

Step 4: Create a Redesign Planning Sheet

A redesign planning sheet connects the audit to the work your team needs to deliver.

Keep it in a shared location and update it throughout the project. One row can represent a page, template or deliverable.

Include these fields:

• Page or deliverable: What needs to be created or changed.
• Current URL: Where it exists today.
• Planned URL: Where it will live after launch.
• Action: Keep, rewrite, merge, remove or create.
• Purpose: The user need or business goal it serves.
• Owner: The person responsible for delivery.
• Dependencies: Content, assets, access or decisions required first.
• Priority: Its importance to the release.
• Due date: When it needs to be ready.
• Status: Its current stage.
• Review link: Where reviewers can inspect the work.
• Approval: Who approved it and when.
• Migration notes: Redirects or other launch requirements.

For example, a services page might need new copy before its layout can be approved. Recording that dependency prevents the design team from waiting on an unexplained delay.

Use the sheet for planning and ownership. Keep detailed feedback attached to the relevant work, with a link back to it.

Step 5: Plan the Sitemap and User Journeys

Your internal company structure may not match how visitors look for information.

Build the sitemap around what people need to understand and accomplish.

Checklist:

• Group pages into clear, meaningful sections.
• Use navigation labels your audience recognises.
• Define a purpose and primary action for each key page.
• Map routes from common entry pages to conversion points.
• Include supporting pages such as FAQs and contact information.
• Consider search, filtering or breadcrumbs where appropriate.
• Review the structure with content and SEO stakeholders.
• Test important journeys before detailed visual design.

Remember that visitors may arrive through a blog post, campaign page or search result. The homepage is only one possible starting point.

Each important entry page should provide enough context and a useful next step.

Step 6: Prepare Content Before Finalising Layouts

Placeholder copy makes designs easier to approve and harder to build accurately.

Real content exposes practical questions. Does the heading fit? Does the page need comparison information? Are there enough useful images? Is the call to action specific?

Checklist:

• Assign writers and reviewers.
• Prepare copy for priority pages.
• Verify product details, prices, claims and contact information.
• Gather approved images, videos and downloadable files.
• Write clear headings and calls to action.
• Plan page titles, descriptions and relevant internal links.
• Review image text alternatives.
• Account for translations where required.
• Approve content before the final migration.

For larger sites, work by template and priority. You can validate the content structure on representative pages before applying it across the full inventory.

Step 7: Plan SEO and URL Changes

Include SEO planning before development is complete, particularly if URLs or content structure will change.

Checklist:

• Record valuable landing pages and their current performance.
• Preserve useful content and search intent.
• Keep existing URLs where a change is unnecessary.
• Map changed URLs to relevant replacement pages.
• Prepare permanent server-side redirects where appropriate.
• Update internal links to point directly to final URLs.
• Check canonical tags and sitemap entries.
• Plan the removal of staging-only indexing restrictions.
• Check language annotations if the site uses them.

Avoid sending every removed page to the homepage. Where there is a clear replacement, redirect to the relevant destination. Where content has no replacement, assess the appropriate removal response.

Google’s site migration guidance explains how to map URLs, implement redirects and monitor changes after a move. Search visibility can fluctuate while changed URLs are processed, so include post-launch monitoring in the plan.

Step 8: Create and Validate the Design

Start with structure and interaction, then develop the visual system.

Review more than polished desktop screens. Include mobile layouts, real content and the states people encounter when something is loading, missing or incorrect.

Checklist:

• Create wireframes for important templates.
• Agree on typography, colours, spacing and shared components.
• Design mobile navigation and responsive behaviour.
• Include focus, hover, loading, error and empty states.
• Test key interactions in a prototype.
• Review designs using realistic content.
• Check accessibility throughout the process.
• Approve shared patterns before extending them across the site.

Use the WCAG 2.2 quick reference to identify relevant accessibility requirements. Include keyboard access, visible focus, contrast, labels and understandable error feedback in your review.

Step 9: Build the Website and Review It in Context

A design approval does not settle every implementation detail. Real browsers, content and integrations introduce behaviour that static screens cannot fully show.

Review the working site regularly.

Checklist:

• Set up staging and appropriate access controls.
• Build reusable templates and components.
• Check layouts with real content.
• Connect forms and third-party services.
• Validate CMS editing permissions and workflows.
• Review responsive behaviour during development.
• Record issues against the affected page or component.
• Verify fixes before closing feedback.

With ruttl’s website commenting tool, reviewers can pin comments to elements on live webpages. Stakeholders can also contribute through a shareable guest link without signing up. This helps keep redesign discussions connected to the work being reviewed.

Agree on one place for actionable feedback. If decisions are also made in meetings or chat, record the outcome against the relevant issue.

Step 10: Complete Pre-Launch Testing

Test the release build against agreed acceptance criteria. Include successful journeys, error paths and the integrations behind the interface.

Checklist:

• Test navigation, search and internal links.
• Verify forms, confirmation messages and delivery.
• Complete sign-in, account or checkout journeys where applicable.
• Check supported browsers and physical mobile devices.
• Test keyboard navigation and relevant assistive technology.
• Review content, media and downloads.
• Validate redirects, metadata, canonical tags and sitemap URLs.
• Verify analytics events and consent behaviour.
• Check permissions and sensitive data handling.
• Retest fixes and run critical regression checks.

For performance, review loading, responsiveness and visual stability across representative templates. Google’s Core Web Vitals guidance defines good thresholds as LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, assessed at the 75th percentile of visits. Use lab checks before launch and field data when available.

Step 11: Launch With a Recovery Plan

Give the launch a named owner, an agreed sequence and a recovery path.

Checklist:

• Confirm release approval and accepted exceptions.
• Back up relevant files, databases and configuration.
• Define rollback triggers and responsibilities.
• Plan any content freeze or final data synchronisation.
• Deploy the approved build.
• Apply production configuration and redirects.
• Remove unintended production indexing restrictions.
• Verify HTTPS, critical pages, forms and integrations.
• Confirm monitoring and alerts are working.
• Record the release time and build version.

Run production smoke tests immediately after deployment. A successful staging test does not confirm that production credentials, domains and services are configured correctly.

Step 12: Monitor Results and Improve

The redesign is live, but the project still needs evidence that it is working.

Compare results with the baseline established at the start. Account for tracking changes, campaign activity and seasonality before attributing every difference to the redesign.

Checklist:

• Monitor errors, failed transactions and form delivery.
• Check redirects and unexpected missing pages.
• Review crawling and indexing reports.
• Confirm analytics data remains accurate.
• Track important conversions and user journeys.
• Review real-user performance as data becomes available.
• Collect feedback from visitors and internal teams.
• Prioritise follow-up improvements.
• Assign ongoing content and maintenance ownership.

A practical review schedule might include immediate launch checks, daily checks during the first week and broader reviews after 30, 60 and 90 days. Adjust that schedule to the site’s traffic and risk.

Common Website Redesign Mistakes to Avoid

Starting With Visuals Before Defining the Problem

A new appearance cannot resolve an unclear proposition or a broken customer journey by itself. Agree on the problems first.

Removing Pages Without Reviewing Their Value

An older page may still generate enquiries, attract useful links or answer an important question. Review evidence before removing it.

Leaving Content Until the End

Late copy and missing assets create avoidable redesign work. Give content its own owners, deadlines and approvals.

Collecting Feedback Across Too Many Channels

Scattered comments make it difficult to establish which decisions are current. Connect feedback to the page, component or deliverable it concerns.

Treating Launch Day as Completion

Reserve time for production checks, monitoring and fixes. Include those responsibilities in the original scope.

Keep Redesign Reviews Organised With ruttl

Website redesigns involve decisions from design, development, content, marketing and client teams. Clear feedback helps those decisions move forward.

Use your redesign planning sheet to manage scope, deadlines and ownership. During website reviews, use ruttl to discuss issues against the relevant page elements.

A useful comment explains what is wrong, where it happens and what outcome is expected. That gives the next person enough context to act without another round of clarification.

Try ruttl free and bring your next website review into one shared workspace.

Wrapping Up

A website redesign checklist helps your team connect the work to the reason for doing it.

Start with clear goals and an audit. Plan content, structure and URL changes before building. Review the implementation throughout development, test the release and keep monitoring after launch.

The result should give visitors a clearer, more reliable way to find information and complete the actions that matter.