Website Redesign Checklist: 27 Things to Do Before You Launch

Why Most Website Redesigns Hurt Before They Help

Here is the uncomfortable truth about website redesigns: most companies see a traffic drop in the first 30 to 90 days after launch. This is not inevitable. It is the predictable result of skipping the steps that preserve your existing search equity.

Google has indexed and ranked your current pages based on years of signals: content, backlinks, user behavior, site structure, and URL authority. When you launch a redesigned site that changes URLs without proper redirects, restructures your information architecture without mapping the old to the new, or redesigns pages in a way that removes the content Google was ranking, you are essentially asking Google to re-evaluate your entire site from scratch.

The businesses that execute redesigns without traffic loss do two things differently. First, they treat SEO preservation as a first-class requirement, not an afterthought. Second, they invest as much effort in migration planning as they do in the design itself. A beautiful new site that loses 40 percent of its organic traffic is not a successful redesign, no matter how good it looks.

This checklist exists because we have seen too many businesses learn this lesson the hard way. Every item on this list addresses a specific failure mode we have encountered in real redesign projects.

Pre-Redesign Audit: What to Document Before You Touch Anything

The audit phase is where successful redesigns are won or lost. You need a complete picture of your current site's performance before you change a single pixel.

Start with Google Analytics. Export monthly traffic trends for the last 12 months, your top 100 pages by organic traffic, your top 50 pages by conversion rate, user flow data showing how visitors navigate your site, and bounce rate and time-on-page for your key landing pages. This data tells you what is working and what should be preserved.

Next, pull data from Google Search Console. Document every keyword your site ranks for in the top 50 positions, especially those in positions 1 through 20. Record which pages rank for which terms. This is your search equity map and it dictates your redirect strategy and content migration priorities.

Run a full technical crawl using Screaming Frog, Ahrefs, or Sitebulb. Document every URL on the site, response codes, internal linking structure, orphaned pages, duplicate content issues, and metadata. This crawl becomes the source of truth for your URL mapping spreadsheet.

Finally, benchmark your Core Web Vitals. Run PageSpeed Insights on your top 10 pages and record LCP, FID, CLS, and TTFB scores. Your redesigned site should match or exceed these scores at launch. If the new site is slower than the old one, you have a problem that will affect both rankings and conversion rates.

• Export top 100 pages by organic traffic from Google Analytics
• Document all keywords ranking in positions 1 through 20 from Search Console
• Run a complete site crawl and export all URLs with status codes
• Benchmark Core Web Vitals scores for your top 10 landing pages
• Record current conversion rates for every form and CTA
• Catalog all inbound backlinks and which pages they point to
• Screenshot your current Google Business Profile and any featured snippets

SEO Preservation: The 301 Redirect Strategy That Saves Your Rankings

Redirects are the single most critical technical element of any website redesign. Get them wrong and you can lose months or years of search ranking progress overnight.

A 301 redirect tells Google that a page has permanently moved to a new location and that the new URL should inherit the search equity of the old one. Every page on your current site that has traffic, rankings, or backlinks needs a 301 redirect to its most relevant counterpart on the new site.

The URL mapping process works like this. Take your crawl export with every URL on the current site. In a spreadsheet, add a column for the new URL. Map each old URL to its closest equivalent on the redesigned site. For pages that are being consolidated, redirect all old URLs to the combined page. For pages being removed entirely, redirect to the most relevant parent or category page. Never redirect to the homepage unless the page truly has no relevant equivalent.

Common redirect mistakes that destroy rankings include redirect chains where page A redirects to page B which redirects to page C, redirecting all old pages to the homepage which Google treats as a soft 404, using 302 temporary redirects instead of 301 permanent redirects, and forgetting to redirect old blog post URLs or resource pages that have accumulated significant backlinks over time.

Test every redirect before launch. Use a crawler to verify that each old URL resolves to the correct new URL with a 301 status code and no chains. A single afternoon of thorough redirect testing can prevent months of traffic recovery.

Technical Requirements and Launch Day Execution

Launch day is not the time for improvisation. Every technical requirement should be completed, tested, and verified before the DNS switch.

Your technical launch checklist should include SSL certificate installed and forcing HTTPS on all pages, XML sitemap generated and validated with no errors, robots.txt reviewed to ensure it is not blocking CSS or JavaScript resources that Google needs to render pages, canonical tags set correctly on every page pointing to the preferred URL version, structured data markup validated using Google's Rich Results Test, Open Graph and Twitter Card meta tags present for social sharing, custom 404 page designed and returning the correct status code, and favicon and web app manifest configured.

For the actual launch, plan for a low-traffic window, typically early morning on a Tuesday or Wednesday. Have your development team, SEO team, and content team available for the first four hours after launch. Execute in this order: deploy the new site to production, implement all 301 redirects, verify the site is accessible and HTTPS is working, submit the new XML sitemap to Google Search Console, use the URL Inspection tool to request indexing of your top 10 pages, verify all forms are submitting correctly and delivering notifications, and run a quick crawl of the new site to catch any broken links or missing pages.

Do not launch on a Friday. If something goes wrong, you do not want the first response to happen on Monday morning. The first 48 hours after launch are critical for catching and resolving issues before they compound.

Post-Launch Monitoring: The First 30 Days

The 30 days after launch are when redesign problems surface. Proactive monitoring during this window is the difference between catching issues early and discovering three months later that your organic traffic dropped by half.

During the first week, check Google Search Console daily. Look for spikes in crawl errors, drops in indexed page count, and any manual action notifications. Monitor your top 20 keywords for ranking movement. A small dip of one to three positions is normal and typically recovers within two to four weeks. A drop of five or more positions on multiple keywords suggests a redirect issue, content change, or technical problem that needs immediate investigation.

During weeks two through four, compare key metrics to your pre-redesign baseline. Organic traffic should be within 10 percent of the old site's levels by week three if redirects and content are handled properly. Conversion rates on key pages should meet or exceed the old site. If conversion rates dropped but traffic is stable, you have a UX issue with the new design. If traffic dropped but conversion rates improved, you may have lost low-quality traffic, which is actually a positive outcome.

Create a monitoring dashboard that tracks daily organic sessions, top keyword rankings, crawl error count, page indexing status, conversion rate by page, Core Web Vitals scores, and broken link count. Set alerts for any metric that deviates more than 15 percent from the baseline. The goal is to catch problems while they are small and fixable rather than discovering them during a quarterly business review.

• Check Google Search Console crawl errors daily for two weeks
• Monitor top 20 keyword rankings for position changes
• Compare organic traffic week-over-week against the pre-redesign baseline
• Verify all 301 redirects are resolving correctly with no chains
• Test conversion forms weekly to ensure they still function
• Run Lighthouse audits weekly and address any performance regressions
• Review Google Analytics for unexpected bounce rate increases on key pages