Google Search Console diagnostic
Your Google traffic changed. Find what changed.
A free Google Search Console comparison diagnostic. Upload two periods of query and page data; RankingDiff runs a deterministic analysis and shows you exactly what moved.
Illustrative example — not your data
Two periods, placed side by side
- brand + product query
- 412/day
- category query, page 1
- 96/day
- long-tail informational query
- 58/day
- comparison query
- 31/day
- brand + product query
- 409/day
- category query, page 1material drop
- 22/day
- long-tail informational query
- 54/day
- comparison query
- 29/day
RankingDiff aligns your before and after exports by query and page, then measures what moved between them — retained, lost, and new entities alike — instead of reading either period in isolation.
Why did your organic traffic change?
An organic traffic drop — or a jump — is rarely one thing. It shows up as a combination of observable signals inside Search Console: clicks fall or rise, impressions shift, click-through rate moves, average position changes, and specific queries or pages gain or lose ground while others stay flat. New queries can appear in the data and old ones can disappear entirely.
None of these signals, on their own or together, proves why Google traffic changed. They describe what changed. RankingDiff's job is to compare two periods of your own Search Console export and surface which of these signals actually moved, how much, and where — so your next investigation starts from evidence instead of a guess.
How to diagnose an organic traffic drop
A useful diagnostic process compares two periods deliberately, rather than eyeballing a single trend line. RankingDiff follows the same sequence you'd use manually, just faster and consistently:
- 01
Compare two periods. Pick a “before” and an “after” window and export both from Search Console.
- 02
Check clicks. Did daily-rate clicks actually fall, and by how much?
- 03
Check impressions. Did the site show up less often, or about the same?
- 04
Check CTR. At similar impressions, did fewer people click?
- 05
Check position. Did impression-weighted average position get worse?
- 06
Identify affected queries. Which retained queries lost clicks, impressions, or position?
- 07
Identify affected pages. Which retained pages carried the loss?
- 08
Look for concentration. Is the loss spread thinly, or do a handful of queries or pages account for most of it?
Analyze your Google Search traffic to run this sequence automatically against your own exports.
Why did Google Search Console clicks drop?
A click decline in Search Console is downstream of a smaller set of observable patterns: fewer impressions, a lower click-through rate at similar impressions, worse average position across retained queries, or a loss concentrated in a small number of queries or pages rather than spread evenly. Sometimes the search composition itself changes — gains and losses in different query groups offset each other, so the net number hides real movement underneath.
RankingDiff does not know the cause of a click decline. It helps identify which of these patterns is present in the data you supplied, with the specific numbers behind it, so you know where to look next.
Search Console impressions dropped
An impression in Search Console represents one time your site appeared in a search result for a tracked query — whether or not anyone clicked it. When search console impressions dropped, it means Search Console recorded fewer of those appearances for the queries in your data. Comparing two periods matters here because impressions swing week to week for reasons unrelated to a real traffic change: seasonal query volume, tracked query mix, and normal variance can all move the number.
RankingDiff normalizes clicks and impressions to daily rates before comparing, so periods of different lengths don't distort the result, and it checks whether an impression decline is concentrated in a few retained queries or spread across most of the cohort — a meaningfully different pattern from a general search traffic change.
Google rankings dropped
"Average position" in Search Console is a single aggregate number, and aggregate numbers can be misleading. Position can improve on average while the queries that actually drove your clicks lose ground — or stay flat while a large share of retained-query impressions sit behind queries that individually got worse. Reading position in isolation, without checking what happened underneath it, is one of the more common ways a diagnosis goes wrong.
Rather than relying on the one aggregate figure, RankingDiff analyzes retained queries and pages directly: it measures the impression-weighted position for the retained cohort, and it flags when aggregate and entity-level signals disagree — for example, when position improved overall but clicks still fell, or when position held steady overall while a material share of retained impressions sit behind queries whose position actually declined.
Organic CTR dropped
Click-through rate is clicks ÷ impressions. Because it's a ratio, CTR can fall even when impressions hold steady — meaning the site is shown just as often but earns fewer clicks per appearance. RankingDiff flags this specific pattern when clicks fell, impressions were broadly stable, and CTR fell by a material amount, with position also broadly unchanged.
What RankingDiff does not do is guess at why CTR moved. It will not attribute a CTR change to AI Overviews, a new SERP feature, or a Google algorithm update — those are hypotheses you'd investigate yourself by looking at how your result currently appears in search for the affected queries. RankingDiff only reports the measured CTR movement and which queries it's tied to.
How it works
RankingDiff's workflow is a straight line: you upload before data, you upload after data, RankingDiff runs the analysis, and you get back the observed patterns. Specifically, you export the Queries and Pages tabs from Search Console's Performance report for each period — four CSV files in total — plus how many days each period covers:
- 01 · Before — Queries
- Search Console → Performance → Queries tab, exported as CSV, for the earlier period.
- 02 · Before — Pages
- Search Console → Performance → Pages tab, exported as CSV, for the same earlier period.
- 03 · After — Queries
- The same Queries export for the later period you're comparing against.
- 04 · After — Pages
- The same Pages export for the later period you're comparing against.
Period lengths don't need to match — RankingDiff normalizes clicks and impressions to daily rates automatically, so a 7-day period can be compared against a 28-day period without distorting the result.
What RankingDiff checks
Every check below is a real, deterministic part of the engine — the same input always produces the same output.
- 01Click, impression, CTR, and impression-weighted position movement between two periods
- 02Which queries and pages are new, lost, or retained across both periods
- 03How concentrated a loss is — a handful of pages/queries (top 1/3/5/10 share of gross loss), or broad and diffuse
- 04Whether gross gains and gross losses are offsetting each other in a way that hides the real movement (a composition change)
- 05Whether aggregate metrics and entity-level metrics agree, or contradict each other
- 06Data sufficiency — retained-entity counts and raw click/impression volume — reflected in a confidence score
What RankingDiff does not claim
RankingDiff analyzes the comparison data you supply and identifies patterns in it. It does not prove why Google traffic changed, and it will never conclude, even as a secondary remark:
- Determine whether a Google algorithm update occurred
- Determine whether a manual action or penalty occurred
- Determine whether AI Overviews caused the change
- Determine whether competitors caused the change
- Determine whether a technical, indexing, or crawling issue occurred
- Determine whether seasonality caused the change
Your CSV files are parsed and analyzed entirely in your browser. Nothing is uploaded to a server, stored in a database, or sent anywhere — there is no account, no Search Console API connection, and no AI in the analysis.
Frequently asked questions
Why did my organic traffic drop?
An organic traffic drop is usually visible in Search Console as a change in clicks, impressions, CTR, or average position — often concentrated in specific queries or pages rather than spread evenly across the site. RankingDiff compares your before and after exports and shows you which of these signals moved, and where. It does not determine the external cause.
Why did my Google Search Console clicks drop?
Clicks can fall because impressions fell, because CTR fell at similar impressions, because average position worsened, or because the loss is concentrated in a small set of queries or pages. RankingDiff checks each of these possibilities against your two uploaded periods and reports which pattern is present in your data.
Why did my search impressions drop?
A drop in impressions means Search Console recorded fewer opportunities for your pages to be shown for the queries in your data. RankingDiff measures the size of the impression change and how widely it's spread across your retained queries, so you know whether to investigate a broad or a narrow set of terms.
How do I compare Google Search Console data?
Export the Queries and Pages tabs from Search Console's Performance report for two periods — the one before the change and the one after — then upload all four CSV files to RankingDiff along with each period's length in days. The analysis runs immediately in your browser.
Can RankingDiff tell me why my traffic dropped?
No. RankingDiff identifies which measurable pattern is present in the data you supply — position-associated decline, CTR-associated decline, search appearance decline, concentrated loss, or a composition change, among others. It does not know why that pattern occurred, and it never attributes a change to an algorithm update, a penalty, AI Overviews, competitors, or seasonality.
Is RankingDiff free?
Yes. There is no account, no paywall, and no usage limit enforced by a server, because there is no server involved in the analysis.
Does RankingDiff connect directly to Google Search Console?
No. RankingDiff does not use the Search Console API and never requests access to your account. You export CSV files from Search Console yourself and upload them; the comparison runs client-side in your browser and nothing is sent anywhere.