Website Redesign Checklist: What Not to Break When You Switch

Every year we see the same pattern: a service business has spent two or three years building up organic rankings, decides its website looks dated, hires a designer or agency to rebuild it, and watches traffic drop 30-plus percent in the weeks after launch. Not because the new design is bad — often it's a real improvement — but because the redesign was treated as a purely visual project, and nobody mapped what would happen to the SEO equity built into the old site's URLs, content, and structure.

None of this is exotic. It's a checklist problem. The businesses that come through a redesign without losing ground are the ones that treat SEO continuity as a project requirement from day one, not a cleanup task after launch.

The specific ways a redesign can quietly damage SEO

Changing URLs without 301 redirects

This is the single most damaging and most common mistake. Every page on your current site that ranks for anything, has any backlinks, or gets any organic traffic has a URL that search engines and other websites have indexed and linked to. If your new site changes those URLs — a new CMS, a new folder structure, a simplified navigation — without a 301 redirect from every old URL to its corresponding new one, you're telling Google that page no longer exists. The ranking history built into that URL doesn't transfer automatically; it has to be explicitly carried over with a redirect.

Deleting pages that have existing backlinks or rankings

Redesigns often come with a content cleanup — cutting pages that seem outdated or unnecessary. Before cutting anything, check whether that page has backlinks pointing to it or organic traffic flowing to it. A page that looks unimportant internally can be quietly carrying real authority from an external link nobody remembers exists. If a page genuinely needs to go, redirect it to the closest relevant replacement rather than letting it 404.

Losing structured data

If your current site has LocalBusiness, Service, Review, or FAQPage schema markup, it's easy for that to get dropped entirely when a site is rebuilt from scratch on a new platform or template, because it's invisible in a visual mockup — nobody notices it's missing until rich results disappear from search. See our structured data guide for what should be preserved and re-implemented on the new site, not just copied as an afterthought.

Breaking internal linking structure

A well-built site links between related service and location pages in a way that helps both users and search engines understand what's important and how pages relate. A redesign that reorganizes navigation without preserving those internal links can leave pages orphaned — technically live, but no longer linked to from anywhere else on the site, which search engines treat as a signal of lower importance. Our website structure guide covers what a sound internal linking structure looks like — worth checking the new site against it before launch, not after.

Losing Google Analytics and Search Console continuity

If a redesign involves a domain change, a subdomain change, or a full platform migration, it's easy to accidentally sever the connection to your existing Google Analytics property and Search Console profile — or to stand up a fresh one without realizing the historical data doesn't carry over automatically. Losing that continuity doesn't hurt rankings directly, but it makes it much harder to diagnose what changed if something does go wrong, since you lose the before/after comparison.

The pre-launch checklist

Everything below should happen before the new site goes live, not after.

1. Build a complete redirect map. Export every indexed URL from your current site (Search Console's coverage report and a crawl of the live site both help catch everything), and map each one to its corresponding URL on the new site with a 301 redirect. Every single indexed URL — not just the obvious top pages.
2. Audit which old pages have backlinks or organic traffic before deciding what gets cut or consolidated, so nothing with real equity gets deleted by accident.
3. Re-implement structured data on the new templates — LocalBusiness, Service, Review, FAQPage, breadcrumb schema — matching what the old site had, at minimum.
4. Rebuild the internal linking structure deliberately, so service and location pages still link to each other in a logical way rather than relying only on top-level navigation.
5. Test everything on a staging environment first, with that staging environment blocked from search engine indexing (a noindex tag or password protection — not just hoping nobody finds it), so nothing gets crawled and indexed prematurely in an unfinished state.
6. Generate and submit a fresh XML sitemap reflecting the new site's actual URLs, submitted through Search Console immediately at launch so Google discovers the new structure as fast as possible.
7. Verify Google Analytics and Search Console are correctly connected to the new site before launch, and confirm historical data is still accessible from the same property if the domain hasn't changed.
8. Check page speed on the new site before launch, not after — redesigns that add heavier images, animations, or third-party scripts can quietly undo the good page speed the old site had.

After launch: monitor, don't assume

The redesign isn't done at launch — the first two to four weeks after are when problems surface, and catching them early is the difference between a minor fix and a lasting ranking hit.

• Monitor 404 errors daily for the first one to two weeks through Search Console's coverage reports and server logs if you have access to them — a spike in 404s almost always means a gap in the redirect map.
• Watch organic traffic and keyword rankings in Search Console for unexpected drops on specific pages, which usually points to a specific missed redirect or a structural change rather than a site-wide issue.
• Spot-check that structured data is actually rendering correctly using Google's Rich Results testing tools, since schema markup can be present in the code but broken in a way that's invisible without testing it.
• Re-crawl the live site after launch and confirm redirects are resolving to the correct final URL, not chaining through multiple redirects or landing on a generic homepage instead of the intended page.

Treat this as one project, not two

The underlying issue behind almost every redesign horror story is the same: SEO gets treated as a post-launch cleanup task instead of a design and development requirement from the start. A redesign brief that includes "preserve rankings and organic traffic" as an explicit, named requirement — with a redirect map and monitoring plan as deliverables, not afterthoughts — is the difference between a redesign that improves your site and one that sets it back six months.