---
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-09-11"
---

Search Console's Search results Performance report provides a **16-month window**. To inspect the available history, open its date filter and select **Last 16 months**. Google recommends this view for [checking seasonal patterns](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops#change_date_range).

If you'll need a period later, save it while it's available. Changing the chart to weekly or monthly groups doesn't extend that window.

## Keep the comparison you will need later

Suppose you're reviewing August 2026 against August 2025. Both months fit inside a 16-month window. August 2024 does not. This is a calendar example, not a guarantee that every site has data for every date inside the window.

Write down the comparison before choosing an export:

- Which months will you compare?
- Which search type, pages, or queries matter?
- Do you need daily rows, or only a period total?

A saved total can answer how many clicks a period received. It cannot later tell you which pages contributed if you never saved that breakdown.

For a visual trend review, use [weekly and monthly views](/learn-google-search-console/weekly-monthly-views). For a saved dataset, choose among the [report and API export methods](/learn-google-search-console/limits/export-row-limits).

## A new BigQuery export starts forward

Enabling bulk export today won't populate earlier months automatically. Google says the [first export contains data for its export day](https://support.google.com/webmasters/answer/12917675?hl=en). Use reports or the API separately for earlier dates that remain available.

This gives you two separate jobs:

| Need                           | Action                                               |
| ------------------------------ | ---------------------------------------------------- |
| Keep earlier available history | Export the dates you need now.                       |
| Build an ongoing bulk dataset  | Start BigQuery export and monitor successful writes. |

Check the saved date ranges before combining those sources. An overlap can duplicate days; a gap can leave days unaccounted for.

BigQuery retention depends on your settings. Google's [table reference](https://support.google.com/webmasters/answer/12917991?hl=en) says tables and partitions persist by default, subject to project or organization defaults. An expiration policy can delete saved data. See the [BigQuery comparison](/learn-google-search-console/limits/bigquery-alternative) before choosing it.

## Check what your saved copy contains

Keep the date range, search type, filters, dimensions, and extraction date beside each export. Confirm that the file opens and contains the periods you intended to save.

A longer history doesn't guarantee every query row. [Row limits and anonymized queries](/learn-google-search-console/limits/1000-row-limit) are separate constraints.

This guide concerns ordinary Search performance history. Check the documentation for other reports and newly added property types before assuming they provide the same historical coverage.

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.