Redesign without losing SEO: a migration checklist

You can redesign your website without losing SEO if you preserve your URLs, 301-redirect anything that changes, carry over the content and metadata that already ranks, and verify everything on staging before launch. Most ranking drops after a redesign come from skipped migration steps — not from the new design itself — so the fix is a disciplined, documented process.

Key takeaways

• Record a full baseline — URLs, rankings, traffic and backlinks — before you change anything.
• Keep high-value URLs identical; where they must change, map a 301 redirect from every old URL to its closest new match.
• Migrate the content and on-page SEO that ranks rather than replacing it with thinner copy.
• Test redirects, mobile, speed and forms on a staging site before going live.
• After launch, submit the new sitemap, watch Search Console, and monitor rankings for four to eight weeks.
• Plan the migration as a defined project with an owner — not an afterthought once the design is approved.

Why redesigns lose rankings (and why it is avoidable)

A redesign rarely hurts SEO because Google dislikes the new look. It hurts SEO because the move quietly breaks the signals search engines already trust: stable URLs, indexable pages, the words on the page, internal links and the backlinks pointing in. When those signals snap, rankings follow. The good news is that every one of these failures is preventable with a checklist and a little discipline.

The most common culprits are deceptively boring. A developer rebuilds the site on a fresh URL structure and forgets to redirect the old pages. The copywriter "cleans up" the homepage and deletes 600 words of text that happened to be ranking for dozens of long-tail queries. A staging site gets indexed by accident. A `noindex` tag left over from development ships to production. None of these are design problems — they are process problems, and a process is exactly what protects you.

For Canadian small businesses this matters more than for a big brand. You probably do not have the domain authority to recover quickly from a bad migration, and a quiet 30% drop in organic traffic can take months to claw back. That is real revenue. Treating the migration as a first-class part of the project — with the same care you give the visual design — is what separates a redesign that grows traffic from one that sets it back a year.

Step 1: Audit and baseline what you have

You cannot protect what you have not measured. Before anyone touches a design file, capture a complete snapshot of the current site so you have something to compare against after launch. This baseline is your insurance policy and your early-warning system.

What to record

• A full crawl of every live URL (Screaming Frog, Sitebulb or a similar tool exports this in minutes).
• Your top organic landing pages and the keywords they rank for, pulled from Google Search Console.
• Current organic traffic and conversions by page, from Google Analytics 4.
• Existing titles, meta descriptions and H1s for at least your top 50 pages.
• Your backlink profile — which external sites link to which pages.
• Current Core Web Vitals scores so you can confirm the new site is faster, not slower.

Sort that crawl by traffic and links so the pages that earn the most attention rise to the top. These are the pages you protect at all costs. If you are still setting up measurement, our guide to analytics for small business and the SEO basics for Canadian businesses will get you a usable baseline before the build begins.

Step 2: Map your URLs old to new

The single biggest source of lost rankings is a URL that changed without a redirect. Search engines treat /services/web-design and /web-design as two entirely different pages. If the old one disappears and nothing points users or crawlers to the new one, the authority it earned evaporates.

The simplest rule: keep URLs identical

If a page is ranking and you do not have a compelling reason to move it, leave the URL exactly as it is. The cleanest migration is one where 80% of your URLs do not change at all. Restructure only where the old structure is genuinely confusing or duplicated.

Build a redirect map

For every URL that does change, create a spreadsheet with two columns: the old URL and the single closest new URL. Work through the entire crawl from Step 1 so nothing is missed. A few rules keep this clean:

1. Map each old URL to the most relevant new page — never default everything to the homepage.
2. Use permanent 301 redirects, not temporary 302s, so authority transfers fully.
3. Avoid redirect chains (old → interim → final). Point each old URL straight to its final destination.
4. Redirect retired pages to the closest surviving topic rather than letting them 404.
5. Preserve the trailing-slash and HTTP/HTTPS conventions you already use to avoid accidental duplicates.

If you are also changing platforms during the redesign — say moving from a builder to a custom build, or between custom code and WordPress — the redirect map becomes even more important, because platform changes almost always alter URL patterns.

Step 3: Preserve content and on-page SEO

A prettier site with thinner content frequently ranks worse than the dated site it replaced. Designers love whitespace and short copy; search engines reward pages that thoroughly answer a query. Both can be true at once if you migrate the substance and restyle the presentation.

Carry over what already works

• Keep the page titles and meta descriptions that earn clicks — refine them, do not wipe them.
• Preserve your H1 and heading structure so topical relevance stays intact.
• Migrate body copy on ranking pages in full; trim only genuine filler.
• Keep image alt text and descriptive file names.
• Maintain internal links between related pages so link equity keeps flowing.
• Re-implement any structured data (schema) the old site had.

This is the moment to improve, not just preserve. If your old content was right but reads like it was written for a search engine, rewrite it to copy that actually sells while keeping the keywords and depth. A redesign is also a natural point to strengthen weak pages — just expand them, never gut them. If you are unsure what content you even have, our checklist on preparing content before a website project helps you inventory it first.

Step 4: Protect speed, mobile and accessibility

A redesign should make the site faster and more usable — and if it does not, that itself can cost rankings. Google measures real-world loading and interaction, so a heavier, image-stuffed redesign can quietly undo months of progress.

