
Organic Traffic Drop: Diagnose the Cause Before You Act
On this page
- Step 0: Is the change larger than noise, with clean reporting windows?
- Step 1: Did clicks fall, or only impressions?
- Step 2: Is the loss everywhere, or concentrated in one segment?
- Step 3: Does the start align with a completed Google update?
- Step 4: Does last year's demand show the same shape?
- Step 5: Which loss type do the four page columns suggest?
- Step 6: With stable rankings, did the results page change?
- Step 7: Are two URLs alternating for the same query?
- Step 8: Has the page eroded for months without a single break?
- Choose the action supported by the evidence
SEO
Your Search Console chart has turned downward, and you are deciding whether to rewrite pages or call the developer. An organic traffic drop needs diagnosis before either action: compare equal periods in whole weeks, check clicks first, and test whether the difference exceeds 2 × √(before + after). A change from 100 to 80 clicks falls inside that noise gate; 400 to 300 clears it.
The thresholds here are our rules of thumb, not Google rules, except where Google's own examples or core-update instructions are identified. They help you choose the next investigation; they do not establish causation.
- →Validate the comparison
Use equal windows, test the size of the change, and check dated reporting issues. Stop if the evidence is only ordinary variation.
- →Locate the loss
Separate clicks from impressions, then isolate the affected section and audience. Compare update dates and last year's demand.
- →Choose a repair
Read clicks, impressions, CTR, and position together. Check the search results, competing URLs, or indexing evidence before changing a page.
Step 0: Is the change larger than noise, with clean reporting windows?
Treat a change as worth investigating when its absolute size exceeds twice the square root of the two period totals added together. This statistical shortcut treats counts as roughly Poisson; real search activity, especially impressions, can be burstier, so passing it is a minimum signal, not proof.
In Performance → Search results, open Date → Compare → Custom. Choose two completed windows of 7, 28, or 91 days, with identical search type and other filters. Whole weeks give each weekday equal representation; avoid comparing an unfinished day with a completed one.
| Before | After | Absolute change | Noise gate | Decision |
|---|---|---|---|---|
| 100 clicks | 80 clicks | 20 | 2 × √180 = 26.8 | Inside noise; keep watching |
| 400 clicks | 300 clicks | 100 | 2 × √700 = 52.9 | Investigate |
| 487 impressions | 454 impressions | 33 | 2 × √941 = 61.3 | Inside noise; keep watching |
Use clicks where there is enough volume. For sparse pages, roughly fewer than 20 clicks per period, impressions provide a more usable initial signal, with the reporting caveats that follow.
Check Google's Data anomalies in Search Console for issues affecting either window. Three comparison traps deserve particular attention:
- The entry dated 3 April 2026 says impressions were inaccurately reported from 13 May 2025 until 27 April 2026. Clicks were unaffected; the correction can produce lower impressions and affect CTR and average position.
- FAQ rich results stopped appearing on 7 May 2026, reducing reported FAQ impressions.
- Around 10 to 14 September 2025, Google was widely reported to have stopped honoring
&num=100. Industry reports associated this with fewer desktop impressions and better average position, while clicks were largely unaffected; Google made no formal announcement of the change.
Check report-specific incidents too. For example, Generative AI Search impressions had a logging problem from 13 to 17 August 2026, with restoration recorded on 21 August.
If the change remains inside the gate, stop corrective work and collect another complete window. If a reporting issue explains it, annotate the comparison; otherwise continue to Step 1.
Step 1: Did clicks fall, or only impressions?
If impressions fell while clicks held steady, you have not established a loss of search visits. If clicks fell beyond the gate, continue to Step 2 even when average position appears unchanged.
Enable Total clicks, Total impressions, Average CTR, and Average position in the Performance report. Keep the comparison active and inspect the four metrics together, starting with clicks.
Average position depends on which impressions enter the calculation. Imagine deep results cease receiving impressions while your prominent results stay unchanged: average position improves because the mix changed, without any individual ranking improving. The widely reported September scraping change is a reason to be suspicious of exactly that combination.
The reverse can happen too. New impressions at lower positions can worsen average position while bringing additional clicks, which is hardly a business emergency.
For an impressions-only change, first check reporting dates and the affected search appearance. If clicks remain stable and there is no technical evidence of lost pages, monitor the affected segment; continue through Step 2 when you need to identify which impressions disappeared.
Step 2: Is the loss everywhere, or concentrated in one segment?
A loss concentrated in one section points you toward that section's pages or template. A similar percentage loss across unrelated sections makes a shared cause, such as demand, a sitewide technical problem, or a ranking change, more plausible.
With the date comparison active, open Pages and sort by Clicks Difference to bring the largest losses together. Then inspect Devices, Countries, and the available search types separately, keeping the dates fixed. Record both the absolute loss and percentage change: losing half of two clicks should not outrank losing a quarter of 2,000.
For section filters, choose Add filter → Pages → Custom (regex). Query patterns use Add filter → Queries → Custom (regex), with Matches regex or Doesn't match regex.
Search Console uses RE2 and partial matching by default; anchors constrain the start or end. UI matching is case-insensitive, and (?-i) makes it case-sensitive, according to Google's filtering and comparison documentation.
Question-shaped queries:
^(how|what|why|when|which|can|does|is|are|should)\b
Brand variants, select Doesn't match regex:
iron ?goo|irongoo
One section, select Pages:
^https://example\.com/guides/
Queries with six or more whitespace-separated words:
^(\S+\s+){5,}\S+$
Several exact pages:
^https://example\.com/(pricing|contact|demo)/?$
These patterns use RE2-supported syntax. The word-count pattern accepts six words and rejects five; the question pattern's boundary prevents how from matching the beginning of however. Replace the example domain and brand with yours, and inspect returned rows before trusting the filter.
RE2 does not support lookaround or backreferences. Use Doesn't match regex for exclusions, and remember that only one comparison can be active at a time.
If one segment contains the loss, keep that filter through the next checks. If the loss is broad, retain the sitewide view and continue to Step 3.
Step 3: Does the start align with a completed Google update?
A matching date makes an update a candidate explanation, not a confirmed cause. For a core update, Google says to wait at least a full week after completion before analyzing the change.
Use the Search Status Dashboard ranking history to mark the rollout against your chart. These are the listed core and spam update starts and durations, checked on 24 October 2026; dashboard times use US/Pacific.
| Update | Start date | Listed duration |
|---|---|---|
| March core update | 13 March 2025 | 13 days, 21 hours |
| June core update | 30 June 2025 | 16 days, 18 hours |
| August spam update | 26 August 2025 | 26 days, 15 hours |
| December core update | 11 December 2025 | 18 days, 2 hours |
| March spam update | 24 March 2026 | 19 hours, 30 minutes |
| March core update | 27 March 2026 | 12 days, 4 hours |
| May core update | 21 May 2026 | 11 days, 21 hours |
| June spam update | 24 June 2026 | 2 days, 1 hour |
| August spam update | 18 August 2026 | 2 days, 16 hours |
| September spam update | 24 September 2026 | 13 days, 16 hours |
The May core update started on 21 May 2026 with a listed duration of 11 days, 21 hours, putting completion at about 2 June 2026. That end date is our arithmetic from the dashboard's start date plus listed duration, not a date Google publishes. Waiting a full week puts analysis from about 9 June: compare 9 to 15 June 2026 with 14 to 20 May 2026, the week before the start. Each seven-day window contains every weekday once.

