—
Most likely measured pattern
—
—
—
—
—
- Baseline clicks
- —
- Comparison clicks
- —
- Net click change
- —
- Impression change
- —
- CTR change
- —
- Row-weighted position
- — —
Browser-local Search Console analysis
Google Search Console Traffic Drop Analyzer
Compare two Pages or Queries CSV exports. Find where clicks were lost, see the evidence behind each pattern, and prioritize what to check next—without connecting an account or uploading your data.
Completely free
No login
No paid API
Files stay in your browser
Run the comparison
Upload two matching Search Console exports
Export one baseline period and one comparison period from the same Pages or Queries tab. Keep search type, country, device, and other filters consistent.
How to export the right CSV files
- Open Search Console → Performance → Search results.
- Choose the first date range and apply the filters you need.
- Open the Pages or Queries tab, click Export, and choose CSV.
- Repeat for the second date range with the same dimension and filters.
- Upload one file in each field below. Do not use Search Console’s combined comparison export.
Measured loss profile
Share of all lost clicks in the uploaded rows, grouped by the evidence thresholds below.
Recommended next step
Safe DIY checks
When specialist help is reasonable
Where losses cluster
| Segment | Baseline clicks | Comparison clicks | Change | Measured loss |
|---|
Prioritized loss evidence
Select a page or query to see the exact evidence used for its classification.
| Confidence |
|---|
Data and interpretation limits
Do not treat a classification as proof. Search Console rows alone cannot establish an algorithm update, penalty, seasonality, technical defect, competitor change, or business impact. Validate important findings with Search Console filters and URL Inspection, Google Trends, analytics, site change logs, and page-level checks.
Optional professional help
Traffic Loss Diagnosis & Recovery Review
For site owners and marketing teams with a commercially important, broad, sustained, migration-related, or technically unclear decline. You receive a manual validation of the report, a prioritized diagnosis plan, and implementation-ready recommendations.
Good fit
- High-value pages or site sections lost meaningful traffic.
- The decline followed a migration, redesign, deployment, or indexing change.
- Mixed signals make prioritization difficult.
- You need implementation help or an evidence-based handoff.
Probably not needed
- Only a few low-value rows changed.
- The decline is clearly seasonal and expected.
- You can validate and fix the affected pages yourself.
- You are looking for a ranking guarantee.
No rankings, recovery date, or traffic outcome is guaranteed. Scope depends on the site, evidence, and implementation access.
Get a professional review of these findingsHow to use the traffic drop analyzer
- Choose comparable periods. Use equal-length date ranges when possible. For seasonal sites, compare year over year rather than only the previous month.
- Keep filters identical. Pages versus Queries, Web versus Image, country, device, and search appearance filters must match.
- Upload separate exports. The analyzer expects one standard table export per period, not Search Console’s combined comparison CSV.
- Read the evidence before the label. A label summarizes crossed thresholds; the row detail shows the metric changes behind it.
- Validate the highest-impact losses. Start with high-priority rows and the section or pattern that accounts for most lost clicks.
Worked example
A service page falls from 80 to 40 clicks. Impressions fall from 1,600 to 1,000, CTR declines from 5% to 4%, and average position worsens from 4 to 8. The analyzer marks this as mixed loss signals because ranking, impression, and CTR thresholds are all crossed. That does not prove one cause. It means the page deserves a layered check: indexability and technical changes first, then the current result set, query intent, content, internal links, and snippet presentation.
What each result type means
Ranking loss signal
Average position worsened beyond a position-sensitive threshold while clicks declined. Validate at query and page level because average position is directional.
CTR / snippet loss signal
Impressions and position stayed comparatively stable, but CTR fell by at least 0.5 percentage points and 20% relative with enough impressions to reduce noise.
Impression / demand decline signal
Impressions fell at least 20% while position stayed relatively stable or was inconclusive. Seasonality, demand, eligibility, or coverage may be involved.
Lost visibility signal
A row had at least 20 baseline impressions and zero comparison impressions. Confirm indexing, URL changes, filters, and Search Console truncation.
Mixed loss signals
Two or more major signals crossed thresholds. Avoid assuming a single cause; use a sequence of technical, SERP, content, and demand checks.
Unclear loss pattern
Clicks fell, but the supporting metrics did not cross minimum thresholds. Treat it as a lower-confidence investigation lead.
How the classifications and priorities are calculated
The detailed findings are more important than the label. The tool does not create a generic 0–100 health score.
| Rule | Transparent threshold |
|---|---|
| Ranking deterioration | Position worsens by at least 1.5 places from positions 1–10, 2.5 places from positions 10–30, or 4 places beyond position 30. |
| Impression decline | At least 20% decline and at least the equivalent of 20 fewer impressions over the baseline period; daily averages are used when date ranges differ. |
| CTR decline | At least 0.5 percentage points and 20% relative, with at least 50 baseline impressions. |
| Lost visibility | At least 20 baseline impressions and zero comparison impressions. |
| Dominant site pattern | One mechanism must account for at least 45% of measured lost clicks. |
| High-priority row | At least 10% of measured lost clicks, a large high-value relative loss, or meaningful clicks on a row that lost all visibility. |
| Broad / sitewide pattern | At least 60% of active rows decline across at least three page sections. |
Common comparison mistakes
- Comparing 7 days with 28 days without normalization.
- Using different country, device, search type, or query filters.
- Treating a 1,000-row export as the complete site or query dataset.
- Assuming a CTR decline is always a title-tag problem.
- Assuming stable average position means rankings did not change for important queries.
- Calling every decline an algorithm penalty without technical, seasonal, and demand evidence.
- Changing many pages before identifying whether loss is sitewide, section-led, or concentrated.
Practical use cases
- Diagnose a sudden or gradual organic click decline.
- Identify pages that lost the largest share of clicks after a redesign or migration.
- Separate possible content decay from broader demand decline.
- Find query groups with stable visibility but weaker CTR.
- Build an evidence-based handoff for writers, developers, or an SEO specialist.
- Repeat the same analysis after fixes to see which rows recovered.
Limitations
The analyzer can only evaluate rows present in the uploaded files. Search Console may omit anonymized or low-volume queries, and interface exports may be limited. Average position is an aggregate, not a rank tracker. The tool does not access analytics conversions, crawl data, backlinks, server logs, Google update dates, competitor results, or page-change history. It cannot prove causation or guarantee recovery.
Frequently asked questions
Does this connect to my Search Console account?
No. Select two exported files. No OAuth permission or Google password is requested.
Are my files uploaded or stored?
No. The CSV parser and analysis run in your browser. Resetting or closing the tab clears the in-memory data.
Can I use a combined Search Console comparison export?
No. Column names vary by date and locale, and combined exports can be ambiguous. Export each date range separately from the same table.
Can I compare periods with different lengths?
Yes. Enter each period’s day count. Clicks and impressions are then compared as daily averages, and the report labels that normalization.
Does this prove a Google algorithm update caused the drop?
No. It identifies patterns in clicks, impressions, CTR, and average position. Update impact needs a timeline, affected page groups, technical checks, demand context, and often manual review.
Why do the row totals differ from the Search Console chart?
Search Console can omit anonymized queries and limit rows shown or exported through the interface. Aggregation and filtering can also change totals.
Is every feature free?
Yes. Analysis, row evidence, filters, copy, CSV download, JSON download, print, and sample data are all free. No contact information is required.
Related checks for validating a traffic loss
Review details and sources
Product specification and implementation prepared July 14, 2026. Diagnostic guidance is based primarily on Google Search Central documentation for Search performance reports, comparing data, data limits, and debugging search-traffic drops. Thresholds are product heuristics disclosed above, not Google rules.