Why Is Search Console Data Limited to 16 Months?

A client asks, "Can we compare this with the same period last year, or even two years ago?" You open the date filter in Search Console and find that the longest option is "Last 16 months". Two years ago simply isn't there. That's not a bug or a limit on your account; the Search Console 16-month data limit applies to everyone.

This article explains what the limit means, what Google has said about it, exactly what disappears when the window moves on, and how to keep your history.

What the 16-month limit actually means

The Search Console Performance report, and the Search Analytics API that serves the same data, show clicks, impressions, CTR and average position for at most the last 16 months. Each time a new day is added, the oldest day in the window falls out. It's a rolling window: a day you can't see today is a day you'll never see again.

The limit applies to every way of getting the data out, not just the report. Downloads from the interface, the Looker Studio connector and the API all draw from the same source. Connecting a new tool "so it can go further back" won't help unless that tool was already storing the data.

Why does Google keep 16 months?

Google hasn't published a detailed technical rationale for the 16-month figure, but its official material offers two clues.

1. It was designed for year-over-year comparison. When Google introduced the new Search Console in 2018, it said users had long been asking for more data, and that the new Performance report's 16 months of data would make it easier to analyse longer-term trends and compare year over year. Offering 16 months rather than 12 leaves enough buffer to set the last few months beside the same months a year earlier. That's a natural reading of the stated goal, not a formula Google has spelled out.

2. Serving data has a cost. When explaining row limits in performance data, Google mentions constraints around serving latency, storage and processing resources. That explanation wasn't given for the retention period specifically, but it is reasonable to assume that keeping every query, page, country and device breakdown for every site indefinitely would be expensive. Beyond that, it's best not to speculate past what Google has documented.

The practical takeaway is clear. Google tells anyone who needs a longer history to keep the data themselves. Its guide to debugging traffic drops says that if you want to extend beyond 16 months, you can use the Search Analytics API or bulk data exports to pull the data and store it in your own systems.

What you lose when the window moves on

For agencies and consultants the problem is sharper. When you take on a new client, their history is only the last 16 months. A year later, when you want to "compare with where we started", that starting period is about to fall out of the window.

When 16 months isn't enough

Seasonality needs more than one year

Google's guide suggests widening the date range to 16 months when assessing a traffic drop, so you can see whether it repeats at the same time every year. But a single previous year is thin evidence for a pattern; last year's period may have been unusual itself. Two or three years of data make "it's always like this at this time of year" a much safer statement.

Long-term effects show up slowly

Content strategy, site structure changes or a domain migration can take months to play out. To compare before and after, you need both the period before the change and a long stretch after it. We explain why rankings drift over time in why Google rankings keep changing.

Reporting continuity

If you produce monthly or annual reports, the figures in old reports should remain verifiable. Once the source data is gone, you can no longer recalculate a number from an old report.

How to keep Search Console data: four options

1. Regular exports from the interface

The simplest option is downloading the Performance tables every month. However, Google notes that the interface exports a maximum of 1,000 rows. That may be enough for small sites, but it's impractical for storing several breakdowns (query × page × country × device) completely and regularly, and it's easy to forget.

2. The Search Analytics API

The API lets you pull data day by day with whatever dimensions you need. According to Google, it can return up to 50,000 rows per day per site per search type; the default is 1,000 rows and you page through the rest. It needs technical skills and a database, but it's flexible.

3. BigQuery bulk data export

In 2023 Google announced bulk data export, which sends Search Console data to BigQuery on an ongoing, daily basis. According to Google, it includes all performance data except anonymized queries, which are filtered out for privacy, and it isn't affected by the daily row limit. It requires a Google Cloud project, and only property owners can set it up. Because it runs on an ongoing basis once configured, your archive grows from that point on, which is why setting it up early matters. It suits large sites with many pages or queries best. Keep in mind that BigQuery brings its own costs and maintenance.

4. A tool that stores the data for you

If you'd rather not build infrastructure, you can use a tool that connects to Search Console and saves the data to its own database every day. One point to keep in mind: on the day you connect, such a tool can import the last 16 months, but nothing older, because Google no longer has it. Your archive grows from the connection date onward.

Comparing the options

A checklist you can start today

• Confirm you're a verified owner of your most important Search Console properties.
• Decide which breakdowns you'll need long term (query, page, country, device).
• Pick one of the options above and start it this month; every month you wait moves the start of your archive forward.
• Before a big change such as a migration or redesign, save the current 16 months somewhere.
• Keep a separate log of important changes with dates; context matters as much as data.
• Remember how average position is calculated when you read stored data; see how to read Search Console average position.

How SEOLOK keeps your history

SEOLOK's Search Console analytics connects read-only through your Google account. On connection it imports the last 16 months of daily data (query, page, country, device, clicks, impressions, CTR and average position), then adds new days every night. Google's data arrives about two days late, so the newest days appear with that delay.

Because the data is stored in SEOLOK's database, days that later fall out of Google's 16-month window aren't lost from your account. The archive grows from the day you connect; we can't retrieve data older than 16 months before that date, because Google no longer provides it.

That lets you compare Search Console data with your tracked keyword rankings and your monthly reports in one place, across years. To see the opportunities in your Search Console data right away, try the free keyword opportunity finder.

In short: your archive starts today

The 16-month limit isn't a setting you can change; it's a design choice in Search Console. Its consequences aren't inevitable, though. The day you start storing the data yourself, the window stops limiting you. A simple archive started today means that in a year you can say "let's compare with last year", and in two years "let's compare with two years ago". Every month you wait is a month you can't get back.