How to Redesign or Move a Website Without Losing Google Rankings

A redesign is usually a good decision. The old site looks dated, it is slow, or nobody can edit it anymore. The risk is that the new site launches, looks great, and organic traffic drops in the weeks that follow. That drop is rarely bad luck. It usually comes from avoidable mistakes: pages that disappeared, missing redirects, or a staging setting that was never switched off.

This is the process I follow when I rebuild or move a site, written for business owners rather than developers. Good website migration SEO is mostly careful bookkeeping, and you do not need to be technical to follow it.

Why redesigns lose rankings

Google ranks individual pages. Each has a URL, its own content, and links from other sites. Change those without a plan, and Google has to work out the new site almost from scratch. The usual causes of lost traffic:

• Changed URLs with no redirects. Old addresses return a “page not found” error, and the signals they built up are lost.
• Removed or thinned content. A detailed service page becomes three short lines and a photo.
• Lost metadata. Page titles and descriptions that were working get replaced with defaults.
• Staging settings carried into the live site. The new site tells search engines not to index it.

Step 1: Build a URL inventory of the current site

Before anything is designed, make a complete list of every URL on the current site. I collect URLs from several sources, because no single one is complete:

• A crawl of the site with a crawler tool, which follows links the way a search engine does.
• The XML sitemap, a file that lists the pages you want search engines to find.
• Google Search Console, where the Pages and Performance reports show which pages Google knows about and which ones get clicks.
• Analytics and backlink data, for pages that get visits or links from other sites.

Put everything into one spreadsheet. For each URL, note its traffic, links from other sites, page title and meta description, then mark the pages that matter most and protect those first.

Step 2: Create a 301 redirect map

A 301 redirect is a permanent forwarding instruction: when a visitor or Google requests an old URL, the server sends them to the new one. This is how a page passes its ranking signals to its new address.

The redirect map is a two-column table, old URL and new URL. The rules I follow:

• Redirect to the closest equivalent page. An old “Roof Repair” page should point to the new “Roof Repair” page.
• Do not send everything to the homepage. Google can treat redirects to an unrelated page as “soft 404s”, handling them like missing pages, so the value is lost anyway.
• Avoid chains. If page A redirects to B, and B redirects to C, update A to point straight to C.
• Let obsolete pages go. A page with no traffic, no links and no replacement can return “not found” or “gone”.
• Keep the redirects for the long term. Google advises keeping them as long as possible, generally at least a year. I prefer to leave them in place indefinitely.

When moving to a new domain, keep the old one registered and serving the redirects. Letting it expire undoes this work.

Step 3: Keep the content and metadata that works

Pages that rank well should not be stripped down for a cleaner layout. Check in Search Console which search terms bring a strong page its traffic, and make sure the new version still answers them. On every important page, carry over or deliberately improve:

• The page title and meta description, the text often shown in search results.
• Headings, body text and image alt text, the short descriptions that help search engines and screen readers understand images.
• Structured data, code that describes things like your business details, products or articles to search engines.
• Canonical tags, which tell Google which version of a page is the main one.

Also update internal links, the links between your own pages, so they point directly to the new URLs instead of relying on redirects.

Step 4: Avoid staging and noindex pitfalls

A staging site is a private copy where the new site is built and tested, and you do not want Google to index it. A common safeguard is a noindex instruction, which tells search engines not to list a page. In WordPress, the “Discourage search engines from indexing this site” checkbox under Settings, Reading does this.

This setting easily gets carried over to the live site, and rankings fade until someone notices. My approach:

• Protect staging with a password, which keeps out search engines and the public more reliably than noindex alone.
• Check robots.txt, the file that tells crawlers which areas to stay out of, so the live version does not block the whole site.
• Make “remove noindex and staging blocks” a required launch item, and check the live page source afterward.

Step 5: Launch day checklist

If the preparation was done, launch day is calm. What I check, in order:

1. Confirm the live site is indexable: no noindex tags, no blocking rules in robots.txt.
2. Activate the redirect map and test old URLs, starting with every high-priority page.
3. Check that each redirect is a 301, lands on the right page and does not chain.
4. Confirm the site loads on HTTPS everywhere and that HTTP versions redirect to it.
5. Generate a fresh XML sitemap that lists only the new URLs.
6. Check that canonical tags point to the live domain, not to staging.
7. Make sure analytics and conversion tracking are installed and recording.
8. Test the forms, so leads keep arriving.
9. Crawl the new site to catch broken links and missing titles.

Step 6: Monitor Search Console after launch

Google Search Console is Google’s free tool for seeing how your site appears in search. After launch, I submit the new sitemap there and watch these reports for the first weeks:

• Pages report. A rise in “Not found (404)” errors usually points to a missing redirect.
• Performance report. Compare clicks and impressions with the period before launch, page by page.
• URL Inspection. Check that key new pages are indexed and that Google picked the correct canonical.
• Core Web Vitals. Google’s page experience metrics: LCP (how fast the main content loads), INP (how quickly the page responds to clicks and taps) and CLS (how much the layout shifts). The report uses data from real visitors, so it takes a few weeks to reflect the new site.

For a move to a new domain, verify both domains in Search Console and, once the redirects are live, use the Change of Address tool to tell Google the whole site has moved.

What to realistically expect

Even a well planned migration can move rankings, because Google needs time to recrawl old URLs, follow redirects and reassess the new pages. Some fluctuation in the first weeks is normal, and larger sites and domain changes usually take longer to settle.

A steep, lasting drop is not normal. It usually has a specific cause, such as missing redirects, an indexing block or lost content. Nobody can honestly promise rankings after a migration, but a clear process makes a serious loss much less likely and problems quick to diagnose.

Planning a redesign or a site move?

If you are about to rebuild your website or move it to a new platform or domain, I can help you plan it so your search visibility is protected. I build WordPress and Elementor sites and Next.js applications, and the SEO side of the migration is part of the work. Send me a short message through the contact form about your current site and what you want to change, and I will reply within one working day.