Google Search Console CSV Analyzer
Free, no signup. One local CSV upload powers page/query pivots, transparent stem topics, a site CTR curve, cannibalization checks, and the same opportunity scorer used elsewhere. Compare a prior Pages export for winners, losers, stable-ranking decay, and directory-level content-group reports. Your exports stay in this browser.
Optional shortcut
Load directly from Search Console
Connect for this browser session, choose a property, and load two comparable 28-day periods. You will still choose Analyze below.
Privacy, dates, and data limits
Google's read-only access token exists only in page memory. It is not stored, sent to this site, used by telemetry, or transferred to Traverse. Ending the session clears the token and loaded analyzer data without revoking your Google grant.
Dates use Search Console's Pacific-time calendar: 28 complete days ending two days ago, compared with the immediately preceding 28 days. Search Console returns top rows rather than a guaranteed exhaustive export; this shortcut also stops at 10,000 top rows per table to match the analyzer's safety limit. Upload an export when you need different filters or a separately preserved source file.
Paste current GSC Pages first, then a current combined page×query export. Optionally add prior-period Pages and Dates exports. Separate data sets with a line containing ---. Files never leave your browser.
Optional comparison: add a prior-period GSC Pages export third for winners, losers, decay, and content-group deltas. A GSC Dates export can be third or fourth; confirmed Google algorithm updates in that range will be shaded over the clicks chart.
Search Console export limit: the UI can return only about 1,000 representative rows, and privacy-anonymized queries are omitted. Treat every analysis as a view of the exported sample, not the complete query set.
Analysis complete
Results
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Rate this tool
Pasted files stay in your browser. Each optional Google connection is separately authorized; selected Search Console or GA4 data travels directly between Google and this browser, and each read-only token stays only in page memory. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
How to use it
- Export the current Pages table for the date range and filters you want to analyze.
- Export a current combined page-by-query table for the same scope.
- Paste current Pages first, add a line containing only
---, then paste current page-by-query rows. - For period comparisons, add another separator and a prior-period Pages export with comparable filters. For the update overlay, add one more separator and a GSC Dates export. You may supply Dates without a prior period.
- Select Analyze. Start with the period and content-group reports, opportunities, and cannibalization, then use topics, the CTR curve, and time-chart context.
Example result Illustrative data
This compact static report uses fictional rows. It demonstrates the output fields without claiming typical CTR or traffic.
/crawl-budget/ and /guides/crawling//technical-audit/Striking-distance and CTR-gap reasons; modeled upside is not a forecast.What the results mean
- Pivot pages is the count of normalized URLs represented in the page-by-query table.
- Winners and losers compare current-minus-prior clicks and impressions by normalized page URL. A click decline with less than one position of movement is labeled stable-ranking decay.
- Template-like URL segments aggregate pages with the shared deterministic URL-pattern registry, such as product detail, article/post, documentation, or a transparent fallback pattern. They are inferred cohorts, not proof of an implementation template.
- Topics groups queries with shared word stems so the grouping can be inspected rather than treated as an opaque semantic label.
- Curve is a position-level CTR model derived from eligible supplied rows; a sparse export may return little or no curve.
- Cannibalization lists queries associated with multiple URLs. Alternation can be intentional, so inspect intent and dates.
- Opportunities ranks pages using modeled click upside plus CTR-gap signals; reasons show which query triggered each score.
How it works
The workbench normalizes page URLs, compares current and prior page metrics, aggregates pages by shared template-like URL patterns, builds a page-to-query pivot, clusters query wording by stem overlap, and derives a CTR curve from queries with at least 10 impressions and average positions 1–20. It separately groups identical normalized queries across URLs. Finally, it feeds page totals and query rows into the shared opportunity scorer, which looks for positions 4–20 and CTR below its expected curve.
Features
- Seven related GSC reports from the same two required exports.
- Optional prior-period winners/losers, stable-ranking decay, and inferred URL-cohort deltas with CSV export.
- Optional clicks timeline with confirmed Google update rollout ranges shaded onto the chart.
- Visible query evidence behind page opportunities and cannibalization candidates.
- Local parsing, explicit header checks, and normalized URL joins.
- Optional read-only browser-session connection that loads standard Pages, page×query, prior Pages, and Dates tables without saving a Google credential.
Limitations
- Brand terms are excluded from CTR-curve construction only when you supply them; review the resulting curve before using it as a benchmark.
- Search Console exports and API responses can omit low-volume or anonymized queries and aggregate data differently across dimensions.
- The session shortcut uses fixed Pacific-time periods and up to 10,000 top rows per table; use uploads for custom filters or preserved exports.
- Algorithm-update overlap is timing context, not evidence that an update caused a traffic change.
- Average position, click-upside estimates, and stem clusters are directional models, not forecasts or causal findings.
- All uploaded tables must use comparable date, country, device, and search-type filters.
Frequently asked questions
Which Search Console exports does the Google Search Console CSV Analyzer need?
It needs a current Pages export with Page, Clicks, Impressions, and Position, followed by a current combined page-by-query export with those metrics plus Query and Page. Add a prior-period Pages export for winners, losers, decay, and content-group deltas. An optional Dates export adds a clicks chart with confirmed Google algorithm-update rollouts shaded over it.
How does the workbench detect cannibalization?
It flags a normalized query when two or more distinct normalized page URLs appear for it. That is a review candidate, not proof that the pages harm performance.
How is the site CTR curve calculated?
The tool uses non-brand-eligible query rows with at least 10 impressions and positions from 1 through 20, then fits the shared CTR curve used by the opportunity model.
What are the topic clusters?
They are transparent stem-overlap groups built from query wording. They are not embedding-based topics and may separate synonyms or combine words with the same stem.
Does the Google Search Console CSV Analyzer connect to my Google account?
Optionally. When the browser-session connection is configured, you can grant read-only Search Console accessA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. long enough to choose a property and load the standard tables. The token is kept only in page memory and is not saved. Paste and upload remain available without a Google login.
Feature requests for Gsc Workbench
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Common issues & how to fix them
- Warnings One query is split across multiple pages Fix: Choose one primary URL for the query intent, consolidate overlapping content and internal signals, and redirect only when the secondary page has no distinct purpose.
- Information Query ranks within striking distance Fix: Improve the ranking page’s intent coverage, internal links, and snippet for the flagged query while preserving content already earning positions near page one.
- Information CTR underperforms the position benchmark Fix: Compare the live SERP, then rewrite the title and description to better match the query and differentiate the result without making unsupported promises.
- Warnings Query traffic is declining Fix: Compare pages, devices, countries, and dates for the query to distinguish ranking loss from demand change, then fix the affected page or snippet signal.
- Warnings Page traffic is declining Fix: Segment the page’s losing queries and inspect indexing, content, links, SERP changes, and seasonality before updating the specific cause.