Website redesign checklist: preserve what works

What should a redesign checklist protect?

A redesign should keep everything that already works: pages that rank, links other sites point to, and forms that bring in leads. It should also let go of what does not work. Most redesign losses come from skipping the decisions, not from the new design.

This checklist covers the decisions you make before launch: the content inventory, keep or remove calls, the URL map, measurement, freezes, validation and rollback. Each step uses real numbers from our own rebuild of w3experts.com. Launch-day operations, such as DNS, cutover and monitoring, are covered in our website migration checklist. If you want a team to run the whole process, see website redesign.

What is the checklist, in order?

1. Export a baseline. Save search, analytics and link data before anything changes.
2. Build the content inventory. List every URL the old site serves, with its numbers.
3. Decide each URL. Keep, merge, move or remove, using written rules.
4. Write the URL map. One row per old URL, with a target and a status code.
5. Protect what converts. Record current form and call conversions, and keep working paths intact.
6. Freeze design, then content. Stop new pages on the old site once the inventory is done.
7. Validate the map on the new build. Test every row before launch.
8. Back up and write the rollback plan. Know how to go back before you go forward.

The sections below explain each step and show what it looked like on our site.

Why export a baseline before you change anything?

You cannot tell whether a redesign helped unless you know where you started. Export these before the first design review:

• Search Console performance by page and by query, for at least 12 months if you have it.
• Search Console links: top linked pages and top linking sites.
• Analytics: sessions, form submissions and calls by landing page.
• Every sitemap the site publishes, and a CMS export of all posts and pages.

For w3experts.com we used a 12-month Search Console export covering November 8, 2025 to November 8, 2026. We also checked the live sitemaps the same day. They listed 54 posts, 12 pages, 6 categories and 2 authors.

Tip: check the export’s row cap. Our pages sheet had 72 rows, well under the 1,000-row limit, so we knew it was complete. A sheet that stops at exactly 1,000 rows is missing data.

How do you build the content inventory?

Join the baseline files into one sheet with one row per URL. Add clicks, impressions, average position, backlinks, conversions and the topic. Then sort by clicks.

Our sheet told a plain story:

• The whole site earned 185 clicks and about 147,000 impressions in 12 months, at an average position around 40.
• Four URLs produced 88% of the clicks.
• 38 posts had zero impressions in 12 months.
• 51 of the 54 posts covered SEO, lead generation, advertising or B2B sales. Under our two-brand model, those topics belong to our sister brand BizAttic, not to a build studio.

Your numbers will differ, but the pattern is common. A small share of URLs carries most of the value, and many pages carry none.

How do you decide what to keep, merge, move or remove?

Write the rules first, then apply them to every URL with no exceptions. Rules stop the decisions from becoming a debate about each page. These are the rules we used:

Our decision rules. Signal means at least 1 click or 1,000 impressions in 12 months.

Two guard rails sit on top of the rules. First, never 301 a post to the homepage or an unrelated page. Google’s site-move guide warns against sending many old URLs to an irrelevant page such as the home page. It also says each redirect should go straight to its final target, with no chains. Second, any URL marked 410 that has external backlinks gets upgraded to a 301 to its closest relevant page.

Why 410 and not 404? Google’s documentation says it treats all 4xx errors except 429 the same way. We use 410 because it states the removal is deliberate, which helps anyone reading server logs later. Do not expect it to change rankings on its own.

What did the rules decide for w3experts.com?

Decisions for the 54 old posts and 26 other URLs on w3experts.com, decided November 8, 2026.

The one post we kept is a guide to the 414 “Request-URI Too Large” error. It is on topic for a build studio and it was the top-performing post on the site. It now lives at its old address as our 414 error guide.

Moving 10 posts away sounds drastic, since they carried 59% of the clicks. But those clicks came from searchers who would never hire a design studio. On BizAttic, the same readers land where SEO is actually sold.

How do you write the URL map?

The URL map is a plain file with three columns: the old path, the new target and the status code. One row per old URL. Keep it in the repository, because the build should test it.

from,to,status
/blog/website-maintenance-costs-in-2022/,/services/website-maintenance/,301
/blog/what-is-a-uiux-developer/,/services/ui-ux-design/,301
/blog/what-is-an-seo-campaign/,https://bizattic.com/blog/what-is-an-seo-campaign/,301
/blog/what-are-b2c-and-b2b-sales/,https://bizattic.com/blog/what-is-b2b-and-b2c-sales/,301
/author/roman/,/authors/raihanul-roman/,301
/blog/what-are-the-types-of-erp-systems/,,410

