Website Redesign Checklist for 2026: What to Do Before, During, and After

Why do website redesigns go wrong?

When a redesign goes wrong, people blame the visuals. Usually the real problem sits earlier. Nobody defined what the site needed to do, nobody protected the pages that already bring in traffic, and the content showed up two weeks before launch.

This checklist is the order we follow on our own projects. It covers the audit, the design work, the launch, and the weeks after. Work through it top to bottom, and use the tables and diagrams to check your progress.

What is the short answer?

A good website redesign checklist has four phases: audit what you have, plan structure and content, design and build, then launch and monitor. The step that protects your search rankings most is mapping every old URL to a new one with a 301 redirect. The step that saves the most time is writing content before design is signed off.

What should you do before you design anything?

Step 1: Write the goal in one sentence

"Get more demo requests from small B2B teams" is a goal. "Make it look modern" is not. Every later decision, from the navigation to the hero headline, gets checked against this sentence. If a design choice does not help it, it is decoration.

What does a good redesign goal look like?

A useful goal names a visitor, an action, and a reason. A few examples of the shape we mean:

• Get more qualified enquiries from small teams who compare us with two or three other providers.
• Help existing customers find answers without contacting support.
• Make the pricing and process clear enough that fewer calls start with basic questions.

Write two or three of these, then choose one as the main goal. The others become supporting goals. When the team disagrees later, you return to this list and let it settle the argument.

Step 2: Audit what you have

You cannot protect what you have not measured. Pull these before anyone opens Figma:

• The last 12 months of analytics. Which pages bring traffic? Which ones bring leads?
• Every URL that ranks in Google or gets links from other sites. These are the pages you must not break.
• Your current speed and Core Web Vitals scores, so you can prove the redesign improved them.
• Where users drop off. Heatmaps or session recordings help here.
• A list of integrations: forms, CRM, chat, booking, payments, analytics.

If you want a structured way to find usability problems in the existing site, our guide on how to do a UX audit walks through it.

Step 3: Take a content inventory

List every page, then give each one a decision: keep, rewrite, merge, or delete. Most sites carry pages nobody has opened in a year. A redesign is the right moment to cut them, and cutting is cheaper than redesigning pages nobody needs.

Use this table as a quick rule when you go through the list:

Step 4: Look at three competitors

Not to copy them. Look at what buyers in your market expect to see, then decide where to match that and where to stand apart. Note how they explain pricing, proof, and next steps.

What should you do during the redesign?

Step 5: Fix the sitemap before the visuals

Structure comes first. If people cannot find pricing in two clicks, no layout will save it. Draw the sitemap, agree on the main navigation, and only then start wireframes.

Step 6: Write the content first

At least write the headlines and the main section copy. Designing around placeholder text hides problems that show up the moment real copy arrives: headlines that wrap badly, buttons that do not fit, sections that have nothing to say.

Step 7: Design mobile alongside desktop

Not after. A large share of visitors will never see the desktop version, so it should not be an afterthought scaled down at the end.

Step 8: Give every page one clear call to action

Two competing buttons usually mean neither gets clicked. Decide the one action a visitor should take on each page, and make it the most obvious thing on the screen.

Step 9: Plan for speed from the start

Image sizes, font choices, and third-party scripts are much easier to control in design than to fix after launch. Ask for a performance budget before development starts.

Step 10: Check accessibility

Contrast, focus states, alt text, and keyboard navigation. It helps every visitor, and it protects you legally in many markets.

Step 11: Choose the platform on purpose

Your platform affects how fast you can edit, how fast the site loads, and what the team can maintain. If you are weighing options, read Webflow vs WordPress, and if you are moving off WordPress, our migration guide covers the redirect and content steps in detail.

Who should be involved in the redesign?

Fewer people, with clear roles, works better than a large committee.

• One decision maker. Someone who can say yes and settle disagreements.
• A content owner. The person who writes or gathers the copy and chases the deadlines.
• A designer and a developer. Ideally involved from the sitemap stage, so nothing is drawn that cannot be built well.
• An SEO or marketing lead. Someone who owns the redirect map, tracking, and metadata.
• A few reviewers. Sales and support see what customers ask. Give them a set moment to review, not open access.

What should you check right before launch?

This is where most SEO damage happens, and most of it is avoidable. Go through the list below on the staging site, not on launch day.

Launch-day checklist

