The Search Console 1,000 row limit is a display cap, not a data cap. Every table in the performance report tops out at 1,000 rows, and the Export button hands you exactly what the table was showing. Most sites have far more queries than that; Google just isn't showing them here.
The API is more generous with the same data. One Search Analytics request returns up to 25,000 rows, and you can page though roughly 50,000 a day per property per search type. So the useful question isn't how to raise the 1,000 row cap. It's how to get the API's rows out and keep them.
Get early access Free during early access. No card required.
What's in the rows you don't see
The 1,000 rows you get are the top 1,000 for the date range and filters you set, sorted by clicks. Everything cut from the bottom is the long tail, where queries have a handful of impressions each.
That tail is where most diagnostic work lives: a query drifting from position 14 to position 9, the near-duplicate terms that show two of your pages competing for the the same intent, the high-impression terms whose titles need rewriting. Those are the first rows the export drops.
Exporting more than 1,000 rows by hand
The workaround everyone arrives at is to slice the report until each slice fits: shrink the date range, add a page or country filter, export, repeat. It works. It also never reassmbles into one dataset, because each slice was sorted and truncated on its own, so a genuinely new query looks identical to one that was always below the cut. And it only reaches dates Google still holds, which is a target that moves every night.
How far each route reaches
| Route | Rows you get |
|---|---|
| UI export | 1,000 per table, per filter combination |
| Search Analytics API | 25,000 per request, about 50,000 a day per property per search type |
| BigQuery bulk export | Everything Google exports, starting the day you enable it |
| Month17 | Every row the API returns, pulled daily and kept with no retention limit |
What Month17 changes
Month17 queries the Search Analytics API for each connected property every day and stores what comes back, so your ceiling is the API's rather than the interfaces. On connect it backfills the full window Search Console still holds. Nothing expires after that, so the tail accumulates instead of rolling off at 16 months.
The archive sits behind an MCP server, so Claude or Cursor reads across years of rows instead of one truncated table. Asking which queries entered the top 20 this quarter but weren't there a year ago takes one question, where the manual route takes four exports and a merge.
One limit Month17 doesn't remove: it reads the same API you would, so queries Google anonymizes for privacy never arrive. The bulk export counts those as a flagged total, and if reconciling exact impressions is the job, BigQuery is the better tool. What the archive takes away is the 1,000 row ceiling, the repeat exports, and the expiry date.
Whatver route you pick, the rows you can reach today are the most of your history you will ever be able to reach. The data loss calculator shows which dates go next.