Website redesign checklist: the full pre-launch framework

A website redesign fails in one of two places: before a pixel is drawn, when nobody agreed on what the site is supposed to do, or after launch, when the new design ships without a system underneath it. This checklist is built to catch both failure modes, in order, before they cost you four months and a five-figure build.

Want a website live fast? You can build one in Framer (View more here). Have a quick question about website redesign checklist? Read our expert answers on website redesign checklist.

Why most website redesign checklists miss the point

Search for a website redesign checklist and you'll get variations of the same list: audit your content, check your SEO, make it mobile-friendly. That's not wrong. It's just downstream of the actual problem.

The mistake I see most often is founders treating a redesign as a visual refresh when they have a strategic positioning problem. A new homepage won't fix unclear messaging. A faster load time won't fix the fact that your ICP lands on the page, reads three sentences, and still can't tell what you do or why it matters to them.

Before you open Figma or brief an agency, you need answers to three questions: What does this site need to do for the business in the next 12 months? Who is the primary buyer and where are they in the decision cycle? What does success look like, measured in a number you can pull from analytics in 90 days?

If you can't answer those cleanly, the redesign will be cosmetic. And cosmetic redesigns, in my experience across growth-stage B2B SaaS companies, produce roughly the same conversion rates as what they replaced.

1. Revisit your website goals

This sounds obvious. It's almost never done properly.

Most B2B SaaS sites serve three to five different audiences simultaneously: enterprise buyers, SMB buyers, investors, potential hires, and partners. The mistake is trying to serve all of them equally on the same homepage. Pick one primary audience. The rest get secondary paths.

Then set a specific goal per page type. For a Series-B SaaS whose primary motion is inbound demo requests, the homepage has one job: get a qualified visitor to book a demo call or start a trial. Not educate them on every feature. Not showcase your entire customer list. One job.

Write your goals in this format: By [date], [page] will achieve [metric] for [audience segment]. Vague goals produce vague briefs, which produce sites that look fine but do nothing.

The tradeoff worth naming: narrowing to a primary audience will make some secondary visitors feel underserved. That's correct. A site that speaks well to one buyer outperforms a site that speaks adequately to five.

2. Note changes to your branding

If your brand positioning has shifted since the last build, resolve it before the redesign starts. Not during. Not after. A redesign done on top of unclear positioning just bakes the confusion into a new design system.

Brand changes that need to settle before design starts: a shift in ICP (you moved upmarket or changed vertical), a new category you're trying to own, a product name change, or a pricing model change that affects how you describe value. If any of these are still in flux, pause the redesign until they settle. Building on a shifting foundation is how companies end up redesigning twice in 18 months.

What I mean by "note changes" is specific: document the gap between your current brand position and where you're going. What have you stopped being? What are you now? What's the one line a new visitor should understand in the first eight seconds? That line goes in the brief, becomes the hero headline test, and governs every copy decision from there.

For companies working through a full positioning reset alongside a site rebuild, the brand positioning agency topic covers how that process runs and what it costs.

3. Analyze user behavior before touching the design

Don't guess what's broken. Read the data first.

The tools that give you actual signal: Hotjar or FullStory for session recordings and heatmaps, Google Analytics 4 for acquisition source and drop-off by page, and your CRM data to work backwards from closed deals to the traffic source that produced them.

Three numbers to pull before any redesign brief goes out:

• Your current homepage-to-demo conversion rate. Industry average for B2B SaaS is 1.5-3%. If you're below 1%, the issue is usually messaging, not design.

• Your top organic landing pages by traffic. These pages survive the redesign; they don't get deleted or restructured without SEO analysis first.

• Your exit rate on the pricing page. Above 80% usually means the page is doing something wrong: anchoring too high, missing social proof, or not giving buyers enough information to self-qualify.

What I typically find when we run this analysis for a growth-stage company is that 80% of conversion problems live on three pages: the homepage, the pricing page, and the primary use-case page. Fix those three before rebuilding the whole site.

4. Fine-tune the user experience

UX in a B2B context is not about making things pretty. It's about reducing the cognitive load between "I arrived" and "I understand what to do next."

The 3-second rule in web design refers to the window you have to communicate enough value that a visitor decides to keep reading. Three seconds is not a long time. In practice it means your headline needs to communicate what you do, for whom, and why it's different. Not a tagline. An actual statement. "Revenue forecasting for SaaS finance teams" is clearer and faster to process than "The future of financial intelligence."

On a redesign engagement for a B2B infrastructure tooling company, we cut the homepage from 11 sections to 6, removed two navigation items, and rewrote the hero from a concept-forward headline to a function-forward one. Demo request rate went from 1.1% to 2.8% in the first 60 days post-launch. The design change was smaller than most people expect. The copy and information architecture change was significant.

