Marketing tool

Search Console quick-win CSV analyzer

Find high-impression pages or queries with weak clicks from exported reports.

Your inputs

English Queries.csv or Pages.csv from Search results. CTR accepts 5% or decimal fraction 0.05. Use one date range without comparison columns.
A selected file takes precedence over pasted CSV. Up to 5 MB and 20,000 rows; processed in your browser.
Leave blank to omit the click scenario. Choose a target appropriate to your audience; there is no universal CTR benchmark.

Your results

Ready when you are
Add your inputs or try an example.
Your results will appear here.

How it works

Find exported queries or pages with enough impressions, a chosen average-position range and low CTR. Export a single date range from Google Search Console’s Search results report, then select its Queries.csv or Pages.csv file. Review the highest-scoring rows as candidates for investigation. Download the filtered ranking; optionally model a CTR target. Google documentation: https://support.google.com/webmasters/answer/7576553?hl=en

Priority proxy = impressions × (1 − reported CTR). Modeled extra clicks per row = max(0, impressions × target CTR − existing clicks), with unchanged impressions. Combined CTR = sum(clicks) / sum(impressions). These are transparent heuristics, not predictions.
Read the source reference ↗

A few things to know

Report exports are commonly limited to 1,000 representative table rows. Rare/anonymized queries and other rows can be omitted, so this file is not a full-site total. Queries and Pages use different aggregations: a query-only export does not identify its landing pages, and a page-only export does not identify its queries; no query–page pairs are inferred. Average position is an average of topmost positions, not a fixed rank. Rounded CTR can make the priority proxy approximate. Zero-impression rows are excluded. English comma-separated exports only; no ZIP, Excel, comparison or BigQuery formats. Source: https://support.google.com/webmasters/answer/12919797?hl=en

A little context

When to use this tool

A Search Console export can reveal pages and queries that already receive search visibility but attract relatively few clicks. This analyzer turns that export into a filtered investigation list. You choose the impression threshold, position range and CTR ceiling, then review the matching rows in priority order. The optional target CTR models a scenario at unchanged impressions; it does not forecast rankings, traffic or revenue.

  • Find visible queries worth investigating for search-intent and snippet improvements.
  • Review page-level CTR candidates in a consistent position range.
  • Estimate a transparent click scenario for a proposed CTR target.

How to use search console quick-win csv analyzer

  1. Export one Search results table

    Use an English Queries.csv or Pages.csv export for a single date range. Paste the CSV or select a file; an uploaded file takes precedence. Do not use comparison, chart, ZIP or spreadsheet formats.

  2. Set your investigation filters

    Choose minimum impressions, minimum and maximum average position, and maximum CTR as a percentage. Add an optional target CTR only when you want a scenario. There is no universal appropriate target.

  3. Investigate matching rows

    Inspect the sorted table and download the filtered CSV. Return to Search Console to examine devices, countries, search appearance and relevant pages or queries before changing a title, snippet or page.

Try the numbers

Review the supplied four-query export

Inputs

Use the example CSV with minimum impressions 100, position range 3–30 and maximum CTR 5%. Leave target CTR blank.

Result

Three of four rows match. Shipping threshold calculator ranks first with 2,000 impressions, 60 clicks and a 1,940 unclicked-impression proxy. Matching rows have a combined CTR of 2.08%.

What it means

The proxy is a sorting aid, not recoverable traffic. The excluded profit-calculator row has 10% CTR and average position 2.1, outside these filters. Different filters answer different investigation questions.

Common mistakes to avoid

Reading average position as a fixed rank

A reported average combines multiple impressions and contexts. A row at position 8.4 does not mean every searcher saw the same eighth result.

Equating low CTR with a bad title

Search intent, result features, devices and competition can affect clicks. Inspect the result context before assuming a title rewrite will solve the issue.

Treating an export as complete site traffic

The analyzer sees only the supplied table rows. Omitted queries and aggregation differences can prevent those rows from matching the chart’s totals.

Useful answers

Frequently asked questions

Definitions, edge cases, and practical next steps for this tool. Search all tool FAQs ↗

Which Search Console files are accepted?

Use the English comma-separated Queries.csv or Pages.csv table from Search results, with Clicks, Impressions, CTR and Position columns. Analyze one grouping and date range at a time. The tool does not combine queries with pages or parse comparison exports.

How are rows prioritized?

The score is impressions multiplied by one minus the reported CTR fraction. This approximates visible but unclicked impressions. Larger values appear first, with additional tie-breaking rules. It is a transparent heuristic rather than a measure of ranking difficulty or likely gains.

How is the combined CTR calculated?

It divides the sum of matching rows’ clicks by their summed impressions. It does not average individual percentages, which would give a small row the same weight as a large one. The figure describes the matching export rows, not the whole property.

What does the target CTR scenario mean?

For each matching row, modeled extra clicks are the greater of zero and impressions multiplied by your target CTR minus current clicks. Impressions are held constant. A 5% target on 2,000 impressions with 60 clicks models 40 extra clicks, without predicting they will occur.

Should I choose a standard 5% target?

No single target fits every query or result layout. The default filter is a starting point for investigation. Choose a target using comparable performance in your own data, then label the output as a scenario rather than an expected outcome.

Why do some rows disappear from the result?

Rows must meet every filter, and zero-impression rows are excluded. Check the impression threshold, both position boundaries and CTR ceiling. If nothing matches, widen the range or lower the threshold; do not assume the absence of matches means there are no opportunities.

Can I identify a query’s landing page from this export?

A query-only table does not contain its page relationships. Likewise, a page-only export does not identify its queries. Filter the relevant row in Search Console and inspect the other dimension there. This tool never invents query–page pairs.

What should I do after downloading the list?

Investigate a small group of high-priority rows, record the issue and proposed change, and compare later performance using suitable dates and context. Review page usefulness and intent as well as the snippet. The list helps organize that work; it does not replace diagnosis.

Explore the topic in the blog

Sources and method

Use the references below to check definitions and platform guidance. The model’s scope and limits are explained above. Read our editorial standards.

Help

How can we help?

Find instructions, report a problem, or leave a message.

Read this tool’s FAQs ↗

Guides for this tool

When two pages share a query, investigate the job each one does.
Common questions

Where do I start? Try an example, then replace its values with yours.

Why did my upload fail? Check the field error, accepted format and file-size limit. Start with a small sanitized sample.

Where are my results? Review the result panel, then use its copy or download controls. If a calculation fails, check the error beside the input.

Message us

Chat opens Tawk.to. It processes your messages and connection data. Do not paste private inputs or file contents. Availability and response times vary.