How to Redesign Your Website Without Losing Google Rankings: The SEO Migration Checklist

On this page

1. Why redesigns lose rankings
2. Phase 1: Benchmark before you touch anything
3. Phase 2: Crawl and inventory every URL
4. Phase 3: Build the URL map and redirects
5. Phase 4: Keep content parity on pages that rank
6. Phase 5: Keep staging out of Google
7. Phase 6: Launch-day checklist
8. Phase 7: Monitor for the first two months
9. Redesigns that also change platform or domain
10. Quick check: what do you have to protect?
11. When to get help
12. FAQs

To redesign a website without losing rankings, protect what Google already ranks: keep URLs where you can, 301-redirect every URL that changes to its closest new equivalent, keep the content, titles and internal links of pages that bring traffic, keep the staging site out of Google, and remove that block at launch. Then watch Search Console closely for the first few weeks and fix anything that slips.

Most ranking drops after a redesign come from skipped steps, not from the new design itself. This is the redesign-specific checklist I follow on website redesign projects. If the redesign also brings a new business name, see rebranding your website; if the domain changes too, follow changing your domain without losing SEO as well.

Why redesigns lose rankings

What goes wrong	What Google sees	How to prevent it
URLs change with no redirects	404s, lost links and lost history	A URL map and 301 redirects
Ranking pages removed or merged	The content it ranked has gone	A content inventory before design starts
Copy cut for a "cleaner" look	A thinner, less relevant page	Content parity on pages that rank
Titles, headings or schema lost	Weaker signals about the page	A parity checklist
Staging noindex goes live	Pages dropping out of the index	Launch-day checks
Links point to staging or old URLs	Broken crawl paths and redirect chains	A crawl after launch
The new site is slower	A worse page experience	Speed tests before launch

Phase 1: Benchmark before you touch anything

You can't tell whether a redesign hurt rankings without a record of where you started. Save these in one spreadsheet, dated:

• Search Console > Performance: export pages and queries with clicks and impressions for the longest range available. These are the pages that need the most care.
• GA4 landing pages: sessions and key events by page, so you know which pages bring enquiries, not just visits.
• Search Console > Links > Top linked pages: pages other sites link to. Losing these URLs without redirects throws away those links.
• Positions for your important searches, checked manually or with a rank tracker.
• Speed: PageSpeed Insights results for your homepage, a service page and a blog post.

Phase 2: Crawl and inventory every URL

Crawl the old site with a tool such as Screaming Frog SEO Spider, which has a free version for smaller sites, then add URLs from your XML sitemap, the Search Console export, GA4 landing pages and your linked pages list. Crawlers only find pages that are linked, so these extra sources catch orphan pages, old PDFs and campaign pages that still get visits.

For every URL, decide one action:

• Keep: the page stays at the same URL
• Move: the page continues at a new URL, with a 301 redirect
• Merge: its content joins another page, and it redirects there
• Remove: no equivalent exists; only acceptable for pages with no meaningful traffic or links

On Shopify the URLs usually survive a redesign, but titles, templates and app embeds do not always; see changing a Shopify theme without losing SEO.

Phase 3: Build the URL map and redirects

The safest URL is the one that doesn't change. A WordPress-to-WordPress redesign can usually keep every important slug. Moving from Wix, Blogger or a hand-coded site often forces changes, which is when the map matters most; see moving from Wix to WordPress for a platform-change example.

Old URL	New URL	Action
/about-us/	/about-us/	Keep
/services/solar-installation.html	/solar-installation/	301
/products/inverter-batteries/	/batteries/	301 (merged)
/diwali-offer-2019/	None	Remove (no traffic or links)

• Redirect to the closest equivalent, page by page. Sending everything to the homepage loses relevance, and Google tends to treat it as a soft 404.
• Avoid chains. If an old redirect points to a URL that is now changing, update it to point straight at the final URL.
• Use 301s for permanent moves, not 302s; see 301 vs 302 redirects.
• Keep your existing HTTPS and www rules working alongside the new redirects.

On WordPress, the Redirection plugin or Rank Math's redirections module handle most sites. For long lists, server-level rules in .htaccess on Apache or LiteSpeed hosting are faster:

Redirect 301 /services/solar-installation.html https://www.example.com/solar-installation/
Redirect 301 /products/inverter-batteries/ https://www.example.com/batteries/

Phase 4: Keep content parity on pages that rank

A redesign changes how pages look. It shouldn't quietly remove what made them rank. For every page in your benchmark's top list, check that the new version keeps:

• The substance of the copy: sections, details, FAQs and examples. Restyle long text with headings, columns or accordions rather than deleting it.
• Title tags and meta descriptions, carried over or improved deliberately, not reset to defaults.
• The H1 and main headings that match what people search.
• Internal links: a slimmer menu can leave ranking service pages with no links pointing at them. Add them to the footer, hub pages or in-content links.
• Images and alt text, and image URLs if images bring traffic from Google Images.
• Structured data: LocalBusiness, breadcrumbs, FAQ, product or article schema.
• Canonical tags, hreflang on multilingual sites, and robots settings.
• Tracking: GA4, key events, Google Ads and Meta tags.

A practical check is to crawl the old site and the staging site and compare titles, H1s, word counts and indexability side by side.

Phase 5: Keep staging out of Google

WordPress's "Discourage search engines from indexing this site" setting (Settings > Reading) adds a noindex tag. It works, but it's risky: the setting lives in the database, so if the staging site is copied to live, the noindex goes live with it. A password on the staging site, which most hosts offer, keeps out search engines and everyone else, and can't be indexed by accident.

