Redesigning Your Website Without Losing Google Rankings

A website redesign can quietly erase years of Google visibility if old page addresses disappear without redirects, content that ranked is thrown away, or the new site launches with technical mistakes. You can avoid that by treating the redesign as a site move: record what currently brings traffic, map every old URL to its new equivalent, set up permanent 301 redirects, keep the content that works, submit new sitemaps, and watch closely after launch. This checklist follows Google’s own guidance on site moves and redirects, and applies whether you’re changing design, platform or domain.

Why redesigns lose traffic

Most traffic losses after a redesign come from a handful of avoidable mistakes:

• Page addresses change and the old ones return “page not found” errors, so visitors and search engines hit dead ends.
• Content that ranked is shortened or deleted because it didn’t fit the new design.
• Titles, headings and descriptions are lost when pages are rebuilt in a new theme or platform.
• The staging site’s “don’t index” setting is left on at launch, telling search engines to ignore the new site.
• Internal links still point to old addresses, creating chains of redirects.
• Tracking breaks, so nobody notices the drop until weeks later.

Google says that when you make significant changes to a site, rankings may fluctuate while it recrawls and reindexes, and that for medium-sized sites it can take a few weeks or more for Google to start showing the new URLs (Google Search Central: site moves). Planning keeps that period short and the drop small.

Phase 1: Before you design anything

1. Record what currently works

Export and save:

• Pages that get search traffic, from Google Search Console’s performance report: pages, the searches they appear for, clicks and impressions
• Pages with links from other websites, from Search Console’s links report
• Top landing pages and conversions, from Google Analytics
• A full list of your current URLs, from your sitemap or a site crawl

This is your “before” picture. Without it you can’t tell what was lost.

2. Decide what stays, what changes and what goes

For each existing page, decide:

• Keep: same content, same URL where possible
• Move: content kept, new URL
• Merge: several thin pages combined into one better page
• Remove: genuinely obsolete pages, redirected to the closest relevant page, or allowed to return a proper “gone” response if nothing relevant exists

Keeping URLs unchanged wherever you can is the simplest way to protect rankings.

Phase 2: Build the redirect map

3. Map every old URL to a new URL

Create a spreadsheet with two columns: old URL and new URL. Every page on your “before” list needs a row. Map each old page to the most relevant new page, not simply to the homepage. Sending many old pages to the homepage frustrates visitors and loses the relevance those pages had.

4. Use permanent redirects

Google recommends permanent server-side redirects, such as 301 or 308 status codes, when a page has moved permanently (Google Search Central: redirects). Google’s site move guidance also says that 301 and other permanent redirects don’t cause a loss in PageRank (Google Search Central: site moves).

Practical points:

• Redirect directly to the final URL. Avoid chains where page A redirects to B, which redirects to C.
• Keep redirects in place long term. Removing them a few weeks after launch brings the errors back.
• Handle both versions of a URL, with and without a trailing slash, and old http addresses, so they all reach the same final page.
• Test redirects on the staging site before launch where your hosting allows it.

Phase 3: Build the new site without losing SEO basics

5. Carry over the on-page essentials

For every important page, check that the new version keeps or improves:

• a unique title tag and meta description
• one clear main heading (H1)
• the body content that answered searchers’ questions
• image alt text
• structured data such as business, breadcrumb or FAQ markup
• internal links to related pages

6. Update internal links

Change links in menus, footers and page content to point directly to the new URLs, rather than relying on redirects.

7. Check speed and mobile experience

A redesign is a chance to improve performance. Test key templates against Google’s Core Web Vitals on mobile (web.dev: Web Vitals), and don’t let heavy sliders, large images or extra plugins make the new site slower than the old one.

8. Prepare tracking

Install Google Analytics and any ad pixels on the new site, and test form, call and WhatsApp click tracking before launch.

Phase 4: Launch day

9. Launch checklist

• Remove any “noindex” setting or password protection left from staging
• Switch on the redirect map and test a sample of old URLs, including your top pages
• Check the robots.txt file doesn’t block important sections
• Generate and submit the new XML sitemap in Google Search Console and Bing Webmaster Tools
• Confirm analytics and conversion tracking are recording
• Test forms, phone links and WhatsApp buttons on a phone

10. If you’re changing domain name

If the redesign also moves the site to a new domain, set up redirects from the old domain to the matching pages on the new one and use the Change of Address tool in Search Console for the old property (Search Console Help: Change of Address). Keep control of the old domain and its redirects for the long term.

Phase 5: After launch

11. Monitor closely for the first weeks

• Search Console coverage and pages reports: watch for spikes in “not found” errors and fix missing redirects quickly.
• Performance report: compare clicks and impressions for your top pages against your “before” export.
• Analytics: check landing pages and conversions against the same period before launch.
• Crawl the new site: look for broken links, redirect chains, missing titles and duplicate pages.

12. Fix, don’t panic

Some fluctuation is normal while Google processes the changes. Fix genuine problems such as missing redirects, lost content and blocked pages, then give it time. A sustained, significant drop on specific pages usually points to a redirect or content issue on those pages.

Common redesign scenarios

Scenario	What to watch most
Same platform, new design	Theme changes dropping titles, headings and structured data
Moving from a page builder or old CMS to WordPress	URL structure changes and missing redirects
Moving an online store to Shopify	Product and category URL changes; keeping product descriptions
Merging several websites into one	Mapping each site’s pages to the right new sections
Changing domain name	Domain-level redirects and Search Console Change of Address

We plan redirects, content and tracking as part of every rebuild. See how we approach website development in Assam and ongoing SEO for Guwahati businesses.

Sources

• Google Search Central: Site moves with URL changes
• Google Search Central: Redirects and Google Search
• Search Console Help: Change of Address tool
• web.dev: Web Vitals