SaaS Website Redesign Checklist (with SEO Migration Steps)

The short answer

A safe SaaS website redesign comes down to three things: map every old URL to a new one with permanent redirects, carry your analytics and tracking across without gaps, and check everything on launch day before you announce it. Keep the redirects for at least a year, submit a new sitemap in Search Console, and expect some ranking movement for a few weeks. The checklist below covers pre-launch, launch day and the month after.

Why redesigns lose traffic

Most traffic drops after a redesign come from a short list of causes: URLs that change without redirects, pages that disappear, internal links that still point at old URLs, a staging site that gets indexed, or analytics that stop recording key events. None of these are design problems. They're process problems, and a checklist fixes them.

Google's own guidance for site moves with URL changes says to expect temporary ranking fluctuation, and that for medium-sized sites it can take weeks or more for new URLs to replace old ones. Plan the launch with that in mind, not on the day before a big campaign.

Pre-launch checklist

Benchmark what you have

• Export the top pages by organic clicks from Search Console for the last 12 months.
• Export top landing pages and key events from GA4, so you can compare after launch.
• Crawl the current site and save the list of every URL, title, meta description and H1.
• Note which pages earn backlinks. These need redirects most of all.

Content and URL plan

• Decide which pages stay, merge or go. Don't drop pages that bring traffic or sign-ups without a replacement.
• Keep URLs the same where you can. Every unchanged URL is one less redirect to get right.
• Carry over the content that ranks. A beautiful page with half the words can lose the queries it used to win.

Redirect map

• Map every old URL to its closest new equivalent in a spreadsheet.
• Use server-side permanent redirects (301 or 308), which is what Google recommends.
• Point each redirect straight at the final URL. Avoid chains.
• Don't send everything to the homepage. Redirect to the most relevant page, or let a page with no equivalent return a 404.
• Include old blog posts, docs links, PDFs and campaign landing pages.

Technical SEO

• One H1 per page, with a logical H2 and H3 structure.
• Unique title and meta description for every page and CMS template.
• Self-referencing canonical tags on the new URLs. Update hreflang if you have more than one language.
• Internal links updated to new URLs, not relying on redirects.
• Staging site blocked from indexing, and that block removed from production at launch.
• Images with alt text and sensible file sizes.

Structured data

• Organisation and WebSite markup on the homepage; Article or BlogPosting on posts; BreadcrumbList where you show breadcrumbs.
• Keep markup consistent with what is visible on the page. Google's guidance asks for this.
• Don't add FAQ markup expecting a Google rich result. Google stopped showing FAQ rich results in May 2026.
• Test templates with Google's Rich Results Test before launch.

Analytics and tracking

• Install the same GA4 property on the new site. Don't create a new one, or you lose your history.
• Recreate every key event: demo requests, sign-ups, contact forms, pricing page visits.
• Check tag manager, ad pixels, CRM forms, chat widgets and cookie consent on staging.
• Keep UTM-tagged campaign URLs working.

AEO basics

AI assistants such as ChatGPT, Claude, Perplexity and Google's AI features lean on the same search signals, so a clean migration protects your AI visibility too. A few extra checks:

• Robots.txt allows search crawlers such as Googlebot, Bingbot, OAI-SearchBot (ChatGPT search), PerplexityBot and Claude-SearchBot, unless you have a reason to block them.
• Key facts about your company (what you do, who it's for, pricing model, integrations) are written in plain text on the page, not only in images.
• Comparison, integration and use-case pages survive the redesign with their URLs or redirects.

QA

• Test every template on mobile, tablet and desktop, and in the main browsers.
• Submit every form and confirm the data arrives in your CRM.
• Check Core Web Vitals on key pages: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, Cumulative Layout Shift of 0.1 or less.
• Run an accessibility check: contrast, focus states, keyboard navigation and alt text.
• Check the 404 page is helpful and returns a real 404 status.

Launch day checklist

• Publish at a quiet time, early in the week, with the team available.
• Upload or switch on redirects and test a sample of old URLs, including the top 50 by traffic.
• Confirm the production site is indexable: no stray noindex tags or robots.txt blocks.
• Check the XML sitemap lists only new, live, canonical URLs.
• Submit the new sitemap in Search Console and request indexing for the most important pages.
• Use Search Console's Change of Address tool only if you're moving to a new domain. It isn't needed for a redesign on the same domain.
• Open GA4 Realtime and confirm page views and key events are recording.
• Submit every form once more on production.
• Submit the sitemap in Bing Webmaster Tools too. Its AI Performance report, in public preview, shows how often your pages are cited in Microsoft Copilot and Bing's AI summaries.

Post-launch checklist

First week

• Check Search Console daily for crawl errors, 404s and pages excluded from the index.
• Crawl the live site to catch broken internal links and redirect chains.
• Compare GA4 key events with your benchmark. A sudden drop usually means broken tracking, not lost demand.

First month

• Compare organic clicks and impressions for your top pages against the benchmark.
• Fix redirects for any old URLs still showing in reports.
• Ask the sites that link to you most to update their links.
• Ask ChatGPT, Perplexity and Google a few questions your buyers would ask, and note whether your new pages are cited.

Ongoing

• Keep redirects in place for at least a year. Google recommends as long as possible.
• Review Search Console monthly and keep the sitemap clean.

Who should own this

Give one person the redirect map and the launch checklist, even if an agency does the build. Redesigns usually land on a fixed date. We rebuilt Sprinto's brand and website for its $20M Series B and the launch of Sprinto AI, so the new site had to be right on announcement day. Our Webflow & Framer Development team works through a list like this on every site we ship.

FAQ

Will a redesign hurt our SEO?

It can, but it doesn't have to. Most losses come from missing redirects, dropped content or broken tracking. With a full redirect map and QA, expect a short wobble, not a lasting drop.

How long should we keep 301 redirects?

Google suggests at least a year, and as long as possible. There's little cost in keeping them.

Should we change platform during a redesign?

It's a good moment to do it, since you're rebuilding anyway. See our Webflow vs Framer comparison if you're choosing.

Do we need a new GA4 property?

No. Keep the existing property so you can compare before and after.

Planning a redesign this quarter? Get in touch and we'll look at your current site with you. You can also see how we approach Website, Product & App Design.