What to Do When Organic Traffic Drops

The instinct when traffic falls is to start fixing. That usually adds new problems on top of the original one and makes the cause harder to identify. The first job is diagnosis, and it can generally be completed in an afternoon.

Establish exactly when, and how much

Find the precise date the drop began, not the week you noticed it. Then determine the scope: all pages or some, all queries or some, all devices or one, all countries or one.

A sharp drop on a single date points at something that changed — a deployment, a migration, a manual action. A gradual decline over weeks points at algorithmic reassessment or competitors improving. These need completely different responses, and the pattern tells you which.

Search Console's comparison view over a sensible period is where this is established, not the analytics traffic graph.

Check the things that are quick and decisive

Manual actions in Search Console. Index coverage changes. Whether robots.txt changed. Whether a noindex tag appeared. Whether the site is returning correct status codes. Whether it is accessible at all to a crawler.

These take ten minutes collectively and explain a large share of sudden drops. An accidental noindex deployed with a release is one of the most common causes and one of the easiest to miss, because the site looks entirely normal.

Compare the date against your own history

Check deployments, plugin updates, hosting changes, DNS changes and content edits against the drop date. Then check whether a broad algorithm update was rolling out at that time.

If the drop coincides with your own release, start there — it is far more likely than an algorithm update that happened to affect only you. Teams reach for the algorithm explanation because it requires no admission, and it is usually wrong.

If it was a migration, check redirects

This is the single most common cause of lasting traffic loss. Crawl the old URL list and check that every one returns a 301 to a relevant destination, not a 404 and not a redirect to the homepage.

Redirecting everything to the homepage is treated similarly to a 404 and is a frequent shortcut. Check for chains as well — a redirect pointing to another redirect dilutes signals and slows crawling.

If it is none of those

Then it is likely content or competitive. Look at which specific queries lost position and examine what now ranks for them. Sometimes the answer is that the search results themselves changed — an AI summary now answers the query, or new result formats pushed organic results down.

That last case is real and increasingly common, and it is worth identifying because it changes what you can do. A query being answered on the results page is not a problem you fix by rewriting the page.

Then fix one thing at a time

Having identified a cause, change that. Changing eight things simultaneously and watching traffic recover teaches you nothing about what mattered, and if it does not recover you have no way to reason about it.

Recovery from technical causes can be quick once fixed. Recovery from quality reassessment is slower and is not guaranteed, particularly after broad updates.