Keep the rollout outside both comparison windows. The later window starts after a full waiting week, so rollout movement does not become your settled result.
Google's core-update instructions also distinguish a small drop, such as a page falling from position 2 to 4, from a large drop, such as falling from position 4 to 29. The former calls for no drastic action; the latter deserves deeper assessment. Google explicitly treats deleting content as a last resort.
If a core update is still rolling out or the waiting week is incomplete, schedule the comparison and continue checking technical evidence. If the dates do not align, or the settled loss persists, continue to Step 4.
Step 4: Does last year's demand show the same shape?
A recurring dip, steady positions, and matching demand movement outside your site support a seasonal explanation. A single year-over-year comparison cannot establish it on its own.
Change the date view to Last 16 months and inspect the affected pages and queries around the same period last year. Then check Google Trends for the five queries contributing most to the loss, using the relevant country. Look for agreement in timing, while remembering that the impression logging correction can contaminate the Search Console comparison.
Separate branded demand before treating a sitewide loss as an SEO failure. Fewer people searching your company name can reduce clicks without your pages losing competitive rankings.
The cleanest available split is Search Console's Branded queries filter. Google announced it on 20 November 2025, with availability extended to all eligible sites on 11 March 2026. Its internal AI-assisted classifier recognizes brand variants and unique products; it is not a regex and can misclassify queries.
Eligibility requires a top-level property with sufficient query and impression volume, excluding URL-path and subdomain properties. Where it is unavailable, use a maintained brand regex and inspect the matched queries.
Filtered query totals will not reconcile perfectly with the unfiltered chart. Anonymized queries appear in totals but disappear from query tables and filtered views.
If demand evidence agrees and positions hold, plan around seasonality. If it does not, continue to Step 5 with brand and non-brand results separated.
Step 5: Which loss type do the four page columns suggest?
Clicks, impressions, CTR, and position together identify a working diagnosis. The thresholds flag candidates; inspect the page's queries before assigning a repair.
Open Pages with all four metrics enabled. Read these checks in script order: each label applies only when the earlier checks did not stop or classify the page.
| Label | Working threshold or fingerprint |
|---|---|
| Noise gate: no label | Use clicks when baseline clicks are at least 20; otherwise use impressions. Stop if the selected metric did not decline or its absolute change does not exceed 2 × √(before + after). |
| GONE | After passing the noise gate: no impressions in the later window |
| RANKINGS | After passing the noise gate and avoiding GONE: average position worsens by at least 3 |
| DEMAND | After passing the noise gate and avoiding all earlier labels: impressions fall more than 20% |
| CTR | After passing the noise gate and avoiding all earlier labels: at least 20 baseline clicks and CTR falls more than 25% |
| MIXED | After passing the noise gate and avoiding all earlier labels: a meaningful loss remains without a clean classification |

