Home › Resources

Website Redesign Without Losing SEO: A Migration Checklist

Published November 21, 2026

Most traffic lost in a redesign comes from a few avoidable mistakes: URLs that change without redirects, pages that quietly disappear, a staging "noindex" or robots.txt block that goes live, and internal links that still point to old addresses. If you inventory every URL before you start, map each one to its new home with a permanent redirect, and check the new site before and after launch, a redesign does not have to cost you rankings.

The checklist below runs in order: before design starts, during build, on launch day, and in the weeks after. Google's own documentation on site moves is the best reference, and this guide points to it where it matters.

Before design starts: take an inventory

You cannot protect what you have not listed. Build a spreadsheet of every URL that matters before anyone changes the structure.

  1. Crawl the current site with a crawler tool and export every URL, title, meta description, H1, canonical and status code.
  2. Export pages with search traffic from Google Search Console's Performance report, so you know which pages earn clicks and for which queries.
  3. Export pages with backlinks from Search Console's Links report or a backlink tool. External links to a page are a reason to keep or redirect it carefully.
  4. Pull your analytics landing pages for the last twelve months to catch pages that convert but do not rank.
  5. Save a copy of the current site, including page text, so you can compare content after launch.

Mark each URL with a decision: keep as is, keep but move, merge into another page, or retire. Pages with traffic or links should almost never be retired without a redirect to the closest equivalent.

Build the redirect map

The redirect map is the most important document in the project. Each old URL gets one row and one destination.

Old URLNew URLTypeNotes
/services/web-design.html/web-design/301Same content, new structure
/blog/old-post-a/guides/topic-a/301Merged with a similar post
/promo-2019/301 or 410Only redirect to the homepage if nothing closer exists

Use permanent server-side redirects (301 or 308) for pages that have moved. Redirect each old URL straight to its final destination, not through a chain of hops. Avoid sending large numbers of unrelated old pages to the homepage; Google may treat those as soft 404s, and visitors land somewhere that does not answer what they came for.

Google's site move guide recommends keeping redirects for as long as possible, generally at least one year, so signals can transfer and links on other sites keep working. In practice, many sites keep them indefinitely.

During the build: keep what ranks

Design changes are fine. Content and signals that rankings depend on are what you need to carry over.

  • Keep the main text of pages that rank. Rewriting is fine, but do not strip out the sections that answer the queries in your Search Console data.
  • Carry over titles and meta descriptions, or improve them deliberately rather than replacing them with template defaults.
  • Keep one H1 per page that describes the page.
  • Preserve structured data such as Organization, Product or FAQ markup if the old site had it, and check that it still matches visible content.
  • Keep image alt text and file names meaningful when images are replaced.
  • Make sure every page in the new navigation is reachable through normal HTML links, not only through search boxes or scripts.

Merging and pruning old content

Redesigns are a natural time to clean up thin or overlapping pages, but pruning needs the same care as moving pages. Before you merge two posts, check which one earns the clicks and links in Search Console, keep that URL if you can, and fold the useful parts of the other page into it. Then redirect the retired URL to the merged page.

Do not delete pages just because they are old. An old guide that still answers a common question can be a steady source of visitors. Update its facts and design instead. Pages with no traffic, no links and no purpose for visitors are the ones that can be retired, with a 404 or 410 if nothing closer exists.

On staging: test before anyone can see it

Staging sites should be hidden from search engines, but the method used to hide them is the thing most often left in place at launch.

  1. Protect staging with a password or IP restriction where you can. That is safer than relying only on noindex or robots.txt.
  2. Crawl the staging site and compare against your inventory: every kept URL should exist, and every moved URL should have a mapped redirect ready.
  3. Check canonicals point to the final production URLs, not to staging addresses.
  4. Test mobile layouts and page speed on real devices.
  5. Write down every setting that blocks indexing on staging, so it can be removed on launch day.

Launch day checklist

Plan the launch for a quieter period for your business, and keep the team available for the following days.

  1. Deploy the new site and the redirects at the same time.
  2. Remove staging noindex tags, password protection and any robots.txt disallow rules meant for staging.
  3. Test a sample of old URLs from your map, including the highest-traffic pages, and confirm each returns a single 301 to the right page.
  4. Submit the new XML sitemap in Search Console, and keep it limited to the canonical URLs that return 200.
  5. Use the URL Inspection tool on key pages to confirm Google can fetch and render them.
  6. Check that analytics and conversion tracking fire on the new templates.
  7. Only if you changed domain or subdomain, use Search Console's Change of Address tool. Google notes it is not needed for moves within the same domain.

After launch: what to watch

Google's documentation says to expect temporary ranking fluctuation after a significant change while pages are recrawled, and that for medium-sized sites it can take a few weeks or more for new URLs to replace old ones in results. Watch for problems that are not normal fluctuation:

  • Spikes in 404 errors in Search Console's Pages report or your server logs. Add redirects for any old URLs you missed.
  • Pages reported as "Excluded by noindex tag" or "Blocked by robots.txt" that should be indexed.
  • Redirect chains or loops introduced by later fixes.
  • Internal links still pointing to old URLs. Update them so visitors and crawlers go straight to the new address.
  • Drops on specific pages that held important queries. Compare old and new content to see what changed.

Compare clicks and impressions for the same pages before and after, week by week, rather than looking only at the site total.

Where redesigns usually go wrong

The repeat offenders are simple: a staging noindex that ships, a new URL structure with no redirect map, blog posts dropped because nobody checked their traffic, and a CMS that adds trailing slashes or capital letters to every URL. None of these need specialist tools to prevent. They need a spreadsheet, someone responsible for it, and a launch-day checklist that is actually followed.

For more on this site, see the resources page and the homepage.

Frequently asked questions

Will a website redesign hurt my SEO?

It can, but it does not have to. Most losses come from URLs that change without redirects, content that is removed, and staging blocks left in place. With a URL inventory, a complete 301 redirect map and checks before and after launch, a redesign can keep or even improve search traffic.

How long should I keep 301 redirects after a redesign?

Google's site move guidance says to keep redirects for as long as possible, generally at least one year, so it can transfer signals and other sites' links keep working. Many site owners keep important redirects permanently because there is little cost in doing so.

Do I need the Change of Address tool for a redesign?

Only if you are moving to a different domain or subdomain, for example from one .com to another. Google notes the tool is not needed when the site stays on the same domain, even if URLs and structure change. Redirects and an updated sitemap do the work in that case.

Is it normal for rankings to drop after a site migration?

Some fluctuation is normal while Google recrawls the site. Google says it can take a few weeks or more for medium-sized sites. Large or lasting drops usually point to a technical problem, such as missing redirects, a noindex tag or removed content, and should be investigated.

Should I redirect deleted pages to the homepage?

Only when there is genuinely no closer page. Redirect each old URL to the most relevant new page. Sending many unrelated pages to the homepage frustrates visitors and may be treated as a soft 404 by Google. If a page has no replacement and no value, a 404 or 410 is acceptable.

Sources