How I Turn GSC CSV Exports Into an SEO Opportunity Queue

Search Console is good at showing rows. It is less good at answering the operational question I usually have at the start of an SEO work session:

Which existing search signal deserves the next hour of work?

Sorting by impressions is not enough. A high-impression query may already be performing normally for its position. A low-CTR query may sit behind a SERP full of ads or rich results. A falling query may simply be seasonal.

I wanted a small, inspectable workflow that narrows the table without pretending it can make the final SEO decision. So I built a free GSC opportunity analysis tool that runs entirely in the browser.

No account is required, and the imported CSV rows never leave the device.

The input contract

The minimum input is the Queries CSV exported from Google Search Console's Search results report for one complete date range.

The tool reads:

• query
• clicks
• impressions
• CTR
• average position

Two optional exports make the analysis more useful:

1. An equal-length Queries CSV from the immediately preceding period.
2. A Pages CSV using the same current date range and filters.

The prior-period file enables trend rules. The Pages file creates a separate page queue.

That separation matters. A standalone Queries export and a standalone Pages export do not prove which URL ranked for which query. The tool does not invent that relationship.

The five opportunity labels

1. Striking distance

The default rule looks for queries with enough impressions and an average position from 8 through 20.

This is a review queue, not an instruction to rewrite the page. For each result I still need to:

• identify the ranking URL in GSC
• verify search intent
• inspect the live SERP
• check whether the relevant section and internal links are actually weak

The position range and minimum-impression threshold are adjustable.

2. CTR gap

Universal CTR benchmarks are usually too blunt. Brand demand, SERP features, device mix, and query type can make two sites at the same position behave very differently.

Instead, the workflow calculates the imported property's observed CTR by position band. A top-10 query is flagged when its CTR is below 70% of that local baseline and it has enough impressions to inspect.

That still does not prove the snippet is bad. It tells me which live result deserves a closer look.

3. Rising demand

With a prior-period CSV, the tool flags a query when impressions increased by at least 30% and by at least 20 rows, while the current average position is 40 or better.

The useful action is often defensive: preserve the part of the page already matching the query, then add evidence or internal support without replacing what works.

4. Decay

A query enters the decay queue when either:

• clicks fell at least 30%, with at least five clicks lost; or
• impressions fell at least 40%, with at least 50 impressions lost

Those absolute minimums suppress tiny percentage changes.

Before refreshing anything, I check seasonality, demand, competitors, indexing, device mix, and the page's edit history.

5. Page opportunity

The optional Pages CSV creates a separate list based on page-level impressions, CTR, and position.

It deliberately does not attach query recommendations to those pages. I open the page in GSC, inspect its actual query mix, and only then choose a page-level action.

Priority is not a traffic forecast

Every finding gets a deterministic priority score from 0 to 100. The score rises logarithmically with impressions and includes a fixed bonus for the opportunity type.

This makes the output sortable without letting one enormous query dominate the whole queue.

It is not a probability of ranking, a traffic forecast, or an estimate of revenue.

Confidence is also separate from priority. It describes sample strength based on impressions and whether a comparison period exists. A high-confidence decline can still be seasonal; a low-volume query can still matter commercially.

Why local-only processing matters

A GSC export can contain client queries, URLs, and performance metrics. Uploading that file to an unknown service creates an unnecessary data boundary.

In this workflow, parsing and scoring happen in client-side JavaScript. Files are not posted to SEO Report Kit. Analytics only records broad actions such as running the example or choosing an export format, never imported values.

You can inspect the complete workflow using synthetic sample data before selecting a real file.

The output is an evidence ledger

The useful endpoint is not another dashboard. It is a short list that can move into the team's existing workflow.

The result can be:

• copied as Markdown
• downloaded as CSV
• exported as Markdown
• exported as JSON

Each row keeps the observed evidence separate from the recommended verification step. That distinction helps prevent a common reporting mistake: turning correlation into a causal claim.

For a monthly process, I keep only a handful of owned actions. I archive the source exports and evidence ledger, ship the selected work, and compare the same dimensions after a complete period.

Important Search Console limitations

This method still inherits GSC's limits:

• average position is aggregated, not a fixed rank
• anonymized queries are omitted
• table rows may not sum to chart totals
• preliminary days can change
• query and page tables use different aggregation
• exported rows are not exhaustive for large properties

The tool analyzes the rows it receives. It does not claim complete query coverage or automatic cannibalization detection.

The GSC opportunity analysis tool is free, has a downloadable synthetic sample, and requires no signup. I would be interested in how other teams choose thresholds for striking-distance and decay reviews.