Five elements of a good website design, stated practically:

1. Clear primary message visible without scrolling

2. Navigation that reflects how buyers think, not how your org chart is structured

3. Load time under 2.5 seconds on mobile (Core Web Vitals LCP target)

4. One primary CTA per page, not four competing buttons

5. Social proof placed near conversion points, not buried in a case studies section two clicks away

5. Clarify the user journey

Most B2B SaaS sites have a homepage-to-demo path that works reasonably well and then a content-to-anything path that's completely broken. A visitor lands on a blog post, reads it, hits a dead-end with no clear next step, and leaves. That's a leaky funnel a redesign can fix, but only if you map it explicitly before you build.

Map three journeys at minimum: the cold visitor who's problem-aware but not solution-aware, the warm visitor who already knows your category and is comparing options, and the existing customer who logs in or visits for documentation. These three visitors need different entry points, different CTAs, and often different homepage experiences.

The 7 C's of website design is a framework from web strategy literature covering context, content, community, customization, communication, connection, and commerce. For a B2B SaaS site, the three that actually move the needle are context (is the page relevant to who landed on it), content (does it answer the question the visitor arrived with), and connection (what's the next logical step I'm guiding them toward). The other four matter, but those three determine whether someone converts or leaves.

User journey documentation doesn't need to be elaborate. A single-page flowchart showing entry point, primary action, secondary action, and fallback for each visitor type is enough to brief a designer and prevent the "but what does a first-time visitor do?" confusion mid-build.

6. Make a design plan

A design plan is not a mood board. It's a scoped document that specifies what's being built, in what order, at what fidelity, and who approves what before development starts.

The components of a usable design plan for a website redesign:

• Page inventory: every page being redesigned versus every page staying as-is

• Component list: the reusable modules that will appear across pages (hero patterns, feature cards, testimonial blocks, CTAs)

• Breakpoint strategy: how the design behaves at mobile, tablet, and desktop specifically (not just "it's responsive")

• Copy ownership: who writes the headlines, who approves them, and whether copy is finalized before design or iterated alongside it

• Design tool and handoff: Figma file structure, how developers access specs, and what constitutes a complete design deliverable

The tradeoff on component-first design: it takes longer upfront. Building a proper component library before designing individual pages adds two to three weeks to the front end of a project. But it cuts the total build time for a 20+ page site significantly and makes post-launch changes faster by a factor of 4-6. For companies on responsive web design builds with multiple breakpoints, component discipline is the difference between a maintainable site and one that breaks every time someone adds a page.

7. Check your SEO before and after

The most common SEO mistake in a website redesign is not the redesign itself. It's the URL migration nobody planned for.

Before the redesign starts, export your full URL list and map every page that has external links pointing to it, organic traffic, or ranking positions. These pages are your SEO equity. They don't get new URLs without 301 redirects. They don't get deleted. They don't get combined with other pages unless you've explicitly modeled the traffic impact.

The checklist for SEO during a redesign:

• Crawl your existing site with Screaming Frog or Ahrefs Site Audit before touching anything

• Identify your top 20 pages by organic traffic. These are protected.

• Map every URL change to a 301 redirect before launch day

• Carry over existing meta titles and descriptions as defaults; optimize them, don't delete them

• Check Core Web Vitals on the new build before launch, not after. PageSpeed Insights takes 90 seconds and tells you where you're bleeding.

• Submit the updated sitemap to Google Search Console within 24 hours of launch

One thing worth watching specifically: internal linking structure. Most redesigns break internal links silently. The homepage links to a blog post that gets a new URL, the redirect doesn't get added, Google sees a 404, the page drops. Run a crawl of your staging environment before launch and check for broken links as a line item on your QA checklist.

8. Test before you call it done

Testing on a website redesign happens at three stages, and most teams only do one of them.

Stage one is design testing: showing wireframes or prototypes to five to eight people who match your ICP and asking them to complete a specific task. Not "what do you think?" That question produces opinions. "Show me how you'd find the pricing" produces behavior data.

Stage two is pre-launch QA: every page at every breakpoint, every form submission, every CTA link, every redirect. This is a checklist inside the checklist. Assign it to a specific person, not "the team." Teams don't do QA. People do.

Stage three is post-launch testing: running A/B tests on the hero headline, the primary CTA copy, and the pricing page layout. This is where most conversion gains actually come from. The initial launch gets you to a baseline. The 90-day optimization window is where you move from 2% to 3.5% conversion, which on meaningful traffic volume is a real revenue number.

