What must the CSV contain, and why does the standard GSC export fail?

Every row needs query, page, clicks, impressions and position together. The GSC UI performance export splits queries and pages into separate files with no combined view, so use an API-based export (for example the GSC Data Exporter tool on this site) that includes both query and page per row. Common column name variants (Top queries, URL, Average position and so on) are auto-mapped.

Why do my results show full URLs instead of folders?

The domain you enter is removed from page URLs by literal string replacement, so it must match exactly, including protocol, www and the trailing slash. If it does not match, nothing is stripped and the folder splitting runs against the full URL text.

How accurate is the Pages count per folder?

It counts pages whose URL contains the folder path as a substring, so overlapping folder names inflate counts: a /car folder would also count /carpets pages. Treat Pages as approximate wherever folder names share prefixes.

Is the Keywords column a count of unique queries?

No, it is a row count. A query that ranks against three pages inside the same folder counts three times, so read it as the number of query-page combinations rather than distinct keywords.

How is the Top Keyword per folder chosen?

Per page, the top keyword is the query with the most clicks, and its impressions and position become the Volume and Top Position figures. At folder level the tool takes one page's top keyword per folder rather than recomputing across all pages, so treat the folder-level Top Keyword as indicative rather than a strict maximum for the whole folder.

Back to Tools

GSC Folder Analyser

Use cases

Understanding which site sections perform best Identifying underperforming folders Content strategy by site section Quick site performance overview

Maps various GSC column names to standard labels, converts metrics to appropriate data types, removes domain prefix/query parameters/anchors, and splits URLs into folder hierarchy levels.

Aggregates by folder path summing traffic and counting keywords.

Extracts highest-traffic query per page using forward-fill technique.

Adjustable folder depth slider (1-10).

Streamlit App GSC Data

Platform

Browser-based (no installation required)

Input

GSC export CSV

Supports various column naming conventions

Output

CSV: Traffic (summed clicks), Keywords (query count), Pages (count per path), Path, Top Keyword, Volume (impressions), Top Position.

Launch App View Source

Features

Auto column name mapping (Top queries, Query, Queries, etc.)
URL cleaning: removes domain, query params, anchors
Path segmentation into folder hierarchy
Folder depth slider (1-10 levels)
Traffic summing and keyword counting per path
Top keyword extraction via forward-fill

How to use

1 Export data from Google Search Console
2 Upload CSV to the tool
3 Enter your domain with protocol and trailing slash (e.g., https://example.com/)
4 Set maximum folder depth (1-10)
5 Review aggregated metrics in interactive table
6 Download CSV with folder analysis

Frequently asked questions

What must the CSV contain, and why does the standard GSC export fail?: Every row needs query, page, clicks, impressions and position together. The GSC UI performance export splits queries and pages into separate files with no combined view, so use an API-based export (for example the GSC Data Exporter tool on this site) that includes both query and page per row. Common column name variants (Top queries, URL, Average position and so on) are auto-mapped.
Why do my results show full URLs instead of folders?: The domain you enter is removed from page URLs by literal string replacement, so it must match exactly, including protocol, www and the trailing slash. If it does not match, nothing is stripped and the folder splitting runs against the full URL text.
How accurate is the Pages count per folder?: It counts pages whose URL contains the folder path as a substring, so overlapping folder names inflate counts: a /car folder would also count /carpets pages. Treat Pages as approximate wherever folder names share prefixes.
Is the Keywords column a count of unique queries?: No, it is a row count. A query that ranks against three pages inside the same folder counts three times, so read it as the number of query-page combinations rather than distinct keywords.
How is the Top Keyword per folder chosen?: Per page, the top keyword is the query with the most clicks, and its impressions and position become the Volume and Top Position figures. At folder level the tool takes one page's top keyword per folder rather than recomputing across all pages, so treat the folder-level Top Keyword as indicative rather than a strict maximum for the whole folder.

Want me to run this for you?

I run this tool as a managed service, or build something custom around your data. You get the insights without touching the code.

Tell Me What You Need

Keyword Cannibalisation FinderAppSearch Console

Find keywords where multiple pages compete for the same query.

Title Keyword Gap Finder v2AppSearch Console

Two-mode title analysis: find GSC keywords missing from titles and surface title segments with no search volume.

Striking Distance CSVScriptSearch Console

Find striking distance keywords from GSC and crawl CSV exports.

Top Traffic Pages (GSC API)ScriptSearch Console

Pull GSC data via API and analyse traffic distribution across pages.

GSC Coverage VisualiserScriptSearch Console

Visualise indexing issues from Search Console coverage reports with interactive Plotly treemaps and sunbursts.

Redirect List FormatterBrowserMigration

Convert URL lists into redirect rules for different platforms.

Need something built for your business?

This tool started as bespoke client work. I build custom scripts, data pipelines, and full apps for SEO and product data problems that off-the-shelf tools don't solve.