A Website Redesign Checklist That Protects Your Rankings

What Is a Website Redesign Checklist?

A website redesign checklist is not a design mockup. A mockup shows how pages look. A checklist ensures the site functions, ranks, and converts after the new version goes live. Teams that focus only on the visual work often end up with a beautiful site that loses search visibility, breaks form submissions, and confuses visitors.

The checklist covers six areas in a single document: design and branding, SEO, content migration, analytics and tracking, hosting infrastructure, and launch readiness. Each area has specific items that must be verified before the new site replaces the old one.

Redesigns fail when teams jump straight to visuals without protecting what already works. Traffic drops because URLs change without redirects. Leads disappear because form endpoints shift. Rankings fall because heading structure and schema markup get rebuilt without a keyword map. A checklist forces every team member to sign off on the technical side before anyone touches pixels.

A practical checklist prevents three things: lost traffic from broken links, missed conversions from untracked forms, and wasted budget on a site that does not rank.

Checklist: Pre-launch verification

• All existing high-traffic URLs mapped to new URLs or redirected with 301 rules
• Meta titles, descriptions, and H1 tags verified against the keyword plan
• Form action URLs and tracking IDs confirmed working on staging
• Internal links updated to point to new page URLs
• Sitemap.xml generated and submitted to Search Console
• Staging blocks (password, noindex tags, robots.txt disallow rules) removed from the live build
• Page speed scores reviewed on mobile and desktop before approval
• Brand colors, fonts, and logo files exported and loaded on the new theme

This checklist is the difference between launching a redesign that preserves revenue and launching one that resets it. The items below walk through how to build that document in practice.

Phase 1: Audit Your Current Website Before You Start

Skipping the audit and starting with design is one of the quickest ways to lose search visibility. The audit must happen while the current site is still live because you need real data, not estimates.

Step-by-step: the pre-launch audit

1. Run a full SEO crawl of the current site. Use a site crawler tool to identify broken links, redirect chains, missing meta tags, and crawl errors. Export the report. Every URL flagged as a 404 or returning a soft error needs a redirect plan. Do not fix these on the new site first. Fix them on the old site, then capture the clean state.

1. Document every page that drives traffic or leads. Open Google Search Console and pull the top 100 pages by impressions and clicks. Open analytics and pull the top 50 landing pages by sessions and conversions. Cross-reference the two lists. Any page on both lists is a revenue asset. Do not remove it without a replacement that carries equal keyword weight.

1. Map existing content to the new site structure. Create a spreadsheet with three columns: current URL, new URL, and redirect type. If a page will be deleted or merged, note the closest relevant page it will redirect to. Plan a 301 redirect for every URL that will change. A 302 tells search engines the move is temporary, so the old URL can stay in the index longer than you want.

1. Check analytics and conversion tracking to establish a baseline. Export form submissions, phone calls, and key events (what GA4 calls conversions) from your analytics platform. Record the numbers in a simple table. After launch, compare the new numbers against this baseline. If conversion drops, you know where to look first.

Audit your current SEO health

The crawl report should flag these specific issues before any design begins: redirect chains longer than two hops, orphaned pages with no internal links pointing to them, meta descriptions missing on many URLs, and H1 tags duplicated across multiple pages. Fix those items on the live site first, then capture a snapshot of the clean version. That snapshot becomes your reference point when the new site launches.

Map your existing content

Content mapping is where most redesigns lose their voice. Take every blog post, service page, and landing page and note its primary keyword, search intent, and conversion role. When the new site structure goes live, every page must have a clear purpose. A page that used to rank for a specific query cannot simply become a generic contact page. It needs a replacement that targets the same query or redirects cleanly to one that does.

Set your analytics baseline

Baseline data answers one question after launch: did the redesign hurt conversions? Without a baseline, you are guessing. Export form submission counts, phone call tracking numbers, and key event rates from the 30 days before launch. Record them in a spreadsheet. After launch, compare week by week against those numbers. A small dip in the first few weeks is common as Google re-crawls the new structure. A sustained drop means something broke in the migration.

Phase 2: Protect Your SEO During the Redesign

Technical SEO is not optional in a redesign. The new site either preserves search visibility or it loses it. The difference comes down to decisions made before anyone writes code.

Checklist: SEO protection items

