Your new site launched, everyone was pleased with it, and two weeks later organic traffic is down by a third. This is one of the most common and most recoverable SEO problems there is — and the reason it is recoverable is that relaunch drops almost always have a mechanical cause rather than a mysterious one.
What follows is a diagnostic order. Work it top to bottom, because the early checks are both the most likely culprits and the fastest to fix. If you are reading this before a relaunch, our guides on redesigning without losing SEO are the version that prevents all of this.
First, Confirm It Is Real
Before diagnosing, rule out two things that look like a drop and are not.
Analytics broke, not rankings. A new site frequently means a new tracking setup, and a missing or misconfigured tag will show traffic falling off a cliff. Check Search Console clicks and impressions, which are independent of your analytics. If Search Console is steady and analytics collapsed, you have a measurement problem, not an SEO one — and you should fix it immediately before you lose weeks of data.
Seasonality or an algorithm update. Compare against the same period last year, not last month. And check whether a known Google update landed in the same window, because attributing an update to your relaunch sends you looking in the wrong place. Our core update recovery guide covers that case.
If Search Console clicks are genuinely down, continue.
Check One: Redirects
This is the cause in most cases, so start here.
When URLs change and old ones are not redirected, every ranking signal those pages accumulated is thrown away. The old URL 404s, the new page starts from nothing, and anyone arriving from a search result or an old link hits an error.
What to check:
- Export your old URL list from Search Console, your old sitemap, or analytics going back twelve months. You need to know what existed.
- Test each one. Does it return 301 to a relevant new page? Not the homepage — a relevant page. A mass redirect of everything to the homepage is treated roughly as a soft 404 and preserves very little.
- Look for chains. Old URL redirecting to a second URL which redirects again. Each hop dilutes and slows things. Point the original straight at the final destination.
- Check for loops, which break the page entirely.
- Check the protocol and host. http to https, www to non-www. A relaunch sometimes changes one of these without anyone noticing.
Search Console's coverage report, filtered to "Not found (404)", is the fastest way to see what is currently breaking.
Check Two: Is the New Site Indexable At All?
A surprising number of relaunch drops come down to a staging configuration that shipped to production.
- robots.txt — a
Disallow: /left over from staging will remove your entire site. Check it first; it takes ten seconds. - noindex tags — staging environments are often set to noindex at template level. If that template went live, so did the directive.
- Canonical tags pointing at staging. Common with content management systems that hardcode a base URL. If your live pages canonicalise to a staging domain, you are telling Google the real page is somewhere it cannot reach.
- The sitemap — does it exist, does it list the new URLs, and has it been submitted? And does it still list the old ones?
Check Three: Did the Content Survive?
Designers simplify, and simplification removes text that was doing work.
Compare the old and new versions of your most important pages — Search Console will tell you which earned the most clicks. Look for:
Word count collapse. A 1,200-word service page that became 300 words of elegant copy over a hero image has lost the substance it ranked on.
Headings gone. If H2s and H3s became styled paragraphs, the structure that told search engines what the page covers has disappeared.
Titles and meta descriptions overwritten. New sites often generate these from a template, replacing carefully written ones with "Services | Company Name".
Internal links lost in the redesign. A new navigation and new templates frequently remove contextual links from body copy, changing which pages receive authority.
Pages that quietly did not get rebuilt. Content inventories slip. Ask whether every old page has a new equivalent, and if not, whether that was a decision or an oversight.
Check Four: Rendering
If the new site is built on a JavaScript framework and the old one was not, this is a live possibility.
View the page source — the raw source, not the browser inspector — and search for a sentence you can see on screen. If the text is not in the source, it is rendering client-side, and search engines may not see it. Search Console's URL Inspection tool will show you the rendered HTML Google actually got.
This one is less common than redirects but considerably more damaging when it happens, because the page looks perfect to everyone except a crawler.
Check Five: Speed and Core Web Vitals
A heavier new site can lose ground, though this is usually a contributing factor rather than the whole story. Check Core Web Vitals in Search Console by template rather than as a single site-wide figure, and compare against your pre-launch data if you have it.
Be careful about priority here. If you have broken redirects and a slower site, fix the redirects first. Speed is a tiebreaker; indexation is binary.
How Long Recovery Takes
Honest answer: it depends on what you fix.
Redirect and indexation fixes often recover quickly — days to a few weeks — because the pages were already capable of ranking and simply became unreachable. You are restoring access rather than building something new. Requesting indexing on your most important URLs can speed up the recrawl.
Content that was cut takes longer, because you are rebuilding substance and waiting for it to be reassessed. Weeks to a couple of months.
Partial recovery is common. Most sites that fix the mechanical causes get most of the traffic back. Getting every last position is harder, particularly if competitors gained ground during the gap.
The thing not to do is wait. The longer broken redirects persist, the more the old signals decay, and recovery gets harder rather than easier. This is the one SEO problem where speed of response genuinely changes the outcome.
Preventing the Next One
Relaunches do not have to cost traffic. What separates the ones that do from the ones that do not is a pre-launch checklist run on staging: a full URL inventory with the redirect map built from it, content parity confirmed on your top pages, titles and metas carried across, robots and noindex verified, and a baseline recorded so you can tell what moved.
That is a day of work and it prevents the problem this article exists to solve.
If you have had a drop and want someone to find the cause quickly, our free SEO audit covers the technical checks above, and our SEO audit service goes through it in full with each finding scoped as a change your developers can action.
Frequently Asked Questions
Why did organic traffic drop after my website relaunch?
Most commonly because old URLs were not redirected to relevant new ones, so the ranking signals those pages had accumulated were lost. Other frequent causes are a staging noindex or robots.txt shipping to production, canonical tags pointing at a staging domain, and content cut during the redesign.
How do I recover organic traffic after a redesign?
Work in order: confirm the drop is real using Search Console rather than analytics, audit and fix redirects from a full list of old URLs, verify the new site is indexable, compare content on your highest-earning pages against the old versions, then check rendering and Core Web Vitals.
How long does it take to recover rankings after a migration?
Redirect and indexation fixes often recover within days to a few weeks, because the pages were already able to rank and had simply become unreachable. Rebuilding content that was cut takes weeks to a couple of months. Most sites recover most of the loss once the mechanical causes are fixed.
Is it normal for traffic to drop after a website launch?
A brief dip while Google recrawls is common. A sustained drop of a quarter or more is not normal and indicates a specific technical cause, almost always something on the checklist above rather than an unavoidable consequence of relaunching.
Could my analytics be wrong rather than my traffic?
Yes, and it is worth ruling out first. New sites often mean new tracking, and a missing or misconfigured tag makes traffic appear to collapse. Check Search Console clicks and impressions — if those are steady while analytics fell, you have a measurement problem to fix urgently.