Why Did My Website Traffic Drop Overnight? The Four Causes, Ruled Out in Order

Traffic that disappears between one day and the next produces a specific kind of panic, and the panic itself is the biggest risk. Most of the expensive mistakes in algorithm recovery happen in the first 48 hours, made by people acting before they know what moved.

This page is the triage. It works through the four possible causes in the order that rules them out fastest, so that within about an hour you know which of the four you are dealing with and what to do next. Roughly one in five drops I audit turns out to be technical rather than algorithmic, and those are fixable the same week, so it is worth doing this properly before assuming the worst.

What are the four causes of a sudden traffic drop?

Every overnight drop I have diagnosed falls into one of four categories. They look identical in a traffic graph and they need completely different responses, which is why guessing is expensive.

Cause	Measurement (how to confirm it)	Time to rule out	Recovery clock
Technical fault	Indexing report shows exclusions, or a noindex or canonical change on live pages	10 minutes	1 to 4 weeks after recrawl
Manual action	Security and Manual Actions report in Search Console is not empty	1 minute	Days to 4 weeks after approval
Reporting change	Impressions moved but clicks and position did not, or analytics tag changed	15 minutes	Nothing to recover
Algorithm update	Break date falls inside a confirmed rollout, loss is broad across templates	20 minutes	Waits for the next core update

Notice the last column. Only one of these four requires waiting months. The other three can move within weeks, which is why ruling them out first matters more than confirming the one everybody assumes.

How do I check for a manual action?

Open Search Console, then Security and Manual Actions, then Manual actions. If the report says no issues detected, you do not have a manual penalty and you can stop considering it entirely.

This takes one minute and it is the single highest-value check available, because a manual action is the one cause that comes with an explicit message naming the problem. If the report is not empty, everything else on this page is irrelevant to you and the process is a reconsideration request instead, covered in the reconsideration request guide.

Most people skip this check because they assume they would have been notified. Notifications go to the verified Search Console account, which on an inherited site is frequently a developer or an agency who left years ago. Check the report itself rather than your inbox. The wider distinction is covered in manual action versus algorithmic penalty.

How do I rule out a technical fault?

Technical faults cause the most dramatic overnight drops, because a single wrong tag can remove an entire site from the index in one crawl cycle. They are also the fastest to fix, which makes them worth eliminating before anything else.

• Check for a stray noindex tag on live pages. Why: A staging environment shipped to production carries its noindex with it. View source on your homepage and search for the word noindex. This is the most common catastrophic cause and it takes thirty seconds to check.
• Open the Pages report under Indexing in Search Console. Why: It names the exclusion reason for every URL Google chose not to index. A sudden jump in excluded pages, with a reason attached, is a diagnosis rather than a symptom.
• Check robots.txt for a blanket disallow. Why: Visit yoursite.com/robots.txt directly. A Disallow line covering the whole site blocks crawling entirely, and it survives until someone notices.
• Check your canonical tags on a few important pages. Why: A canonical pointing every page at the homepage collapses your entire index into one URL. It is a common CMS or plugin misconfiguration and it produces exactly the overnight pattern.
• Confirm the site actually loads for Googlebot. Why: Use the URL Inspection tool and fetch a live page. A server error, a firewall rule or an aggressive bot blocker can shut Google out while the site works perfectly in your browser.

If the Pages report shows a jump in excluded URLs, the reason it gives is the diagnosis. Google deindexed my pages explains what each exclusion reason means and how long each takes to reverse.

On WordPress, a plugin or theme update is the most common way these faults arrive, usually without anyone recording it: traffic dropped after a WordPress update covers the seven things that break and how to find which.

If any of these turns up a problem, fix it and stop. Recovery follows recrawling, typically one to four weeks, and there is no reassessment cycle to wait for. Requesting indexing on your most important pages speeds it up.

If the drop began within days of a redesign, migration or platform change, the cause is almost certainly mechanical rather than algorithmic, and it is diagnosed differently. Start with traffic dropped after a website redesign instead of continuing here.

How do I tell a reporting change from a real drop?

Some drops are not drops. The numbers changed, the site did not, and there is nothing to fix. This is more common than most owners expect and it has caught out large sites repeatedly.

The test is to look at three metrics together rather than clicks alone.

Clicks	Impressions	Average position	What it means
Fell	Fell	Got worse	A genuine ranking loss
Fell	Held	Held	Click displacement, not a demotion
Held	Fell	Improved	A reporting change, nothing happened
Fell	Fell	Held	Demand fell, often seasonal

The third row is the one that catches people. In September 2025 Google removed the ability to load 100 search results per page, and impressions fell across a huge number of sites overnight while clicks and rankings were untouched. Average position appeared to improve, because the impressions being removed were low-position ones that had never earned clicks. Nothing had happened to those sites at all.

The second row is the other one worth knowing, because it is now extremely common. If your rankings held and your clicks fell, an AI Overview or another SERP feature is answering the query above your result. That is displacement, and it will not recover at the next core update because nothing was demoted. An AI Overview is only one of eight reasons this happens, and the others are more common: traffic dropped but rankings the same works through all eight.

