ToolsHub4u

Turn a Search Console export into a list of pages worth fixing

This does not connect to your account. It reads the CSV you export and flags the rows worth a second look: no clicks, a weak rate for the position, or a place just outside the top three.

  • CSV in, actions out
  • No Google connection
  • Opportunity list
Ready SEO & Web
Your data, not a simulationThe numbers come from your export. The tool compares each row with the rest of the same file, so it cannot invent traffic, impressions or a benchmark CTR curve.
1Enter
2Adjust
3Copy result

Search Console Export Analyser

1

Export and filters

Export Queries or Pages from Search Console as CSV. A header row is detected; columns are matched by name.

No data yet Live
2

Opportunities

7 opportunities found in 10 rows

Rows to review

7

  • 7 rows are worth reviewingEach has at least one reason: no clicks, a CTR below its position band, or a position close to page one. Read the reasons, not only the count.
  • Average CTR in this export: 1.36%327 clicks from 24,100 impressions across 10 rows. This is your own data, not a benchmark.
  • 24,100 impressions in the fileEnough for the position-band averages to mean something.
  • No duplicate namesEach row has a unique name in this file.
  • CTR is compared only within this fileNo external CTR curve is used. A row is flagged when its CTR is well below the average for the same position band in your export, which controls for position without inventing a benchmark.

Average CTR by position band in this export

Position 1-34%
Position 4-101.42%
Position 11-200.27%
Position 21+0%
Rows worth reviewing
Query or pageClicksImpressionsCTRPositionWhy
free seo tools185,20035%12.7Average position 12.7 is close to page one.
meta tag generator964,1002.34%4.2Average position 4.2 is close to page one.
keyword density checker423,8001.11%8.4Average position 8.4 is close to page one.
robots txt generator71,90037%6.9Average position 6.9 is close to page one.
keyword clustering91,50060%9.8Average position 9.8 is close to page one.
search intent141,2001.17%7.3Average position 7.3 is close to page one.
serp snippet229002.44%5.6Average position 5.6 is close to page one.
  • free seo toolsPosition 12.7

    Average position 12.7 is close to page one.

  • meta tag generatorPosition 4.2

    Average position 4.2 is close to page one.

  • keyword density checkerPosition 8.4

    Average position 8.4 is close to page one.

  • robots txt generatorPosition 6.9

    Average position 6.9 is close to page one.

  • keyword clusteringPosition 9.8

    Average position 9.8 is close to page one.

Rows parsed
10
Clicks
327
Impressions
24,100
Average CTR
1.36%

A low CTR can be caused by the query, the device, the snippet, the brand or the other results. Check the actual search result before rewriting a title. A position close to page one is an opportunity only if the page matches the query.

Paste a CSV exported from the Search Console Performance report and this tool sorts the rows into those worth a second look. It flags rows with no clicks, rows whose click-through rate is well below other rows at the same position, and rows sitting just outside the top three.

It never connects to your account. The file you export is the only input, which keeps the data in the tab and means the tool sees exactly the date range, country and search type you chose.

What the file needs

One row per query or page, with a name column and an impressions column. Clicks, CTR and position are optional but make the output useful. The header is detected by looking for clicks or impressions, and the other columns are matched by name: query, top queries, page, landing page, url, ctr and position are all recognised.

If the first row does not look like a header, the tool reads the columns in the order name, clicks, impressions, CTR, position and warns you that it did so. That fallback is useful for a hand-made file and risky for anything else, because a reordered export will be read against the wrong headings without complaint.

Numbers may contain commas or a percent sign. CTR written as 1.11% and CTR written as 1.11 are treated the same, since the symbol is stripped before parsing.

The three reasons a row is flagged

No clicks. Any row with zero clicks is flagged, with severity 3. It had impressions, so it appeared in results, and nobody clicked.

Weak CTR for its position. The tool splits the export into four position bands, works out the average CTR of each band within your own file, and flags a row when its CTR is below 60% of that average. Severity 2. No external CTR curve is used, which is the honest approach: your site's normal rate is a better comparison than a published average built from other sites.

Close to page one. A row with an average position between 4 and 15 is flagged with severity 2. It is already visible, and a small improvement could move it into the top three. Rows are sorted by total severity, then by impressions, then alphabetically, and the table shows the first 15.

