Website Redesign Checklist 2026: Keep the Traffic You Earned

A redesign is a business risk disguised as a design project. The new site is only a success if the old traffic, links and conversions survive the switch.

The redesign is not the risky part

The design phase is slow, visible and full of opinions. The launch is fast, invisible to most of the team and where the damage happens. A missing redirect, a noindex tag left on, a broken form or a tracking script that never fired can cost months of momentum in a single afternoon.

Treat the cutover like a product launch with a checklist, an owner and a rollback plan. The new site can be beautiful and still fail commercially if nobody owns the switch. This checklist is the part that protects the traffic you already paid for.

Inventory every URL before you design

Export a full list of indexed pages, top landing pages and pages with external links. Include the ones you think nobody visits; the internet has a long memory. For each, decide whether it stays, moves or disappears. A page that disappears without a redirect is a dead end for a visitor and a lost signal for search engines.

Do not forget pagination, tag archives, author pages, campaign landing pages and PDFs. Marketing teams create URLs all year; the redesign team often sees only the navigation. Ask support, sales and paid media for the links they use in the wild.

Redirects: one hop, no chains

Map old URLs to the closest new equivalent, not always to the homepage. A redirect to the homepage tells a visitor their page is gone and tells a search engine the topic no longer exists. Use a 301 for permanent moves and keep the chain to one hop so the browser does not have to travel through three rules.

Test the redirects after launch with a crawler and a sample of real links. A rule that worked in staging can behave differently behind a CDN or a trailing-slash setting. Check the versions with and without www, http and trailing slashes if you support them.

If the new site cannot explain where the old page went, it is not ready.

Protect analytics and tracking

Keep the same analytics property and search console verification if you can. Moving to a new property on launch day means you lose the comparison that tells you whether the redesign worked. If you must create a new one, run both in parallel for at least a month.

Test every conversion event before launch: forms, checkout, calls, newsletter signups and downloads. A redesign can easily drop a data layer attribute or a hidden field. Marketing will not notice until a report looks flat, which is usually too late to attribute the cause.

Launch day checks

Freeze major content changes for a few days around launch so you can tell what caused a change in traffic. Announce internally, have the developer and a content owner on call, and watch the error logs and analytics in real time. Launch on a Tuesday or Wednesday morning, not a Friday afternoon.

• Crawl the staging site for broken links and accidental noindex tags.
• Verify the sitemap and robots.txt point to the live domain.
• Test forms, email delivery and payment with a real transaction.
• Check mobile layout, keyboard navigation and page speed on a mid-range phone.
• Confirm the redirect map is live and the old URLs resolve in one hop.

The first month after launch

Expect some movement in rankings and traffic. The goal is to tell normal fluctuation from a real problem. Compare by page, not just the site total. If a page that used to rank disappears, check its redirect, its canonical tag and whether the content still exists on the new site.

Keep the old design accessible in a branch or a subdomain for at least a month. If a critical bug appears, you want the option to restore a known-good version quickly, not a scramble through backups. A rollback plan is not pessimism; it is part of shipping.

When the dust settles, write down what broke and why. The next redesign will be easier, and the checklist will be shorter only because the team learned the hard parts the first time.