Website redesign checklist: launch the new site, keep the leads
The full website redesign checklist for B2B marketing teams, from the first brief to the first 90 days after launch.

- Write the goal as a number and record a 12-month baseline first
- Redirect every old URL with traffic or links using a 301, and keep it live for a year
- Agree each key page's headline, proof and call to action before design starts
- Plan tracking with the build and test every form on staging
- Expect a temporary traffic dip, then judge the new site against your baseline for 90 days
Quick answer
A website redesign checklist covers six stages. Start by agreeing one goal and recording a baseline, then map every old URL to a new one with 301 redirects. Settle each key page's message and call to action, rebuild tracking and forms before launch, test everything on launch day, and watch Search Console and conversions for 90 days.
Plenty of website redesigns go wrong months before launch, usually in a meeting where nobody writes down what the new site is for.
Then the mockups arrive and everyone has an opinion, while the old URLs quietly go missing. A few weeks after go-live, someone asks why demo requests have dipped and nobody has a good answer.
This website redesign checklist is built to stop that, from the first brief to the first 90 days after launch. Work through it with your agency, or use it to poke holes in the plan they hand you.
1. Why do B2B website redesigns go wrong?
Mostly because your website now does a lot of selling before anyone gets to talk to you, and a careless redesign can undo it.
In 6sense's 2025 research with more than 4,000 B2B buyers, the vendor buyers favoured before speaking to sales went on to win 80% of deals. And 94% of buying groups had already ranked their preferred vendors before that first contact (6sense via Business Wire, 2025).
So a redesign that looks better but explains less is an expensive step backwards. The causes are rarely dramatic, and most of them come down to admin:
- No agreed goal, so the loudest opinion wins
- No baseline, so nobody can prove the new site works
- Old URLs with no redirects, so search traffic takes a dive
- Forms and tracking left until last, so leads vanish for weeks
2. Planning: what should you agree before you brief anyone?
Get this on one page before you talk to a single agency. It makes every later decision faster, and it gives you something to point at when the debate about the homepage hero gets heated.
Two items matter more than the rest. The first is the goal: for most B2B sites that means qualified demo or call requests, so write down the number you want to move.
The second is the baseline, which is the last 12 months of sessions, conversions by source and top landing pages. Skip it and nobody can say whether the new site worked, including you.
Then pick one person to sign the site off and let everyone else review, because every extra approver adds another round of "just one small tweak".
- One goal, written as a number
- A 12-month baseline from GA4 and Search Console
- The two or three buying roles, and what each needs to see
- What's staying: brand, domain, platform
- A budget range and a launch window clear of your busiest sales month
- One decision maker
Not sure what to budget? Our guide to what a B2B website costs has UK and US ranges.
3. Content and SEO: how do you keep the traffic you've already earned?
This is the bit nobody puts on the mood board, and it's where traffic is kept or lost. Do it before design starts, while there's still time to fix what you find.
Crawl the current site and list every URL with its traffic, conversions and backlinks. Then go page by page and decide whether to keep it, merge it or let it go. Anything with traffic or links either stays or moves to a close match, while a page with no traffic and no links can usually go.
Next comes the redirect map, a plain spreadsheet that pairs every old URL with its new home. It's the least glamorous document in the project and probably the most important.
Google's site move guidance says to keep those redirects "for as long as possible", and generally for at least a year (Google Search Central, 2026). Permanent 301 redirects, the kind that tell search engines a page has moved for good, don't lose PageRank, so there's no reason to skip them.
While you're in there, put a direct answer near the top of your key pages. People skim, and AI search tools tend to quote pages that answer the question clearly.
- Crawl the old site: traffic, conversions, backlinks
- Keep, merge or remove each page
- Write the redirect map
- Plan short, readable URLs
- A direct answer near the top of key pages
- Titles, descriptions and schema carried over
Changing platform as well? Our WordPress to Webflow migration guide covers the extra steps.
Our website team carries over your URLs, redirects and technical SEO before anything goes live. Book a call.