A CTR loss separates the clicks line from relatively steady impressions. Demand loss moves both downward, while a technical break can produce an abrupt collapse; position helps distinguish demand from ranking loss.
A DEMAND label is provisional: fewer impressions can also reflect lost query coverage. A page average can conceal ranking losses on some queries and gains on others, so open the page and inspect Queries before concluding that positions held.
For GONE, use the Page indexing report and URL Inspection, including a live test. Check the response status, noindex, robots restrictions, canonical destination, and any migration redirects. Our explanation of technical SEO and crawl costs connects those checks to crawling and indexing failures.
A sharp shared collapse suggests a common break. A misplaced noindex can produce a slower decline as Google recrawls affected pages, so absence of a single cliff does not clear the technical branch.
Export complete page comparisons before running the script
The UI export stops at 1,000 rows. For a larger site, use the Search Analytics API and write its results into the same five CSV columns expected by the script.
The Search Analytics query reference allows rowLimit up to 25,000, with 1,000 as the default. This request asks for finalized web data for one section:
{
"startDate": "2026-09-23",
"endDate": "2026-10-20",
"dimensions": ["page"],
"type": "web",
"dimensionFilterGroups": [{
"filters": [{"dimension": "page", "operator": "includingRegex", "expression": "^https://example\\.com/guides/"}]
}],
"rowLimit": 25000,
"dataState": "final"
}
Send it as an authenticated POST to the Search Analytics query endpoint for your encoded property identifier. Repeat for the earlier dates, and paginate with startRow when necessary.
dataState: "final" excludes fresh, unfinished data; "all" includes it. The API specifies RE2 syntax for regex filters; adding (?i) to an API expression is our optional choice when explicitly requesting case-insensitive matching.
Pagination does not remove the reporting ceiling: the API exposes up to 50,000 rows per day per site per search type. Google's API limits documentation also identifies combined page-and-query grouping or filtering as the most expensive work; use page-only requests for the first pass, then query detail for the affected pages. Long date ranges consume more load quota too.
Run the page classifier and inspect its labels
Export each period separately from the English Pages tab with all four metrics enabled. The expected header is Top pages,Clicks,Impressions,CTR,Position; API-derived CSVs need those columns in the same order.
Save the following as gsc_compare.py. Use complete, consistently filtered exports: a page missing because it fell outside an export limit can otherwise look like GONE.
#!/usr/bin/env python3
"""Compare two Search Console page exports and label each page by loss type.
usage: python3 gsc_compare.py before.csv after.csv
Each CSV: the Pages tab export (columns: page, Clicks, Impressions, CTR, Position)."""
import csv, math, sys
def load(path):
with open(path, newline="", encoding="utf-8-sig") as f:
rows = list(csv.reader(f))
out = {}
for r in rows[1:]:
clicks, impr, pos = float(r[1]), float(r[2]), float(r[4])
out[r[0]] = (clicks, impr, pos)
return out
def beyond_noise(a, b):
# counts behave roughly like Poisson: a change smaller than 2 standard deviations is noise
return abs(b - a) > 2 * math.sqrt(a + b)
def label(a, b):
ca, ia, pa = a
cb, ib, pb = b
metric = (ca, cb) if ca >= 20 else (ia, ib) # too few clicks: judge on impressions
if metric[1] >= metric[0] or not beyond_noise(*metric):
return None
if ib == 0:
return "GONE: no impressions, check indexing and status codes"
ctr_a, ctr_b = ca / ia, cb / ib
if pb - pa >= 3:
return "RANKINGS: position worse by %.1f" % (pb - pa)
if ib < ia * 0.8:
return "DEMAND: impressions down, position steady (seasonality or fewer searches)"
if ca >= 20 and ctr_b < ctr_a * 0.75:
return "CTR: same rank and impressions, fewer clicks (SERP feature or snippet)"
return "MIXED: read the queries for this page"
before, after = load(sys.argv[1]), load(sys.argv[2])
w = csv.writer(sys.stdout)
w.writerow(["page", "clicks_before", "clicks_after", "impr_before", "impr_after", "pos_before", "pos_after", "label"])
for page, a in sorted(before.items(), key=lambda kv: -kv[1][0]):
b = after.get(page, (0.0, 0.0, a[2]))
verdict = label(a, b)
if verdict:
w.writerow([page, int(a[0]), int(b[0]), int(a[1]), int(b[1]), round(a[2], 1), round(b[2], 1), verdict])
Run it from the directory containing the files:
python3 gsc_compare.py before.csv after.csv
RANKINGS means position crossed the deterioration threshold; DEMAND means impressions crossed its threshold without that ranking signal. CTR identifies a sufficiently large CTR reduction after the preceding checks; GONE identifies zero later impressions after passing the loss gate, and MIXED sends you back to queries.
The order matters because labels are mutually exclusive. The script uses baseline clicks to choose the metric, checks only pages present in the before file, and leaves gains and changes inside the gate unprinted. It assumes numeric exports with positive baseline impressions; it is a triage tool, not an indexing monitor.
We demonstrated the method on our own small site using finalized web data pulled on 24 October 2026. Across 26 August to 22 September 2026 and 23 September to 20 October 2026, page-grouped impressions were 930 and 1,321 respectively.
Within those windows, one Turkish-language blog post recorded 487 and 454 impressions. The difference of 33 sits inside its 61.3 noise gate, illustrating why a percentage change alone is a poor reason to edit.
If the page is GONE, investigate the technical branch immediately. Send CTR candidates to Step 6, competing-URL candidates to Step 7, and gradual ranking losses to Step 8.
Step 6: With stable rankings, did the results page change?
Traffic can fall while rankings stay similar because fewer impressions turn into clicks. Confirm that pattern at query level before blaming an AI Overview.
Filter to the affected page, open Queries, and sort by lost clicks. Search the largest contributors in a clean browser profile for the relevant country, keeping device context consistent. Record whether an AI Overview appears, whether it cites you, and whether another feature or a changed displayed title gives searchers a different reason to click.
Google's Search Console position documentation assigns an AI Overview one position, shared by every link inside it. External-link clicks count as clicks, and Google says standard impression rules apply. Our reading of those rules is that a link hidden behind an expansion does not automatically receive an impression merely because the overview appears.
Search Console has no AI Overview search appearance filter for isolating those clicks. Check your property's Generative AI performance report where available: it shows impressions without clicks, and its data is a subset of web reporting, so do not add it to web totals.
The studies justify investigation, with limits:
- Pew Research's July 2025 study examined March browsing from 900 US adults. Traditional-result clicks occurred on 8% of visits with a summary versus 15% without; summary-link clicks occurred on 1%. Those are visit-level observations, not your page's position-specific CTR.
- Ahrefs' February 2026 update compared desktop data for 300,000 keywords between December 2023 and December 2025. Position-one CTR fell from 7.6% to 3.9% for informational keywords without an overview, and 7.3% to 1.6% for keywords with one. Its 58% figure is relative to a forecast incorporating the non-overview decline; the finding is correlational.
- Seer's November 2025 study tracked 3,119 informational terms across 42 organizations. From June 2024 to September 2025, organic CTR fell from 1.76% to 0.61% on overview queries and 2.74% to 1.62% on other queries. Groups were defined by September overview presence, limiting causal interpretation.
Both longitudinal studies found falling CTR without AI Overviews too. A current search result can confirm a feature exists now; without historical evidence, it cannot prove when that feature caused your loss.
If the evidence supports reduced click opportunity, reassess the query's value and improve the page's specific reason to visit. The wider question of whether SEO still works with AI answers belongs in that investment decision.
If no results-page explanation fits, inspect query mix and continue to Step 7. Do not rewrite a stable-ranking page solely because a study's average resembles your chart.
Step 7: Are two URLs alternating for the same query?
Two URLs receiving impressions for one query is not sufficient evidence of harmful cannibalization. Our house threshold requires the second URL to receive at least 20% of the page-grouped impressions and the leading URL to change between periods.
In Performance → Search results, add a Query → Exact query filter, then open Pages. Compare the two date windows, calculate each URL's share of the returned page impressions, and check whether the leader switched. An API investigation uses dimensions: ["query", "page"], restricted to the affected queries.
Use page-row impressions for that share calculation. Property-level charts can count one impression where multiple results from the same site appeared, while page grouping produces separate rows; those totals measure different things.
If both conditions hold and the pages serve the same intent, choose one owner. A topical map that assigns one URL to each intent gives that decision a durable home.
Merge useful material and redirect the retired URL with a 301 when consolidation is appropriate, then update internal links. If the pages serve distinct needs, differentiate their content and linking targets.
If ownership is clear and there is no meaningful switching, continue to Step 8. Multiple ranking pages alone are not a reason to remove one.
Step 8: Has the page eroded for months without a single break?
Content decay is a gradual decline as a page loses relevance or competitiveness against current results. Its working fingerprint is clicks and impressions weakening alongside position over at least three months, without a clear update date or technical event explaining the pattern.
Return to the longer date view, filter the page, and inspect monthly movement. Compare its principal queries with the pages now outranking it, looking for observable differences: outdated instructions, changed product capabilities, missing evidence, or a different search intent.
Refresh the substance that the comparison identifies. Replace obsolete examples, verify claims, and answer the task searchers now bring to that query; a new date attached to unchanged content supplies no repair.
After publication, record what changed and evaluate another complete comparison window. Avoid promising a recovery deadline: competitive movement and Google's reassessment do not follow your editorial calendar.
When cannibalization or decay affects a whole cluster, put URL ownership and refresh decisions on a recurring schedule. Our SEO service for ongoing tracking and content refreshes fits that work when you want someone accountable for the calendar.
If the multi-month fingerprint fits, commission a substantive refresh. If it does not, retain the MIXED label and investigate the page's individual queries before approving changes.
Choose the action supported by the evidence
Use the narrowest action that matches the confirmed loss. Keep the original windows, filters, and diagnosis with the change record so the next comparison tests the same thing.
| Loss type | What the four columns show | How to confirm | What to do | What not to do |
|---|---|---|---|---|
| Noise | Small count change; derived metrics may swing | Difference stays inside 2 × √(a + b) | Collect another complete window | Rewrite from one percentage |
| Reporting artifact | Impressions change; clicks often hold; CTR and position shift | Match dates and report scope to anomalies | Annotate; compare clean metrics | Treat logging changes as lost visits |
| Seasonal demand | Clicks and impressions fall; position broadly holds | Prior-year shape and Google Trends agree | Adjust forecasts and publishing timing | Force a ranking repair |
| Rankings | Clicks weaken; position deteriorates | Inspect affected queries after clean update windows | Assess competing pages and relevance | Delete pages after a small movement |
| Lost CTR | Clicks and CTR fall; impressions and position broadly hold | Inspect query-level data and actual results | Improve the reason to click; reassess opportunity | Assume AI Overviews caused it |
| GONE | Impressions reach zero; clicks disappear | Verify export completeness, indexing, and live response | Repair the confirmed technical fault | Start with copy edits |
| Cannibalization | Page averages oscillate; query impressions split | Second URL has 20%+ share and leader switches | Assign ownership; merge or differentiate | Redirect distinct intents together |
| Decay | Position and impressions erode over months | Compare current competitors and query intent | Refresh substantive weaknesses | Change only the publication date |
| Mixed | Meaningful loss without a clean fingerprint | Separate queries and audience segments | Gather narrower evidence | Apply every suggested SEO fix |
Put your next steps in order
Build on what you have just read with a free ebook on semantic SEO and AI visibility. Get worked examples, decision rules, checklists and a do-this-week action in every chapter, plus a six-week plan for your site.

