How to Redesign Your Website Without Losing Google Rankings: A 2026 Migration Checklist

A new website is supposed to bring in more business. But every year, plenty of small businesses launch a beautiful redesign and then watch their phone go quiet. Organic traffic drops, pages that used to rank on Google disappear, and nobody can quite explain why.

The cause is almost never the new design itself. It's the migration: URLs that changed without redirects, content that got trimmed, tracking that broke, or a "noindex" tag left behind from the staging site. The good news is that every one of those problems is preventable with a plan.

If you're thinking about a redesign, a platform switch (say, from WordPress to Webflow or Shopify), or a new domain in early 2027, this guide walks you through how to do it without throwing away the search visibility you've already earned.

Why Redesigns Lose Rankings in the First Place

Google doesn't rank "your website." It ranks individual pages at specific URLs. Over the years, those URLs collect signals: links from other sites, a history of clicks, a clear topic, and a spot in Google's index. When a redesign changes those URLs or the content on them, you're asking Google to figure out where everything went.

The most common ways that goes wrong:

• Changed URLs with no redirects. Your old /services/roof-repair page becomes /roofing, and anyone (or any search engine) following the old link hits a 404 error.
• Thinned-out content. A designer cuts a 1,200-word service page down to three sentences and a hero image because it "looks cleaner." Google loses the content it was ranking.
• Staging settings carried over. Development sites are usually blocked from search engines. If that block (a robots.txt rule or a noindex tag) ships to the live site, Google starts dropping your pages.
• Broken internal links. Menus, footers, and in-text links still point to old URLs, creating redirect chains or dead ends.
• Lost technical details. Title tags, meta descriptions, structured data, image alt text, and canonical tags quietly disappear in the rebuild.
• Broken tracking. Analytics or conversion tags don't make it to the new site, so you can't even tell what happened.

None of this requires advanced SEO to fix. It requires doing the boring steps in the right order.

Step 1: Decide What Kind of Migration You're Doing

Not every "new website" carries the same risk. Be clear about which changes you're making, because each one adds a layer of work:

• Design-only refresh: New look, same URLs, same content. Lowest risk.
• Content and structure changes: Pages merged, renamed, or reorganized. Moderate risk; redirects are essential.
• Platform change: Moving between CMSs or ecommerce platforms. URL patterns often change automatically (product and blog URLs especially), so you need a full redirect map.
• Domain change or rebrand: Moving to a new domain name. Highest risk, and it needs extra steps in Google Search Console.
• HTTP to HTTPS or www to non-www: Technically a migration too, even if nothing looks different.

Our honest advice: don't stack every change at once if you can avoid it. A rebrand, a new platform, and a full content rewrite all in the same launch makes it very hard to diagnose problems afterward.

Step 2: Pick the Right Launch Window

Timing matters more than most people think. If your business depends on the holiday season, a November or December launch puts your busiest stretch on top of the period when rankings are most likely to wobble.

For most US retailers and seasonal businesses, the better plan is to do the planning and build work now, freeze changes through the holidays, and launch in January or early February. Service businesses should look at their own calendar: an HVAC company probably shouldn't launch at the start of summer, and a tax preparer shouldn't launch in March.

Also avoid launching on a Friday afternoon. You want your team (and your developer) available for the first few days after go-live.

Step 3: Inventory Every URL You Have Now

This is the step that gets skipped most often, and it's the one that matters most. Before anything changes, build a complete list of every URL on your current site that has value. Pull from several sources, because no single tool sees everything:

• Google Search Console: Export the Performance report (pages tab) for the longest date range available, ideally a full year so seasonal pages show up.
• Google Analytics 4: Export landing pages that received organic traffic.
• Your XML sitemap: Usually at yoursite.com/sitemap.xml.
• A site crawler: Tools like Screaming Frog crawl your site the way a search engine does and catch pages that aren't in your sitemap.
• Backlink data: Any page that other websites link to is worth protecting, even if it gets little traffic today.
• Your ad accounts: Landing pages used by Google Ads, Meta ads, and email campaigns.

Put everything in one spreadsheet, remove duplicates, and note the traffic, conversions, and backlinks for each URL. This becomes your migration control document.

Benchmark before you touch anything

While you're in Search Console and Analytics, save a snapshot of your current performance: clicks, impressions, top queries, top landing pages, and conversions (calls, form fills, sales). Write down where you rank for the 10 to 20 searches that actually bring you customers. Without a baseline, you'll have no way to know whether the new site is helping or hurting.

Step 4: Build a Redirect Map

A redirect map is just two columns: old URL and new URL. Every old URL with value gets pointed to its closest equivalent on the new site using a permanent (301) redirect.

A few rules that save a lot of pain:

• Redirect one-to-one where possible. The old "kitchen remodeling" page should go to the new kitchen remodeling page, not the homepage.
• Don't dump everything on the homepage. Google generally treats mass redirects to an unrelated page like a missing page, so the value doesn't carry over.
• Avoid redirect chains. If an old URL already redirects somewhere, update it to point straight to the final destination instead of hopping twice.
• Merging pages? Redirect all of them to the merged page and make sure the new page actually covers what the old ones did.
• Retiring a page with no equivalent? If it had no traffic and no links, letting it return a 404 or 410 is fine. If it had value, redirect to the most relevant parent page, such as a category or service hub.
• Keep URLs the same whenever you can. The safest redirect is the one you never need.

