Most homepage redesigns fail in the same quiet way. The new page looks better, the team is proud of it, and three months later the sign ups are flat and a few good search rankings have slipped. Nobody wrote down what the old page was doing well, so nobody noticed it was lost.
This guide shows you a SaaS homepage redesign checklist you can run before you ship. You will get 24 checks in three gates, a table of what to keep and what to change, a launch day sequence and the mistakes that cost teams the most.
Key takeaways
Treat the redesign as three gates: decide, build and launch. Do not start a gate until the one before it is done.
Record a baseline first. Without one you cannot tell if the new page is better.
Fix the message before the layout. A new design over a vague promise is still vague.
Keep URLs and good content stable unless you have a reason to change them.
Test with strangers before launch and watch search and conversion for weeks after.
What is a SaaS homepage redesign checklist?
A SaaS homepage redesign checklist is a list of checks that keeps a redesign from breaking what already works. It covers the decision to redesign, the build and the launch.
The checklist matters because a homepage does several jobs at once. It explains the product, carries search traffic, feeds sales and signals credibility. A redesign that improves one job can quietly damage another.
If you are not sure a redesign is the right move, run the SaaS Website Messaging Audit first. Many homepage problems turn out to be copy problems, and copy is cheaper to fix than a layout.
What is the Three Gate Checklist?
The Three Gate Checklist splits a redesign into three gates, each with eight checks. A gate closes only when every check has an owner and an answer.
Gate | Question it answers | Output |
|---|---|---|
1. Decide | What are we fixing, and for whom? | Baseline, goal and message |
2. Build | Does the new page say and do it? | Copy, design and tested page |
3. Launch | Can we ship without losing anything? | Redirects, tracking and a watch plan |
Teams usually skip gate 1 because it feels like paperwork. It is the gate that decides whether the redesign succeeds.
Gate 1: Decide (8 checks)
Gate 1 sets the goal, the baseline and the message before anyone opens a design tool.
Write the one sentence goal, such as “more qualified demo requests from mid market teams.”
Name the buyer the page is for, and the buyers it is not for.
Save a baseline: traffic, top landing pages, demo or sign up rate and top search queries.
List the pages and terms that bring search traffic, so you know what to protect.
Run a five second test on the current page and write down what strangers say.
Decide the single main action and the single secondary action.
Write the headline and subhead as text, and test them before any layout exists.
Agree who approves and by what date, so reviews do not drift.
Pro tip: Write the headline in a document, not in a design file. People judge words differently when they are not looking at a polished layout.
Gate 2: Build (8 checks)
Gate 2 turns the message into a page that works on a phone and a laptop.
Put the product or its output in the first screen, not only a slogan.
Check the first screen at laptop and phone width, and see what is visible without scrolling.
Order the sections by the questions a buyer asks: who, what, why you, proof, next step.
Give every claim a source, a customer or a screen next to it.
Use real product visuals. Cropped real interface beats a stock illustration.
Write alt text for each image and keep headings in order, one H1.
Check speed and layout shift on a mid range phone.
Show the page to five strangers and fix the lines they misread.
The first screen carries more weight than many teams expect. In Scrolling and Attention (Nielsen Norman Group, April 2018), Therese Fessenden reports that “users spent about 57% of their page-viewing time above the fold,” and 74% within the first two screenfuls. The study is from 2018, so read the numbers as a direction rather than a current benchmark. People do scroll, but attention drops quickly after the first screen. Put the most important content and the main action near the top.
What should you keep and what should you change?
Keep what searchers and customers already rely on, and change what the baseline shows is not working. Use this table to sort each element.
Element | Keep when | Change when |
|---|---|---|
URL | It ranks or has links | It is a redirect chain or has no traffic |
Headline | Strangers describe the product correctly | They describe it wrong or vaguely |
Main action | Its rate is healthy for the traffic | Visitors do not know what happens next |
Proof | It is specific and current | It is old logos or unsourced numbers |
Page copy that ranks | It answers the search query | It repeats other pages |
When you cannot tell, keep it for now and test the change later. Doing everything in one release makes any drop impossible to trace.
Gate 3: Launch (8 checks)
Gate 3 protects your rankings and your tracking on the day you ship.
Keep URLs and slugs unchanged where you can. Google’s site move guidance says to map old URLs to new ones and not to send them all to the homepage.
Use permanent redirects (301 or 308) for any URL that changes, pointing straight to the final page with no chains.
Keep redirects for as long as possible, and at least a year according to Google.
Check titles, descriptions, canonical tags and structured data on the new page.
Check that the sitemap lists the new URLs and submit it in Search Console.
Test forms, the booking tool, analytics events and consent banners.
Test the page on desktop, tablet and phone, plus the 404 page.
Set a watch plan: crawl errors, indexing, rankings, traffic and conversion for the first four to eight weeks.
Pro tip: Change the platform, the URLs and the copy in separate releases when you can. When rankings move after a single change, you know which one caused it.
What goes wrong in a homepage redesign?
Redesigns go wrong when there is no baseline, when new visuals stand in for a clearer message, or when URLs change without redirects. Avoid these six:
No baseline. You cannot prove the redesign worked, or find what broke.
Redesigning the look to fix the message. The words stay vague.
Changing URLs for tidiness. Every change risks lost links and rankings.
Redirecting everything to the homepage. Google advises mapping to relevant pages.
Skipping the phone. Check your analytics before you assume visitors arrive on a laptop.
Launching on a Friday. Problems wait until Monday.
How do you test the redesign before launch?
Run the same five second test you ran on the old page, and compare the answers.
Show five people who match your buyer the first screen for five seconds.
Ask what the product is, who it is for and what they would do next.
Compare with the answers about the old page.
Pass if four of five describe the product correctly and the buyer correctly.
Fix the two most common misreadings and test again.
Also read: SaaS Website Redesign Cost in 2026.
To see how we design product pages, read our ORYN AI agent monitoring landing page case study, or browse all of our case studies.
Is your homepage ready to ship?
Send us your homepage and we will mark which of the 24 checks it fails today. Book a homepage review · See our work
SaaS homepage redesign checklist FAQs
A baseline, a clear goal, a named buyer, the headline and subhead, the first screen, proof, one main action, a redirect plan, metadata checks, tracking tests and a watch plan for the weeks after launch. Group them into decide, build and launch so nothing is skipped.
It depends on scope and approvals. A focused homepage redesign with the message already decided often takes several weeks, while a redesign that also changes the platform, the CMS or the brand takes longer. The slowest part is usually agreeing on the message, not drawing the page.
It can, if URLs, content or metadata change carelessly. Keep URLs stable where possible, redirect any changed URL directly to its closest match with a permanent redirect, keep the pages that rank and monitor Search Console after launch. Done carefully, a redesign does not have to lose rankings.
Compare against a baseline you saved before the redesign: qualified demo or sign up rate, traffic from search, engagement on the first screen and what strangers say in a five second test. Give it several weeks, since early numbers move around with traffic mix.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies. We decide the message and design the page together, so the words, layout and proof come from one plan for the buyer.
Fix the copy first when strangers cannot say what the product does or who it is for. Copy changes are faster and cheaper to test. Redesign the layout when the message is clear but the page hides it, loads slowly or fails on phones.
There is no fixed schedule. Redesign when the product, buyer or positioning changes enough that the page no longer matches, or when the baseline shows the page underperforms. Between redesigns, improve the page in small tested steps rather than rebuilding it.
About the author
Dhaval Agrawal is the founder and CEO of Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
How to move a site (site move with URL changes), Google Search Central, read Nov 2, 2026
Scrolling and Attention, Nielsen Norman Group, April 15, 2018
Webflow to Framer SEO migration guide, Framer, read Nov 2, 2026
Three Gate Checklist: Kraftbase framework, not a published standard
Homepage review
Is your homepage ready to ship?
Send us your homepage and we will mark which of the 24 checks it fails today.
Most homepage redesigns fail in the same quiet way. The new page looks better, the team is proud of it, and three months later the sign ups are flat and a few good search rankings have slipped. Nobody wrote down what the old page was doing well, so nobody noticed it was lost.
This guide shows you a SaaS homepage redesign checklist you can run before you ship. You will get 24 checks in three gates, a table of what to keep and what to change, a launch day sequence and the mistakes that cost teams the most.
Key takeaways
Treat the redesign as three gates: decide, build and launch. Do not start a gate until the one before it is done.
Record a baseline first. Without one you cannot tell if the new page is better.
Fix the message before the layout. A new design over a vague promise is still vague.
Keep URLs and good content stable unless you have a reason to change them.
Test with strangers before launch and watch search and conversion for weeks after.
What is a SaaS homepage redesign checklist?
A SaaS homepage redesign checklist is a list of checks that keeps a redesign from breaking what already works. It covers the decision to redesign, the build and the launch.
The checklist matters because a homepage does several jobs at once. It explains the product, carries search traffic, feeds sales and signals credibility. A redesign that improves one job can quietly damage another.
If you are not sure a redesign is the right move, run the SaaS Website Messaging Audit first. Many homepage problems turn out to be copy problems, and copy is cheaper to fix than a layout.
What is the Three Gate Checklist?
The Three Gate Checklist splits a redesign into three gates, each with eight checks. A gate closes only when every check has an owner and an answer.
Gate | Question it answers | Output |
|---|---|---|
1. Decide | What are we fixing, and for whom? | Baseline, goal and message |
2. Build | Does the new page say and do it? | Copy, design and tested page |
3. Launch | Can we ship without losing anything? | Redirects, tracking and a watch plan |
Teams usually skip gate 1 because it feels like paperwork. It is the gate that decides whether the redesign succeeds.
Gate 1: Decide (8 checks)
Gate 1 sets the goal, the baseline and the message before anyone opens a design tool.
Write the one sentence goal, such as “more qualified demo requests from mid market teams.”
Name the buyer the page is for, and the buyers it is not for.
Save a baseline: traffic, top landing pages, demo or sign up rate and top search queries.
List the pages and terms that bring search traffic, so you know what to protect.
Run a five second test on the current page and write down what strangers say.
Decide the single main action and the single secondary action.
Write the headline and subhead as text, and test them before any layout exists.
Agree who approves and by what date, so reviews do not drift.
Pro tip: Write the headline in a document, not in a design file. People judge words differently when they are not looking at a polished layout.
Gate 2: Build (8 checks)
Gate 2 turns the message into a page that works on a phone and a laptop.
Put the product or its output in the first screen, not only a slogan.
Check the first screen at laptop and phone width, and see what is visible without scrolling.
Order the sections by the questions a buyer asks: who, what, why you, proof, next step.
Give every claim a source, a customer or a screen next to it.
Use real product visuals. Cropped real interface beats a stock illustration.
Write alt text for each image and keep headings in order, one H1.
Check speed and layout shift on a mid range phone.
Show the page to five strangers and fix the lines they misread.
The first screen carries more weight than many teams expect. In Scrolling and Attention (Nielsen Norman Group, April 2018), Therese Fessenden reports that “users spent about 57% of their page-viewing time above the fold,” and 74% within the first two screenfuls. The study is from 2018, so read the numbers as a direction rather than a current benchmark. People do scroll, but attention drops quickly after the first screen. Put the most important content and the main action near the top.
What should you keep and what should you change?
Keep what searchers and customers already rely on, and change what the baseline shows is not working. Use this table to sort each element.
Element | Keep when | Change when |
|---|---|---|
URL | It ranks or has links | It is a redirect chain or has no traffic |
Headline | Strangers describe the product correctly | They describe it wrong or vaguely |
Main action | Its rate is healthy for the traffic | Visitors do not know what happens next |
Proof | It is specific and current | It is old logos or unsourced numbers |
Page copy that ranks | It answers the search query | It repeats other pages |
When you cannot tell, keep it for now and test the change later. Doing everything in one release makes any drop impossible to trace.
Gate 3: Launch (8 checks)
Gate 3 protects your rankings and your tracking on the day you ship.
Keep URLs and slugs unchanged where you can. Google’s site move guidance says to map old URLs to new ones and not to send them all to the homepage.
Use permanent redirects (301 or 308) for any URL that changes, pointing straight to the final page with no chains.
Keep redirects for as long as possible, and at least a year according to Google.
Check titles, descriptions, canonical tags and structured data on the new page.
Check that the sitemap lists the new URLs and submit it in Search Console.
Test forms, the booking tool, analytics events and consent banners.
Test the page on desktop, tablet and phone, plus the 404 page.
Set a watch plan: crawl errors, indexing, rankings, traffic and conversion for the first four to eight weeks.
Pro tip: Change the platform, the URLs and the copy in separate releases when you can. When rankings move after a single change, you know which one caused it.
What goes wrong in a homepage redesign?
Redesigns go wrong when there is no baseline, when new visuals stand in for a clearer message, or when URLs change without redirects. Avoid these six:
No baseline. You cannot prove the redesign worked, or find what broke.
Redesigning the look to fix the message. The words stay vague.
Changing URLs for tidiness. Every change risks lost links and rankings.
Redirecting everything to the homepage. Google advises mapping to relevant pages.
Skipping the phone. Check your analytics before you assume visitors arrive on a laptop.
Launching on a Friday. Problems wait until Monday.
How do you test the redesign before launch?
Run the same five second test you ran on the old page, and compare the answers.
Show five people who match your buyer the first screen for five seconds.
Ask what the product is, who it is for and what they would do next.
Compare with the answers about the old page.
Pass if four of five describe the product correctly and the buyer correctly.
Fix the two most common misreadings and test again.
Also read: SaaS Website Redesign Cost in 2026.
To see how we design product pages, read our ORYN AI agent monitoring landing page case study, or browse all of our case studies.
Is your homepage ready to ship?
Send us your homepage and we will mark which of the 24 checks it fails today. Book a homepage review · See our work
SaaS homepage redesign checklist FAQs
A baseline, a clear goal, a named buyer, the headline and subhead, the first screen, proof, one main action, a redirect plan, metadata checks, tracking tests and a watch plan for the weeks after launch. Group them into decide, build and launch so nothing is skipped.
It depends on scope and approvals. A focused homepage redesign with the message already decided often takes several weeks, while a redesign that also changes the platform, the CMS or the brand takes longer. The slowest part is usually agreeing on the message, not drawing the page.
It can, if URLs, content or metadata change carelessly. Keep URLs stable where possible, redirect any changed URL directly to its closest match with a permanent redirect, keep the pages that rank and monitor Search Console after launch. Done carefully, a redesign does not have to lose rankings.
Compare against a baseline you saved before the redesign: qualified demo or sign up rate, traffic from search, engagement on the first screen and what strangers say in a five second test. Give it several weeks, since early numbers move around with traffic mix.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies. We decide the message and design the page together, so the words, layout and proof come from one plan for the buyer.
Fix the copy first when strangers cannot say what the product does or who it is for. Copy changes are faster and cheaper to test. Redesign the layout when the message is clear but the page hides it, loads slowly or fails on phones.
There is no fixed schedule. Redesign when the product, buyer or positioning changes enough that the page no longer matches, or when the baseline shows the page underperforms. Between redesigns, improve the page in small tested steps rather than rebuilding it.
About the author
Dhaval Agrawal is the founder and CEO of Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
How to move a site (site move with URL changes), Google Search Central, read Nov 2, 2026
Scrolling and Attention, Nielsen Norman Group, April 15, 2018
Webflow to Framer SEO migration guide, Framer, read Nov 2, 2026
Three Gate Checklist: Kraftbase framework, not a published standard
Homepage review
Is your homepage ready to ship?
Send us your homepage and we will mark which of the 24 checks it fails today.