Website redesign checklist for keeping what the old site earned
A redesign loses inquiries through details: an unmapped URL, tracking that was not carried across, a form that stopped recording its source. This website redesign checklist is twelve steps in the order the work happens. We wrote them down because three of the six criticisms in our own Clutch reviews are about details that went unchecked.

A client marked us down on minute details
We redesigned the website of a proprietary algorithmic trading firm. Four of us took it through design iterations, responsive development and go-live. The client told Clutch the execution was fast and that our project manager delivered on every request. Asked what we could do better, they named attention to minute details.
They were not the only client to say so. On October 9, 2026 we read the 15 reviews clients have left us on Clutch and counted the criticisms. Six reviews include one, and three of those six are about checking details. One client asked for a more structured content validation step at key milestones, and one said details they had given us were sometimes missed. The third is the trading firm.
The review does not say which details, so we will not guess. We can say where the details in a redesign sit. An old service page that ranked for your best query returns an error, because its URL changed and was never mapped. The contact form still sends, but the field that recorded where each inquiry came from was dropped in the rebuild. Neither shows up in a design review.
A redesign adds a new design. It can also remove what the old site earned: the pages search engines rank, the links other sites point at, the analytics history, and the record of where inquiries come from. This website redesign checklist is twelve steps that protect those first and add the new things second. Our reviews are the reason the steps are written down rather than remembered.
The checklists that already rank cover part of this. Google ranked eight pages for “website redesign checklist” when we looked on October 10, 2026. Six would open, and all six are checklists, so we counted what each one covers. Five mention redirects and four say to record a baseline.
The gaps are narrower and more specific. One of the six cites Google’s own guidance on site moves, and one says to test that lead attribution survives the form. None says how long to keep redirects. None says to remove the block that hides the staging site from search, though two say to check the robots rules. Steps four, nine and eleven below cover those.
We sell this work as website redesign services for B2B companies, so we gain if you decide a redesign needs doing properly. For that reason the technical rules below are quoted from Google Search Central, web.dev and the W3C, where you can check them. The order of the steps, and the advice on baselines, tracking and testing, are our judgment.
How to plan a website redesign strategy before anyone designs a page
You plan a website redesign by measuring the current site, writing the goal in the buyer’s terms, and listing every URL before any design starts. Five of the twelve steps come before anyone designs a page, because most of what a redesign can lose is protected or lost there.
(opens full size in a new tab)Step one is the baseline. A redesign is a change you will be asked to justify, so take the measurements before you make it. Three months of numbers from the current site is what every later claim gets compared against.
Start with inquiries per month, by source and by the page they started on. If the form does not record a source, fix that before the redesign, not after. From Google Analytics, or whatever the site runs, record the landing pages, the engagement or bounce rate on each, and the split between phones and desktops.
From Search Console, record the pages that bring search traffic, with the queries, clicks and impressions for each. Record the Generative AI performance report too, which shows how the site performs in Google’s AI features. Then list the pages other sites link to. They carry search value, and they point at URLs that are about to change.
Measure speed and stability for the main templates on real devices, so the new site can be held to the same bar or a better one. Last, write down the questions buyers ask on sales calls that the current site does not answer. Those are the pages the redesign should add.
Step two can tell you not to redesign
Step two is to write the goal in the buyer’s terms, and a written goal sometimes shows that a redesign is the wrong job. More inquiries from the right companies is a goal. A modern look is a preference. Writing the goal down settles how much of the site needs to change.
You do not need a redesign when the site works and only looks dated, when few people visit it, or when one page is the problem. A redesign is a large change with real risk, so rule out the smaller answers first.
If the site works and only looks dated, a visual refresh on the same URLs and content carries far less search risk. If few people arrive, search comes first, because a better-looking site with no traffic is still empty. If one journey is broken, such as the contact form or a single service page, fix that page. Our refresh, redesign or rebuild comparison helps you decide between them.
A redesign earns its cost when buyers arrive and leave without inquiring, and the site is the reason. If that is your position, what a website redesign costs covers the budget and how to compare quotes. The remaining ten steps assume you are going ahead.
Write the URL map before the design starts
The URL map is a list of every old URL beside its new destination, and it is the most important document in a redesign. It takes two steps to write, and both come before design.
(opens full size in a new tab)Step three is the list. Pull every URL from the sitemap, Search Console and your analytics, including the pages the menu does not link to. Then mark the ones that bring search traffic, links from other sites or inquiries. Those pages change last, if at all, and their URLs stay the same wherever possible.
Step four is the map itself. Google’s guidance on moving a site is direct about it: once you have the list of old URLs, decide where each one should redirect to.
The map decides whether rankings survive, which puts it at the center of website migration SEO. Google treats a permanent redirect as a signal that the target should be the canonical page, so a mapped redirect carries the old page’s standing to its replacement. A missing redirect leaves a broken link where a ranking page used to be.
| Old URL | What to do | Why |
|---|---|---|
| Has a direct replacement | Permanent server-side redirect (301 or 308) to the new page | Google uses a permanent redirect as a signal that the target should be canonical |
| Merged into a broader page | Redirect to the section of the page that now covers it | The visitor and the search engine both land on the answer they came for |
| Removed with no equivalent | Let it return a 404 or 410, and keep it out of the sitemap | Google advises against redirecting many old URLs to one irrelevant page such as the home page, which can be treated as a soft 404 |
| Already redirected from an older site | Point the old redirect straight at the final page | Google advises redirecting to the final destination directly rather than through a chain |
| Unchanged | Leave it, and check its title, headings and content survived | The URL kept its standing only if the page still answers the same question |
Put two rules from the same guidance in the contract. The first is to use server-side permanent redirects where technically possible, because temporary ones (302 and 307) are not used as a canonical signal. The second is to keep the redirects for as long as possible. Google’s words are generally at least one year. Links from other sites point at old URLs for far longer than that, so many sites keep them indefinitely.
You can avoid most of this work. A redesign that keeps the URLs of the pages that already rank removes most of the risk, and that is usually possible even when everything else on the page changes.
Put speed and accessibility in the brief
Step five is to write the speed and accessibility targets into the brief, because both are decided in design and only confirmed at launch. A new design tends to be heavier than the old one, with larger images, more motion and more scripts. The last week before launch is the most expensive time to find that out.
For speed, use Google’s Core Web Vitals. A good experience means the main content loads within 2.5 seconds (Largest Contentful Paint). The page responds to input in 200 milliseconds or less (Interaction to Next Paint). The layout shifts by 0.1 or less (Cumulative Layout Shift).
All three are measured at the 75th percentile of page loads, on mobile and desktop. Test each template against those numbers as it is built, on real phones and desktops, and in Chrome, Safari, Firefox and Edge.
For accessibility, name the standard: the W3C’s Web Content Accessibility Guidelines 2.2, which set three levels of conformance, A, AA and AAA. Many of the criteria are design choices. Contrast at level AA, for example, needs a ratio of at least 4.5 to 1 for normal text and 3 to 1 for large text. Choosing colors that fail it means redesigning the redesign. Other criteria are content. Every meaningful image needs alt text under success criterion 1.1.1, so the content plan has to carry the alt text across with the images.
Whether a particular level applies to you legally depends on your sector and markets. That is a question for your own advisers, and we cannot answer it here.
While the site is being built
During the build, two steps matter: rewriting the ranking pages without changing what they answer, and carrying the tracking across. Both are easy to skip because the site looks finished without them.
Step six is to keep what ranks and improve what does not. A page that ranks is answering a question well enough for Google to send people to it. Rewrite it with care: keep the question it answers, its main heading and its depth, and improve everything else. A shorter, prettier page that no longer answers the same question can lose its place even with a perfect redirect.
Step seven is to carry the tracking across. Analytics, conversion events and the form field that records where each inquiry came from all need to work on the new site. Test them on staging, before launch. Six months later someone will ask what the redesign did for inquiries, and without the tracking you cannot say.
Launch week
Launch week is four checks: the redirects, the staging blocks, the links and sitemap, and a real inquiry through every form. None of them is difficult. All four are details, and a site can look finished with every one of them undone.
Step eight is to test every redirect before launch. Check every line of the URL map for a single permanent hop to the right page. Google advises redirecting to the final destination directly, so fix any chain left over from an earlier site at the same time.
Step nine is to remove the staging blocks. Google’s site move guidance reminds you to remove any noindex tags or robots.txt blocks that were only needed during the migration. A staging site is hidden from search for good reason, and the block that hid it is easy to carry onto the live site by mistake.
Step ten is to update links, canonicals and the sitemap. Point internal links at the new URLs so they do not rely on redirects, give each page a self-referencing canonical, and submit the new sitemap in Search Console. Then crawl the staging site and the live one for broken links and duplicate content, such as the same page answering at two URLs.
Step eleven is to send a real inquiry through every form. Fill in each one on the new site and confirm the inquiry arrives where it should, with its source recorded. It takes ten minutes, and it is an easy step to skip.
The weeks after launch
Expect rankings to move after launch, and watch the pages that earn before you react to the first week. Google’s own guidance says to expect fluctuations while it recrawls and reindexes a changed site. For a medium-sized website, it says, this can take a few weeks or more.
Step twelve is to watch, then compare against the baseline. Check Search Console and inquiries daily for the first weeks, starting with the pages you marked as earning. Movement is normal. A page that lost its traffic and now returns an error, or redirects somewhere unrelated, is a fault, so fix any broken redirect the day you find it. Hold off changing more pages in the first week, because every extra change makes the picture harder to read.
Once the numbers settle, compare them against the baseline from step one. That comparison is the answer to whether the redesign worked, and it only exists if steps one and seven were done.
The website redesign checklist on one screen
Here are the twelve steps as one list you can tick. Use it in the proposal, to ask the agency how it covers each line, and again in launch week.
Website redesign checklist
Tick what is true for your redesign today. Every unticked line is something the old site has that the new one could lose.
To build a website checklist of your own, start from this one and add the lines your site has that most do not. Name each integration, each language or region, the reviewers who must sign off, and any standard your sector applies. Give every line an owner and a date.
The short version of what a redesign must protect is on our web design page.
If you are briefing a redesign now, send us the address of the current site and the brief, if one exists. The people who would design and build the site will spend 30 minutes on a call going through the twelve steps against your plan, and will tell you which ones it leaves open. If a refresh on the same URLs would do the job, they will tell you that too.
Questions about redesigning a website
How do you plan a website redesign?
Measure the current site first: three months of inquiries, search traffic and speed. Write the goal in the buyer’s terms, list every URL and mark the pages that earn, then write the URL map and put speed and accessibility targets in the brief, all before design starts.
How do you build a website redesign checklist?
Start with what the old site must keep: its ranking URLs, its links, its tracking and its inquiry records. Add what the new site must meet, such as Core Web Vitals targets and a WCAG level, then the launch checks. Give every line an owner and a date, and add lines for your own integrations, languages and reviewers.
Will a website redesign hurt my SEO?
It can. Rankings are lost when old URLs break, when ranking pages are rewritten so they no longer answer the same question, or when a staging block is left in place. They are protected by a URL map, permanent redirects and careful rewriting of the pages that earn traffic. An SEO audit before the design starts records which pages earn traffic and what each one must keep.
How long does it take rankings to settle after a redesign?
Google says to expect fluctuations while it recrawls and reindexes the site, and that for a medium-sized website this can take a few weeks or more. Larger sites can take longer.
Should I use 301 or 302 redirects in a redesign?
Permanent redirects, 301 or 308, for any page that has moved for good, because Google uses them as a signal that the new URL should be canonical. Temporary redirects (302 and 307) are not used that way. Keep them generally at least a year, by Google’s guidance.
Should I redirect deleted pages to the home page?
No. Google advises against redirecting many old URLs to one irrelevant destination such as the home page, which can confuse visitors and may be treated as a soft 404. Redirect a page to its closest equivalent, or let it return a 404 if there is none.
What tools do you need for a website redesign checklist?
Four cover most of it, and the three from Google are free. Google Search Console gives the pages and queries that earn traffic, the links and the indexing after launch. Google Analytics, or the analytics the site already runs, gives landing pages, engagement and the device split. PageSpeed Insights measures Core Web Vitals for each template. A site crawler lists every URL for the map and finds broken links, redirect chains and duplicate pages before and after launch.