Set a performance budget before the build and hold the new site to it. Confirm the redesign passes Core Web Vitals, that it is genuinely mobile-first rather than merely "responsive," and that it meets WCAG accessibility standards. These are ranking and conversion factors, not nice-to-haves. If your redesign also leans on motion, our note on scroll animations that convert shows how to add polish without bloating the page.

Step 5: Test everything on staging

Never validate a migration in production. Build and check the new site on a password-protected or noindex-blocked staging environment so Google never crawls it before launch. Then run a pre-launch checklist.

Pre-launch checklist

• Every redirect in your map resolves to the correct final URL (test a sample plus all top pages).
• No noindex tags or Disallow: / robots rules are left over from development.
• The new XML sitemap is generated and lists only canonical, indexable URLs.
• Titles, meta descriptions and H1s match the migration plan.
• Contact forms, booking flows and any e-commerce checkout submit correctly.
• The site renders and converts on a real phone, not just a resized browser.
• Page speed and Core Web Vitals meet your budget.
• Analytics and conversion tracking fire on the new pages.
• Canonical tags point to the right URLs and there are no accidental duplicates.

If you run a store, add the e-commerce specifics from our conversion optimization checklist to this list before you flip the switch.

Step 6: Launch and monitor

Pick a low-traffic window to go live so any issues affect the fewest visitors. Once the new site is live, the work shifts from building to watching.

The first 48 hours

1. Remove the staging block and confirm the live site is crawlable.
2. Submit the new XML sitemap in Google Search Console (and Bing Webmaster Tools).
3. Spot-check your top old URLs to confirm each 301-redirects correctly.
4. Use the URL Inspection tool to request indexing of your most important pages.
5. Confirm analytics and goal tracking are recording sessions and conversions.

The first eight weeks

Watch the Search Console Coverage and Page Indexing reports for new errors, a spike in 404s, or pages dropping out of the index. Some ranking fluctuation in the first two to three weeks is completely normal as Google re-crawls and re-evaluates — do not panic and start changing things at the first wobble. What you are looking for is a sustained, broad decline, which usually traces back to a missed redirect, a blocked page or deleted content. Catch it early and most damage is reversible.

This is also the moment to confirm the redesign actually fixed the problems that justified it and that the new site is doing its real job — turning visitors into enquiries. Pair your SEO monitoring with the tactics in how to get more leads from your website.

Common redesign SEO mistakes to avoid

Most botched migrations repeat the same handful of errors. Keep this list visible during the project:

• No redirect map. URLs change and old pages 404 — the classic ranking killer.
• Redirecting everything to the homepage. Google often treats these as soft 404s and drops the equity anyway.
• Deleting ranking content. "Cleaner" copy that strips out the words that earned traffic.
• Leftover noindex or robots blocks. The whole site silently falls out of the index.
• Indexed staging site. Duplicate content competing with the real site.
• Slower new site. A heavier design that fails Core Web Vitals.
• No baseline. Without before-data, you cannot tell whether you lost anything or what.

How SK Designz handles redesign migrations

When a Canadian business comes to us for a redesign, the SEO migration is built into the project from day one, not bolted on at the end. We start by crawling and baselining the existing site, we keep URLs stable wherever possible, and we hand-build a redirect map for everything that changes. We migrate ranking content deliberately, hold the new build to a speed and accessibility standard, and validate the entire thing on staging before launch.

After go-live we submit sitemaps, request indexing and monitor Search Console so any issue is caught in days, not months. That process is part of every custom build we deliver — you can see the scope on our services page and how it is priced on our pricing page. If a redesign is on your roadmap, the safest path is to plan the migration before the first mockup is approved.

Frequently asked questions

Will I lose rankings in a redesign?

Not if you migrate carefully. Most losses come from missing 301 redirects, deleted content or leftover noindex tags — all avoidable. Baseline the site first, keep URLs stable where you can, preserve ranking content, and test on staging. Done properly, a redesign holds or improves your rankings rather than hurting them.

Should I keep my old URLs?

Where possible, yes. Stable URLs are the cleanest way to keep the authority a page has earned. Change a URL only when there is a real reason, and when you do, set a permanent 301 redirect from the old address to its closest new match. Aim to keep most of your URLs unchanged.

How long until rankings settle after launch?

Usually four to eight weeks. Some fluctuation in the first two to three weeks is normal as Google re-crawls and re-evaluates the new site. Watch for a sustained, broad decline rather than reacting to daily wobbles, and fix any redirect or indexing issues promptly.

Do I need to redirect every single old page?

Redirect every old URL that changed, especially those with traffic or backlinks. Map each one to the most relevant new page rather than the homepage, which Google may treat as a soft 404. Pages with no value can be redirected to the closest surviving topic instead of being left to return a 404.

Can I improve my content during a redesign without hurting SEO?

Yes, and you should. Keep the keywords, headings and depth that earn rankings, then sharpen the writing and expand thin pages. The risk is deletion, not improvement. Adding clarity and useful detail helps SEO; stripping out the words that already rank is what causes drops.

Will moving from WordPress to a custom site lose my rankings?

Not by itself. Search engines rank pages and content, not platforms. A platform move usually changes your URL structure, so the key is a complete redirect map, preserved content and metadata, and faster performance on the new build. Migrate those signals correctly and the change is invisible to Google.