Skip to content
seostack

How to investigate a drop in organic search clicks

3 min readWorkflowsLast verified 2026-09-16

Use this workflow when a website or important page loses Google Search clicks. The aim is to locate the change, separate possible explanations and produce a specific next action.

1. Confirm the comparison

Select the correct website and open Search Console Comparison. Set two comparable, preferably complete periods. Record their exact boundaries, country, device and any query or page filters. Check date coverage before using a year-on-year comparison.

Start with clicks, impressions, CTR and average position together. A decline in clicks alone does not establish a ranking problem.

PatternWhat to investigate next
Clicks and impressions fall, position broadly stableDemand, affected query mix, lost page coverage and seasonality.
Impressions stable, clicks and CTR fallQuery/device mix, title and snippet relevance, competing search features and result presentation.
Position worsens alongside lower clicksAffected queries and pages, relevance, technical changes and competitors.
Aggregate position improves while clicks fallWhether low-ranking impressions disappeared or the remaining query mix changed.

These are investigation paths, not diagnoses. Average position is an aggregate, and a site's mix of searches can change between periods.

2. Find where the loss is concentrated

Open Losers, then compare page and query results. Start with absolute click losses and commercially important URLs. A 100% decline from one click is usually less consequential than a 10% decline from thousands.

Use Monthly URL Performance to see whether the change is sudden, recurring or gradual. Do not compare a partial current month with a complete month without adjusting the interpretation.

3. Drill into a page's queries

In Search Console Data, apply the exact page filter and review its queries, countries and devices. Keep the same period and filters while checking metrics. Query rows may not reconcile exactly with property-level totals, so preserve the aggregation context.

If several URLs appear for a query, check their purpose before calling it harmful cannibalisation. The URL Query Count and Top-Level Query Trajectory articles explain useful supporting views.

4. Verify technical explanations

For a page suspected of losing visibility, use URL Inspection and Page Indexing. Distinguish an indexed result, a not-indexed result and an unspecified or unavailable result. Then use SEO Site Audit to inspect specific findings.

An HTML-only audit can miss client-rendered content. A zero word count or missing heading in that snapshot warrants checking the rendered page before implementing a fix.

5. Record the conclusion and next action

Write a short finding containing the URL/query, exact dates, observed change, evidence, plausible explanations and what will confirm them. Create a task for the specific investigation or fix. Check Annotations for relevant website changes, but remember that timing alone does not prove causation.

Worked example

In the documented comparison, the booking page showed seven clicks against eleven previously, with CTR falling from roughly 1.04% to 0.65% while average position improved from 4.5 to 3.6. Those observations do not support a simple “rankings dropped” explanation. Review impressions, query mix, snippet relevance and booking demand before rewriting the page.

Success for this workflow is a supported diagnosis or a well-defined next test, not an automatic traffic recovery.

Connect a property. Watch the data start stacking.

Warehousing begins the moment you connect your Search Console property, there is no Google Cloud project to set up, no BigQuery and no schema to design. You simply connect your property and SEO Stack starts storing every row of your data from that day onwards.

  • Credit card required
  • Cancel within the trial and you won't be billed
  • No contracts