In short: most websites lose 20 to 50% of their organic traffic after a redesign, almost always through avoidable mistakes: URLs that change without redirects, content that disappears, internal links that break and technology that was never tested. If you benchmark first, redirect every old URL 1-to-1 and watch Search Console for 2 weeks after launch, you keep your rankings and usually gain.
Why traffic drops after a redesign: the 7 causes
Google does not rank websites, Google ranks URLs. Every page has built up authority over the years through links, behavior and context. A redesign shakes up that structure and Google has to re-learn what lives where. When something goes wrong in that process, you drop. These are the 7 causes we find in almost every failed migration:
- URLs change without a 301 redirect. The page /services/kitchens becomes /kitchens, the old URL returns a 404 and 8 years of links evaporate.
- Content disappears. 'Nobody visited that page anyway' turns out to be the page that brought 40 leads a year on a long-tail keyword.
- Internal links break or change meaning. The new menu has 5 items instead of 12; the other 7 pages are now 4 clicks deep.
- Titles and metadata get overwritten. The new CMS generates 'Home | Company name' for every page.
- The staging site gets indexed, or the live site does not. A forgotten noindex is the classic that costs 3 weeks.
- Technology regresses. Slower, heavier scripts, JavaScript rendering Google cannot see, wrong canonicals or hreflang.
- Everything at once. New domain, new URLs, new content and new design in 1 day. Then you can no longer trace what caused the drop.
A temporary dip of 5 to 10% in the first 2 to 4 weeks is normal, Google has to recrawl. A 30% drop that has not recovered after 6 weeks is a mistake you have to find.
Before the build: benchmark, crawl and keyword mapping
Migration does not start at launch but at kickoff. Before anyone draws a design, you record what the current site is worth.
Benchmark. Export 16 months of clicks, impressions and positions per page and per query from Search Console. Note the top 50 pages by traffic and the top 100 queries by clicks. This is the yardstick the new site has to meet.
Crawl. Crawl the entire site with Screaming Frog or Sitebulb: all URLs, status codes, titles, meta descriptions, H1s, canonicals, hreflang, images and internal links. Keep the export. After launch you crawl the same list again.
Backlinks. Pull the pages with the most external links from Search Console, Ahrefs or Semrush. Under no circumstances may those URLs become a 404.
Keyword mapping. For every existing page, put the main keyword, current position and monthly traffic in a sheet. Add a column: new URL. Every row needs a destination, even if that is 'merge with' or 'retire'. This document is the heart of the migration and the basis for the redirects.
Bring in SEO at this point, not in the week before launch. The decisions about site structure, URL design and which content stays are being made now.
URL mapping and 301 redirects without chains
If you can keep your URLs, do. A redesign does not require a new URL structure, and unchanged URLs are the cheapest way to keep rankings. If you must change them, the table below applies.
| Situation | Action | Watch out for |
|---|---|---|
| URL stays the same | No redirect | Still check title, content and canonical |
| Page moves to a new URL | 301, 1-to-1 to the new page | Never to the homepage |
| 2 or more pages merged | 301 to the page that best covers the topic | Keep the content of both |
| Page retired without replacement | 301 to the nearest category, or 410 | Mass redirects to the homepage read as soft 404s |
| Old redirects from earlier migrations | Point them at the final destination | No chains from A to B to C |
| Images and PDFs | Redirect those too | Images rank in Google Images |
| Filter and parameter URLs | Canonical to the main page | Do not redirect if they are functionally needed |
| http, www and trailing slash | 1 variant, 1 hop | Test every combination |
Rules of thumb: every redirect in 1 hop, every redirect to the most relevant page, and every redirect permanent (301 or 308, never 302). Test the complete list on staging before launch, with the crawler in list mode. Keep the redirects for at least 1 year, preferably forever. On a real estate site with hundreds of listing pages or a car dealership with inventory URLs you handle this with patterns instead of individual rules, and you test the patterns on 20 random URLs.
Preserving content and internal links
Redesigns love to prune. Less text, more imagery, roomier layouts. Often better for visitors, but a loss for Google if the text that ranks disappears. The rule: for every page in the keyword mapping, the core of the content stays, even if the form changes. Move a long text into an expandable block or a separate information page, but do not delete it.
The same goes for internal links. Check in your crawl which pages receive the most internal links and make sure they still get them after the redesign: through the menu, the footer, contextual links in copy and related items. Pages that go from 3 to 6 clicks deep lose visibly. Keep your blog and your local pages too: they are rarely pretty, but often your biggest traffic source.
Titles, meta descriptions and H1s are carried over 1-to-1 from the crawl, unless you deliberately improve them. Do not let the CMS regenerate them.
Technical: hreflang, canonicals, sitemap and Core Web Vitals
The technical check before launch, on staging:
- Indexability. No noindex on live pages, but yes on staging. Robots.txt blocks nothing essential. Important content is in the HTML, not only after JavaScript.
- Canonicals. Every page points to itself, filter variants to the main page, and no canonical points to an old URL.
- Hreflang. On a multilingual site every language version linked reciprocally with the right code, plus x-default. One error here and Google ignores the whole block.
- Sitemap. Only the new, indexable URLs, with 200 status, no redirects, no 404s. Ready to submit right after launch.
- Structured data. Organization, LocalBusiness, Product, FAQ or Article: whatever the old site had, the new one has too, validated with the Rich Results Test.
- Core Web Vitals. LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1 on mobile. A new site that is slower than the old one is a worse site in Google's eyes.
- Tracking. GA4, Search Console verification, tag manager and consent on the new site, tested before launch.
Launch day: the checklist
Launch on a Tuesday or Wednesday morning, never on a Friday. That gives you 3 working days to spot problems. The order:
- Final crawl of the old site for a definitive archive.
- Activate redirects, switch DNS, check SSL.
- Remove noindex, check robots.txt, crawl the live site for 404s and redirect chains.
- Submit the new sitemap in Search Console. With a new domain: file a change of address.
- Manually visit the top 50 URLs from the benchmark through their old URLs.
- Check tracking: are sessions arriving, are conversions firing.
- Submit the 10 most important pages for inspection through URL inspection in Search Console.
What you do not do that day: rewrite content, switch domains or push a second major change. One variable at a time.
After launch: 2 weeks of monitoring in Search Console
The first 14 days decide whether the migration succeeds. Daily:
- Coverage and pages. Is the number of indexed new URLs growing and the number of old ones shrinking. Redirect any 404s in the report immediately.
- Performance. Clicks and impressions per day, compared with the same weekday before the migration. Look per page, not only at the total.
- Crawl stats. A spike is normal, Google is crawling the new structure. Server errors are not.
- Core Web Vitals and mobile. Field data lags 28 days, so rely on Lighthouse and PageSpeed Insights in the first weeks.
- Manual check. The top 50 queries from the benchmark, every 3 days.
After 2 weeks you move to weekly, after 8 weeks to monthly. If a page does not recover, check in this order: redirect present and in 1 hop, content present, internal links present, title and canonical correct, page in the sitemap. In 9 out of 10 cases the answer is in the first 3.
What it costs to do it right
An SEO migration for a small-business website of 20 to 100 pages takes 10 to 30 hours: benchmark and crawl, keyword mapping, redirect list, technical check, launch day and 2 weeks of monitoring. With a specialist that comes to €1,500 to €4,000 excl. VAT. Sites with thousands of URLs, several languages or a domain change sit between €5,000 and €15,000. Put that next to what 30% less organic traffic costs you per month and the sum is usually quick.
RABZI estimate: every website we rebuild includes the SEO migration in the price: benchmark, keyword mapping, redirects, technical check and 2 weeks of monitoring after launch. Website development starts at €4,950 excl. VAT (Launch), from €9,500 for Growth and from €19,500 for Flagship, including migration of large sites. If you have the site built elsewhere, we guide the migration alone from our SEO services, with an upfront audit from €1,450. What a new site costs beyond that is in how much a website costs.
Frequently asked questions
How long does it take for rankings to recover after a redesign? With a well-executed migration you see a stable picture after 2 to 4 weeks and the full effect after 6 to 8 weeks. A small dip in the first weeks is normal because Google has to crawl the new structure. A drop that persists after 6 weeks points to missing redirects, lost content or a technical error.
Do I have to change my URLs with a new website? No, and if you do not have to, do not. Unchanged URLs are the cheapest way to keep rankings. Change URLs only if the old structure is illogical or the new platform does not support it, and then redirect every old URL 1-to-1 with a 301.
Can I just remove old pages in a redesign? Only after the keyword mapping. Pages with no traffic, no links and no keyword can go, with a 410 or a redirect to the nearest category. Pages that rank or receive links you keep, or merge into a page that covers the topic.
What do I do if traffic collapses after launch? Check in this order: is there no noindex on the live site, do the old URLs return a 301 in 1 hop, are the content and the title present, do the pages receive internal links, are they in the sitemap. Look in Search Console for 404s and server errors. In most cases you find the cause within an hour.
Conclusion
Redesigning a website without losing rankings is not a matter of luck but of sequence: measure first, then build, then redirect 1-to-1, then watch closely for 2 weeks. Use the checklist above as your runbook and require your builder to tick off every step in writing. Facing a redesign and want to be sure your traffic comes along? Book an intro call, we assess your current site within 2 business days and tell you what it takes.