Journal
Website RedesignWebsite AuditUX DesignSEOWeb DesignNovember 17, 2026

Website Redesign Checklist: What to Audit Before You Rebuild

A practical website redesign checklist covering goals, analytics, content, SEO, accessibility, performance, launch QA and the first 30 days after release.

By Rixlab Agency

A website redesign starts with evidence

A website redesign is useful when the current site no longer helps the right people understand your offer, trust your business, or complete a meaningful action. A new color palette alone cannot solve unclear messaging, broken journeys, slow pages, or missing search traffic. Before anyone designs a new homepage, record what the current website does well and where it fails.

This website redesign checklist is for founders, marketing teams, and product owners preparing a rebuild. It moves from diagnosis to content, UX, SEO, accessibility, development, launch, and measurement. Use it as a working document: assign an owner and evidence to each item, then decide what to keep, change, or remove.

The photos in this article are real editorial references to the type of work involved. They are not screenshots of a Rixlab client project or proof of any measured result.

The 12-point website redesign checklist

Before design: (1) Agree on business goals and target users. (2) Record a baseline for traffic, leads, and key actions. (3) Interview users or review real customer questions. (4) Inventory every important page and asset.

During planning and design: (5) Define the site map and user journeys. (6) Rewrite priority content before polishing layouts. (7) Design mobile, accessibility, and form states. (8) Plan search intent, page titles, URLs, and redirects.

Before and after launch: (9) Build for performance and maintainability. (10) Test the full experience, including errors and tracking. (11) Launch with a rollback plan. (12) Compare results over the next 30 days and improve the weak points.

The checklist is a sequence, not twelve isolated boxes. A conversion problem may come from the offer, the page structure, the form, or the traffic source. The job is to connect evidence to the design decision and then to a measurable outcome.

A simple example: a service page with visits but few inquiries

Suppose a service page receives steady search visits, but very few qualified inquiries. A visual refresh may help, yet first inspect the full path. Is the page answering the query that brought the visitor in? Can a reader tell who the service is for, what is included, and what the next step costs in time or effort? Does a case study provide relevant proof? Does the form work on mobile?

A useful redesign brief would connect observation → hypothesis → change → measure. For example: visitors scroll past a vague hero but pause at a detailed process section; the hypothesis is that the offer is unclear; the response is a more specific headline and early proof; the measure is qualified inquiry rate from that page. Keep other changes documented so the team can interpret the result.

This is a hypothetical example, not a Rixlab client result. The method matters: redesign choices should be testable explanations of a real problem.

1. Define the goal and capture a baseline

Start with one primary outcome: more qualified inquiries, more product sign-ups, clearer service discovery, or fewer support questions. Add two or three supporting measures. For a service business, that might mean inquiry form completions, booked calls, and visits to service pages. Record current numbers for the same period and traffic source so the redesign has a fair comparison.

Review analytics by device and landing page. Which pages attract people? Where do they leave? Which calls to action receive clicks but no completed forms? Analytics reveal patterns, but they do not explain every motive. Pair the numbers with session observations, sales questions, support conversations, and direct user feedback.

Deliverable: a one-page brief with the audience, primary action, baseline, constraints, and success measures. If a proposed design change cannot connect to that brief, ask why it belongs in the project.

Performance data can reveal where to investigate, but a redesign needs context as well as charts. Photo: Luke Chesser / Unsplash.
Performance data can reveal where to investigate, but a redesign needs context as well as charts. Photo: Luke Chesser / Unsplash.

2. Learn where real visitors get stuck

Walk through the current website as a first-time visitor. Can someone understand what you offer in a few seconds? Can they find the right service, see credible proof, and know what happens after they contact you? Test the flow on a phone, with a keyboard, and on a slower connection. Include the form confirmation and error states; a polished landing page does not help if the next step fails.

Talk with a small set of people who resemble your intended customers. Ask what they came to do, what they expected to find, and where they hesitated. Avoid asking whether they “like” the page: preference alone is a weak diagnosis. Watch whether they can complete a realistic task. Record their words, not only your interpretation.

Deliverable: a short friction log. For each problem, note the page, evidence, likely cause, severity, and a possible response. This keeps the redesign focused on observed needs rather than internal taste.

A researcher records what people actually do and say during a website review. Photo: UX Indonesia / Unsplash.
A researcher records what people actually do and say during a website review. Photo: UX Indonesia / Unsplash.

3. Rebuild the page map and write the content

List every current URL. Mark each page as keep, improve, merge, redirect, or remove. Keep pages that answer a distinct need and perform a clear job. Merge overlapping pages when they confuse readers or compete for the same search intent. Do not delete a useful page simply because it looks dated.

Sketch the path from entry point to decision. A prospective client may land on a service page, read a case study, compare your process, and then book a call. The navigation should make that journey easy without forcing everyone through the homepage. Write page headings and core messages before selecting visual effects. Use the words customers use for their problems, and give each important page a clear next action.

Deliverable: a URL inventory, proposed site map, content owner, and draft copy for priority pages. A wireframe helps test hierarchy before the team invests in final visuals.

Photographed website wireframes show how page hierarchy can be tested before visual polish. Photo: Hal Gatewood / Unsplash.
Photographed website wireframes show how page hierarchy can be tested before visual polish. Photo: Hal Gatewood / Unsplash.

4. Protect search visibility during the change

