Seeing organic traffic drop sharply a few days after a new website goes live is the most common and most expensive surprise in a redesign. The cause is rarely the design itself; it's a migration that wasn't planned: missing pages, URLs that aren't redirected, a forgotten noindex tag. The good news is that almost all of these losses are preventable.
How risky is your change?
Not every redesign carries the same risk. Before planning, work out which group your project falls into:
- Only the design changes; URLs and content stay the same: low risk. Still check that titles, internal links and page speed are preserved.
- The CMS or URL structure changes: medium to high risk. Every old URL needs to be redirected to a new equivalent.
- The domain changes: high risk. The whole site moves to a new address, and it takes time for Google to reassign its signals.
- Several sites merge into one: the most complex scenario. What stays, what merges and what goes has to be decided page by page.
1. Before launch: take a snapshot of where you are
If you don't know what you have, you won't notice what you've lost. Before the migration, record:
- A full list of URLs on the current site, from a crawling tool
- The pages and queries with the most clicks and impressions in Search Console
- The landing pages that bring the most visits and conversions in GA4
- The pages that attract the most links from other sites
- Your current rankings for important keywords
This list becomes the basis of your redirect plan and lets you compare results after launch.
2. The URL map: the heart of the migration
Build a table that maps every old URL to the most relevant new one. This table is the source for your permanent (301) redirects. Keep in mind:
- Don't change URLs if you don't have to. The safest redirect is the one you never need.
- Use permanent (301) redirects, not temporary (302) ones. A permanent redirect clearly signals that the old page's signals should pass to the new one.
- Don't redirect everything to the homepage. Google often treats mass redirects to an irrelevant page as “soft 404s”. Send a page with no equivalent to the closest parent category; if there's genuinely no match, returning a 404 or 410 is a more honest signal.
- Avoid redirect chains. Instead of A to B to C, redirect A straight to C. Update old redirects left over from previous redesigns, too.
- Don't forget images and files. Images that get traffic from image search and PDFs that other sites link to should be redirected as well.
Photo: Nick Fewings / Unsplash
3. Keep the content that ranks
A redesign is often used as a chance to “simplify” content. But unknowingly removing pages or passages that bring traffic is one of the most common causes of lost rankings. For the valuable pages you identified in step one, keep or improve the titles, meta descriptions, H1s and main copy. Carry structured data, canonical tags and, on multilingual sites, hreflang markup over to the new templates in full; for hreflang, see our guide to multilingual websites.
4. Keep staging closed, and remember to open it at launch
The test version of the new site must not be indexed, and the most reliable way to ensure that is password protection. Relying only on a noindex tag or a robots.txt block is risky: forgetting to remove them on launch day can wipe the site out of search results entirely. It's the most common, and most easily prevented, migration problem we see.
5. Launch-day checklist
- Redirects from the URL map have been bulk-tested; each goes to the right page in a single hop.
- robots.txt doesn't block the site, and no pages carry a leftover noindex tag.
- Canonical tags point to the new URLs.
- A new XML sitemap has been generated and submitted to Search Console.
- Internal links point directly to new URLs, not through redirects.
- Analytics and conversion tags work; forms have been tested.
- If the domain changed, the Change of Address tool in Search Console has been used.
- Monitoring for 404 errors is in place.
6. The weeks after launch
Some ranking fluctuation in the first few weeks is normal; Google needs time to crawl the new structure and reassign signals. During this period, keep an eye on the indexing and 404 reports in Search Console, compare against your step-one data, and add redirects for any URLs you missed. Keep redirects in place for at least a year, ideally indefinitely, and if the domain changed, keep the old domain registered. We cover crawling and indexing in detail in our technical SEO guide.
Frequently asked questions
Is a traffic drop after a redesign inevitable?
No. Short-term fluctuation is normal, but after a well-planned migration traffic returns to its previous level within weeks, and often exceeds it if content and speed improved. A sharp drop that persists for weeks usually points to missing redirects, removed content or an indexing block.
Does changing domain hurt SEO?
Done correctly, most signals transfer to the new domain, but the transition takes longer than in other scenarios. Where possible, do a domain change and a redesign as two separate steps rather than at once; it makes the source of any problem much easier to find.
Should I redesign my site or improve it?
Not every problem needs a new site. We cover how to make that call in our article on when to redesign your website.
In short
The secret to a successful migration is a plan that starts weeks before launch day: a record of where you are, a complete URL map, protected content and a checklist applied with care. At Kasel, we treat the SEO migration as an integral part of design and development in our website redesign projects. If you're planning a redesign and don't want to put your rankings at risk, get in touch.
