Sudden drop in website traffic? A checklist for finding the cause
You open your analytics and the line has fallen off a cliff. Before you rewrite your homepage, work through the causes in this order. The first few are the most common and the cheapest to check.
1. Is your tracking still working?
A drop to almost nothing overnight is far more often broken tracking than a vanished audience. Check:
- The analytics script is still in the page source on your homepage and a few other pages. A layout or template change in the last deploy can remove it.
- Nothing is blocking it, such as a new Content Security Policy that doesn't allow the script's host.
- Your hosting provider's own request stats, if it has them. If those are flat while analytics fell, your tracking broke, not your traffic.
2. Is everything down, or one slice?
Break the drop down. This single step usually points straight at the cause:
- One source fell (for example a social post slid off the front page or a newsletter wasn't sent): a channel problem.
- One page fell: that page changed, lost its link, or lost its search ranking.
- One country fell: a holiday, an outage, or a network that blocks you.
- One browser or system fell: likely a compatibility bug you shipped.
3. Compare like with like
Compare the same weekday in previous weeks, not yesterday against today. Weekends, public holidays and school terms all move traffic. Also check whether the "drop" is just the end of an earlier spike: a post that brought a thousand visitors last week will always make this week look worse.
4. Check search
If most of your traffic comes from search, open Google Search Console and look at impressions, clicks and average position over the same dates. A fall in impressions means your pages are shown less (a ranking change or a search update); a fall in clicks with steady impressions means the listing is less attractive. Also check you didn't ship a noindex tag or a robots.txt rule that blocks the site.
5. Check where visitors used to come from
A link that was removed, a directory listing that expired, or a campaign that ended all show up as one referrer losing visits. Look at the top referrers for the previous period and see which fell.
6. Look at what you changed
List every deploy, redirect, URL change and design change in the days before the drop. Slow pages, broken internal links, a changed canonical tag and a new consent banner can all cut the traffic you see. If you log deploys as annotations, this step takes a minute instead of an hour.
7. Rule out bot filtering
If you recently changed your analytics or filtering settings, the "drop" may be bot traffic you used to count. A flat real audience with fewer bots looks like a fall.
Quick triage
| What you see | Most likely cause |
|---|---|
| Near zero from one moment | Tracking broke |
| One source or referrer down | Channel lost its audience or link |
| Search traffic down, others steady | Ranking or indexing change |
| Gradual slide for weeks | Seasonality or slow ranking loss |
| One country or browser down | Outage, holiday, or a compatibility bug |
Using agentlytics for this
The overview shows the change against the previous period, and you can click any source, page, location, browser or system to filter the whole dashboard to it, then click a bar to narrow to a single day. Spike detection looks for sudden jumps, so for a drop you use the comparison and the filters. You can also ask your agent: "compare this week's traffic with last week by source and page, and tell me what fell". See why traffic spiked for the other direction.
See it on your own site
agentlytics is cookieless analytics your coding agent can read. Free for 5,000 pageviews a month, no card.
Start free See the live demoAdd agentlytics analytics to this project. Follow the instructions at measuremy.site/llms.txt