Export the same report twice
In Google Search Console, export the same Pages or Queries report for an earlier period and a recent period. Keep the dimensions consistent.
Upload two Google Search Console exports—or one comparison CSV—and turn a traffic drop into a prioritized diagnosis instead of guessing what changed.
Use two equivalent Search Console exports from an earlier and recent period, or upload a single comparison export.
Start with exported data, keep the comparison consistent, and use the result to decide what deserves deeper investigation.
In Google Search Console, export the same Pages or Queries report for an earlier period and a recent period. Keep the dimensions consistent.
Drop both CSVs into the analyzer, or switch to comparison mode if your export already contains earlier and recent columns.
The tool groups lost clicks into ranking loss, CTR/SERP pressure, demand/impression loss, visibility-loss candidates and mixed decline, then ranks the biggest losses.
This is a diagnostic tool, not another generic analytics dashboard.
See how much of the lost-click total is associated with ranking, CTR, demand, visibility or mixed patterns.
Find the exact pages or queries responsible for the largest traffic losses instead of treating the entire site the same.
The analyzer does not diagnose from clicks alone. It compares the signals that usually tell very different stories.
Each dominant pattern gets a short verification checklist so you know what to inspect before editing content.
Common Search Console column names are detected automatically, and unusual exports can be mapped manually.
CSV files are read by JavaScript in your browser. They are not uploaded to IM Review HQ by this tool.
Give your visitors the same browser-local analyzer directly inside an article, resource page, agency site or client portal.
A fall in organic clicks can come from very different mechanisms. A page can lose rankings, keep its ranking but lose click-through rate, lose impressions because demand changed, disappear from visibility because of a technical problem, or experience several of those at once. Treating every decline as a 'content quality' problem can waste time and make a healthy page worse.
The diagnostic compares the earlier and recent period at the page or query level. A meaningful position decline points toward ranking loss. Stable rankings and impressions with a large CTR decline are flagged as CTR or SERP-pressure candidates. Stable rankings with materially lower impressions point more toward demand or visibility changes. Very large visibility collapses are separated for technical verification. Anything that does not fit one pattern cleanly is kept in a mixed bucket rather than forced into a false answer.
Start with the rows responsible for the most lost clicks. Verify the live SERP, Search Console URL Inspection, indexing and canonical status, query intent, template changes and internal links as appropriate. The output is designed to narrow the investigation—not replace direct verification in Google Search Console or the live search results.
For the cleanest comparison, export the same dimension and similar-length periods. If your niche is seasonal, compare year-over-year as well as period-over-period. A December-to-January decline can look severe even when rankings are unchanged and demand simply returned to normal.
This tool works from the fields present in your export. It cannot see data that Google Analytics, Search Console or your tracking setup did not record. Diagnostic labels are designed to narrow investigation and should be verified before major SEO, analytics or blocking decisions.
No. The free version works from CSV exports, so no Google login or OAuth permission is required.
No. Stable rankings plus lower CTR is a useful diagnostic pattern, but the cause can also be ads, rich results, stronger competitor snippets, seasonality or other SERP changes. Verify the actual results page.
Yes. Root-cause analysis works with either. For page-specific decisions, use the Pages export; for search-intent investigation, use Queries.
No. The analyzer reads them in your browser. The page does not send the CSV contents to an IM Review HQ server.
Yes. Use the free iframe embed code provided below.
Use another free analyzer when the next question is about CTR, content decay, traffic quality or monetization.
Compare Search Console clicks with GA4 organic sessions to uncover tracking gaps, URL mismatches and measurement loss.
Open GSC vs GA4 Traffic Analyzer →Find queries where multiple pages compete, identify URL switching and decide which page should own the search intent.
Open Keyword Cannibalization Analyzer →Compare website and social search demand to uncover topics that deserve new articles, updates or video content.
Open Social-to-Search Content Gap Analyzer →Break down Discover losses by page, impressions and CTR to see whether exposure vanished or engagement weakened.
Open Google Discover Traffic Drop Analyzer →Find the pages and queries where Google visibility stayed relatively stable but clicks disappeared—then estimate the cli…
Open free tool →Stop refreshing content because it feels old. Upload Search Console page data and build a priority queue around actual t…
Open free tool →Traffic is not the same as value. Upload page-level analytics and see which landing pages produce revenue, which are hid…
Open free tool →