SaaS Website Redesign Checklist: Before You Touch Anything

Most SaaS website redesigns fail before they start. Not because the design is bad. Because the team skipped the work that happens before design begins.

This checklist is not about what to include on your new site. It is about what to do before you open a design tool, brief an agency, or choose a platform. The steps here are what separate a redesign that improves the business from one that looks better but performs the same or worse.

Step 0: Decide whether you actually need a redesign

This is the step most teams skip entirely, and it is the most important one.

A redesign is the right call when the platform is genuinely limiting what your team can build or maintain, when the positioning has changed significantly and the current site no longer reflects it, when conversion rates on key pages have been declining for multiple quarters and targeted iteration has not moved them, or when the site's technical performance is consistently failing Core Web Vitals in ways that affect organic visibility.

A redesign is not the right call when the underlying problem is messaging or positioning. A better-looking site with unclear messaging converts at the same rate as a worse-looking one. If buyers land and do not understand what the product does within ten seconds, the problem is not the design system. Solve the positioning problem first. Then redesign.

The honest test: could you solve this problem with targeted changes to two or three pages rather than a full redesign? If yes, do that first. The risk is lower, the speed is higher, and the learning is faster.

Step 1: Audit what exists before touching anything

Before a single wireframe or design concept, run a complete audit of your current site. This audit is not about finding what is wrong visually. It is about understanding what has SEO and conversion value that must be protected.

Pull your Google Search Console data and identify every URL with organic impressions, clicks, or position in the top twenty for any keyword. These pages represent accumulated SEO equity. Changing their URLs without redirects, removing content that is ranking, or significantly altering their structure introduces ranking risk.

Export your analytics data for the past twelve months. Which pages are driving the most conversions? Which are the most-visited entry points from organic search? Which have the highest bounce rates? This data tells you where to focus redesign effort and what to protect.

Document your current URL structure, meta titles, meta descriptions, and heading hierarchy for every page in the top fifty by traffic. This becomes your SEO preservation checklist during the build.

Step 2: Lock your positioning before briefing design

Design gives form to positioning. If the positioning is unclear when the design process starts, the design process becomes a positioning process, which is significantly more expensive and slower.

Before you brief a designer or agency, be able to answer these questions clearly and concisely: Who is the specific buyer this site is built for? What problem are they experiencing before they find your product? What does your product do that changes that situation? Why would they choose you over alternatives? What is the one action you most want a first-time visitor to take?

If you cannot answer these questions confidently, the redesign should wait. A two-week positioning sprint now saves six weeks of revision cycles in the design process. It is the best investment you can make before starting any redesign project.

Step 3: Define your success metrics before launch

Set the metrics you will use to evaluate the redesign before launch, not after. This seems obvious. Almost nobody does it.

The most useful metrics for a tech company marketing site are conversion rate on demo or trial request pages compared to a 90-day pre-launch baseline, organic traffic on your core keyword clusters tracked weekly for 60 days post-launch, and Core Web Vitals scores compared to the pre-redesign baseline.

Write these down with their current values before the new site launches. This gives you an honest baseline to compare against rather than a post-hoc rationalisation of whatever the data shows.

Step 4: Choose your platform intentionally

Platform choice should follow positioning and scope, not precede them. Once you know what the site needs to do, which team will manage it after launch, and how frequently you will be iterating, the platform decision becomes more obvious.

For most tech company marketing sites, the choice is between Framer and Webflow. Framer fits teams that prioritise editing speed and design quality. Webflow fits teams with more complex CMS needs or large content operations. Custom code in Next.js or similar frameworks is rarely necessary for a marketing site and significantly increases cost and maintenance overhead.

If you are also planning to change platforms, decide whether you are migrating before redesigning or building the redesign on the new platform from scratch. These are different projects with different risks. Separating them wherever possible reduces the chance of something going wrong.

Step 5: Build a redirect map before writing a line of code

If any URLs are changing, build the complete redirect map before the build starts. Not during. Not after launch. Before.

Every URL that currently has organic traffic, backlinks, or conversion activity should appear in your redirect map with its old URL, its new destination URL, and a confirmed status. Set up all redirects in your platform before switching DNS.

The teams that discover redirect gaps after launch, when Google has already started recrawling and recording 404s, face a cleanup problem that can take months to fully resolve. The teams that complete redirect mapping before launch almost never have this problem.

Step 6: Build mobile first, not mobile last

More than half of B2B SaaS site visits now happen on mobile, including initial research from buyers who will eventually convert on desktop. A site that works well on desktop but poorly on mobile creates friction early in the buyer journey that affects conversion rates even on desktop later.

Mobile is not a responsive afterthought. It is a first-class design context. Make design decisions for mobile first and adapt them to desktop, not the reverse. Test on real devices at every stage of the build rather than running a single mobile check at the end.

Step 7: Verify everything before switching DNS

Before you switch your DNS to point at the new site, run through a complete pre-launch checklist. Every page has a meta title and meta description. No pages are set to noindex unless deliberately intended. All redirects are in place and tested individually. Forms are connecting to the correct integrations. Analytics tracking is firing correctly on every page. Core Web Vitals scores on the new build are at least as good as the current site.

This checklist should be a documented process that a second person reviews, not a mental walkthrough by the person who built the site. The builder is the least likely person to catch their own omissions.

Step 8: Submit your sitemap and monitor for 60 days

After launching, submit your new sitemap to Google Search Console and request indexing on your highest-priority pages using the URL Inspection tool. Do not wait for Google to discover the new site organically.

Monitor Search Console daily for the first two weeks. Watch for 404 errors, coverage drops, and position changes on your core keywords. A small fluctuation in the first week or two is normal as Google recrawls. Sustained drops beyond 30 days need active investigation and diagnosis.

How Studio Maydit approaches redesigns for tech companies

Every redesign we run starts with the audit and positioning work, not with design. We protect what has organic value, build redirect maps before any code is written, and measure outcomes against baselines we set before launch.

If you are planning a SaaS website redesign and want to make sure the process is structured to protect what is working while improving what is not, book a free 30-minute call with Studio Maydit.