Two filters sit above the result: a minimum impressions figure, which defaults to 500, and a maximum position, which defaults to 20. Raising the minimum removes low-volume noise. Lowering the maximum hides rows that are too far down to act on.

A worked example

A ten-row query export produced seven flagged rows, 327 clicks and 24,100 impressions, an average CTR of 1.36%. Every flag came from the position rule rather than the CTR rule, because each row sat between position 4.2 and 12.7.

Average CTR by position band in the example export
Position bandAverage CTRWhat it suggests
1 to 34%Two rows, one of them converting well
4 to 101.42%Six rows, the bulk of the file
11 to 200.27%Two rows, much weaker
21 and beyond0%No rows in this export

The band averages are the interesting part. The same page at position 5 and position 12 is not the same opportunity, and the export shows how steeply CTR fell between the bands on this site. A row at position 12.7 with 5,200 impressions and 18 clicks was flagged for position, not for its rate, because its rate was normal for that band.

Why the flag list is not a to-do listSeven of ten rows were flagged, which is too many to act on. The position rule is deliberately broad. Sort by impressions, take the top two or three, and check the actual search result for each before editing anything. A page at position 8 that already answers the query well may need links, not a new title.

A known quirk in the CTR column

If your export writes CTR as a percentage below 1%, with a percent sign, the table can show it multiplied by 100. In the example, a row with 18 clicks from 5,200 impressions is 0.35%, and the table showed 35%. Rows above 1% are shown as written.

Until that is fixed, read CTR from the clicks and impressions in the same row, or from Search Console itself. The flag reasons are based on clicks, impressions and position, so the list of rows to review is not affected by the display error; the percentage beside each row can be.

What the export cannot tell you

A low CTR has several possible causes: the query, the device, the snippet, the brand, the other results on the page, or a title that promised something the page did not deliver. The tool cannot see any of them. It knows only that the rate is low for the position.

Nor can it join queries to pages unless the export contains both dimensions. The Performance report exports one dimension at a time, so a queries file and a pages file are separate views of the same traffic. Comparing them by hand is possible; treating one as the other is not.

Finally, Search Console totals do not always add up the way you expect. Google's documentation notes that data grouped by queries is aggregated by property, while data grouped by pages is aggregated by page, and that chart totals can differ from table totals for that reason. A row-by-row sum will not always match the site total.

Turning the list into work

Export queries first and look for pages that appear for several related queries at once. Then export pages and check whether the same URL shows the same weakness. Two exports, read together, tell you whether the problem is the snippet or the page.

For a flagged row, open the query in the target market and look at the result as a searcher would. If the title is cut or the description is generic, fix the snippet with the snippet simulator. If the page does not answer the query, no title change will help, and the content optimiser is the better next step.

Questions

Common questions

Short answers about this tool and its limits.

Does this connect to my Search Console account?

No. There is no sign-in and no API call. You export a CSV from the Performance report and paste it here, and the rows are processed in the tab.

Which columns does the CSV need?

A name column, such as query, page or URL, and an impressions column. Clicks, CTR and position are optional but are needed for the CTR and position flags. Standard Search Console exports contain all five.

Why is a row flagged when its CTR looks normal?

Because position is a second reason. Any row between positions 4 and 15 is flagged as close to page one, even when its click-through rate matches the band average.

What counts as a low CTR here?

Below 60% of the average for the same position band in your own export. The bands are 1 to 3, 4 to 10, 11 to 20 and 21 and beyond. No external benchmark is applied.

Why does the CTR column show 35% for a row with 0.35%?

That is a known display fault. When CTR is written as a percentage below 1% with a percent sign, the table can multiply it by 100. Read the clicks and impressions in the same row, or check Search Console, until it is fixed.

Why do the rows not add up to the site total?

Search Console aggregates by property for some dimensions and by page for others, and the chart totals can differ from table totals. Google documents this. Treat the export as a view, not a ledger.

Can I analyse queries and pages in one file?

Only if the file contains both, which the standard export does not: one dimension is exported at a time. A combined file works if each row has a name and a unique key, but the table will treat each row as one item.

How many rows can I paste?

The tool applies no row cap, so the limit is what the browser tab can hold. Large exports are best filtered in a spreadsheet first, then pasted in: the analysis only needs the rows above your minimum impressions.