How does the tool avoid API timeouts on long date ranges?

Any date range longer than 30 days is split into 7-day chunks and fetched batch by batch, with a progress bar and running row count. The batches are concatenated at the end, so the final CSV still covers the full range in one file.

Is there a row limit?

The tool itself sets no cap; it keeps fetching until the API returns no more rows. It warns if the running total passes roughly 1 million rows mid-fetch and again above 500,000 rows before CSV generation, because very large exports can hit browser memory limits. For big sites, split exports into monthly or quarterly ranges.

How do I get the query position analysis chart?

Select both the query and date dimensions before fetching. The tool then counts unique queries per month in position bands 1-3, 4-10, 11-20 and 20+, shows a stacked bar chart, and offers a separate query analysis CSV. If either dimension is missing, the analysis is skipped.

What permission does the Google sign-in ask for?

The OAuth flow requests the https://www.googleapis.com/auth/webmasters scope, which is the full Search Console scope rather than Google's separate read-only variant. The tool only ever reads data, and tokens are held in the Streamlit session rather than being stored anywhere.

Why does the date range stop at 16 months?

Google Search Console only retains 16 months of performance data, so the longest preset is Last 16 Months (480 days). Requesting older dates via the custom range returns nothing.

GSC Data Exporter: free Search Console tool

#about

Export complete Google Search Console data without the 1,000 row limit.

Automatically batches requests in 7-day chunks to prevent API timeouts on large date ranges.

Includes query analysis showing monthly distribution across position ranges (1-3, 4-10, 11-20, 20+).

Memory-optimized for datasets exceeding 100,000 rows with automatic category type conversion.

Streamlit appUses Search Console data

Platform: Browser-based (no installation required)
Input: Google Search Console access
Output: GSC data CSV with performance metrics
Category: Search Console

Use cases

Exporting full keyword data for analysis in Excel or Python
Building historical keyword tracking across long date ranges
Analysing query position distribution over time
Feeding complete GSC data into other SEO tools

#features

Unlimited data extraction (bypasses 1,000-row limit)
Auto-batching in 7-day chunks for large date ranges
Search types: web, image, video, news, discover, googleNews
Query position analysis with stacked bar visualisation
Memory optimisation for datasets over 100,000 rows
Large dataset warnings for 500k+ rows

#how-to-use

Sign in with Google via OAuth (full webmasters scope)
Select property and search type
Choose date range (7 days to 16 months, or custom)
Select dimensions: page, query, country, date, device
Include query and date dimensions for the position analysis chart
Download CSV with real-time batch progress

#faq

How does the tool avoid API timeouts on long date ranges?: Any date range longer than 30 days is split into 7-day chunks and fetched batch by batch, with a progress bar and running row count. The batches are concatenated at the end, so the final CSV still covers the full range in one file.
Is there a row limit?: The tool itself sets no cap; it keeps fetching until the API returns no more rows. It warns if the running total passes roughly 1 million rows mid-fetch and again above 500,000 rows before CSV generation, because very large exports can hit browser memory limits. For big sites, split exports into monthly or quarterly ranges.
How do I get the query position analysis chart?: Select both the query and date dimensions before fetching. The tool then counts unique queries per month in position bands 1-3, 4-10, 11-20 and 20+, shows a stacked bar chart, and offers a separate query analysis CSV. If either dimension is missing, the analysis is skipped.
What permission does the Google sign-in ask for?: The OAuth flow requests the https://www.googleapis.com/auth/webmasters scope, which is the full Search Console scope rather than Google's separate read-only variant. The tool only ever reads data, and tokens are held in the Streamlit session rather than being stored anywhere.
Why does the date range stop at 16 months?: Google Search Console only retains 16 months of performance data, so the longest preset is Last 16 Months (480 days). Requesting older dates via the custom range returns nothing.

/contact

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.

Book a 30 minute call → [email protected]