Watch out for platform URL patterns

Platforms format URLs differently. Shopify, for example, puts products under /products/ and pages under /pages/, while WordPress lets you set almost any structure. Moving between them often changes every product and blog URL automatically. Plan for that early, and use pattern-based redirects only when the old and new patterns line up cleanly.

Step 5: Protect Your Content and On-Page SEO

Rankings are earned by content, so treat your best-performing pages carefully during the redesign.

• Keep the substance of top pages. You can rewrite for clarity and update outdated details, but don't strip out the information that answered people's questions.
• Carry over title tags and meta descriptions for pages that perform well, then improve them deliberately rather than by accident.
• Keep one clear H1 per page that matches what the page is about.
• Migrate structured data. LocalBusiness, Product, FAQ, and Review schema often live in a plugin or theme and don't come along automatically.
• Bring over image alt text and file names, especially for product images.
• Check canonical tags so each page points to itself (or the correct preferred version), not to the staging domain.

A useful gut check: if a page brought you customers last year, someone should be able to explain exactly where that page lives on the new site and what changed about it.

Step 6: Test on Staging Before Launch

Your new site should be fully built and reviewed on a staging environment that's hidden from search engines. Before you go live, run through these checks:

• Crawl the staging site and look for broken links, missing title tags, duplicate titles, and pages missing H1s.
• Test a sample of redirects from your map, including your top 20 pages.
• Confirm internal links point directly to new URLs, not to old URLs that then redirect.
• Test every form, phone link, booking widget, and checkout flow on both desktop and mobile.
• Check page speed and Core Web Vitals. A redesign heavy on video and animations can be noticeably slower than the site it replaces.
• Run a basic accessibility review: color contrast, keyboard navigation, form labels, and alt text.
• Confirm analytics, Google Tag Manager, conversion tracking, and ad pixels are installed and firing.

Step 7: Launch Day Checklist

Launch day should be calm if the prep work is done. Work through this list in order:

1. Remove staging blocks. Check robots.txt and make sure there's no sitewide noindex tag. This single item causes more post-launch disasters than anything else.
2. Turn on redirects and spot-check them from the live domain.
3. Confirm HTTPS works on every page with no mixed-content warnings.
4. Submit your new XML sitemap in Google Search Console and Bing Webmaster Tools.
5. Use URL Inspection in Search Console on your most important pages and request indexing.
6. If you changed domains, verify the new domain in Search Console and use the Change of Address tool. Keep the old domain registered and redirecting for the long term.
7. Update ad destination URLs so paid traffic lands directly on new pages instead of passing through redirects, which can strip tracking parameters.
8. Update your Google Business Profile website link and any key directory listings if URLs changed.

Step 8: Monitor the First 60 Days

Some ranking movement after a migration is normal while Google recrawls and reprocesses your pages. What you're watching for is whether things settle back toward your baseline or keep sliding.

First week

• Check Search Console daily for spikes in 404 errors, "Excluded by noindex," or server errors.
• Watch Analytics to confirm traffic and conversions are being recorded.
• Review server logs or crawl reports for redirect loops or chains.

Weeks two through eight

• Compare organic clicks and impressions against your pre-launch baseline every week.
• Check rankings for your 10 to 20 money keywords.
• Look at the Pages report in Search Console to make sure new URLs are being indexed and old ones are dropping out.
• Fix any 404s that show up from old URLs you missed by adding redirects.
• Reach out to sites that link to you most and ask them to update links to the new URLs where it makes sense.

If traffic to a specific page falls off sharply and doesn't recover, compare the old and new versions side by side. Usually the answer is a missing redirect, a content cut, or a technical tag that changed.

Questions to Ask Your Web Developer or Agency

Whether you're hiring someone or working with an existing partner, these questions tell you quickly whether SEO is part of the plan or an afterthought:

• Will you create a full URL inventory and redirect map before launch? Can I see it?
• Which current URLs are changing, and why?
• How will you carry over title tags, meta descriptions, and structured data?
• How is the staging site blocked from Google, and who removes that block at launch?
• Who verifies analytics and conversion tracking on the new site?
• What does post-launch monitoring look like, and for how long?

If the answers are vague, that's a signal to slow down before anything goes live.

The Bottom Line

A redesign should be an upgrade, not a reset. The businesses that come through a migration with their rankings intact aren't lucky. They inventoried their URLs, mapped every redirect, protected their best content, tested before launch, and watched the numbers closely afterward.

If you're planning a new website for early 2027, now is the right time to start the groundwork, so the launch happens after the holiday rush instead of in the middle of it.

At Kodbee, we plan redesigns and platform migrations with search visibility built into the process from day one, from the URL audit to post-launch monitoring. If you'd like a second set of eyes on your migration plan, get in touch with our team and we'll help you map out a launch that keeps your customers finding you.