Key takeaways
- Redesign the message before the visuals: positioning, ideal customer and pricing should be settled before anyone opens a design file.
- Record a conversion baseline (signups, demo requests, trial starts) before launch, or you will never know whether the new site works.
- Treat the launch as an SEO migration: map every old URL and use permanent server-side redirects, which Google suggests keeping for at least a year.
- Build to Google's "good" Core Web Vitals thresholds: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
- Pick a CMS your marketing team can run without filing engineering tickets.
A SaaS website redesign checklist after product-market fit comes down to three jobs: rewrite the story for the buyer you now sell to, rebuild the paths to signup, demo and pricing around that buyer, and protect what already works (search traffic, tracking and speed) during the switch. Most failed redesigns get the visuals right and skip the third job. The checklist below is split into before, during and after launch so nothing important falls through the gaps.
Why a post-PMF redesign is different from a launch
At launch you are guessing. Our startup website checklist covers that stage: getting a credible site live that generates leads. After product-market fit, you have evidence. You know which segment converts, which features close deals, which objections come up on sales calls and which pages bring in organic traffic. A redesign at this stage should be built on that evidence, not on a new color palette.
It also carries more risk. You now have rankings, backlinks, integrations, ad campaigns and dashboards that all depend on the current site. If you are still deciding whether to redesign, our guide to the signs your website needs a redesign is a better starting point. This post assumes the decision is made.
Messaging, positioning and the pricing page
Rewrite for the buyer you actually have
Early SaaS sites often speak to everyone, or to the founder's original vision. Pull language from sales call notes, onboarding surveys and support tickets. Then answer three questions on the home page above the fold: who it is for, what problem it solves and what the visitor should do next. If you have moved upmarket, add security, compliance and integration pages that procurement teams will look for.
Show your pricing
Nielsen Norman Group's research on B2B sites found that prospective customers rank price as their top information need, and that in usability studies participants went to competitors' sites when websites did not show prices. NN/g also notes that hidden costs make companies look "evasive and untrustworthy." If enterprise deals are custom, show starting prices or typical scenarios for your self-serve tiers and explain what drives an enterprise quote. A clear plan comparison table, an FAQ on billing and a visible path to sales usually belong on the same page.
Signup, trial and demo flows
Product-led and sales-led motions need different paths, and many SaaS companies now run both. Decide which call to action is primary for each audience and page, rather than putting "Start trial," "Book a demo" and "Contact sales" side by side everywhere.
- Self-serve signup: keep the form short, allow single sign-on where your product supports it and hand users straight into a useful first screen.
- Demo requests: ask only for what routing needs (work email, company size, use case) and offer a calendar booking on the confirmation screen.
- Handoffs: make sure UTM parameters and referral data survive the jump from the marketing site to the app or CRM.
Analytics and conversion baselines before you touch anything
You cannot judge a redesign without a "before" number. In Google Analytics 4, a key event is defined as "an event that measures an action that's particularly important to the success of your business", and Google Ads conversions can be created from those key events. Before the redesign, confirm that signups, trial starts, demo requests and pricing-page visits are tracked as key events, then export at least a few months of data by channel and landing page.
List every script on the current site too: analytics, tag manager, chat, ad pixels, A/B testing and consent tools. Redesigns quietly drop tags, and the first sign is often a sales team asking where the leads went.
SEO migration: redirects, sitemaps and Search Console
If URLs change, and in a redesign they usually do, treat the launch as a site move. Google's guidance on moving a site with URL changes recommends mapping each old URL to its new counterpart, using server-side permanent redirects, avoiding redirect chains and keeping redirects for "generally at least 1 year." It also advises against sending many old URLs to one irrelevant page such as the home page, giving each new URL a self-referencing canonical tag and submitting the new sitemap in Search Console.
Google's redirects documentation explains that 301 and 308 status codes mean a page has permanently moved, and that JavaScript redirects should be a last resort. Expect some movement in rankings after launch; Google says this is normal and rankings "will settle down over time." Don't forget the long tail: blog posts, comparison pages, docs and changelog entries often hold more organic traffic than the home page.
Redesigns tend to add video, animation and third-party scripts. Set performance budgets early. web.dev defines the "good" Core Web Vitals thresholds as Largest Contentful Paint of 2,500 ms or less, Interaction to Next Paint of 200 ms or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page views. Google's own Search Central guidance says it highly recommends good Core Web Vitals "for success with Search," while its page experience documentation is clear that Search "always seeks to show the most relevant content, even if the page experience is sub-par."
Build accessibility into the design system rather than bolting it on later: color contrast, keyboard navigation, labeled form fields and captions for product videos. It helps every buyer, including those using assistive technology at the companies you sell to. If you sell to consumers in the EU, note that the European Accessibility Act has applied since 28 June 2025 and covers services including e-commerce; whether it touches a particular SaaS product depends on details such as who your customers are, so ask a lawyer. Our website accessibility team can audit the new templates before launch.
Docs, changelog and a CMS your marketers can run
After product-market fit, the marketing team ships more pages each month: landing pages for campaigns, integration pages, customer stories, comparison pages. If every change needs a developer, the site stalls. Choose a CMS that lets marketers build pages from approved components while engineering keeps control of the design system. Traditional platforms such as WordPress or Webflow suit most marketing teams; headless CMS setups are worth considering if the site shares components with your app.
Decide where documentation and the changelog live. Keeping them on a subdomain or separate tool is fine, but link them clearly from the main navigation. A visible, regularly updated changelog is one of the simplest signals that a product is actively maintained.
The phased SaaS website redesign checklist
| Phase | Checklist items | Owner |
|---|
| Before | Positioning and ideal customer agreed; pricing model confirmed; conversion baseline exported; script and tag inventory; full URL crawl and redirect map; Core Web Vitals and accessibility baseline | Founder, marketing lead, product |
| During | Component-based design system with accessible patterns; pricing and plan comparison page; separate signup and demo paths; key events rebuilt and tested on staging; performance budgets checked on every template; CMS roles and workflows set up | Design, development, marketing |
| Launch day | Permanent server-side redirects live; self-referencing canonicals; new sitemap submitted in Search Console; tags firing; forms routing to CRM; robots rules checked | Development, marketing ops |
| After | Monitor 404s and crawl errors; compare key events against baseline; review field Core Web Vitals; update external profile links; keep redirects for at least a year; iterate on pricing and signup pages | Marketing, development |
Who should build it
Seed to Series B teams rarely have spare in-house engineers for the marketing site, and the product roadmap should not wait for it. A fixed-scope project with an outside team is a common route; our startup launchpad is built for this stage, and it can run alongside your in-house product team. Whoever builds it, insist on a written redirect map, a tracking plan and performance budgets as deliverables, not afterthoughts.
Frequently asked questions
When should a SaaS startup redesign its website?
Usually when the product, ideal customer or pricing has changed enough that the current site no longer explains what you sell or to whom. Raising a round, moving upmarket or adding a sales team are common triggers.
Will a redesign hurt our SEO?
It can if URLs change without proper redirects. Google's site-move guidance recommends mapping old URLs to new ones, using permanent server-side redirects and submitting a new sitemap. Some temporary ranking movement is normal.
Should we publish pricing if most revenue is enterprise?
Showing at least starting prices or typical scenarios usually helps. Nielsen Norman Group found B2B buyers rank price as their top information need and move to competitors when it is missing.
What should we measure after launch?
Compare signups, trial starts, demo requests and pricing-page visits against your pre-launch baseline, alongside 404 errors, Search Console coverage and field Core Web Vitals.