A redesign changes how a site looks and works. A migration changes where its pages live. Most redesigns are both, and the migration half is where rankings and leads are lost, so this website redesign SEO checklist spends most of its time there.
This article is part of our web design guides. For how the same mistakes play out on very large sites, see enterprise SEO mistakes, where migrations without a gate are mistake number three.
Why redesigns lose rankings and leads
Search engines rank URLs, not designs. When a redesign changes addresses, drops pages that earned impressions, or launches with a staging block still in place, the signals built over years are cut. Leads are lost more quietly: a form that posts to a decommissioned endpoint, a phone number inside an image, a thank-you page that never loads, and nobody notices until the sales team asks why the inbox is empty.
The fix is a process with a baseline and a gate, so that nothing with value is lost by accident and nothing goes live untested.
Step 1: Record the baseline before the design starts
You cannot protect what you have not measured. Before anyone opens a design tool:
- Export twelve months of Search Console data per URL: clicks, impressions, click-through rate and average position, from the Performance report, by country if you sell in more than one.
- List every URL the site has, from the sitemap and a crawl, and mark each with its traffic.
- List every lead path: each form and where it posts, each phone number and whether it taps, each messaging button, each thank-you page. Test each one and keep the evidence.
- Record current speed against Google's Core Web Vitals thresholds: LCP within 2.5 seconds, INP 200 milliseconds or less, CLS 0.1 or less at the 75th percentile (web.dev, updated 31 October 2024).
- Note the analytics, tag and tracking set-up, so the new site measures the same things.
Step 2: Decide what to keep, improve or retire
Sort every URL by what it earns. Our rule, from our own migration: every URL with clicks or impressions in the last twelve months is a kept URL with a home on the new site, either rewritten at the same address or mapped in one hop to its closest replacement. Nothing with traffic is dropped for lack of time; a page that cannot be rewritten before launch is carried over as it is and improved afterwards. Pages with no traffic and no links can be retired with a clean not-found response. Record the decision for every URL in one sheet.
Step 3: Build the single redirect map
Google's documentation on site moves with URL changes is the standard: map every old URL to its new destination before the move, use server-side permanent redirects (301 or 308), avoid chains (Google advises redirecting straight to the final page and keeping any chain to three hops or fewer), keep the redirects for at least a year, move a very large site in sections, and keep both old and new properties verified in Search Console so you can watch the hand-over.
Keep one map, in one file, with one owner. Every change to the site's structure updates the map, and someone outside the build team checks it before launch, because the people shipping on a deadline are poor judges of their own launch risk.
Step 4: Protect the pages that earn and the words they earn with
For each kept page, keep the topic, the heading ideas and the facts that earn its impressions; a page can be rewritten on its own address without losing what made it rank, and it should not be gutted as a shortcut. Keep internal links pointing at the final addresses, not at redirects. Keep the title intent the same or better. Where a page is improved, note the date facts changed; where only the design changed, the content's date should not move.
Step 5: Test every lead path before launch
On the staging site, at phone width, submit every form and confirm the lead arrives where it should, with the right fields; tap every phone number and messaging button; load every thank-you page. Check that a form still posts if scripts fail to load, that a failed send tells the visitor so, and that the thank-you stays on screen. Test one real path end to end for double sends. Record each result beside the baseline from step 1.
Step 6: Hold the staging gate
Build on a staging address that search engines cannot index, run the checks there (redirect map, lead paths, speed against the thresholds, titles and descriptions, structured data that matches visible text, analytics firing), and fix before launch. The staging block itself is the classic launch mistake: a robots rule or a noindex header meant for staging goes live with the site. Make its removal a named step with a named owner, and check it with a live fetch after launch.
Step 7: Launch with the redirects live
On launch day, in order:
- Turn on the redirects and the new site together, then fetch twenty old URLs and confirm each lands on its final page in one hop.
- Confirm the staging block is gone: fetch the live robots file and a few page headers.
- Submit the new sitemap in Search Console; keep the old property verified.
- Re-run every lead path on the live site at phone width and keep the evidence with the time of the test.
- Check speed on the live site against the thresholds recorded in step 1.
Step 8: Watch every kept page for thirty days
For the first month, watch clicks, impressions and position per kept URL against the baseline and raise any page that loses position the same day, because a redirect typo or a missing page is cheap to fix in week one and expensive in month three. Read trends, not days: Google's starter guide says to wait a few weeks before judging whether a change helped, and that some take months. Keep the redirects in place for at least a year, as Google asks, and longer if old links still bring visitors.
The redesign checklist in one table
The table below is the checklist in summary: what to do at each stage, what to record, and who owns it. Print it and tick it; the stages that are skipped are the ones that lose rankings.
Common redesign mistakes this checklist prevents
The mistakes repeat:
- Dropping pages because they look old. A dated page with impressions is an asset; redesign it, do not delete it.
- Redirect chains and wildcard redirects. Everything to the home page is a redirect in name only; Google asks for one hop to the closest match.
- The staging block going live. Name the removal step and verify it with a live fetch.
- No lead-path test at phone width. The form that worked on a laptop fails on a phone, and nobody checks.
- Changing content dates when only the design changed. A clean-up that changes no facts should not look like new information.
- Judging the redesign in week one. Record, wait a few weeks, then read the trend.
Conclusion
A website redesign keeps its rankings and leads when it is run as a migration with a baseline and a gate: measure first, keep every URL that earns, map the rest in one hop in a single owned redirect map, test every lead path at phone width before and after, stage behind a block that is removed on purpose, launch with the redirects live, and watch kept pages for a month against the numbers you recorded. Google's own site-move guidance is the standard; the checklist is how you follow it under deadline.
PromotEdge International is an international strategy, technology, marketing and design company, and our delivery team is in India. Our web design and SEO teams run redesigns this way, with the baseline and the redirect map before the design. If you are choosing who runs yours, our guide on how to choose a web design company has the ten checks, and how much an ecommerce website costs covers store rebuilds.
Facts we rely on: see our company facts for what we state about ourselves and where each fact comes from.