--- title: "Google Search Console Data Retention: The 16-Month Limit Explained" description: "Search Console exposes 16 months of search performance data. Learn what ages out, what BigQuery does not backfill, and how to preserve your history." canonical_url: "https://gscdump.com/learn-google-search-console/limits/16-month-data-retention" last_updated: "2026-07-20" --- Google Search Console gives you a [rolling 16 months of data](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops#change_date_range) in its Performance reports. The Search Analytics API draws from the same reporting window. Once a date falls outside it, you can't retrieve that date's performance data from either source. ## What Ages Out The limit applies to Search performance metrics and their dimensions, including: - Queries that led to your property - Pages shown in search results - Clicks, impressions, click-through rate (CTR), and average position - Country, device, date, and supported search appearance breakdowns You get aggregated reporting data rather than a log of individual impressions or visitors. Search Console also omits anonymized queries and can truncate lower-priority detail rows even while a date remains inside the 16-month window. Other Search Console reports have their own windows or show current state rather than a 16-month history. Do not assume that the Performance report's retention period applies to every report. ## Historical Context Search Console previously provided only 90 days of Search Analytics data. In January 2018, Google [introduced the new Search Console](https://developers.google.com/search/blog/2018/01/introducing-new-search-console) with 16 months of Search performance data, specifically to make longer-term trends and year-over-year comparisons easier. Google can also correct previously reported data. Its [data anomalies log](https://support.google.com/webmasters/answer/6211453) lists recent known logging and processing issues, and BigQuery's export log can record a revised version of an earlier data day. If Google reprocesses a date, an older archive may no longer match Search Console. ## The Comparison Window Is Narrow Sixteen months is enough to compare a month with the same month one year earlier, but only for about four months after the newer period ends. For example: ```text April 2024: Record the baseline April 2025: Compare year over year while both periods are available September 2025: April 2024 is outside the 16-month window ``` Keep an external archive if you need multi-year comparisons or want to revisit the baseline for an algorithm update or content change more than 16 months later. ## BigQuery Starts With Its First Export Google's [Search Console bulk data export](https://support.google.com/webmasters/answer/12918484) sends daily performance data to BigQuery without the Search Analytics API's daily row limit. It does not backfill the preceding 16 months. Google states that the [first export contains data for the day of that export](https://support.google.com/webmasters/answer/12917675). To preserve earlier dates that are still available, export them from the report or API separately. BigQuery tables and partitions are retained indefinitely by default, subject to any expiration policy set by your Google Cloud project or organization. Check those policies when you configure the export. ## Manual Export and API Archiving You can preserve data without BigQuery by exporting it from the Search Console interface or querying the Search Analytics API on a schedule. Both approaches have limits: - [UI exports](https://support.google.com/webmasters/answer/12919797) contain up to 1,000 representative rows from the report. - [API requests](https://developers.google.com/webmaster-tools/v1/searchanalytics/query) return at most 25,000 rows each and can be paginated. - The API [exposes at most 50,000 rows](https://developers.google.com/webmaster-tools/v1/how-tos/all-your-data#data-limits) for each data day, property, and search type, and that upper limit might not be reached. - Anonymized query text remains unavailable through either method. - You must handle authentication, retries, storage, and gap detection. Automation helps with missed runs and retries. It still cannot recover detail that Google never exposed. ## How gscdump Preserves Available Data For sites using its stored-data sync, gscdump: - Initially imports up to 180 days of history returned by the Search Analytics API - Can run separate Pro backfills for older dates that remain inside Google's available window - Re-fetches recent data as Google finalizes it, then continues with daily synchronization - Stores analytics tables in Cloudflare R2 using an Iceberg-backed data layout - Makes the stored data available through its API and MCP tools Those stored dates remain queryable after they leave Search Console. Coverage still depends on what the Search Analytics API returned, including Google's query-text anonymization and daily row limit. The hosted archive and daily sync require Pro access. Free accounts can query supported dashboard views and composed MCP reports live, but those requests do not preserve data after it leaves Google. The MIT-licensed CLI can run a separate local sync on your own machine. ## Retention and State by Report Search Console does not use one retention rule for every report:
Report or tool Window or state shown
Search performance 16 months
Crawl Stats Last 90 days
Temporary Removals Requests and blocks are shown for about 6 months
Core Web Vitals Current field assessment based on a rolling 28-day CrUX window
URL Inspection Google's most recently indexed version; optional live test of the current page
Page indexing Current status, historical charts, and limited example URLs; Google does not publish a fixed 16-month retention promise
Links A non-comprehensive sample of links Google has found over time; some may no longer exist
Sitemaps Latest submitted, fetched, and processing state for displayed sitemaps
Manual actions Current actions, their status, and manual-action history
## FAQ ### How is the 16-month window calculated? The reporting window rolls forward over time. Check the Performance report's date picker or query the API before planning a backfill. Calendar-month arithmetic and Pacific Time boundaries can make a hard-coded day count inaccurate. ### Can I request older performance data from Google? Google documents no recovery or extended-retention option for Search Console performance data after it leaves the 16-month report and API window. An external export created while the data was available is the practical recovery path. ### Does BigQuery export preserve data beyond 16 months? Yes, unless you or your organization applies an expiration policy. However, bulk export starts with the day of the first export and does not backfill earlier performance data. ### Was the retention limit always 16 months? No. Search Console previously provided 90 days of Search Analytics data. Google expanded the Performance report to 16 months in 2018. ### Does the 16-month limit apply to the API too? Yes, for the Search Analytics API. BigQuery bulk export is different: it accumulates daily data from the day the export starts and is governed by your BigQuery retention settings. ## Related Articles - [GSC Export Row Limits](/learn-google-search-console/limits/export-row-limits): How UI and API row limits work - [BigQuery Alternative](/learn-google-search-console/limits/bigquery-alternative): Compare BigQuery with API-based archiving - [1,000-Row Limit](/learn-google-search-console/limits/1000-row-limit): Retrieve more than the UI export provides - [Data Delay](/learn-google-search-console/limits/data-delay): Preliminary data, finalized data, and report updates - [GSC API Authentication](/learn-google-search-console/api/authentication): Set up OAuth for automated data access