A website redesign checklist is the ordered set of checks that stops a new site from losing the rankings, traffic and leads the old one earned. The short version: benchmark everything first, map every old URL to a new one with permanent redirects, keep analytics running without a gap, and watch Search Console closely for weeks after launch. Most redesign losses come from skipped steps, not from the new design.
I organize the work in four phases I call Measure, Map, Match, Monitor: measure the old site, map every URL, match what search engines and analytics already rely on, and monitor until the numbers settle. The eight steps below follow that order.
Why do websites lose rankings after a redesign?
Rankings drop when a redesign changes what Google already knows (URLs, internal links, content or structure) without saying where things went.
Google’s site move documentation says a small to medium-sized site “can take a few weeks for most pages to move,” and larger sites take longer. Its guide to changing hosting adds that Googlebot may crawl less right after a switch before it recovers. During that window, every missing redirect costs you.
What should you benchmark before a website redesign?
Benchmark search, conversions and speed for every important page before anyone touches the design.
- Search Console: export the last 3 to 12 months of queries and pages, plus the Page indexing report.
- Analytics: record conversions by landing page, not just total sessions.
- Speed: save field data for your top templates. Google’s Web Vitals guidance defines “good” as an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less, at the 75th percentile.
How do you build a content inventory for a redesign?
Crawl the live site, list every URL that returns a page, then decide each one’s fate: keep, merge, rewrite or retire.
Pull URLs from a crawler, your XML sitemap and the Search Console pages export. Add columns for clicks, conversions and backlinks. Pages that earn traffic or links keep their substance. Google’s migration guide calls it “important to map your old site’s URLs to the URLs for the new site,” and this is where it starts.
How do you set up 301 redirects in a website redesign?
Redirect every changed URL to its closest new equivalent with a permanent, server-side redirect in one hop, then leave it in place for at least a year.
Google’s redirects documentation recommends “a permanent server-side redirect whenever possible,” because a permanent redirect tells Google the target should be canonical. Here is how the common types compare:
| Redirect type | How Google reads it | Use it when |
|---|---|---|
| 301 or 308 (server-side) | Permanent; the target becomes canonical | A page has moved for good |
| 302 or 307 (server-side) | Temporary; the old URL can stay in results | A short-term change you will undo |
| Instant meta refresh | Treated as permanent | Your platform can’t do server redirects |
| JavaScript redirect | Last resort; Google may never see it | Nothing else is possible |
Google’s John Mueller kept it simple in a January 2024 Search Engine Journal report: “Ideally, you’d redirect the old website to the new one.” Send retired pages with no real equivalent to a 404 or 410, not the homepage. I cover the mechanics in my WordPress to Next.js migration playbook.
How do you keep analytics working through a redesign?
Install the same analytics property, conversion events and Search Console verification on the new site before launch, so the data never has a gap.
Google’s hosting change guide says to make sure your Search Console verification file, meta tag or Google Analytics setup carries over to the new site. Check that every form, phone click and booking fires the same event name, because renamed events break year-over-year reports, and annotate the launch date. Tracking setup is part of my marketing and analytics service.
What accessibility checks belong on a website redesign checklist?
Check color contrast, image alt text, form labels, link and button names, keyboard navigation and page language before launch. A redesign is the cheapest moment to fix them.
The WebAIM Million 2026 report found detectable WCAG 2 failures on 95.9% of the top million home pages, averaging 56.1 errors per page. The most common were:
- Low contrast text: 83.9% of home pages
- Missing image alt text: 53.1%
- Missing form input labels: 51%
- Empty links: 46.3%
- Empty buttons: 30.6%
Design to WCAG 2.2, the current W3C Recommendation (latest version dated December 2024). This is education, not legal advice. If you’re worried about legal exposure, talk to a lawyer.
What speed budget should a redesigned site meet?
Set the budget before design starts: every key template should pass all three Core Web Vitals on mobile.
Most sites miss. In the HTTP Archive Core Web Vitals technology report, only 52.8% of mobile origins passed all three Core Web Vitals in September 2026. A practical budget caps image weight, limits third-party scripts, self-hosts fonts and reserves space for every image so nothing shifts. If the platform is also on the table, my comparison of Next.js and WordPress shows how each performs in field data.
What should you test on launch day?
On launch day, confirm the new site can be crawled and indexed, every redirect resolves in one hop and every conversion path works.
- Remove staging blocks. Google’s hosting guide says to remove any temporary robots.txt disallow rules or noindex tags before the switch.
- Run the old URL list through a crawler and confirm each returns a single 301 to the right page.
- Submit the new XML sitemap in Search Console.
- Test every form and phone link on a real phone.
- Confirm the admin login is protected. My WordPress security checklist covers this for WordPress sites.
How long should you monitor a site after a redesign?
Watch closely for the first four to six weeks, then monthly for a year while the redirects stay live.
Each week, compare indexed pages, clicks by page, conversions and Core Web Vitals against your benchmark, and check the Page indexing report for new 404s. Google’s site move guide says to keep redirects “generally at least 1 year.” A dip in week one is normal; one still growing in week four means it’s time to audit, as does a fall in AI answer visibility, covered in how to rank in AI Overviews.
How I run website redesigns without losing rankings
I treat the website redesign checklist as part of the build, not an afterthought. I’ve delivered more than 350 projects and spent 8+ years leading teams. My published results include a 136% peak organic-traffic lift and 99.9% uptime maintained, and you can see the work in my SEO portfolio and case studies.
Through my web design and development service, I build on Next.js, Supabase and Vercel with a custom CMS, and I also work on WordPress sites. After launch, ongoing web care keeps the site healthy (see my guide to website maintenance cost). I’m based in Jacksonville, FL and work across the US, including web design in St. Augustine.
Frequently asked questions
How long does it take to recover rankings after a website redesign?
If the URLs, content and internal links carry over cleanly, many sites see little lasting change. When URLs change, Google says most pages on a small to medium-sized site move within a few weeks, and larger sites take longer. A drop that keeps growing after a month usually points to a real problem, such as missing redirects, noindex tags left over from staging, or content that was cut. Compare page by page against your pre-launch benchmark to find exactly which pages lost ground.
Do I need to change my URLs during a website redesign?
No. If your current URLs are clean and descriptive, keeping them exactly as they are is the safest option. Change URLs only when there is a real benefit, such as fixing messy parameter URLs, merging duplicate pages, or moving to a clearer structure. If you do change them, map every old address to its closest new one and use permanent server-side redirects. Never send old pages to the homepage as a shortcut, because that tends to throw away their value.
Should I redesign and change domains at the same time?
Avoid it if you can. When you change the design, the URLs and the domain in one launch, you can’t tell which change caused a drop in traffic, and that makes it much harder to fix. A safer order is to move the domain first with a one-to-one URL mapping, let it settle, then redesign. If business reasons force both at once, keep detailed records of every change, benchmark carefully beforehand, and set expectations with your team that results may swing for a while.
What is the most common website redesign mistake?
Launching without a complete URL map. Teams often redirect the main pages and forget blog posts, old landing pages, PDFs and image URLs that still earn links and traffic. The second most common mistake is leaving a staging block in place, such as a robots.txt disallow rule or a noindex tag, which can quietly remove the new site from search. Both are easy to catch with a crawler and a launch-day checklist, and both are far cheaper to prevent than to recover from.
Start your redesign with the checklist, not the mockups
Run the website redesign checklist from benchmark to monitoring and the new design gets to keep what the old one earned. If you’re planning a redesign, get in touch or read more about my website design and development work.