Most B2B website redesigns do not fail at launch. They fail in the first two weeks, when the team starts designing before anyone has agreed what the site should say, and then spend the next two months redesigning the same homepage. The fix is not a better designer. It is doing things in the right order.
This guide splits a redesign into five phases: decide, write, design, build, launch. Each phase ends with a short checklist. Do not start the next phase until the current list is done. That one rule prevents most of the delays, rewrites and lost rankings that make redesigns expensive.
Before you start: should you redesign at all?
A redesign is the right call when the site no longer describes the company: the product has moved upmarket, the buyer has changed, or sales keeps sending prospects a deck because the website does not explain the product. It is the wrong call when the real problem is traffic, a single weak page, or a team that wants something new to look at.
- Redesign if sales regularly says "ignore the website, here is what we actually do"
- Redesign if the positioning, pricing model or primary buyer has changed since the site launched
- Redesign if every new page needs a developer and marketing has stopped publishing
- Fix one page instead if a single template (usually pricing or the homepage hero) is the bottleneck
- Fix acquisition instead if the site converts the visitors it gets but simply gets too few
Phase 1: Decide (week 1)
The first phase produces no screens. Its output is a page of decisions that everyone with a veto has signed. In B2B that usually means a founder, someone from sales and whoever owns marketing. If one of them disagrees in week four, you are back at week one.
The most important decision is the primary buyer. B2B products are bought by committees: the person who finds you, the person who evaluates you, the person who signs and the person who can block the deal. The site has to serve all of them, but the homepage can only lead with one. Pick the person whose question, answered well, moves the deal forward.
- One positioning sentence, signed off by the founder and not only by marketing
- Primary buyer named, with a written reason why, plus the two or three other readers the site must serve
- The one action you want a qualified visitor to take (book a call, start a trial, request a demo)
- A list of what the site will not do, so scope arguments end before they begin
- Analytics reviewed: top landing pages, top converting pages, top organic URLs exported to a sheet
- Success measures agreed, for example demo requests per month or trial starts from organic
Who to involve, and when
A redesign needs a small group with clear roles, not a committee. Give each person a phase where their input is decisive, and keep them out of the reviews where it is not. Five roles cover most B2B companies:
- Founder or CEO: signs off positioning in phase 1 and the final homepage, nothing in between
- Sales: supplies objections and real questions from calls, reviews the pricing and proof pages
- Marketing: owns the sitemap, the content inventory and the CMS, and runs the 30-day follow-up
- An engineer or product lead: checks every technical claim, so the site never promises what the product does not do
- Legal or compliance, if you sell to regulated buyers: reviews security, data and legal pages before launch
Name one person who breaks ties. When two reviewers disagree in week three, the redesign either waits for a meeting or moves on with a decision. Having that person named in week one is what keeps the calendar honest.
Phase 2: Write (weeks 1 to 2)
Write before you design. Copy decides structure, and structure decides design. A designer handed lorem ipsum will produce a beautiful page that the real words do not fit, and the team will then cut the words to fit the page. That is backwards.
Start with a sitemap, then write the pages that carry the most weight: the homepage, the main product or service page, pricing, and one proof page such as a case study. Everything else can follow a template.
- Sitemap agreed, with every page tied to a reader and a job
- Homepage hero and primary call to action written and approved
- Pricing decisions made before the pricing page is designed (published prices, starting prices or "talk to us")
- Objections from sales calls collected and answered somewhere on the site, often in an FAQ
- Proof gathered: case studies, product screenshots, metrics you can defend, named quotes with permission
- Content inventory of the old site: every page marked keep, merge, rewrite or delete
- Legal pages drafted or reviewed: legal notice, privacy policy, cookie policy, terms
Move, merge or cut: the content inventory
The inventory from phase 2 is where most of the cleanup happens. Every B2B site older than two years carries pages nobody remembers writing: old webinars, retired features, three versions of the same integration page. Moving all of it to the new site doubles the work and dilutes the pages that matter.
- Keep pages that rank, convert, or answer a question sales hears every week
- Merge near-duplicates into one stronger page, and redirect the others to it
- Rewrite pages whose topic still matters but whose claims are out of date
- Cut pages with no traffic, no links and no business reason, and redirect them to their closest parent
A useful rule: if nobody on the team would notice a page disappearing, it should not survive the redesign. Decide this in a sheet before any template is built, so the new site is designed for the content it will actually hold.
Phase 3: Design (weeks 2 to 3)
With the words fixed, design becomes a series of decisions about emphasis instead of guesses about content. Design the hardest templates first: the homepage, a dense product page and a long article. If the system holds for those, it will hold for the rest.
- Mobile layouts designed alongside desktop, not adapted afterwards
- A small design system: type scale, spacing, colour tokens, buttons, cards, one way to show proof
- Real screenshots of the product, not illustrations that could belong to any company
- Accessibility checked at design time: contrast, focus states, readable sizes
- Open Graph and social card images designed per locale
- One review round with every decision maker in the same session, not five rounds by email
Phase 4: Build (weeks 3 to 5)
The build is where performance and search visibility are won or lost. Both are far cheaper to build in than to fix later. Whatever the stack (Webflow, Next.js, Astro or a CMS-driven setup), hold the build to the same bar.
- Core Web Vitals in the green on a mid-range phone, with a Lighthouse performance score above 90 on mobile
- Structured data for Organization, Service or Product, FAQPage and BreadcrumbList where they apply
- One H1 per page, descriptive titles under 60 characters, meta descriptions under 160
- Hreflang and locale-specific URLs if the site is multilingual
- A CMS or content model that lets marketing publish without a developer
- Analytics, conversion events and consent handled before launch, not after
- Forms and booking flows tested end to end, including the confirmation emails
The SEO migration plan
This is the part most redesigns skip, and the reason many lose a third of their organic traffic the month after launch. Search engines rank URLs, not companies. If a URL that ranks disappears without a redirect, its ranking disappears with it.
Build the redirect map
Export every URL the old site has: from the sitemap, from a crawl, from Search Console and from your analytics landing pages. Combine them in one sheet with three columns: old URL, new URL, and status. Every old URL ends in one of three states.
- Kept: same URL on the new site, nothing to do
- Moved: a 301 redirect to the closest matching new page, never to the homepage by default
- Removed: a 301 to the most relevant parent page, or a 410 if the content is genuinely gone and has no equivalent
Redirect directly to the final URL. Chains such as /pricing to /pricing-v2 to /plans waste crawl budget and leak link equity. Keep the map in the repository or the CMS so the next redesign starts from it.
Protect what already ranks
- Pages with organic traffic or backlinks keep their URL where possible, or get a one-to-one 301
- Titles and H1s of ranking pages are improved carefully, keeping the query they rank for
- Internal links updated to the new URLs instead of relying on redirects
- Canonical tags point to the new URLs; no staging domain leaks into canonicals or the sitemap
- The staging site is blocked from indexing, and that block is removed at launch
Analytics that survive the switch
A redesign without a baseline cannot prove it worked. Before anything changes, record four weeks of the numbers you care about: organic sessions, top landing pages, conversion rate on the main call to action, and the share of leads that came from the website. Screenshots are enough. The point is to have something honest to compare against in month two.
- Export the current baseline: traffic by channel, top 50 landing pages, conversions by page
- List every conversion event the old site fires, and decide which ones the new site keeps
- Recreate those events on staging and test them with real form submissions or bookings
- Keep the same analytics property, so history and comparisons stay in one place
- Check UTM-tagged links in email signatures, ads and partner sites still land on live pages
If the site serves visitors in the European Union, the consent setup belongs in this list too. A new cookie banner or a new tracking script is a legal change, not a cosmetic one, and it should be reviewed before launch rather than patched after.
Phase 5: Launch (week 5 or 6)
Launch day should be boring. Everything risky has already been tested on staging. What remains is a short, ordered list that one person owns.
- Search Console verified for the domain before the DNS switch
- Redirect map deployed and tested: a script that requests every old URL and checks for a single 301 to the right page
- New sitemap submitted in Search Console on the day
- Robots.txt checked: nothing important disallowed, staging rules removed
- Analytics and conversion events firing on the live domain
- Social cards checked with the LinkedIn Post Inspector and a share preview
- A rollback plan, even if you never use it
The first 30 days after launch
A redesign is not finished at launch. The first month is when you find out which assumptions were right. Check Search Console weekly for 404s and coverage errors, and fix them the same week. Watch rankings for the pages in your redirect map; a short dip is normal, a steady slide means a redirect or a canonical is wrong.
On the conversion side, watch where visitors stop. Session recordings and a simple funnel (landing page, key page, call to action, confirmation) will show which section does not earn its scroll. Small weekly copy fixes in this period often do more than the redesign itself.
A realistic timeline
For a B2B site of ten to twenty pages, with one decision maker who is available, the phases above take five to six weeks. The calendar rarely slips because of design or development. It slips because a decision from phase 1 is reopened in phase 3. A smaller team can go faster: a focused positioning week followed by a two to three week build is enough for most sites, provided the decisions stay closed.
- Week 1: decide, plus the content inventory and analytics export
- Weeks 1 to 2: write the key pages and agree the sitemap
- Weeks 2 to 3: design the core templates and the small design system
- Weeks 3 to 5: build, structured data, redirect map, QA on staging
- Week 5 or 6: launch, then 30 days of measurement and fixes
Seven mistakes that delay B2B redesigns
Most delays are not technical. They come from decisions that were never made, or were made by the wrong person, too late.
- Designing before the positioning is signed off, then redesigning when it changes
- Writing for the founder instead of the buyer, so the homepage explains the technology and skips the outcome
- Inviting every stakeholder to every review, which turns feedback into negotiation
- Treating copy as something to "drop in later", so the layout never fits the real words
- Leaving the redirect map for launch week, when nobody has time to check it
- Launching on a Friday, or right before a holiday, with nobody available to fix what breaks
- Declaring victory at launch instead of measuring the first 30 days
What drives the cost of a B2B redesign
Prices vary widely, and the quote you get depends less on the number of pages than on four things. Knowing them helps you compare proposals that look very different on paper.
- Strategy and copy: whether the provider writes the positioning and the words, or expects you to supply them
- Number of templates, not pages: twenty case studies on one template cost far less than twenty unique pages
- Content model and CMS: how much your team needs to publish on its own after launch
- Migration work: the content inventory, the redirect map and the SEO checks described above
When two quotes differ by a factor of three, it is usually because one includes positioning, copy and migration, and the other assumes you will handle them. Ask each provider which of the five phases in this guide they cover, and who does the work in each one.
The checklist on one screen
- Decide: positioning sentence, primary buyer, one action, success measures, analytics export
- Write: sitemap, key pages, pricing decisions, objections, proof, content inventory, legal pages
- Design: mobile and desktop together, a small design system, real product screens, one review session
- Build: Core Web Vitals, structured data, titles and descriptions, CMS, analytics and consent
- Migrate: full URL list, one-to-one 301s, internal links and canonicals updated, staging blocked
- Launch: Search Console ready, redirects tested, sitemap submitted, social cards checked, rollback plan
- After: weekly checks for 30 days, rankings on redirected pages, conversion funnel, small copy fixes
This checklist is the execution side of the SaaS website redesign playbook and of how we run SaaS website projects. For a product positioned for a cautious buyer, see the Marianne case study.
If you want this checklist run on your own site, that is what the positioning sprint is for: one week, a written plan of the items that matter most for your site, credited in full against the build. A 15-minute call tells us whether it fits.