Our final map has 72 rows: 33 redirects and 39 removals. This is how they break down:

The 72 rows of the w3experts.com redirect map.

Two rules kept the map honest. Every 301 points at a page that will return 200 on launch day, never at a future article. And every row was decided once, in one report, then copied into the build unchanged. Our build check compares the CSV against that report and fails if a single row differs.

Note: pages that stay at the same URL, such as the homepage, About, Contact and the kept 414 guide, need no row. Nor do fragment links like #Causes_Of_414_Error_Code, because browsers never send fragments to the server.

How do you preserve what ranks and converts?

Measure before you change, then change as little as possible on the pages that earn.

1. Keep the URL. A kept page stays at its exact old address. We kept the 414 guide’s long slug even though it breaks our slug rules, because the ranking is worth more than a tidy URL.
2. Keep the headings that earn. Search results showed jump links to three sections of the 414 guide. The new page keeps those heading IDs, such as Causes_Of_414_Error_Code, so the links still resolve.
3. Keep the answer. Rewrite for accuracy and depth, but do not remove the part of the page that matches what searchers wanted.
4. Record conversions per page. Note which pages produce form fills or calls, and test the new forms end to end before launch.
5. Keep moved content live first. A 301 into a missing page throws away its history. Our plan requires all 10 BizAttic destinations to return 200 before cutover.

When should you freeze design and content?

Freeze in two stages. Each freeze stops a different kind of rework.

• Design freeze comes after the page templates are signed off. From then on, new ideas go to a list for after launch. Late design changes ripple through every template and every test.
• Content freeze comes once the inventory is final. Pause new pages and URL changes on the old site. Any edit that cannot wait goes into a change log, so it is carried into the new site.

Our build had no editors adding posts, so the content freeze was simple. On a busy site, agree the freeze date with everyone who publishes, and say what counts as urgent.

How do you validate the redesign before launch?

Run every check on the finished build, on a staging or local copy, before the live switch.

Pre-launch validation checks from the w3experts.com plan.

On our build, the redirect check passed all 72 rows against the local build on November 11, 2026. The backlink check is still open, because no backlink export was in the repository when the decisions were made. It must pass before cutover.

What is your rollback plan?

Write the rollback plan before launch day, while nobody is under pressure. It needs three parts.

1. A full backup stored off the host. For our old site that means a database dump, the uploads folder, a WordPress XML export and saved HTML of the 13 posts being kept or moved.
2. Clear triggers. Decide in advance what forces a rollback, for example key pages returning errors, or forms failing in production.
3. Safe fallbacks for partial readiness. If the BizAttic destinations are not live on cutover day, those 10 rows are not swapped to 410. We either wait or publish the posts in their current form first.

After launch, watch for 14 days: the 404 log, search coverage, clicks on kept pages and referral traffic to moved pages. The day-by-day cutover, DNS changes and monitoring steps are in the website migration checklist.

Worked example: what did the w3experts.com redesign decide?

Put together, the numbers from our own rebuild show the checklist in use:

• 54 old posts were reviewed with one set of rules. 1 stayed, 13 moved or merged to BizAttic, 2 were redirected to new pages and 38 were removed with 410.
• The URL map has 72 rows, 33 redirects and 39 removals, and it is tested by the build on every run.
• The one kept post holds 35% of the old site’s clicks and keeps its URL and its earning headings.
• Redirects stay in place for at least a year, which Google’s site-move guide recommends.
• Two checks remain before cutover: the backlink check on the 410 rows and the 10 BizAttic pages going live.

We have not launched yet, so we have no after-launch results to report. When we do, the 14-day watch figures will be published as a dated update to this guide.

If your redesign also changes budgets and scope, read how much a website redesign costs next.

Limits: what this checklist does not cover

• Cutover day, DNS, email moves and post-launch monitoring. See the website migration checklist.
• Ecommerce migrations, which also move products, orders and customers.
• Our example is a small site with modest traffic. A large site needs the same steps with more automation and a longer watch period.
• We report decisions and pre-launch checks only. No post-launch ranking or traffic results exist yet.
• Ongoing search campaigns after launch are a growth service. W3Experts builds the site; our sister brand BizAttic runs campaigns.