Check the shape of the drop first. A cliff edge overnight is almost always something you or your developer changed - a noindex tag, a broken redirect, a robots.txt block. A gradual slide over weeks is competitive or algorithmic. The two need completely different responses.
The instinct when traffic falls is to assume Google has done something. Usually Google has not. Most sudden drops are self-inflicted, recent, and reversible within days — provided you diagnose before you start changing things.
Work through this in order. It is arranged by how often each cause turns out to be the answer.
First: what shape is the drop?
Open Google Analytics or Search Console and look at the line, not the number.
| Shape | Almost always means |
|---|---|
| Cliff edge — normal one day, gone the next | Something changed on the site. Technical fault. |
| Gradual slide over several weeks | Competition, or an algorithm update. |
| One page collapsed, everything else fine | That page lost its ranking, or its URL changed. |
| Whole site down proportionally | Site-wide technical issue, or a manual action. |
The date matters as much as the shape. Note the exact day it started, then ask what happened that week. A launch, a plugin update, a hosting change, a developer "just tidying something up".
The technical causes, in order of frequency
1. A noindex tag left behind
The most common cause of an overnight collapse. Staging sites are built with search engines blocked. Somebody forgets to remove that on launch day.
Check: view your page source and search for noindex. Or use URL Inspection in Search Console — it tells you plainly whether indexing is allowed.
2. robots.txt blocking the site
Check: visit yourdomain.com/robots.txt. If you see Disallow: /, that is your answer. In WordPress, the "Discourage search engines" setting does this silently.
3. Missing redirects after a rebuild
If URLs changed and nothing points the old addresses at the new ones, every ranking and backlink those pages held now leads to a dead end.
Check: the Pages report in Search Console for a spike in "Not found (404)". Then search site:yourdomain.com and click a few older results.
4. The site is slow or intermittently down
If Googlebot cannot reach the site reliably it crawls less, and if it fails repeatedly pages start dropping out.
Check: Crawl Stats in Search Console for a rise in server errors. Ask your host about downtime around the date the drop began.
5. Analytics tracking broke
Worth ruling out early, because it is the happiest outcome. If a redesign dropped the tracking code, traffic looks like it collapsed while nothing actually changed.
Check: does Search Console show the same fall as Analytics? Search Console does not depend on your tracking code. If Search Console is steady and Analytics collapsed, your problem is measurement, not traffic.
6. HTTPS or certificate problems
An expired SSL certificate produces browser warnings that stop visitors instantly.
Check: load the site in a private window and look for warnings.
Then check for a manual action
Search Console, Manual Actions. This is rare, and if there is nothing there, there is nothing there — it is not hidden anywhere else.
Also check Security Issues in the same menu. A hacked site injecting spam pages produces exactly this pattern, and it is more common on unmaintained WordPress installations than owners expect.
Then consider an algorithm update
Only after the technical checks. Roughly:
- Did the drop start on a date matching a known update?
- Did it affect the whole site rather than a section?
- Are competitors in the same results also moving?
If it is an update, there is no switch to flip. The response is improving the pages that lost ground — better answers, better structure, genuine expertise — rather than looking for a technical fix that does not exist.
Then the unglamorous explanations
Two that get overlooked because they are boring:
Seasonality. Compare with the same period last year rather than last month. A restaurant in January and a restaurant in July are different businesses.
A competitor did something. Search your main terms. If someone new is above you with a genuinely better page, that is not a fault to fix — it is a page to beat.
What not to do while diagnosing
- Do not change ten things at once. You will never know which mattered.
- Do not use the Removals tool on old URLs. It destroys the value redirects are meant to recover.
- Do not rebuild the site. If the cause is a leftover noindex tag, a rebuild fixes it by accident and charges you for everything else.
- Do not buy backlinks in a panic. This turns a recoverable problem into a manual action.
What to record while you diagnose
Whatever the cause turns out to be, keep a short written log: the date the drop started, what you checked, what you found, what you changed and when. Two reasons.
First, if the drop has more than one cause — which happens more often than people expect — a log stops you chasing your own tail. Second, if you need to bring in help later, a documented timeline turns a three-hour investigation into a twenty-minute one.
Note the deploy dates too. "Traffic fell on the 14th, we pushed a plugin update on the 13th" is most of a diagnosis on its own.
How long recovery takes
| Cause | Typical recovery once fixed |
|---|---|
| noindex tag or robots.txt block | Days to two weeks |
| Missing 301 redirects | Two to six weeks |
| Server errors or downtime | One to three weeks |
| Hacked site, once cleaned | Two to eight weeks |
| Algorithm update | Months, and only with genuinely improved pages |
| Competitor overtook you | However long it takes to build a better page |
Once the fix is live, submit the sitemap again and use URL Inspection on your most important pages to request a recrawl. Do that for the handful that matter rather than for everything — there is a daily quota and it is not needed at scale.
Then leave it alone. Making further changes every few days while Google reprocesses means you will never know what worked.
The first ten minutes
- Look at the shape of the line and note the exact start date.
- Ask what changed that week.
- Check for
noindexin the page source. - Check robots.txt.
- Check Manual Actions and Security Issues in Search Console.
- Compare Search Console against Analytics to rule out a tracking fault.
- Check the Pages report for a 404 spike.
In our experience the majority of sudden drops are answered somewhere in that list, usually by item three or item seven. The remainder need real work — but you cannot tell which you have until you have ruled the simple ones out.
Frequently asked
Why did my website traffic drop suddenly?
A sudden overnight drop is almost always a technical change rather than an algorithm update. The most common causes are a leftover noindex tag from a staging site, a robots.txt blocking crawlers, or missing 301 redirects after a rebuild.
How can I tell if a traffic drop is technical or algorithmic?
Look at the shape. A cliff edge from one day to the next indicates something changed on the site. A gradual slide over several weeks points to competition or an algorithm update. The two need entirely different responses.
How do I check if my site is blocked from Google?
Look at your page source for a noindex tag, visit yourdomain.com/robots.txt to check for Disallow rules, and use URL Inspection in Search Console, which states plainly whether indexing is allowed.
Could my traffic drop just be a tracking problem?
Yes, and it is worth ruling out first. Compare Search Console with Google Analytics. Search Console does not rely on your tracking code, so if it shows steady traffic while Analytics collapsed, the problem is measurement rather than actual traffic.
Related guides
- Is your website breaking EU accessibility law? What the EAA means for small businesses
- Is your website an ADA lawsuit risk? What US small businesses need to know
- Which SaaS should you build? How to find an idea people will actually pay for
Book a free consultation.
A 30-minute call where we open your site together and go through what is costing you enquiries. No charge, no obligation.