If a staging subdomain is already in Google, password-protect it and use the Removals tool in a Search Console property for that subdomain. More on safe testing in staging sites explained.

Phase 6: Launch-day checklist

1. Untick "Discourage search engines" and check the page source of key pages for a noindex tag.
2. Check robots.txt doesn't contain Disallow: / from staging.
3. Run your full old-URL list through a crawler in list mode: each should return one 301 to a page that returns 200.
4. Check canonical tags, internal links and image addresses use the live domain, not staging. A database search and replace fixes leftovers, for example with WP-CLI: wp search-replace 'staging.example.com' 'www.example.com' --dry-run, then without --dry-run once the preview looks right.
5. Confirm HTTPS works everywhere and only one version of the domain loads.
6. Submit the XML sitemap in Search Console and inspect your most important URLs with URL Inspection; see getting pages indexed faster.
7. Test forms, email delivery, WhatsApp and call buttons, and check GA4 Realtime for key events.
8. Clear caching plugin, host and CDN caches, then run PageSpeed Insights on key templates and compare with your benchmark.

Phase 7: Monitor for the first two months

• Daily for two weeks: the Search Console Pages report for "Not found (404)", "Excluded by noindex tag" and redirect errors, plus spot checks with URL Inspection.
• Weekly for the next six weeks: Performance with date comparison (compare equal periods with the same weekdays), clicks by page against your benchmark, and positions for your tracked searches.
• Fix fast: redirect any 404 that has traffic or links, and for pages that lose clicks, compare the old content (the Wayback Machine helps) with the new page.

Some movement for a few weeks is normal while Google recrawls. A sharp site-wide drop usually points to a noindex, robots or canonical problem; see Search Console indexing errors and the traffic drop checklist.

Redesigns that also change platform or domain

A redesign that keeps the same platform and domain is the safest kind. Many projects change more than the design, and each extra change adds its own risks to plan for.

Moving from a builder or custom code to WordPress

Old builder sites often use URLs with IDs, query strings or a .html ending. WordPress will produce clean, different URLs, so every ranking page needs a one-to-one 301 redirect. Export the old page list before the old account is closed, because some builders remove access once the subscription ends.

Moving a store to Shopify or WooCommerce

Shopify forces fixed URL patterns such as /products/ and /collections/, so product and category URLs will almost always change. Plan redirects for products, categories, and important filtered pages, and carry over product descriptions, image alt text and reviews where the platform allows. Check that out-of-stock and discontinued products redirect to the closest live product or category rather than to the home page.

Changing the domain at the same time

If you are also moving to a new domain, redirect every old URL to its exact new equivalent, keep the old domain registered and its redirects live for at least a year, and use the change of address tool in Google Search Console. Avoid combining a domain move with heavy content cuts in the same week, because it becomes hard to tell which change caused any drop.

Switching from www to non-www, or http to https

These are small changes but they affect every URL. Pick one version, redirect all others to it in a single hop, and update canonical tags, the XML sitemap and internal links so nothing still points at the old form.

If traffic does drop after launch, work through the traffic drop checklist step by step, and check that new pages are being indexed; see getting indexed faster.

Quick check: what do you have to protect?

Before any design work, export two lists:

1. In Search Console, open Performance, Search results, set the date range to the last 12 months, open the Pages tab and export it. These are the URLs that bring clicks.
2. Fetch yourdomain.com/sitemap.xml (or /sitemap_index.xml on Yoast and Rank Math sites) and save every URL listed.

Every URL on either list needs to stay the same or get a 301 redirect on launch day. After launch, curl -I https://yourdomain.com/old-page/ should return 301 with the new address in the location line.

After launch, crawl the new site to catch pages left out of the menus; see how to fix orphan pages.

When to get help

Get help when the site already brings steady traffic or enquiries, when the platform or domain is changing too, or when nobody on your side has done a redirect map before. A website redesign is built on a staging site, keeps important URLs, maps and tests redirects, carries over SEO settings and is watched in Search Console after launch. Not sure you need a full redesign? Read refresh vs redesign first, or send your website address.

For the redirect map itself, the WordPress 301 redirects tutorial shows how to add, test and monitor redirects after launch.

FAQs

Will redesigning my website affect SEO?

It can, in either direction. A redesign that keeps URLs, content and internal links while making the site faster and clearer often helps. One that changes URLs without redirects or strips content usually hurts. The difference is the process, not the design.

How do I redesign my website and keep my rankings?

Benchmark your top pages, crawl every URL, keep URLs where possible, 301-redirect the rest to their closest equivalents, keep the content and on-page SEO of ranking pages, password-protect staging, run launch-day checks and monitor Search Console daily for two weeks.

Should I keep the same URLs when redesigning?

Yes, wherever you can. Unchanged URLs need no redirects and keep their history. Change a URL only when there's a clear reason, such as a platform move or merging duplicate pages, and redirect it.

How long do rankings take to settle after a redesign?

Usually a few weeks as Google recrawls the site and processes redirects. Problems such as missing redirects or a leftover noindex show up in Search Console within days, which is why the first two weeks need daily checks.

Can I change my WordPress theme without losing SEO?

Yes, if URLs stay the same and the new theme keeps your content, headings, internal links and schema. Test it on staging first, because some themes move content into builder layouts, drop breadcrumbs or load much more slowly.

Should I redirect deleted pages to the homepage?

No. Redirect each page to its closest equivalent. If nothing relevant exists, letting it return a 404 or 410 is better than a homepage redirect.