Algorithm Diagnosis

Diagnosing Which Update Hit Your Client

Before you can recover, you need to know what hit you.

Where to find it: Google Search Console > Performance > Compare date ranges | Ahrefs > Traffic history | Semrush Sensor / MozCast

What It Is

Algorithm recovery begins with accurate diagnosis. A traffic drop has many possible causes — a manual action, a technical error, a competitor surge, a seasonality shift, or one of Google's named (or unnamed) algorithm updates. Misdiagnosis leads to wrong fixes: a site hit by a content quality update that's treated as a link spam problem will never recover. This episode covers the systematic process for diagnosing which update caused a drop, confirming the diagnosis with data, and ruling out non-algorithmic causes.

Why It Matters

The recovery process is entirely different depending on which update caused the drop. A Helpful Content System demotion requires a fundamentally different remediation than a Core Algorithm Update, which requires a different approach than a Link Spam update or a Manual Action. Starting recovery without accurate diagnosis wastes months of effort on the wrong fixes.

Root Diagnostics

Common Causes

Understanding why this failure occurs is the first step to fixing it permanently.

Wrong Comparison Date

Correlating the traffic drop with the wrong date — comparing to a seasonal period rather than an update window — leads to false conclusions about which update caused the problem.

Technical Blind Spots

Blaming an algorithm update when the real cause is technical — a broken canonical, an accidentally added noindex tag, or a crawl error introduced at the same time.

Recency Bias

Assuming the most recent update is always the cause. Multiple updates can overlap, and older lingering signals may be the actual driver of current performance.

Skipping Manual Actions

Not checking Manual Actions in Search Console before assuming algorithmic cause. Manual Actions are shown explicitly; algorithm updates are not.

Interactive Standard Operating Procedure

The Fix Blueprint (Interactive SOP)

Check off each step to monitor your implementation progress live!

Implementation Progress: 0% Completed (0/7)

1. Establish the Exact Traffic Drop Date

Open Google Search Console > Performance. Use the date comparison feature to compare the week before versus the week of the drop. Identify the precise date the traffic change began, not just the overall trend.

2. Check Search Console for Manual Actions

Navigate to Search Console > Security & Manual Actions > Manual Actions. Rule out manual penalties before assuming algorithmic cause. A manual action is shown with a specific description; an algorithm demotion is not.

3. Cross-Reference Against Algorithm Update History

Compare the drop date against the Google Search Status Dashboard, Semrush Sensor, and MozCast. Identify any confirmed updates within plus or minus 7 days of the traffic change date.

4. Check Which Types of Pages Lost Traffic

Filter Search Console Performance by page type — product pages, blog posts, category pages. The pattern of which pages lost traffic narrows down which update type is responsible.

5. Rule Out Technical Causes

Check robots.txt changes, noindex tags, canonical errors, or crawl errors introduced around the same date as the traffic drop. Use the URL Inspection tool to verify individual pages.

6. Analyze the Surviving Pages

Identify which pages did NOT lose traffic. What do they have in common? This reveals what the update was rewarding and helps confirm the diagnosis.

7. Confirm With Industry-Wide Patterns

Compare against industry-wide data — if 10 competitors in the same niche also dropped on the same date, it's algorithmic repositioning, not a site-specific problem. This changes the recovery strategy entirely.

Tools

Google Search Console
Free | Traffic history, manual actions, coverage reports, and URL Inspection for technical diagnosis
Ahrefs or Semrush
Paid | Historical traffic trends and competitor traffic comparison to confirm industry-wide patterns
Semrush Sensor / MozCast
Free | Algorithm update history timeline to cross-reference drop dates against confirmed update windows

Time to Fix

2–4 hours

Diagnosis

30–60 minutes

Documentation

Pro Tip

Check competitors before assuming something is wrong with the client's site.

If 10 competitors in the same category also dropped on the same date, the issue is competitive repositioning within the algorithm — not a problem specific to the client site. That completely changes the recovery strategy: instead of finding and fixing what's wrong, you need to identify what competitors improved and build a plan to outperform it.

Ep 2: Recovering from Helpful Content System...