• Redirect map tested on the staging site with a list of every old URL.
• Sitemap generated and ready to submit.
• Every form submitted once as a real test, and the message received.
• Analytics and conversion tracking confirmed in real time.
• Robots settings checked, and the search-blocking setting removed from the live site.
• Custom 404 page in place with a link back to the homepage.
• Backups or a rollback plan ready, in case something breaks.

How do you build a redirect map?

The redirect map is a simple list with two columns: the old URL and the new one. Building it is careful work, but it is not complicated.

1. Export every old URL. Use your sitemap, analytics, and a crawl of the current site so nothing is missed.
2. Add the pages that rank or have links. Search Console and a backlink report show which URLs matter most.
3. Match each old page to its closest new page. Pick the page with the same purpose, not simply the homepage.
4. Avoid chains. An old URL should go straight to the final page in one step.
5. Test on staging. Check a sample of old URLs, then check the full list once the site is live.

If a page is deleted with no equivalent, redirect it to the most relevant category or guide. Sending everything to the homepage tends to confuse both users and search engines.

What should you do after launch?

• Submit the new sitemap in Google Search Console.
• Watch for crawl errors and 404s for the first few weeks, and fix each one with a redirect.
• Compare traffic and leads against your pre-launch baseline. A small dip right after launch is common. A steady decline means something was missed.
• Collect real user feedback and fix the top three friction points first.
• Update internal links that still point to old URLs.

What does the first month after launch look like?

• Week one. Check crawl errors daily, confirm forms and tracking, and fix any broken links or missing redirects.
• Week two. Compare traffic and leads against your baseline. Review mobile behavior with recordings.
• Weeks three and four. Improve the weakest pages, update titles that underperform, and publish a first round of new content.

Keep a short log of what you changed and why. It makes the next round of decisions easier.

What are the most common redesign mistakes?

• Changing URLs without redirects. Rankings and backlinks disappear overnight, and recovery takes months.
• Starting design without a goal. Approval turns into personal taste.
• Waiting for content. Design is signed off, then the copy is longer or shorter than assumed and everything is reworked.
• Deleting pages that rank. The inventory should be based on analytics, not on how a page feels.
• Too many approvers. Feedback from ten people with no single decision maker stalls a project faster than any technical problem.
• Skipping mobile testing. A layout that looks fine in a browser window can fail on a real phone.
• Launching and disappearing. The weeks after launch are when problems surface.

Why do these mistakes cost so much?

Most of them are invisible until it is too late. Broken redirects do not look like a problem on launch day, but rankings slip over the following weeks. Missing content shows up as delays, and delays push teams to rush the final steps. Too many approvers quietly turn a plan into a compromise. The cure is to move the hard decisions earlier: goals, structure, content, and ownership. For a deeper look at the search side of a launch, use our Webflow SEO checklist, and for the design that sits underneath the pages, read about how to design a website that converts.

What does a typical redesign look like in practice?

This is a common pattern we see, described as typical practice rather than one specific project. A services company has a site built several years ago. It looks dated, and visitors rarely reach the contact page.

The audit shows that a handful of articles bring most of the traffic, while the main service pages get very little. The team decides to keep and rewrite the articles, merge three thin service pages into one strong page, and delete a set of old news posts. The sitemap gets simpler. Content is written before design starts, so the layouts are drawn around real headlines. The redirect map covers every old URL, and the launch happens on a quiet weekday morning so someone can watch the results.

In the weeks that follow, the team fixes a few missed redirects, updates internal links, and improves the two pages where users hesitate most. Nothing dramatic happens. That is the goal. A calm launch is a sign the earlier steps worked.

How long does a redesign take?

It depends on page count, content readiness, and how quickly feedback comes back. A focused marketing site can come together in a few weeks. A larger site with a lot of content and integrations takes months. The biggest schedule killer is almost never design. It is waiting for content and approvals, so book both early.

Should you redesign, or fix what you have?

Not every problem needs a full redesign. If the structure is sound and only the look is dated, a partial refresh may be enough. If visitors cannot find what they need, or the site cannot support your business anymore, a redesign is justified. Our post on when to redesign your website gives clear signs for each case. Budget matters too, and what drives UI/UX design cost explains why scope decides the quote.

The takeaway

A redesign is not a visual refresh. It is a chance to fix structure, message, and performance at the same time, without losing what already works. Do the audit, protect your URLs, and the design work gets much easier.

Want a second pair of eyes on your current site before you commit? Send it over and we will tell you what to keep and what to fix.