Website redesign without losing SEO: full checklist

The pattern repeats: a business launches its new website, the team celebrates, and three weeks later someone asks why the leads stopped. They open Search Console and organic traffic dropped in half. The redesign looked better, but it erased years of rankings in a single deploy. The good news: a website redesign planned with SEO in mind doesn't have to lose anything. The condition is treating SEO as a project requirement, not a last-minute review.

Why a redesign can kill your traffic

Google doesn't rank "your site" as a whole: it ranks specific URLs, each carrying its own history of accumulated signals. A typical redesign breaks that in several ways at once:

• URLs change. /services/implants now lives at /treatments/dental-implants and nobody set up the redirect. To Google, the old page died and the new one starts from zero.
• Ranking content gets deleted. That "ugly" page nobody on the team liked is usually the exact one bringing in traffic.
• Rendering changes. Migrating to a SPA without pre-rendering turns indexable content into JavaScript that search engines process poorly and LLMs don't process at all.
• The basics get lost. Titles, descriptions, headings, and structured data someone tuned for years get replaced by generic template text.

None of this shows in the demo. All of it shows in Search Console a month later.

What Google documents about migrations

No guessing required: Google maintains an official guide for site moves with URL changes. Three points from that documentation that prevent most of the disasters that land on our desk:

• Server-side permanent redirects (301 or 308) from every old URL to its new equivalent. Redirecting everything to the homepage doesn't count: Google treats that as a soft 404.
• Keep redirects in place for at least 1 year. That's how long Google recommends so all signals transfer, including external links still pointing at the old URLs.
• Avoid redirect chains. When unavoidable, the guide asks for fewer than 3 hops: every extra hop degrades crawling.

If your redesign vendor can't explain how they'll cover these three points, that's the moment to pause the project, not launch week.

The pre-launch checklist

This is what we execute on every redesign, in order:

1. Full URL inventory. Export every indexed URL from Search Console and the current sitemap. That list is your treasure map: everything you could lose is on it.
2. Identify what ranks today. Flag the pages with clicks and impressions over the last 12 months. Those get preserved or redirected with surgical care, never deleted "because they don't fit the new brand".
3. A 1-to-1 redirect map. Every old URL points to its closest new equivalent. Tested before launch, not after.
4. Migrate the metadata. Titles, descriptions, headings, and schema from the pages that work travel to the new site. A redesign doesn't force you to rewrite what already ranks.
5. Verify rendering. The content must exist in the HTML the server returns, via SSR or SSG. We cover this in depth in what an SEO audit includes.
6. Protect performance. A redesign is the chance to improve your Core Web Vitals, not to sink them with heavy animations.
7. Check robots.txt and the sitemap. Classic mistake: launching with the staging noindex still active. Confirm the new sitemap is submitted in Search Console.
8. Measure before and after. Save a snapshot of rankings and traffic before launch. Without a baseline you can't tell a temporary dip from a hemorrhage.

The mistakes that cost the most

Three classics we see over and over: launching on a Friday with nobody monitoring through the weekend, taking the blog down "temporarily" during the migration, and trusting that the CMS "handles redirects automatically". No platform redirects a structural change for you: someone has to build the map.

There's also the normal dip: even in well-executed migrations, Google takes weeks to reprocess the site and positions can fluctuate. The difference between that dip and a real drop is that the dip recovers on its own and the drop doesn't. That's why the baseline in step 8 is not optional.

Redesign without betting the traffic

A well-executed redesign usually ends with more traffic, not less: better performance, better architecture, and preserved content stack on top of the authority you already had. That's how we approach web development in Mexico: the SEO migration is part of the scope from the quote onward, with inventory, redirect map, and measurement included. What took you years to rank shouldn't die in a deploy.