Also check the boring possibility: did your analytics tag get removed in a deploy? A traffic graph that goes to literal zero rather than merely low is almost always a tracking failure, not a ranking one.

The fourth cause, seasonality, is ruled out with a single comparison: the same weeks against last year rather than against last month. That test, and what each combination of metrics means, is in is my traffic drop seasonal or an algorithm update.

How do I find the exact date the drop started?

The date you noticed is not the date it started, and the difference matters enormously. In periods where several updates ran close together, being three days out points at the wrong cause and sends the entire project in the wrong direction.

1. Open Search Console, Performance, Search results.
2. Set the date range to the last 6 or 12 months rather than the default 3.
3. Export the Dates tab as CSV.
4. Paste it into the Search Console drop analyzer, which finds the break point using a centred moving average and tells you whether you lost rankings or lost clicks.
5. Match that date against confirmed updates with the date checker.

Both tools run entirely in your browser and nothing is uploaded. If no confirmed update matches your date, that is normal rather than mysterious: Google confirmed four updates in the whole of 2025 while measured volatility stayed high. Check the volatility sensor for that date, then work through the seven causes of a drop with no update.

How do I know if it was an algorithm update?

Two things have to line up. The date has to fall inside a confirmed rollout window, and the scope of the loss has to match what that kind of update does.

Scope is the stronger signal, and it is the one most people skip. A core update reassesses quality across a whole site, so the loss is broad. A narrower system hits one page type. Competitors taking a handful of queries is not an algorithm event at all.

• Most pages lost a similar share. Points at: a site-level quality judgement, usually a core update.
• One folder or template fell while the rest held. Points at: a narrower system or a template problem, which is faster and cheaper to fix.
• A handful of pages carry the whole decline. Points at: competitors or SERP features, not an update, which is worked through in a competitor overtook me overnight.
• Traffic went to near zero rather than falling partially. Points at: a policy violation or a technical fault, not a quality reassessment.

Segment by device as well as by page. A loss confined to one device is a template or rendering problem rather than an algorithmic one, and it is covered in traffic dropped on mobile but not desktop.

The page scope analyzer settles this from a Search Console comparison export, and it also lists the pages that gained. That list is usually more useful than the losers, because whatever is different about your survivors is what the update rewarded.

This is not your cause if

Worth stating plainly, because a lot of recovery budget is spent on problems people did not have.

• It is not an algorithm update if your average position held while clicks fell. Nothing was demoted, so nothing will be restored at the next reassessment.
• It is not a penalty if the Manual Actions report is empty. There is no appeal, no message and nothing to submit, because no human decision was made.
• It is not a site-wide quality problem if only one section fell. A site-level judgement does not spare your other templates.
• It is not a spam problem if nothing on your site engages a published spam policy. Spam systems enforce specific policies; they do not assess general quality.
• It is not Core Web Vitals if the drop was sudden. Your speed scores were the same the week before. Experience signals are a tie-breaker, not a cause of overnight collapse.

What should I do before I know the cause?

Two things, and then nothing else until the diagnosis is done.

Record your baseline. The 28 days before the drop began is the number any recovery will be measured against later. Export it now, because Search Console retains only 16 months and the comparison you need is the one before the decline, not the one after it.

Change nothing else. Every change made before the cause is known destroys your ability to attribute what happens next. If a core update is rolling out, rankings move in both directions for 12 to 24 days and sites regularly recover part of a loss before it finishes with no intervention at all. Acting mid-rollout converts a diagnosable situation into a guess.

The full sequence for the first two days is in the first 48 hours checklist, the reactions that cause the most self-inflicted damage are in what not to do in the first week, and once you have a cause, how long recovery takes sets the timeline expectations for each type.

Frequently asked questions

Can Google traffic really drop overnight?

Yes. A technical fault such as a noindex tag or a broken canonical can remove pages within one crawl cycle, and a short algorithm rollout can move rankings within days. A genuinely instant drop to near zero is more often technical than algorithmic.

How long should I wait before reacting to a traffic drop?

Rule out technical causes and manual actions immediately, since both are fast and both change everything. Beyond that, wait until any rollout completes before measuring, because core updates run 12 to 24 days and rankings move in both directions throughout.

Why did my traffic drop with no Google update?

Because Google confirms only a fraction of what it ships. It confirmed four updates in 2025 while measured volatility stayed high. A drop with no matching announcement is normal, and the other common causes are technical faults, reporting changes, competitors and seasonality.

Is a sudden traffic drop always a penalty?

No, and penalties are the least likely of the four causes. A penalty means a manual action, which appears as a message in Search Console. If that report is empty you do not have one, and the cause is algorithmic, technical or a reporting artefact.

Should I change my site while traffic is down?

Not until you know the cause. Changes made before diagnosis remove your ability to attribute any later recovery, and several common reactions, including mass deletion and uploading a disavow file, are slow to reverse and capable of causing further harm.

How much of a drop is normal fluctuation?

Day-to-day movement of 10 to 15 percent is ordinary and not worth investigating. What matters is a sustained step down that holds for more than a week, rather than a single bad day or a weekend dip.

How long to hold off before changing anything, and the situations where waiting is the wrong answer entirely, are in how long should I wait before doing anything.