A website redesign done without a checklist is the single most common way businesses destroy their own search rankings. The new site launches, everyone celebrates the design, and four weeks later organic traffic is down 40 percent not because the design is bad, but because nobody mapped the old URLs, carried over the metadata, or benchmarked what was working before it was replaced.
This checklist prevents that. Fifteen steps in three phases: ten before anyone opens a design tool, three during the build, and two at launch. The before-phase feels bureaucratic and is where every ranking-protecting decision happens; teams that skip to the design phase are redecorating a house without checking which walls hold the roof.
Phase 1: Before Design Starts (Steps 1–10)
Step 1: Benchmark current performance
Export 12 months of Google Search Console and GA4 data: top pages by clicks, the keywords each ranks for, conversion paths, and top entry pages. This snapshot is your insurance policy after launch it is the only objective way to know whether the redesign helped or hurt, and which specific pages need rescue. Save the exports outside the analytics tools; you want the record even if tracking breaks during migration.
Step 2: Crawl and record every URL
Run Screaming Frog (free up to 500 URLs) across the current site and export every URL with its title tag and meta description. This inventory becomes the left-hand column of your redirect map in step 9 and your metadata source in step 12. Sites accumulate more URLs than anyone remembers old campaign pages, PDFs, forgotten blog posts and each one Google knows about needs a decision.
Step 3: Identify your money pages
Cross-reference the crawl with the benchmark: which pages rank, convert, or earn backlinks? These are your money pages, and the redesign rule for them is preserve, not reinvent keep their URLs where possible, keep the content substance, improve the presentation. A redesign is allowed to change everything about the pages nobody visits; it must be conservative with the pages that pay the bills.
Step 4: Audit backlinks
Run the domain through a backlink checker (Ahrefs, Semrush, or a free tier) and note which URLs other sites link to. Those URLs carry accumulated authority that took years to earn and transfers only through exact 301 redirects. A linked URL that dies in the redesign takes its authority to a 404 page. Flag every linked URL in your crawl export as protected.
Step 5: Define measurable goals
“Increase quote requests 30 percent” and “cut bounce rate on service pages below 50 percent” are goals a designer can design toward and you can verify afterward. “Modernize the look” is a goal that succeeds the moment money is spent. Write three measurable goals and put them at the top of the project brief — they will settle a dozen design debates later by giving every disagreement a tiebreaker.
Step 6: Interview real customers
Talk to three to five actual customers: what did they come to the site to do, what almost stopped them, what words do they use for your services? Their vocabulary belongs in your headlines, and their friction points define the redesign priorities. One hour of customer calls reliably outperforms ten hours of internal opinion about what the website should say.
Step 7: Map the new sitemap and get sign-off
Draw the full page structure of the new site every page, every section and have every stakeholder approve it in writing before design begins. Structural changes cost minutes at this stage and weeks once designs exist. The sitemap review is also where duplicate-content risks surface: two planned pages targeting the same keyword should be caught here, not discovered in Search Console six months later.
Step 8: Write the content first
Design around real copy, never pour copy into finished designs. Lorem ipsum layouts collapse on contact with actual headlines that are twice as long as the placeholder. Content-first also fixes the number one cause of project delays clients writing pages at midnight while the developer waits. If writing is the bottleneck, professional website copywriting [→ /content-writing/website-copywriting/] at the start of the project costs less than the weeks of delay it prevents.
Step 9: Build the 301 redirect map
The non-negotiable step. In a spreadsheet: every old URL from your step 2 crawl on the left, its closest equivalent new URL on the right. Every URL gets a destination no exceptions, and no lazy blanket redirect to the homepage, which Google treats as a soft 404. Pages being genuinely retired redirect to the most relevant surviving page. This map is why redesigns done properly keep their rankings and redesigns done casually lose them.
Step 10: Set the technical requirements
Decide before the build: CMS and hosting, a speed budget (LCP under 2.5 seconds on mobile), accessibility target (WCAG 2.1 AA), analytics and tag migration plan, and form or integration requirements. Written technical requirements turn “the new site is slow” from a post-launch argument into a pre-launch specification the build must pass.
Phase 2: During the Build (Steps 11–13)
Step 11: Design mobile-first
Over 60 percent of traffic is mobile for most businesses, so approve mobile designs before desktop versions. Designs reviewed only on large monitors hide the problems most visitors will meet: cramped tap targets, headlines that wrap into six lines, forms that fight the keyboard. Every approval meeting should start with the phone view.
Step 12: Preserve on-page SEO
Carry over the optimized titles, meta descriptions, heading structures, and schema markup from every money page, using the step 2 export as the source of truth. A redesign that rewrites a ranking page’s title tag because the old one “did not fit the new design” is trading rankings for typography. Improvements are welcome; accidental replacement is not.
Step 13: Test on staging before launch
On the staging site, with fresh eyes and a written checklist: every form submits and notifies the right inbox, checkout completes end to end, the redirect map returns 301s (test a sample of at least 30), analytics fire, and Core Web Vitals pass on mobile. Every defect found on staging costs minutes; the same defect found by customers costs revenue and trust.
Phase 3: Launch and After (Steps 14–15)
Step 14: Launch mid-week and verify immediately
Launch Tuesday or Wednesday morning never Friday so the full team is available for the first 48 hours. Within the first hour: submit the new sitemap in Google Search Console, request indexing for your top money pages, re-crawl the live site, and click through the top 20 redirects manually. The goal is to find anything broken before Google and your customers do.
Step 15: Monitor daily for two weeks
Daily for 14 days: the GSC coverage and 404 reports (new 404s mean redirect map gaps fix same day), ranking positions for money-page keywords, and conversion tracking against the step 1 benchmark. Small ranking wobble in week one is normal as Google re-crawls; sustained drops on specific pages point to a missed redirect or replaced metadata, both fixable fast if caught fast.
The Step Everyone Skips (and Regrets)
Step 9, the redirect map is skipped in most self-managed redesigns, and it is the direct cause of the classic post-redesign traffic collapse. Google treats a changed URL without a redirect as a deleted page: the rankings, the backlink authority, the indexed history all evaluate to nothing. If your current site ranks for anything at all, treat the redirect map as a launch blocker with the same status as a broken checkout. Any provider of professional web design services should produce this map as a standard deliverable and show it to you before launch; a redesign proposal that never mentions redirects is telling you, politely, that your rankings are not part of the scope.
When a Redesign Is the Wrong Answer
If the site converts poorly but ranks well, consider a targeted refresh instead: a new design system applied to the existing URLs and content structure. It costs a fraction of a rebuild, ships in weeks, and carries near-zero SEO risk because nothing Google cares about changes address. Full redesigns earn their price when the structure itself is broken wrong pages for the current business, a platform you have outgrown, or an architecture no refresh can save. Knowing which project you actually have is worth a diagnostic conversation before any proposal is signed; the answer changes the budget by thousands. The current web design trends for 2026 can all be adopted incrementally within a refresh, which surprises teams who assume a modern look requires starting over.
The 48-Hour Post-Launch Protocol
A compressed version of the two checks that catch nearly everything, for the two days after launch. Hour one: sitemap submitted, top-20 redirects clicked, one test lead submitted through every form. Day one close: GSC crawl stats reviewed, 404 report empty or being fixed, analytics receiving data. Day two: first ranking spot-check on five money keywords, page speed re-tested on mobile now that real traffic and scripts are live. Teams that run this protocol convert launch week from an anxiety event into a controlled verification and when something does break, they are the ones who found it first.
FAQ
What should I do before redesigning my website?
Benchmark your current traffic and rankings, crawl and record every URL, identify the pages that earn links and conversions, and build a complete 301 redirect map. These four steps protect the SEO value you already own.
Does redesigning a website affect SEO?
Yes, in either direction. With preserved URLs, proper 301 redirects, and carried-over metadata, redesigns often improve rankings. Without them, traffic losses of 30 to 50 percent in the first month are common and largely permanent if uncorrected.
How long does a website redesign take?
Typically 4 to 10 weeks for business websites: one to two weeks of the preparation phase in this checklist, two to six weeks of design and build, and a structured launch. Content readiness is the usual schedule risk.
How often should a website be redesigned?
Every 3 to 5 years for most businesses, or sooner if the site fails on mobile, no longer reflects your services, or its platform blocks changes you need. If it ranks well but converts poorly, consider a refresh before a rebuild.
