Website Redesign SEO Checklist: Don’t Lose Your Rankings During a Rebuild

Updated August 2026 • 15 min read

The single biggest cause of ranking loss after a website redesign is missing or broken 301 redirects — old URLs that used to rank simply disappear, and Google has to figure out where the content went with no signal telling it. Before you launch a new site, build a full URL redirect map from every old page to its new equivalent, keep the copy and headings on your highest-traffic pages substantially intact, and treat the redesign as a migration project with an SEO checklist attached to it, not a design project that happens to touch the same domain.

Home service businesses redesign their sites more often than most industries — a new logo, a competitor’s site that looked better, a web designer who pitched a “modern refresh.” The problem is that rankings built over months or years live on specific URLs, specific headings, and specific internal linking patterns, and a redesign frequently changes all three at once without anyone checking what was there before.

Why Redesigns Tank Rankings

It’s rarely one catastrophic mistake — it’s usually a handful of smaller ones stacking up:

• Missing or wrong redirects. By far the most common cause of lost traffic after a redesign. If /plumbing-services becomes /services/plumbing with no 301 redirect connecting them, Google treats the old URL as gone and has to discover and re-rank the new one from scratch.
• Thinned-out content. A designer cuts a 1,200-word service page down to 300 words of punchy marketing copy because it “reads better” — and removes most of the text that was actually ranking the page.
• Changed headings and page structure. An H1 that used to say “Emergency Plumber in [City]” becomes a generic tagline; H2s that matched real search queries get replaced with vague marketing headers.
• Broken internal links. Old pages linked to each other in a structure that told Google which pages mattered most. A new site built without mapping the old link structure often loses that signal entirely.
• New platform quietly breaking schema or page speed. A migration from one CMS or framework to another can silently drop structured data markup or add enough page weight to hurt Core Web Vitals, even when the visual design looks like an upgrade.

Before Launch: The Pre-Redesign SEO Audit

Do this before a single new page goes live, not after you notice traffic dropping:

1. Export every indexed URL on the current site (Search Console’s coverage report or a crawl tool both work) along with its organic traffic and ranking keywords over the last 6–12 months.
2. Identify your top 20–50 pages by traffic — these are the pages that need the most protection during the rebuild.
3. Save a copy of the existing copy, headings, and meta tags for those top pages before anyone starts “refreshing” them.
4. Map every old URL to its new equivalent, even for pages being consolidated or removed — a redirect target should always exist, even if it points to a broader category page rather than a 1:1 match.
5. Note existing backlinks to your top pages (a backlink checker or Search Console’s links report) — those pages carry authority that a broken redirect would waste.

Protecting Your Highest-Traffic Pages

The pages already generating calls and rankings deserve the least amount of change, not the most. For your top 20–50 pages by traffic:

• Keep the URL the same if at all possible. A redesign doesn’t require a new URL structure — you can put a new visual design on an old, proven URL.
• Keep the H1 and core body copy substantially intact. Rewrite for tone and clarity if needed, but don’t delete the paragraphs and headings that match real search queries just because they’re not the newest writing on the site.
• Preserve internal links pointing to and from the page. If a page that used to link to your top service page no longer exists, make sure its replacement still links there.
• Carry over existing schema markup (Article, LocalBusiness, FAQPage, whatever the page had) — new platforms sometimes drop this by default unless someone rebuilds it deliberately.

See our website must-haves guide for the baseline elements every page should keep regardless of how the design changes.

301 Redirect Mapping, Done Right

A 301 redirect tells Google (and visitors) that a page has permanently moved, and passes along most of the ranking value from the old URL to the new one. Getting this right is mechanical but unforgiving of shortcuts:

• 1:1 mapping wherever possible. Every old URL should redirect to the single most relevant new URL — not a blanket redirect of every old page to the new homepage, which wastes almost all the accumulated authority.
• No redirect chains. If page A redirects to B, which redirects to C, fix it so A redirects straight to C. Chains slow crawling and can lose value at each hop.
• Test every redirect after launch, not just a sample — a spreadsheet of a few hundred old URLs is tedious to check by hand, but a crawl tool can verify the whole list returns the right status code in minutes.
• Keep the redirect map live indefinitely, not just for a few weeks. Backlinks and bookmarks pointing to old URLs can surface years later, and a dead redirect at that point still costs you the referral traffic and link value.

The First 30 Days After Launch

Even a well-planned redesign causes a temporary dip while Google re-crawls and re-evaluates the new site — that’s normal. What’s not normal, and worth investigating immediately:

• A traffic drop of 50% or more in the first two weeks, rather than a gradual dip and recovery.
• Traffic that hasn’t started recovering at all a month post-launch — a modest dip that flattens is expected; one that keeps falling usually means an ongoing technical issue, not a normal re-indexing curve.
• A sudden spike in 404 errors in Search Console’s Page Indexing report — almost always a sign redirects are missing for URLs Google or visitors are still trying to reach.
• Specific high-value pages disappearing from rankings for their core term while overall traffic looks fine — check that page individually for a heading, content, or redirect problem rather than assuming it’s a site-wide issue.

Submit the new sitemap in Search Console immediately after launch, and manually request indexing on your top pages rather than waiting for Google to discover the changes on its own schedule.

When a Full Redesign Isn’t Worth the Risk

Not every site that “looks dated” needs a ground-up rebuild. If your current site is ranking well and generating calls, and the actual complaint is that it looks outdated, a visual refresh on the existing URLs and content structure — new design applied to the same pages, same headings, same content — captures almost all of the upside with a fraction of the SEO risk of a full platform migration.

Reserve a full rebuild for cases where the current site has a real structural problem a visual refresh can’t fix: it’s on a platform that can’t support the content types you need, mobile performance is fundamentally broken, or you’re consolidating multiple location sites into one. In those cases, the migration risk is worth it — but go in treating it as a migration, with the checklist above, not as a design refresh that happens to change every URL on the site.

Frequently Asked Questions