A redesign can change URLs, headings, internal links, images, and page content at once. That makes SEO migration a project task, not a final check. Export the current URL list and identify pages that already receive search visits or links. Preserve a URL when its page purpose remains the same. If a URL must change, map the old page to the closest relevant new page with a permanent redirect; avoid sending every old URL to the homepage.

Write descriptive titles and meta descriptions for the new pages, keep important content in crawlable HTML, update internal links, and submit a current sitemap. Check canonical tags and remove any staging noindex rules before launch. Google’s site-move guidance explains URL mapping, redirects, testing, and post-launch monitoring. Its redirect guidance describes permanent redirects as a signal to the new canonical URL.

Deliverable: an old-to-new URL mapping sheet and a launch crawl. Search traffic may fluctuate during a migration, so monitor indexing and query performance rather than judging success from one day of data.

Review search and traffic data before changing pages that people already find. Photo: Carlos Muza / Unsplash.
Review search and traffic data before changing pages that people already find. Photo: Carlos Muza / Unsplash.

5. Design for mobile use and accessibility

Design the narrow view early. Check whether headings wrap well, navigation is understandable, buttons can be reached, forms are easy to complete, and important content is visible without hunting. Test on a real phone as well as a desktop browser resize. Include loading, empty, error, and success states, because those are part of the experience.

Accessibility belongs in the design and content decisions. Use semantic headings, readable contrast, descriptive link text, visible focus, keyboard-operable controls, labels for fields, and meaningful alternative text for informative images. Do not rely on color alone to communicate status. Use the W3C Web Content Accessibility Guidelines as the reference, then combine automated checks with manual keyboard and screen-reader review.

Deliverable: responsive layouts and an accessibility review with named issues and owners. A visual mockup cannot prove that a finished website is accessible; verify the implementation.

Test the real experience on a handheld device, including navigation and touch targets. Photo: Balázs Kétyi / Unsplash.
Test the real experience on a handheld device, including navigation and touch targets. Photo: Balázs Kétyi / Unsplash.

6. Build for speed and easy maintenance

Measure performance before and after the rebuild on representative pages, especially mobile pages with large images, video, animation, or third-party scripts. Keep the important content visible quickly, make interactions responsive, and prevent layout movement while assets load. Google’s Core Web Vitals guidance explains Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift and how to assess field data.

Set image dimensions, use suitable formats and sizes, defer work that is not needed for the first view, and audit third-party tags. A simpler page with a clear message often performs better than a page that asks the browser to animate everything at once. Also decide who will update service copy, case studies, team details, and calls to action after launch. The best redesign is one the team can maintain.

Deliverable: a tested build, a content editing workflow, and a short handoff document for the people who will own the site.

The development phase should include performance, responsive behavior, and maintainable content. Photo: Christopher Gower / Unsplash.
The development phase should include performance, responsive behavior, and maintainable content. Photo: Christopher Gower / Unsplash.

7. Run launch checks, then watch the first 30 days

Before launch, test the top journeys end to end: navigation, forms, booking, search, downloads, email notifications, and confirmation pages. Check mobile and desktop browsers, keyboard use, image loading, metadata, social previews, analytics events, redirects, and the XML sitemap. Keep a record of who approves content, technical QA, and the final release. Have a rollback plan for a broken deployment.

After launch, inspect priority URLs in Google Search Console. Review indexing, search queries, impressions, clicks, and crawl errors. Compare conversion actions with the baseline, segmenting by device and traffic source. Give the new site enough time to collect meaningful data, then fix the highest-impact friction. A redesign is complete when the new experience works for people and the team can see whether it improved results.

Deliverable: a launch log and a 30-day review with three decisions: keep, investigate, and improve.

A launch works best when design, content, and development owners review the same checklist. Photo: Annie Spratt / Unsplash.
A launch works best when design, content, and development owners review the same checklist. Photo: Annie Spratt / Unsplash.

When should you avoid a full rebuild?

Not every website problem needs a new platform or a complete visual identity. If the site is technically sound and visitors mainly struggle with a vague offer, rewrite the key pages first. If one form is failing, repair and test that flow. If a few high-traffic pages are slow, optimize them before replacing the entire site. A focused improvement can be faster to ship and easier to measure.

A full redesign makes more sense when the business has changed direction, the information architecture no longer matches the offer, the current system blocks essential updates, or several connected problems need a coordinated solution. Keep what already works. The point is to make the next website more useful, not merely newer.

Frequently asked questions

How long does a website redesign take? Scope drives the timeline. A small marketing site with approved content is different from a large site with many templates, integrations, stakeholders, and URL changes. Estimate discovery, writing, design, build, testing, and launch separately before committing to a date.

Will a redesign improve Google rankings? It can improve content, usability, performance, and crawlability, but no redesign guarantees a ranking increase. Poor redirects, removed content, or accidental noindex settings can cause losses. Preserve useful pages and monitor Search Console after launch.

What should I measure first? Choose the action the site exists to support—qualified inquiries, bookings, sales, or sign-ups—then add supporting measures such as page engagement, form completion, and organic search visibility. Compare like with like by device and source.

Should the copy or design come first? Define the page purpose, audience, and key message before final visual design. Copy and design should then be refined together so the layout supports the information people need.

If you are preparing a rebuild, Rixlab’s digital audit guide explains the diagnosis stage, while our web design service shows how we approach the work. Start with evidence, agree on the outcome, and build only what moves visitors toward it.

Let's make your next move.

Share what you are building. We will reply within one working day with a clear read on fit, scope, and timing.