Someone calls me in a panic — traffic is down 30 percent and they want to know what to do. My first question is always the same: when did it drop, and was it gradual or sudden? That answer determines almost everything about where to look next.

Acting before you understand the cause is how a bad situation gets worse. I have seen sites undo perfectly good optimization trying to recover from what turned out to be a temporary algorithm fluctuation. I have seen teams spend three months on content quality work when the actual problem was a misconfigured robots.txt. Diagnosis first. Always.

Step One: Establish the Timeline

Pull organic traffic from Google Analytics or Search Console and look at it day by day, not week by week. Find the exact date the drop started. Then do two things with that date.

First, check it against Google algorithm update history. Google publishes confirmed core updates, spam updates, and product reviews updates. Independent trackers like Semrush Sensor or Mozcast track unconfirmed volatility. If your traffic drop lines up within a few days of a confirmed or suspected update, that is your first hypothesis.

Second, check your deployment logs. Was anything changed on the site around that date? A plugin update, a theme change, a new developer deployment, a hosting migration. Technical changes frequently cause traffic drops that get mistaken for algorithm issues.

The Four Main Causes of Traffic Drops

In my experience, organic traffic drops fall into four categories, and the symptoms of each are distinct enough that you can usually identify which one you are dealing with before doing deep investigation.

Algorithm update impact: The drop correlates with a known or suspected Google update. It tends to affect certain types of pages more than others — product review pages, affiliate content, thin informational pages, or YMYL topics depending on which algorithm changed. Rankings decline across a consistent topic or page type, not randomly. Recovery from algorithm updates typically requires addressing whatever Google determined was lacking — usually content quality, authority signals, or experience signals. The overlap between content marketing and SEO is especially relevant here, since quality recovery usually requires both editorial improvement and distribution thinking.

Technical failure: The drop is sudden, severe, and often affects the entire site rather than specific page types. Common culprits: accidental noindex tags deployed sitewide, robots.txt blocking Googlebot, broken canonicals pointing to wrong pages, a migration that did not redirect correctly, or site speed degrading past a threshold that affects crawling. Technical issues can cause dramatic drops very quickly — 50 to 80 percent in days — and they can be fixed and recovered from relatively quickly once identified.

Content quality or relevance issues: The drop is gradual, often over weeks or months, and affects pages with thin content, duplicate content, or content that no longer matches current search intent. This can also happen when competitors have significantly improved their content and yours has not kept pace. Recovery requires substantive content improvement, not just minor edits.

Competitor or SERP changes: Your rankings held but your traffic fell because Google added a featured snippet, a people-also-ask block, a map pack, or a knowledge panel that now sits above organic results and captures clicks. Or a strong competitor entered the space and is now outranking you for terms you previously owned. This category is often missed because people check rankings and they look fine — but the SERP landscape changed around those rankings.

The Technical Checklist to Run First

Before assuming the cause is content or algorithm, rule out technical issues. They are the most fixable and the fastest to confirm.

  • Check Google Search Console Coverage report for indexing errors or excluded pages
  • Verify robots.txt is not blocking Googlebot from important sections
  • Check for sitewide noindex tags (look at the page source of multiple pages)
  • Run a crawl with Screaming Frog and look for 404s, redirect loops, and canonical issues
  • Check Core Web Vitals in Search Console for any sudden deterioration
  • Verify structured data is still valid using the Rich Results Test
  • Check if the XML sitemap is still accessible and current

If you find a technical issue, fix it, request re-indexing for affected pages in Search Console, and monitor. Recovery from technical issues is usually faster than recovery from algorithm impacts — often within 2 to 6 weeks of the fix going live.

Diagnosing an Algorithm Hit

If the timeline matches an update and technical issues are ruled out, you need to identify what the update was targeting and whether your site fits that profile.

For a core update, Google has consistently stated that the fix is not to look for technical tricks but to address genuine quality issues. Ask honestly: are the pages that dropped actually the best available answer for what the user is searching for? Do they demonstrate real expertise and experience? Do they have issues with thin content, excessive ads, poor mobile experience, or misleading titles?

Pull the specific pages that lost the most traffic and rankings. Look at what is now outranking them. What does that content have that yours does not? More depth, more specificity, more recent information, more credible authorship signals? Often the pages outranking you are targeting narrower, more specific queries with better intent alignment. That comparison tells you more than any guide on what Google updated.

Recovery from core update impacts typically takes months, not weeks, because it requires genuine content improvement and Google needs to re-evaluate those improvements across multiple crawl cycles. Expecting fast recovery from a quality-related algorithm hit is unrealistic — and chasing shortcuts usually makes things worse. The topic of E-E-A-T and SEO is directly relevant here, since most recent core updates have been heavily weighted toward experience and authority signals.

When Traffic Dropped Without a Clear Cause

Sometimes the timeline does not match any known update, technical checks are clean, and content looks fine. In those cases, look at these less obvious causes.

Seasonality. Some niches have strong seasonal patterns that can look like a drop if you are comparing to the wrong baseline. Compare to the same period last year, not the prior month. A seasonal SEO strategy built around your traffic cycles makes this kind of misread much less likely.

Brand traffic shift. If a significant portion of your traffic was branded (people searching your company name) and that traffic declined, something affected your brand recognition or search behavior — not your organic rankings. That shows up in overall organic numbers but is not an SEO problem.

Tracking or attribution change. An Analytics update, a GA4 migration, a change in how sessions are counted. Confirm the traffic actually dropped in Search Console (which measures impressions and clicks directly from Google) not just in Analytics.

Building a Recovery Plan

Once you have identified the cause, the recovery plan follows logically. Technical fix: implement and monitor. Algorithm quality impact: identify the weakest content on affected pages and improve it substantively, then build supporting authority signals through internal linking and legitimate external references. SERP landscape change: adjust your targeting to terms where you can still capture clicks, or optimize your existing rankings for featured snippets and other SERP features.

What does not work: changing a bunch of things at once without knowing what the cause was, hoping something will stick. You lose the ability to know what fixed it and you risk introducing new problems while trying to solve the original one.

The SEO consulting work I do often starts with exactly this kind of diagnostic when a client comes in after a traffic event. If you need a second set of eyes on what happened and what to do next, that page explains how to engage. If you are evaluating a new provider in the process, the guide on how to read an SEO proposal will help you avoid common traps.

  • SEO During a Website RedesignHow to protect your rankings through a site migration or design overhaul
  • SEO Red FlagsSigns that the SEO work being done on your site may be causing more harm than good
  • SEO MythsCommon beliefs about SEO that lead to wasted effort and bad decisions