Traffic falls for mundane reasons far more often than dramatic ones. Work through the cheap checks first; most drops are explained before you get to the fourth one.
Check that it is real
Open analytics and compare like with like. A fortnight against the fortnight before, same days of the week. Seasonality catches people out: a roofing company is not in trouble because August was quieter than July.
Then check whether the drop is in all traffic or one channel. A fall in direct traffic with search steady is usually a tracking problem. A fall in search alone is a search problem.
Check that tracking still works
More apparent drops are broken analytics than anything else. The tag gets removed in a deploy, a consent banner starts blocking it by default, or a migration carries the old property’s ID. View the page source and confirm the measurement ID is there. Compare against server logs or your hosting analytics, which do not depend on a script running.
Check the site is actually up and indexable
In Google Search Console, look at the Pages report for a jump in Excluded. The specific ones worth finding:
- Blocked by robots.txt. A staging rule reached production.
- Excluded by noindex. A redesign shipped with a global noindex.
- Not found (404). URLs changed without redirects.
- Redirect error. A chain or a loop.
Also fetch your homepage with a plain request and read what comes back. A site that looks fine in your browser can be returning a 500 to crawlers.
Check for a recent change on your side
Nine times in ten the answer is here. Did you launch a redesign, move host, change CMS, prune pages, or let a certificate lapse? Line the drop up against your deploy history. If the dates match, you have your cause.
After a migration, the usual culprits are missing redirects, changed URL structure, lost title tags, or a robots directive that came along for the ride.
Check for a change on Google’s side
If nothing changed on your site, look at whether a core update landed around that date. Core updates move whole categories. The response is not a quick fix; it is improving the pages that lost ground, which takes months.
Distinguish between a drop in rankings and a drop in impressions. If impressions held but clicks fell, the results page changed around you: an AI overview, more ads, or a competitor with better titles.
Check which pages and which queries
Search Console’s Performance report, compared across the two periods, will tell you whether this is one page, one template, or everything. A single template losing traffic points at a code change. One page losing traffic points at a competitor or a lost link. Everything losing traffic at once points at a site level issue, which takes you back to indexability.
When to worry
Worry if: traffic to your commercial pages fell, the cause is not a tracking or indexing error, and it has not recovered in three weeks. That is a genuine ranking change and needs content work rather than a fix.
Do not worry if: the drop is in a long tail of informational pages, or it coincides exactly with a holiday, or it only shows in one analytics tool.