Insights / Article
Website redesign checklist: what we check firstBefore anything is drawn
A website redesign checklist from our own redesigns and Google's guidance: what the site must say, what the product does now and how to move old URLs.

This is the website redesign checklist we go through before a redesign starts. Most of it happens before anyone opens a design file. It covers what each page has to do, what the product does today that the site does not say, whether the site and the product share one system, and how every old URL moves to its new address. Four of the checks come from sites we redesigned or built, and each of those links to the case. Two come from how we work, and two follow Google’s and the W3C’s own guidance. Our web design service starts from the same place: the words, written before anything is drawn.
The website redesign checklist at a glance
| Check | The question it answers | Where we saw it |
|---|---|---|
| 1. One job per page | What should a visitor understand when they leave this page? | Simplisales |
| 2. What the product does now | Which features does the site leave out? | Screenloop |
| 3. Words before design | Is every page written before it is drawn? | Our own process |
| 4. One system or two | Will the site and the product share tokens and components? | Guideflow |
| 5. The system at page 150 | Can the team add a page without the design falling apart? | PetDesk |
| 6. Every old URL mapped | Where does each current URL go after launch? | Google Search Central |
| 7. Speed and accessibility | Which targets go into the brief? | Google, W3C |
| 8. Who edits after launch | Can your team change the words without us? | Our own process |
1. Name the one job each page has to do
Start with a single sentence per page: what someone should know or do by the time they reach the bottom. If you cannot write that sentence yet, write it before the page is designed.
Simplisales is a wholesale platform with four surfaces: a dashboard, e-commerce, a mobile app and a marketing suite. Its old landing page named the category and stopped there. Someone with a real problem could read the whole page and still not know what the software did or whether it was for them.
We rebuilt the page around one job, explaining the product, and rewrote every section to serve it. The hero puts the dashboard right under the headline, so a visitor sees the product before reading about it. The scope was web design only, with no product work and no rebrand. The full story is in the Simplisales redesign.
2. List what the product does now that the site does not say
A product keeps shipping while its site stays the same, and after enough releases the site describes an earlier product. Before a SaaS website redesign, put two lists side by side: what the product does today, and what the site claims. Whatever is on the first list and missing from the second goes into the brief.
Screenloop is a hiring platform that did more than its website let on. We designed the new site around what the product does: reporting, AI notes from interviews, integrations and enterprise security. We also developed it end to end, with no handoff between design and build. You can see how that played out in the Screenloop case.
A quick test: ask someone from sales or support which questions prospects ask that the site never answers, and plan a section for each one.
3. Write the words before anything is drawn
Our order is write, design, build, launch. What the site says is written page by page, with you, before anything is drawn. Design then works with real headlines and real lengths instead of placeholder text. Nobody has to squeeze a longer sentence into a box sized for three words, and design reviews start from what each section says.
4. Decide whether the site and the product share one system
If you have a product, decide early whether the new site will be built on the same design system as the product, or on its own.
Guideflow had a product built fast on off-the-shelf UI kits. Over six months we rebuilt the product, every page of the marketing site and a design system underneath both, so the site and the product use the same parts. The Guideflow case shows the editor and the pages around it.
When the site reads the product’s tokens, the colors and type are the same in both. A visitor who clicks the sign-up button lands on a first screen that looks like it came from the same company. We wrote about how that setup works in one design system for site and product.
If the product’s system has gaps, fix them first, because a site on a separate system leaves two sets of colors, type and components to keep in step.
5. Check that the system holds at page 150
Most of a site is inner pages, and after launch the team keeps adding ones nobody designed. Judge the redesign on those as well as the homepage.
We designed and built PetDesk’s entire website, more than 150 pages, developed alongside the design. At that size the question is whether the system holds: page 150 should be as considered as page one, and the team should be able to add the next page without the design falling apart. See how that is set up in the PetDesk case.
Before you approve a redesign, ask to see an inner page built from the components.
6. Map every old URL before launch
These are the steps Google’s own guide to a site move with URL changes sets out:
- Prepare a URL mapping from every current URL to its new address.
- Configure the server to redirect each old URL to its new one. Google recommends a permanent server-side redirect whenever possible; HTTP 301 and 308 both mean moved permanently.
- Change the internal links on the new site from the old URLs to the new ones, using the same mapping.
- Monitor the traffic on both the old and new URLs after launch, in Search Console and your analytics, and expect some movement.
Build the list of old URLs from what the current site actually serves, page by page. Google says that with any significant change to a site, rankings may fluctuate while it recrawls. For medium-sized websites, it can take a few weeks or more before Google starts showing the new URLs instead of the old ones, and longer for large sites.
7. Set the speed and accessibility bar in the brief
Put the targets in the brief, so the build is checked against them from the first page.
For speed, use Google’s Core Web Vitals thresholds: Largest Contentful Paint within 2.5 seconds of the page starting to load, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1.
For accessibility, name the standard. The W3C publishes the Web Content Accessibility Guidelines, and says each WCAG version (2.0, 2.1 and 2.2) is a stable standard once it is published as a W3C Recommendation. Its success criteria sit at three levels, A, AA and AAA, so the brief should name a version and a level, for example WCAG 2.2 at level AA.
Add the search groundwork to the same list: page titles, share images, structured data and search verification. On our builds that is set up before launch.
8. Decide who edits the site after launch
Decide before the build who will edit the words after launch, and how. If only the designer can change the site, every update waits on them.
On our sites, the words live in plain files your team can change, and we show you how. A visual editor or CMS is not part of the build, so if your team needs one, say so at the start. At the end, the site, its code and its words are handed over in full.
Questions to ask before a website redesign
Will a website redesign hurt our Google rankings?
It can move them for a while. Google says rankings may fluctuate during any significant change, and a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results. Google’s site move guide sets out the steps for that period: a full URL mapping, permanent server-side redirects and internal links updated to the new URLs.
How long does a website redesign take?
It depends on the product, so we set the timeline when we scope the work. One reference point: for Guideflow, the product, every page of the site and the design system under both took six months together.
Do we need to redesign the product at the same time?
No. The Simplisales project was web design only, with no product work. If the product is due for changes too, look at it first, because the site should sell the product people will actually use. Our product audit before a relaunch covers what to check.
Can our team edit the new site ourselves?
Yes. The words live in plain files your team can change, and we show you how. A visual editor or CMS is not included, so if you need one, it belongs in the brief from the first day.
Go through this website redesign checklist before the first design review and bring the answers to it. If your site still sells the first version of your product, tell us where your site stands and we will start from what you already have.



