The short answer
- Before a redesign, list every URL that has traffic, links or rankings, and map each one to its closest equivalent on the new site.
- Redirect every changed URL with a permanent 301 redirect to its most relevant new page, and keep the redirects in place for at least a year.
- For a move to a new domain, use the Change of Address tool in Google Search Console once the redirects are live.
You keep search traffic through a redesign by making sure every page that earns traffic today either keeps its URL or permanently redirects to an equivalent page, and by keeping the content that made it rank. A site migration is any change to a site’s URLs, domain, structure or platform that search engines have to relearn. The work is mostly an inventory, a redirect map and careful checks on launch day and in the weeks after.
Why redesigns lose traffic
Search engines rank individual URLs. When a URL disappears, its rankings and the links pointing to it have nowhere to go unless a redirect says where the page now lives. The usual causes of a drop after a relaunch are a short list.
- URLs changed without redirects, so old links and rankings lead to 404 pages
- Pages that ranked were removed, merged badly or cut down to a few lines
- Titles, headings and internal links all changed at once
- The staging site’s noindex tag or robots.txt block went live with the new site
- The new site draws its content with JavaScript that crawlers can’t see
Every one of these is preventable. The safest migration changes as few things at once as possible. If you can keep the URLs the same and change only the design, do that.
Build a full URL inventory
Start with a list of every URL that matters on the current site. No single source has them all, so combine several:
- a crawl of the live site with a site crawler tool
- your XML sitemaps
- pages with clicks or impressions in Search Console’s Performance report, which keeps 16 months of data
- landing pages from your analytics
- pages with links from other sites, from Search Console’s Links report
- PDFs, images and other files that receive traffic or links
Put them in one spreadsheet, with columns for traffic, external links and the new URL. That spreadsheet becomes the redirect map. Before launch, also record benchmarks for the pages that matter most, such as their clicks, impressions and average position, so you have something to compare against afterwards.
Write the 301 redirect map
A 301 redirect is a permanent redirect. It tells browsers and search engines that a page has moved for good, and Google treats it as a strong signal that the new URL should replace the old one in its index. Map each old URL to the single most relevant new page.
| Old page | Situation on the new site | What to do |
|---|---|---|
| Same content, new URL | A direct equivalent exists | 301 to the new URL |
| Two pages merged into one | A combined page covers both | 301 both old URLs to the combined page |
| Product or service discontinued | A close replacement or category exists | 301 to the closest relevant page |
| Content removed with no equivalent | Nothing relevant on the new site | Return 404 or 410; don’t redirect to the home page |
| URL unchanged | Same page, new design | No redirect; check the content survived |
Avoid sending everything to the home page. Google may treat a redirect to an unrelated page as a soft 404, so the old page’s value is lost anyway. Redirect straight to the final URL with no chains of one redirect leading to another, and update redirects left over from earlier redesigns so they point at the new destinations. Google advises keeping redirects for as long as possible, and generally for at least a year. Keeping them permanently is safer, because other sites may link to the old addresses for years.
Keep the content, titles and canonical tags
A redesign is a common moment to cut copy, and cutting copy from pages that rank is one of the quickest ways to lose traffic. Keep the substance of each ranking page, including its main headings, its answers to the questions people search for and its links to related pages. Improve it if you like, but check that nothing a searcher relied on has gone.
Then check the technical details page by page. Each new page should have a canonical tag pointing to its own new URL, never to the old one. Titles and meta descriptions should carry over unless there is a reason to improve them. Internal links should point straight at the new URLs instead of relying on redirects, which is part of good internal linking. Structured data, hreflang tags, image URLs and analytics tracking need the same check.
Sitemaps and Change of Address for domain moves
Publish an XML sitemap listing only the new URLs, and submit it in Search Console on launch day. It helps Google discover the new pages quickly. Google will recrawl the old URLs over time and follow the redirects it finds there.
If you are moving to a new domain, verify both domains in Search Console, put the 301 redirects live, and then use the Change of Address tool in the old domain’s property. It tells Google the whole site has moved. The tool is meant for moves between domains or subdomains. It isn’t needed for a switch from HTTP to HTTPS, and it doesn’t apply to URL changes within the same domain.
A step-by-step migration checklist
- Record benchmarks for traffic, key rankings and the number of indexed pages.
- Build the URL inventory and the redirect map, and have someone check it.
- Protect the staging site with a password so it can’t be indexed.
- Crawl the staging site to check titles, canonical tags, internal links and content.
- Test every redirect in the map on staging, looking for chains, loops and 404s.
- Launch at a quiet time for the business, with the team available that day.
- Check straight away that no noindex tag or robots.txt block has come across from staging.
- Submit the new sitemap and, for a domain move, use Change of Address.
- Crawl the full list of old URLs against the live site and confirm each one redirects correctly.
- Inspect the most important pages with the URL Inspection tool.
- Monitor Search Console and analytics daily for the first two weeks, then weekly.
Monitoring after launch
Expect some movement. Rankings can shift for a few weeks while search engines recrawl the site and process the redirects, and larger sites take longer. What matters is anything that doesn’t recover.
In Search Console, watch the Page indexing report for unexpected rises in “Not found (404)” and “Soft 404”, and use the Performance report to compare clicks for your key pages before and after. Check server logs or a fresh crawl for redirect errors, and fix them the same day. If a page that used to rank has dropped and stayed down, compare the old and new versions side by side. The cause is often something that was removed. New sites built on a JavaScript framework need extra checks, set out in SEO for JavaScript sites.
Questions people ask
Will a website redesign affect SEO?
It can, in either direction. If URLs, content and internal links are kept or properly redirected, rankings usually hold and can improve with a faster, clearer site. If pages disappear without redirects or lose their content, traffic to them falls.
How long should 301 redirects stay in place?
Google recommends keeping redirects for as long as possible, and generally for at least a year. Keeping them permanently is safer, because other websites, emails and bookmarks may point at the old URLs for many years.
How long does it take for traffic to settle after a migration?
A well-planned migration often settles within a few weeks, as search engines recrawl the old URLs and follow the redirects. Larger sites take longer. A drop that lasts well beyond that usually points to missing redirects or removed content.
Should we change domain and redesign at the same time?
Separating them is safer, because if traffic falls you can tell which change caused it. If you must do both together, the redirect map, content checks and monitoring matter even more.