“We redesigned and our traffic fell off a cliff” is one of the most common things we hear from new clients. It is also almost entirely preventable, and the prevention has very little to do with design.
Why redesigns lose traffic
Four causes, in order of how often they turn out to be the culprit:
- URLs changed without redirects. Every ranking page became a 404, and every backlink pointing at it stopped counting.
- Content quietly disappeared. Pages that earned traffic were dropped because nobody checked what they were worth before deciding the new sitemap.
- Metadata was lost. Titles, descriptions and structured data did not survive the migration, so pages that used to describe themselves clearly now do not.
- The new site is slower. A heavier build undoes performance gains that were quietly holding rankings up.
Notice that none of these are aesthetic. The design is almost never the problem.
Start with a crawl, not a moodboard
Before any design work begins, you need an inventory of what exists and what it is worth. Crawl the site and pull, for every URL: current rankings, organic traffic over the last twelve months, backlinks pointing to it, and conversions attributed to it.
That list is the thing the redesign has to protect. Without it, decisions about the new structure are guesses, and some of those guesses will be expensive.
Decide what happens to every URL
Every existing URL gets one of four outcomes, decided in a spreadsheet before anyone opens a design tool:
- Keep. Same URL, same purpose, possibly improved content.
- Move. New URL, 301 redirect from the old one.
- Merge. Several thin pages combined into one stronger page, with 301s from all of them.
- Retire. Genuinely worthless and unlinked — 410, or 301 to the nearest relevant parent.
Merging is underused and frequently the biggest win available. Nine mediocre pages competing with each other for the same term will usually be beaten by one good page that absorbs all of them.
Redirects, done properly
A few rules that prevent most of the damage:
- Redirect to the most relevant page, not to the homepage. Bulk-redirecting everything to the homepage is treated as a soft 404 and passes almost nothing.
- Use 301, not 302. A temporary redirect tells search engines to keep the old URL indexed.
- Avoid redirect chains. A → B → C loses value and slows the crawl. Point A directly at C.
- Test on staging before launch. Run the old URL list through the staging redirects and check every single one resolves with a 200.
Carry the metadata across
Titles, meta descriptions, canonical tags, structured data, image alt text, Open Graph tags and internal anchor text all need to survive the move. On a large site this is scripted rather than done by hand, and then spot-checked.
Structured data is the one people forget most often. If your old pages had FAQ or Product schema earning rich results, and the new build does not, you will notice it in your click-through rate before you notice it in rankings.
Fix internal links, do not just redirect them
Redirects are a safety net for external links you do not control. Your own internal links should point directly at the new URLs. Leaving them pointing at redirects wastes crawl budget and slows every page that carries them.
Launch and then actually watch
Deploy in a low-traffic window with a rollback ready. Then, for at least six weeks:
- Watch Search Console for a spike in 404s or crawl errors
- Compare indexed page counts before and after
- Track your top twenty ranking pages individually, not just sitewide traffic
- Check Core Web Vitals field data as it accumulates on the new build
Sitewide traffic can look stable while your five best pages quietly collapse and seasonality masks it. Track them individually.
What normal looks like
Even a well-executed migration usually shows a small dip for a few weeks while search engines recrawl and reassess. That is expected. What is not expected is a sustained drop, or a fall that keeps deepening after a month — that means something is genuinely broken, and the sooner you look, the cheaper it is to fix.