Article
Website Redesign Checklist: How to Rebuild Your Site Without Losing Rankings
A website redesign checklist covering the audit, migration, and launch steps that keep your new site ranking, not just looking better.
By Ranmi Sandalika · August 30, 2026
A website redesign checklist has one job: stop you from launching a site that looks better and ranks worse. Most redesigns lose 20 to 40% of their organic traffic in the first three months. Almost none of that loss is unavoidable. It happens because URLs change, redirects get skipped, and nobody benchmarks the old site before anyone tears it down.
Why most website redesigns tank rankings
Google has already indexed and trusted your current pages. A redesign resets that trust the moment your URL structure or internal links change without a mapping plan behind them. The team building the new site is usually optimizing for how it looks in a browser. They're not thinking about the 200 backlinks pointing at pages that are about to disappear.
The pattern repeats across almost every redesign we've audited after the fact. Someone flattens the site architecture to "clean it up." Three-level category pages become one flat list, and every internal link built up over two years now points at a 404. Traffic dips and someone panics. By the time SEO gets called in, the damage is six weeks old and half-indexed by Google as broken.
The pre-redesign audit before anyone touches a template
Do this before a single wireframe gets approved. Skipping it is the single most common reason a website redesign checklist fails to protect rankings.
Pull twelve months of Search Console data. Export every page with impressions, clicks, and average position. This is your baseline, and you'll need it in month two to prove the redesign didn't hurt anything.
Rank every URL by organic traffic. The top 20% of pages usually carry 80% of the value, so those get manual redirect mapping. Nothing on that list gets deleted or merged without a plan.
Screenshot and archive the current sitemap.xml and robots.txt. Redesigns break both more often than anyone expects, usually because the new CMS generates them differently by default.
Back up the full CMS database and media library, not just the front-end files. If the redesign goes sideways in week three, you want a working rollback, not a scramble.
If you'd rather hand this whole process to a team that's mapped a hundred of these, that's exactly what our website development service is built around. Migrations that don't cost you the rankings you already earned.
The website redesign checklist: 14 steps that matter
Before you migrate anything
Map every existing URL to its new destination, one row per URL, in a spreadsheet the whole team can see. No exceptions for "small" pages.
Write 301 redirects for the full list, not just the top pages. A redesign with 40 orphaned old URLs looks fine at launch and bleeds traffic for months.
Preserve your existing page titles and H1s where the topic hasn't changed. A cosmetic redesign is not a reason to rewrite copy that's already ranking well.
Flag any page merges or deletions to the SEO lead before dev starts building. That way redirect logic gets built in from day one, not patched afterward.
Set up a staging environment with noindex tags so Google never crawls two versions of the same content mid-build.
During the rebuild
Keep your internal linking structure intact, or improve it deliberately. Don't let a template swap flatten three years of link equity by accident.
Test page speed on the new build before launch, not after. A redesign that adds 2 seconds to load time will cost you more in rankings than the visual refresh gains you in conversions.
Carry over schema markup for every page type that had it. Product schema, FAQ schema, review schema. If the old site had it and the new build drops it, you lose rich results the day you launch.
Check mobile rendering on at least five real devices, not just a browser's responsive view, because Google indexes the mobile version first.
Confirm forms, chat widgets, and tracking pixels fire correctly on staging. A redesign that quietly breaks your lead capture is worse than one that hurts rankings. You won't notice for weeks.
At launch
Push the redirect map live at the same moment the new site goes public, not a day later. A gap between launch and redirects is when the worst traffic loss happens.
Submit the new sitemap to Search Console within the hour, then request indexing on your top 20 pages manually.
Monitor crawl errors daily for the first two weeks. Set an alert. This is the window where broken redirects surface.
Compare rankings and traffic against your baseline at day 7, day 30, and day 90. A redesign isn't finished at launch. It's finished when the data confirms nothing was lost.
The website redesign SEO steps most checklists miss
Redirects and sitemaps get remembered. Canonical tags and structured data usually don't, and both quietly decide how much of your old authority survives the move.
Check that every page's canonical tag points to itself on the new domain structure, not a staging URL left in the template. Confirm your XML sitemap only lists live, indexable URLs. A sitemap full of redirects or 404s tells Google your site isn't well maintained.
If your old site ranked for featured snippets or "People Also Ask" results, check the HTML structure behind them. Usually that's a table, a numbered list, or a direct-answer paragraph, and it needs to survive into the new template. A visual refresh that drops the table your pricing page used to rank in loses that snippet on day one.
Making the new site visible to AI search, not just Google
A redesign is the moment to fix this, since you're already rebuilding templates anyway. AI answer engines like ChatGPT, Perplexity, and Google's AI Overviews pull from pages that answer a question directly under a heading. They skip past pages that bury the answer in paragraph four.
Build that structure into the new templates now:
A direct-answer paragraph under every major H2, 40 to 60 words, before any supporting detail.
FAQ schema on pages where customers actually ask questions, not bolted onto every page as a formality.
Clear author and organization markup, since AI engines weight source credibility more than traditional search does.
This is the same groundwork covered in our AEO and generative engine optimisation work. It's far cheaper to build in during a redesign than to retrofit six months later. For the deeper mechanics of how AI engines pick sources, we've covered that in how to rank in ChatGPT search.
How long a website redesign takes and what it costs
A realistic website redesign timeline runs 8 to 16 weeks for a standard business site. That breaks down to roughly 2 weeks for audit and planning, 4 to 8 for design and build, 2 to 4 for QA and redirect mapping, and 1 to 2 for launch and monitoring. Ecommerce sites with large product catalogs run longer, mostly because redirect mapping scales with SKU count.
Cost tracks the same variables as timeline: page count, custom functionality, and how much old content needs rewriting rather than migrating as-is. We broke down the actual pricing ranges, and what drives a quote up or down, in how much does a website cost.
Your pre-launch website checklist: the final 72 hours
This is the last pass before the new site goes live, and it's the stage most teams rush.
Re-crawl the staging site with a tool like Screaming Frog. Check for broken internal links, missing meta descriptions, and duplicate title tags.
Confirm noindex tags are removed from staging and that the live site is set to allow indexing, since this single checkbox has taken down more redesigns than any redirect mistake.
Verify Google Analytics and Search Console tracking codes are on the live domain, not the staging one.
Test the checkout or lead form end to end. Use a real transaction or submission, not just a validation check.
Have the redirect map ready to push the second DNS propagates. Don't wait until Monday morning.
Where to start
If you're three weeks from a redesign launch and none of this has happened yet, start with the audit. Pull your Search Console data and rank your top pages by traffic today. Everything else on this website redesign checklist builds on that baseline.
Teams that skip it are the ones we hear from after traffic drops 30%, unable to say which pages used to rank. If you'd rather not run this internally, AiM Growth handles redesign audits and migrations end to end, from redirect mapping through post-launch monitoring.
Frequently asked questions
How much organic traffic do you actually lose during a website redesign?
Traffic loss ranges from near-zero to 40%, and the difference almost always comes down to redirect mapping. Sites that map every URL and push redirects live at launch typically recover within 30 to 60 days. Sites that skip mapping can take six months or longer to recover, if they recover at all.
Should you redesign and change your URL structure at the same time?
Only if there's a real reason, like consolidating duplicate content or fixing crawlability problems. Changing URLs adds risk on top of the redesign itself. If the current structure isn't broken, keep it and save the URL overhaul for a separate project.
Do you need to redo your content during a redesign, or just the design?
Keep ranking content as-is unless it's genuinely outdated. Rewriting copy purely because it's in scope, when it's already ranking well, is one of the most common ways teams lose rankings they didn't need to touch.
How soon after launch will you know if the redesign hurt your SEO?
Crawl errors and indexing issues usually show up within 48 hours in Search Console. Ranking and traffic impact takes longer to read clearly, generally 2 to 4 weeks. Google needs that time to recrawl and re-evaluate the new URLs against your redirect map.