• Preserve URL structure wherever possible; change only what must change
• Use 301 redirects for every URL that moves or disappears
• Verify mobile-first rendering on the staging build before approval
• Confirm heading hierarchy (one H1 per page, logical H2 to H4 flow)
• Add schema markup for Organization, LocalBusiness, and FAQ where relevant
• Build internal links between related pages before going live
• Submit the new sitemap to Google Search Console shortly after launch
• Check robots.txt allows indexing of all public pages

Do not panic if rankings do not jump immediately after launch, or wobble for a while. Google needs time to recrawl and reindex the new structure, and gains from the redesign build gradually. The redirect map you built during the audit is the single biggest factor in whether that process goes smoothly.

URL structure and redirects

The simplest rule is: keep the old URL if the content still lives there. If a page moves from one section to another, set up a 301 redirect. If a page is deleted entirely, redirect it to the closest relevant category page. Avoid redirecting deleted pages to the homepage. Google often treats an irrelevant redirect like that as a soft 404, so the old page's signals are lost. Every redirect must point to a live page with comparable content.

Technical SEO foundations

Before launch, verify these items on the staging environment: canonical tags point to the correct version of each page, hreflang attributes are set correctly if the site targets multiple regions, Open Graph and Twitter card meta tags render properly when shared on social platforms, and the mobile viewport meta tag is present. A missing viewport tag means mobile users will see a desktop layout zoomed out, which makes pages hard to use on a phone.

Content and keyword mapping

Every page on the new site needs a primary keyword target. Without one, pages end up competing with each other for the same queries. Map each page to a single primary keyword, note its search intent (informational, transactional, or navigational), and ensure the heading structure supports that intent. An informational page should lead with an H2 that answers the query directly. A transactional page should lead with an H2 that presents the offer. Do not mix intents on the same page.

Phase 3: Plan Your Launch Timeline and Hosting

A redesign is more than a design project. It is a production timeline with infrastructure decisions that most checklists ignore. The difference between a smooth launch and a broken one comes down to planning.

Build time depends on the number of pages, the integrations, and whether the site sells online, and any estimate assumes a clear brief, responsive stakeholders, and no scope creep. If the project team adds pages mid-build or changes the sitemap structure after approval, the timeline extends. Build buffer time into every phase.

Choose hosting with a strong uptime record and a published service level, because downtime during launch means lost leads while visitors hit an error page. Ideally, staging runs on the same hosting setup that will serve the live site. If launch requires pointing DNS to a new server, lower the DNS record's TTL ahead of time and keep the old site running until the change has propagated, so no visitor lands on an empty server.

Plan a soft launch with a staging environment before going live to the public. Put the staging URL behind a password or IP whitelist. Run through every form, checkout flow, and contact page on staging before approving the build. Schedule the final launch during a low-traffic period, typically early morning on a weekday, so any issues get caught before they affect customers.

Framework: the launch decision rule

Before approving a launch date, ask three questions. Is every redirect map verified against a live crawl? Are all conversion tracking IDs confirmed working on staging? Has the new sitemap been submitted to Search Console? Yes to all means the launch is ready. One no means hold the date and fix the gap first.

Phase 4: Post-Launch Monitoring and Optimization

Launching the site is not the end of the work. The early days determine whether the redesign preserves revenue or resets it, so monitoring needs an owner and a schedule.

Step-by-step: the first 30 days after launch

1. Monitor Google Search Console daily for crawl errors, indexation issues, and broken links. Check the Page indexing report for newly reported 404s, pages blocked by robots.txt, and pages marked as crawled but not indexed. Fix any new errors within a short period.

1. Track conversion rates and form submissions to ensure the new site captures leads. Compare the new submission volume against the baseline recorded during the audit. If form submissions drop significantly in the first week, check the form action URL, the hidden field values, and the analytics tracking code on the submission confirmation page.

1. Check page speed and mobile usability on Google PageSpeed Insights. Run the live URL through PageSpeed Insights weekly for the first month. Note the Core Web Vitals scores. If the new site scores lower on Largest Contentful Paint, Interaction to Next Paint, or Cumulative Layout Shift than the old one, identify the heaviest assets and compress or defer them.

1. Review analytics weekly for the first month to catch drops in traffic or engagement. Pull the top landing pages from analytics each week, and compare their impressions and clicks in Search Console against the pre-launch baseline. A page that lost impressions likely lost its keyword target during migration. A page that gained clicks without a ranking change likely improved its click-through rate, which means the new meta title is performing better than the old one.