Short answer
To avoid losing SEO in a website redesign, list every address on the old site and send each one to its counterpart on the new site with a single 301 redirect. On launch day check robots and noindex settings, canonical tags and the sitemap; then watch index coverage and 404 errors for 4 to 8 weeks.
The new site goes live on Monday, clicks in Search Console start falling by Thursday, and the first suspect is the design. Yet when a website redesign loses SEO, the cause is usually the addresses. The new site may well be faster, better organised and better looking. But search engines, and the sites that link to you, know your old addresses; if the new site doesn’t answer at those addresses, value built up over years is lost overnight. In this article we walk through a site migration in four stages: before the rebuild, on the new site, on launch day and in the weeks after launch. At the end there is a checklist you can use as it stands.
Before the rebuild: take stock of what you have
In company website rebuilds, the step most often skipped is taking a snapshot of the old site. Once the old site is gone, it is hard to go back and find which pages existed and which brought in traffic. So start this work before development begins.
URL inventory
A list of every address on the old site is the foundation of the migration. Build it by combining several sources rather than relying on one:
- Sitemap: every address in the current sitemap. But sitemaps are often incomplete; old campaign pages or pages added by hand may not be in it.
- Search Console: indexed pages and addresses that have had impressions in search results in recent months. Pages that never appeared in the sitemap can turn up here.
- Crawl: go through the whole site with a crawling tool and collect the addresses that can be reached through internal links.
- Most valuable pages: mark separately the pages that get the most organic traffic in your analytics tool and the addresses with the most external links in your link analysis. In the migration you will give these pages individual care. On a site that sells to other businesses, add the pages that get little traffic but bring quote requests; our guide to B2B SEO explains why.
Once you combine these lists into a single table and remove the duplicates, you have a real map of the old site.
Titles, descriptions and structured data
For every important page, record the title tag, the meta description, the H1 heading and any structured data (such as product, article, frequently asked questions or business information). The text may be rewritten on the new site; that is a good thing, but changing the title of a page that ranks well without knowing it makes it harder to understand later why it dropped.
Tracking tags
Analytics, ad pixels, conversion tags, heatmaps and form tracking: list every piece of tracking code running on the old site, where it is installed and which event it tracks. When the new site goes live, work through this list, ticking items off one by one. In a migration without measurement, you cannot tell whether a drop comes from SEO or from a broken tag. If you are setting up GA4 from scratch on the new site, our GA4 setup checklist lists, in order, the settings and tests to complete before launch.
On the new site: set up the addresses and signals correctly
Mapping old addresses to new ones
Next to every old address in the inventory, write its counterpart on the new site. This mapping table is the source of your 301 redirects. The rule is simple: the new address should be the page that covers the same topic as the old one. A product page goes to the new product page, a blog post to the new address of the same post, a service page to the new page for the same service.
We did the same when we rebuilt our own site. On the old site, pages sat under language folders and had different names; we mapped each page to its new counterpart one by one and left general, section-level rules for the very end of the list. That way the exact matches run first, followed by a safety net for everything else.
How to set up 301 redirects
A 301 means “this page has moved permanently”, and it lets search engines pass the old address’s signals on to the new one. How you set it up depends on your platform: the server configuration, the hosting platform’s redirects file or a plugin in your content management system. Whichever you choose, the things to watch for are the same:
- Redirect one to one. Each old address should go to its closest counterpart.
- Don’t build chains. If address A goes to B and B goes to C, that is a chain. Each step slows crawling and adds to the risk of errors. Google’s site move guidance also recommends pointing straight to the final address instead of chaining; update redirects left over from past migrations to point to the new addresses too.
- Don’t use temporary redirects. A 302, or JavaScript redirects that only work in the browser, are not the right signal for a permanent move.
The risk of redirecting everything to the homepage
When mapping feels like too much work, the obvious shortcut is to send every old address to the homepage. Don’t. Someone looking for an old product page who lands on the homepage won’t find what they were after. Search engines also often treat this as a soft 404, meaning the page looks as though it exists but is ignored, and the old address’s value isn’t passed on. For a page that truly has no counterpart, it is better to redirect to the closest parent category, or to return an honest 404 or 410.
If a redirect doesn’t take the visitor to what they were looking for, it isn’t a redirect; it is a polite way of closing the door.
Canonical and hreflang
Each page’s canonical tag should point to its own final address on the new site: not the old domain, not the staging environment and not an address that redirects. On multilingual sites, hreflang tags should also be updated for the new addresses, and each language version should point to the others in both directions. If the structure of your language folders is changing, test this part separately.
What must not come across from staging
During development, the staging environment is usually closed to crawling with the robots file, or noindex is added to its pages. That is correct, but if these settings are carried over to the live site on launch day, the whole site can drop out of search results. Just before launch, check the live site’s robots file and the robots tag in the source code of a few pages with your own eyes.
Internal links and the sitemap
Redirects rescue old links, but the site’s own links shouldn’t need redirects. Every link in the menu, in the body text and in the footer should point straight to the new addresses. Be consistent about the trailing slash too: across the whole site use either /en/services/seo/ or /en/services/seo every time, and redirect the other form to the one you prefer. The sitemap should also contain only new addresses that you want indexed and that return a 200 code.
Launch day
The launch-day tasks are short, but the order matters:
- Test the old addresses in the mapping table in bulk with a tool; confirm that each one goes to the right new address with a single 301.
- Submit the new sitemap in Search Console.
- Check a few of the most important pages with the URL Inspection tool; look at how Google sees each page and whether it can be indexed.
- Verify the tags on your tracking list one by one; send a test conversion.
- If the domain has changed as well, use the Change of Address tool in Search Console. If the domain stays the same and only the addresses have changed, you don’t need this tool.
The 4 to 8 weeks after launch
A migration doesn’t end on launch day. It takes time for search engines to crawl the new addresses and put them in place of the old ones; during that time, keep an eye on the following:
- Index coverage: in the page indexing report in Search Console, check that the new addresses are being indexed and the old ones are marked as redirects. Look into pages that are excluded unexpectedly.
- 404 errors: check the list of pages not found every week. If an address that was missed in the mapping turns up, add its redirect.
- Rankings and traffic: compare the organic traffic and queries of your most valuable pages with the period before. Look page by page in your analytics tool; the overall figure can hide the pages with problems.
Some movement in rankings in the first weeks is normal. Panicking during this period and changing addresses again, or breaking redirects, usually drags things out. If after a few weeks the movement has still turned into a lasting drop on particular pages, look at those pages’ redirects, content and internal links one by one. Once things have settled, you can use our technical SEO checklist to audit the new site’s technical foundations from end to end.
Site migration checklist
We suggest sharing the list below at the start of the project and giving every step an owner:
- A single URL inventory has been built from the sitemap, Search Console, a crawl and analytics data.
- The pages with the most traffic and links have been marked.
- The title, description, H1 and structured data of important pages have been recorded.
- All tracking tags and the events they track have been listed.
- A new counterpart has been written for every old address; a decision has been made for those without one.
- Redirects have been set up as 301s, one to one and without chains.
- There are no bulk redirects to the homepage.
- Canonical tags and hreflang point to the new addresses.
- There is no robots block or noindex left over from staging on the live site.
- Internal links go to the new addresses without redirects; trailing slashes are consistent.
- The sitemap contains only new addresses that return 200, and it has been submitted.
- Important pages have passed URL Inspection; tracking tags have been verified.
- If the domain changed, the change of address has been reported.
- Index coverage, the 404 list and page-level traffic have been monitored for at least 4 to 8 weeks.
If you are curious about how speed affects SEO and conversion, take a look at why a fast site sells more while you plan the new site’s performance.
Common questions
Will my rankings drop after a website redesign?
They don’t have to. If addresses are mapped correctly, content is kept or improved and the technical signals are set up correctly, rankings usually settle back into place after some movement in the first weeks. Most lasting drops come from missing redirects, removed content or mistakes such as a noindex carried over to the live site.
How long should 301 redirects stay in place?
Google’s site move guidance recommends keeping them for as long as possible, generally at least a year; where possible we prefer to leave them permanently. Old links live on for years on other sites, in emails and in bookmarks; the day you remove the redirect, those visitors land on a 404 page.
Is it safer not to change the URL structure at all?
If your current addresses are clean and meaningful, keeping them reduces the risk. But if the old structure is messy, or the language folders or naming are inconsistent, a rebuild is a good chance to fix that. What matters is making the change in a controlled way, with a mapping table.
What happens if we remove some old pages on the new site?
Removing unnecessary pages isn’t a problem. If you are removing a page that gets traffic or links, redirect it to the closest related page; if it truly has no counterpart, return a 404 or 410. Don’t send it to the homepage.
Even if the rebuild is still only an idea, build the URL inventory this week. It is the one document you need before design starts, and once the old site is gone it may be impossible to rebuild. If an agency will handle the move, put the questions from choosing an SEO agency on the table alongside the mapping table. At Detmore this work is split between two teams: web and software builds the new site, and SEO takes on the mapping and the monitoring after launch.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 25 October 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.