Find opportunities in a Search Console CSV

1. Export the right table

In Google Search Console, open Performance → Search results. Choose the search type, date range, and filters you want to review, then select the Queries or Pages tab and export CSV. If the download is a ZIP, extract the relevant CSV first.

The analyzer supports English-language Queries.csv and Pages.csv exports with Clicks, Impressions, and Position columns. Date, country, and device tables serve other purposes and are not interchangeable with query or page reports.

2. Keep comparisons comparable

For a period comparison, export the current and previous periods separately. Use the same property, dimension, search type, and filters, and usually periods of equal duration. A Pages export cannot be matched to a Queries export.

Consider weekdays, seasonality, site changes, and data freshness when choosing periods. Two exports with different filters can produce apparent changes that say little about the underlying page performance.

3. Use low CTR as a review list

Upload the current CSV and choose a minimum impression count and a CTR threshold. The defaults are starting points for finding candidates, not universal benchmarks. The tool calculates CTR as clicks divided by impressions.

Inspect a candidate's search intent and average position before rewriting its title. A page at a lower position may naturally receive fewer clicks. Search result features and the mix of branded versus unbranded queries also affect CTR.

18 clicks ÷ 2,500 impressions × 100 = 0.72% CTR
This identifies a candidate to investigate, not a guaranteed opportunity for extra clicks.

4. Distinguish a decline from an absent row

When both periods are supplied, the analyzer compares clicks for matching queries or pages. The decline list shows the previous click count and the change for those matched rows.

Rows found only in the previous export appear in a separate missing list. They are not assigned zero current clicks: export limits, anonymized queries, filters, and omitted rows can affect what is available. Totals from the supplied rows can differ from the totals shown in Search Console.

5. Turn the report into a small set of actions

Export the findings and review a manageable number of pages. Confirm that the content still answers the query, that the page works, and that the title describes it accurately. Use a snippet preview to review proposed copy before publishing.

Record what changed and the date, then revisit comparable reports. This workflow helps prioritize investigation. It does not isolate the effect of a title edit or establish the cause of a traffic decline.

• Group similar pages or templates when looking for shared problems.
• Check indexing and technical issues separately from copy.
• Keep the original exports so another reviewer can reproduce the comparison.