Skip to content

GSC CSV Export Combiner

Combine matching Google Search Console CSV rows with explicit dimensions, recalculated CTR, and a local review file.

Choose GSC CSV exports

Combine matching Search Console export rows with explicit dimensions and metrics. Exports stay on your device.

2–20 files · Up to 10 MB each · UTF-8 · Same headers and order

Data handling

Processing
The selected input is processed in your browser. Got A Tool does not send it to our servers.
Retention
Inputs and results are not saved to persistent storage. Resetting or closing this page clears the tool's working state.
Export
The tool may prepare a result after you run it. It downloads or copies it only when you choose that action.

Advertising and analytics are separate site services. We do not send selected file contents to them. Read the Privacy Policy for details.

How it works

Combine repeated Search Console rows with explicit rules

01

Choose matching exports

Every CSV must have the same header names in the same order, so no columns are guessed or remapped.

02

Define a duplicate

Select dimensions such as Date, Query, Page, Country, or Device that identify the same row.

03

Review the aggregate

Clicks and impressions are added, CTR is recalculated, and average position is weighted by impressions.

Output

A clean aggregate plus a review file when a row is unclear.

The ready CSV includes selected dimensions, Clicks, Impressions, CTR, and optionally Average position. A malformed metric or unsafe position calculation is kept in review.csv rather than silently excluded. If source exports overlap, matching rows are summed; choose non-overlapping date ranges or remove duplicate source exports first.

Why dimensions are selected manually

A report grouped by Query should not be combined the same way as one grouped by Date and Page. Choose the rows that represent the same measurement before the totals are calculated.

Questions

GSC CSV Export Combiner questions

Does this connect to Google Search Console?
No. Export CSV files from Search Console yourself, then choose them in this browser. The tool does not sign in to Google or make an API request.
How are overlapping exports handled?
Matching rows are summed. Use non-overlapping date ranges, or remove duplicate source exports first, to avoid counting the same Search Console data twice.
How is average position combined?
Each position is weighted by its row's impressions. If a selected position has zero impressions, that row is sent to review because no meaningful weighted position can be calculated.
Why must all headers match exactly?
A similar-looking column can have a different definition or source. Exact headers and order prevent a quiet merge of unlike exports.
Can I only stack CSVs without aggregating duplicate rows?
Use CSV Merge & Reconciliation when you need a reviewed union of source rows instead.

Keep working