4. Design and build: what does good look like?
Good design here means a buyer finds their answer, and the next step, without hunting for either.
So agree the words before the layout: for each key page, settle the headline, the proof and the one call to action before anyone opens a design tool. A single "Book a call" button beats a row of five. Put case studies, numbers and client logos right next to the claims they back up, because that's where the buying decision happens.
Then give the build targets it has to hit. Google's Core Web Vitals, its three measures of how fast, responsive and stable a page feels, say the main content should load in 2.5 seconds or less. Clicks should get a response within 200 milliseconds, and layout shift should stay at 0.1 or less (web.dev, 2024).
For accessibility, build to WCAG 2.2 level AA, which has been a W3C Recommendation since October 2023 (W3C, 2023).
- Headline, proof and one call to action agreed for each key page
- Short forms that ask only what sales needs
- A CMS your marketers can use without a developer
- Core Web Vitals targets written into the brief
- WCAG 2.2 AA from the start
Why sites slow down covers what usually breaks speed, and our WCAG 2.2 guide has the accessibility checks.
5. Tracking: how do you make sure no lead goes missing?
On the redesigns we see, tracking is often the afterthought. It's also how you understand success, and it's what lets you keep improving the site after the migration.
Leave it until last and you could launch a lovely site that can't tell you where its leads came from. Worse, a form might be quietly sending them nowhere.
So plan tracking alongside the build, starting with a list of every form and where its data goes: the CRM, your email tool, a Slack alert or all three. Set up GA4 and Google Tag Manager on staging, the private copy of the new site, and test each conversion event before launch. Our guide to tracking conversions with GA4 and GTM shows the setup.
- Every form mapped to where its data goes
- GA4 and GTM conversion events tested on staging
- Cookie banner and Consent Mode working before any tag fires
- New leads landing in the CRM with the right source and owner
- Ad conversion tags and landing page URLs updated
6. Launch day: what should you check before anyone celebrates?
The launch party can wait until the afternoon, because the morning is for this list.
- Redirects live, with your top 50 old URLs tested
- No leftover "noindex" from staging
- The new XML sitemap submitted in Search Console
- A test lead through every form, landing in the CRM
- GA4 real-time showing page views and conversions
- Key pages checked on a phone, a tablet and a laptop
- Sales and customer success told what moved
That "noindex" one sounds silly until it happens to you. Staging sites switch it on, for good reason, to tell search engines to stay away. Forget to switch it off and your shiny new site politely asks Google to leave it out of search.
7. What happens in the first 90 days after launch?
A temporary dip in traffic is normal, and the fewer changes you make to URLs and structure, the smaller it will be. Google says that for a medium-sized site, new URLs can take a few weeks or more to replace the old ones in search (Google Search Central, 2026). Within 30 days, you'd expect traffic to be climbing again, so keep calm in week two and watch closely.
Sometimes it won't climb, and that can be by design. If the new site has a new focus, or it has dropped traffic that was never relevant, a lower number can be the right result. That's why you judge the site against the baseline you recorded at the planning stage, looking at conversions by source as well as total traffic. A site with a little less traffic and more demo requests is doing its job.
Check Search Console every week for the first month and fix any 404s with a redirect. After that, fix the friction you can see: session recordings and form analytics show where buyers give up. And keep publishing, because a new site full of old content soon stops improving.
Want a second pair of eyes on your plan? Book a call about your redesign.
Sources
FAQs
Six stages: planning, content and SEO, design and build, tracking, launch day and the first 90 days. Each one has its own short checklist in this guide.
It depends on the number of pages, the content and the integrations. Ask your agency for a week-by-week plan before you sign. If they can't give you one, that tells you something.
It can, if old URLs aren't redirected. Map every page with traffic or links to a new URL with a 301 redirect, and keep URL and structure changes to a minimum. A temporary dip is normal, and within about 30 days you'd expect traffic to be climbing again.
Google advises keeping them for as long as possible, and generally for at least a year.
Conversions by source, organic traffic, top landing pages and Core Web Vitals, all compared with the baseline you recorded before the redesign.
One decision maker, with a short list of reviewers. Every extra approver adds another round of changes.


%20(1).avif)





.avif)




.avif)


%20(1).avif)
%20(2).avif)
%20(1).avif)
.avif)
.avif)
%20(1).avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
%20(1).avif)
.avif)
%20(1).avif)


.avif)

%20(1).avif)
%20(1).avif)
%20(1).avif)


















%20(2).avif)
.avif)



.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
.avif)
%2520(1).avif)
%2520(1).avif)
.avif)
%2520(1).avif)
%2520(1).avif)
%2520(1).avif)
%2520(1).avif)
%2520(1).avif)
%2520(1).avif)
.avif)
.avif)





.avif)

