--- title: "GSC 1000 Row Limit: How to Get All Your Keyword Data" description: "Google Search Console caps UI exports at 1,000 rows. Learn how to access your full keyword data using the API, BigQuery, or automated sync tools." canonical_url: "https://gscdump.com/learn-google-search-console/limits/1000-row-limit" last_updated: "2026-04-30T06:42:19.353Z" --- Google Search Console's UI only exports 1,000 rows. If your site ranks for more than 1,000 keywords — and most do — you're working with incomplete data every time you hit "Export." ## Why the 1,000 Row Limit Exists The GSC interface is a monitoring tool, not a data warehouse. Google designed it for quick checks: top keywords, trending pages, recent errors. The 1,000 row cap keeps the UI fast and the export files small. But the limit creates a blind spot. A site ranking for 15,000 keywords sees only 6.7% of its data in a single export. For enterprise sites with hundreds of thousands of keywords, the visible data drops below 1%. ### What Gets Cut GSC sorts by clicks (descending) before truncating. The 1,000 rows you see are your **highest-traffic terms**. Everything else disappears: - Long-tail keywords with 1-5 clicks/month - New keywords you just started ranking for - Position 5-20 keywords with high impressions but low CTR - International variants and misspellings These hidden keywords often represent your biggest growth opportunities. [Patrick Stox at Ahrefs](https://ahrefs.com/blog/gsc-hidden-terms/) found that **46% of clicks** in GSC are attributed to hidden terms that don't appear in standard exports. For some sites, this reaches 90%+. ## Method 1: GSC Search Analytics API The API raises the ceiling from 1,000 to **25,000 rows per request**, with a daily limit of **50,000 rows per property**. ### How It Works The [Search Analytics API](https://developers.google.com/webmaster-tools/v1/searchanalytics/query) accepts a POST request with dimensions, date range, and row limit: ```bash curl -X POST \ 'https://www.googleapis.com/webmasters/v3/sites/https%3A%2F%2Fexample.com/searchAnalytics/query' \ -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "startDate": "2026-02-01", "endDate": "2026-02-28", "dimensions": ["query", "page"], "rowLimit": 25000, "startRow": 0 }' ``` To get beyond 25,000 rows, paginate using `startRow`: ```bash # First request: rows 0-24,999 "startRow": 0, "rowLimit": 25000 # Second request: rows 25,000-49,999 "startRow": 25000, "rowLimit": 25000 ``` ### The 50,000 Daily Ceiling Even with pagination, Google enforces a hard limit: **50,000 rows per day per property per search type**. This is the real bottleneck for large sites. **Workaround: narrow date ranges.** The 50,000 limit applies per API call context. Request one day at a time instead of a 30-day range: ```text Feb 1: up to 50,000 rows Feb 2: up to 50,000 rows Feb 3: up to 50,000 rows ... Feb 28: up to 50,000 rows Total: up to 1,400,000 rows for February ``` This is how automated sync tools work — they stay under the daily limit by fetching narrow date windows. ### Limitations - Requires OAuth 2.0 setup (service account or user consent) - Token refresh handling needed for long-running scripts - Still subject to Google's sampling on very large sites — a [Similar.ai analysis](https://similar.ai/blog/search-console-api-limits/) found **66% impression data loss** even with API access - Rate limiting: 1,200 requests per minute (rarely hit, but can matter for multi-site operations) ## Method 2: BigQuery Bulk Data Export Google's [BigQuery export](https://support.google.com/webmasters/answer/7491450) bypasses row limits entirely. A [FindLaw white paper](https://www.findlaw.com/marketing/blog/google-search-console-ui-api-vs-google-bigquery-gsc-comparison-of-data-storage-access.html) found BigQuery returns **8.75x more data** than the API for the same site and date range. ### Pros - No row limits whatsoever - Complete, unsampled data - SQL-queryable warehouse ### Cons - **No historical backfill** — only captures data from the day you enable it forward - Requires Google Cloud billing account - SQL knowledge mandatory - 2-3 day data delay - Query costs ~$5/TB scanned (can add up with frequent dashboard refreshes) - [Feb 2026 pricing changes](https://cloud.google.com/storage/docs/pricing#network-transfer) added multi-region egress charges BigQuery is ideal if you already use Google Cloud and have SQL expertise. For most site owners, it's overkill. ## Method 3: Automated Daily Sync The most practical approach for complete keyword data: sync your GSC data daily to your own database. gscdump connects to your GSC account via OAuth and runs daily syncs automatically. Each sync fetches one day of data at a time, staying well under the 50,000 row API limit. Your data accumulates in a dedicated Cloudflare D1 database with no export caps. **What you get:** - Every keyword, page, country, and device combination — not just the top 1,000 - Historical data preserved permanently (no 16-month deletion) - Query via API or MCP (natural language) — no SQL required - Automatic backfill of your existing 16 months on signup Setup takes 5 minutes: OAuth connect, select your sites, and syncing starts immediately. ## Comparison Table
Method Row Limit Setup Time Cost SQL Required Historical Backfill
GSC UI Export 1,000 None Free No N/A (16 months only)
GSC API (manual) 25k/request, 50k/day Hours-days Free No (but code required) N/A (16 months only)
BigQuery Unlimited 1-2 hours + 2 day delay $0-50+/mo Yes No
gscdump Unlimited 5 minutes Free beta No Yes (16 months)
## When 1,000 Rows Is Actually Enough Not every site needs to worry about this limit. If your site has: - Fewer than 1,000 unique keyword+page combinations per date range - Primarily informational content (fewer keyword variations) - Limited international traffic (fewer country/device splits) Then the UI export gives you complete data. This typically covers sites under 50k monthly search impressions. ## FAQ ### How many keywords does my site actually rank for? Check GSC → Performance → Queries tab. The number shown at the top (e.g., "Rows: 5,432") is the total unique queries for your selected date range. If this exceeds 1,000, you're losing data in exports. ### Can I get more than 1,000 rows without coding? Yes. gscdump provides a no-code solution that syncs all your keyword data automatically. Alternatively, third-party tools like SEOTesting, Ahrefs, and Semrush pull data via the API on your behalf — though they're subject to the same API limits. ### Does the 1,000 row limit apply to all GSC reports? Yes. Pages, Queries, Countries, Devices — every report tab in the UI caps exports at 1,000 rows. The only exception is the Links report, which has its own separate limits. ### What about the "anonymous queries" Google hides? Even with API access, Google filters "rare queries" for privacy. These are typically long-tail terms with very few impressions. Ahrefs estimates this affects 46% of total clicks across sites they studied. No export method recovers these — they're server-side filtered before the data reaches any export. ### Is the API free? Yes. The Search Analytics API is free to use with a Google Cloud project. You need OAuth credentials but no billing account (unlike BigQuery). The only limits are 50,000 rows/day/property and 1,200 requests/minute. ## Related Articles - [GSC Export Row Limits](/learn-google-search-console/limits/export-row-limits) — The full breakdown of UI, API, and daily limits - [BigQuery Alternative](/learn-google-search-console/limits/bigquery-alternative) — When BigQuery makes sense (and when it doesn't) - [16 Month Data Limit](/learn-google-search-console/limits/16-month-data-retention) — Your historical keyword data is disappearing - [GSC API Authentication](/learn-google-search-console/api/authentication) — Set up OAuth for API access