How to triage organic traffic losses with an AI agent
Where organic clicks went, page by page and query cluster by query cluster: decay, cannibalisation, or SERP change, each with its own fix.
IntentSeparate the three causes of organic loss that get confused, because each has a different owner and fix.
- 5
- Steps
- 6
- Tools
- 4
- Rules
- 3
- Failure modes
When to use it
Use it when
- Organic clicks down month over month and nobody knows where.
- A content refresh cycle needs a priority list.
- Before blaming paid changes for blended traffic loss.
Do not use it when
- Right after a site migration: everything moves at once; wait for indexation to settle and run indexation-health first.
- Sites too young for Search Console history to hold a baseline.
What it needs first
Required
Optional
Preconditions
- The property ticked, with at least two comparable periods of data.
Inputs
window- Comparison window.Default: last 28 days vs previous 28.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Run the losses and gains comparison over queries and pages.
On the top losers, check for cannibalisation: several pages competing on one query.
Cluster the losing queries by intent to find thematic decay.
Check whether the loss is clicks-per-impression rather than rank: SERP feature changes.
If GA4 is connected, confirm the traffic loss lands where Search Console says.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Position held but CTR fell on a losing query
Conclude
SERP change, not content decay: the result looks the same, the page around it changed. Fix is snippet and feature work.
When
Two or more of the site's pages alternate on one losing query
Conclude
Cannibalisation: consolidation decision, name the pages and the winner candidate.
When
Position fell with content untouched for months
Conclude
Decay or competitor gain: refresh candidate, ranked by lost clicks.
When
The losses concentrate in one cluster while others hold
Conclude
Thematic, not sitewide: scope the fix to the cluster and say so.
Evidence every conclusion must carry
- Every finding carries both periods' clicks, impressions, CTR and position.
- Data freshness is checked and quoted: Search Console lags days.
- gsc_get_data_freshness
Where the agent stops
- Content consolidation and rewrites are editorial decisions; the skill delivers the ranked triage.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Seasonality read as decay: compare year over year on seasonal clusters before concluding.
- Search Console samples long-tail queries; small losses on huge sites need the sampling plan.
- A tracking change on the site moves GA4 while Search Console holds; disagreement between them is itself a finding.
What the answer contains
- 01Triage
- Losses bucketed: decay, cannibalisation, SERP change, seasonal.
- 02Fix list
- Per bucket, ranked by recoverable clicks, with owners.
- 03Confirmations
- Clusters that held, so wins are visible too.