The mistake I see in post-launch testing is running too many tests at once. One variable at a time. Minimum two weeks per test at statistical significance. If your traffic is under 2,000 unique visitors per month, A/B testing won't give you reliable signal. Use qualitative methods instead: user interviews, session recordings, and a direct conversation with five prospects about what confused them on the site.

10 factors that influence the cost of a website redesign

Scope drives cost more than anything else, but scope is rarely defined precisely enough early in the process. Here are the ten variables that actually move the number:

1. Page count: A 10-page site and a 60-page site are different projects. Not 6x different in cost, but meaningfully different.

2. Custom design versus template: A Webflow template build with brand customization runs €8,000-€20,000. A fully custom design system plus build runs €30,000-€80,000 and up.

3. Copy: If the agency is writing copy, not just designing around your existing content, add 20-40% to the budget.

4. Integrations: CRM, marketing automation, live chat, analytics events. Each integration adds scope. A HubSpot integration with custom form logic and CRM field mapping adds a week of work.

5. Illustration or custom photography: Stock photography is cheap. Custom illustration for a SaaS UI concept is not. Budget €3,000-€12,000 separately if custom visual assets are in scope.

6. Animations and micro-interactions: Scroll-triggered animations and interactive demos add significant development time. Treat them as a separate line item.

7. Multilingual support: A site in three languages is not three times the work, but it's significantly more than one.

8. Accessibility compliance: WCAG 2.1 AA compliance adds design and development overhead. Required for any company selling to enterprise or regulated industries.

9. Post-launch support: Who maintains the site after launch? If it's the agency, that's a retainer. If it's your team, they need to be able to operate the CMS.

10. Iteration rounds: Two rounds of design feedback is standard. Five rounds is a scope problem. Agree on the number upfront.

For a detailed breakdown of what these variables mean for total budget, the website redesign cost pillar covers realistic ranges by project type, from a basic Webflow refresh to a full custom build with a design system.

The fragmentation problem most redesigns don't fix

Here's what I see in growth-stage tech companies that have gone through one or two redesigns already: the website looks good, but it says something different from the sales deck, which looks different from the product UI, which has nothing to do with the demo environment the AE walks prospects through. Four touchpoints. Four different visual and narrative stories. The buyer gets a fragmented experience and quietly makes a judgment about how together your company actually is.

A website redesign done in isolation fixes one of those four touchpoints. The others stay misaligned. The result is a better-looking site that still doesn't close the trust gap.

The projects we run at Daasign that produce the strongest commercial outcomes are ones where the redesign is part of a broader system: website, sales deck, and product UI all built on the same positioning, the same component architecture, and the same visual language. On a McKinsey workstream we shipped a full visual system across six touchpoints in 11 weeks. The individual deliverables were faster because everything shared the same foundation.

This doesn't mean you need to redesign everything at once. It means your website redesign checklist should include an audit of what the other buyer touchpoints say, and whether the new site will create more or less coherence with them. If your sales deck is two years old and the new site positions you in a completely different way, someone on your sales team is going to have a confusing conversation.

The brand-led growth topic covers how this multi-touchpoint coherence connects directly to acquisition, for teams ready to think beyond the site itself.

The website redesign checklist, consolidated

Run through these in order. Don't skip to design before the strategy work is done.

1. Define one primary goal per page type, with a specific metric and a date

2. Document your brand position delta: what changed, what the new one-line statement is

3. Pull three behavioral data points: conversion rate, top organic pages, pricing page exit rate

4. Map three user journeys: cold visitor, warm buyer, existing customer

5. Audit your SEO equity: crawl the current site, protect your top 20 pages, plan redirects

6. Build a page inventory and component list before design starts

7. Define your breakpoint strategy and copy ownership upfront

8. Run design testing with five to eight ICP-matched users on wireframes, not finals

9. QA every page, every breakpoint, every form, every redirect before launch

10. Run one A/B test per 90 days post-launch, one variable at a time

11. Audit how the new site aligns with your sales deck and product UI

What to look for when redesigning a website

The short version: clarity before aesthetics. A site that clearly communicates what you do, for whom, and why someone should care in the first three seconds will outperform a beautiful site with ambiguous messaging every time. Look for those three things first. Then design.

The longer version: figure out whether your current site's failure is a positioning problem, a messaging problem, or a design execution problem. These require different fixes. A positioning problem means the site is saying the right things to the wrong audience. A messaging problem means the right audience lands and still doesn't understand your value. A design problem means they understand but the experience makes them distrust you. Diagnose before you prescribe.

If your team is ready to scope the actual build, book a 20-min intro and we'll tell you within the first call whether what you're describing is a strategy problem, a design problem, or both.