Google Search Console historical data: how to keep it past 16 months

Google Search Console keeps 16 months of historical performance data. Every day, the oldest day in that window is deleted: the web interface stops showing it, the API stops returning it, and nothing can bring it back afterward. Any Search Console data you have from further back exists only because someone saved it before it expired.

This page covers what that historical data includes, the four ways to keep it (manual export, the Search Console API, Google's BigQuery bulk export, and an automatic archive), and a worked example of querying an archive with Claude. GSC PAP's archive starts on its own when you sign in with Google: it saves the full 16 months Google still has, then adds each new day.

How long does Google Search Console keep historical data?

16 months. That is the limit for the Performance report: clicks, impressions, click-through rate and average position. It is a rolling window, so each new day of data pushes the oldest day out. The Search Console API serves the same 16 months; there is no longer archive behind it.

Google introduced the 16-month window in January 2018 with the new Performance report, the successor to the old Search Analytics report, to make longer-term trends and year-over-year comparisons easier. It is still 16 months today. At the recent end, new data usually shows up two to three days late.

Can you recover Search Console data older than 16 months?

No. Once a day falls out of the 16-month window, Google deletes it on its side. The Performance report cannot show it, the API cannot return it, and no third-party tool can recover it, GSC PAP included. When a tool shows you older Search Console data, it is because that tool saved the data while it was still inside the window.

So the useful question is not how to get old data back, but how to stop losing more of it. Until you start saving it somewhere, one more day of your site's history expires every day.

What does Search Console historical data include?

Four metrics (clicks, impressions, CTR and average position) that you can break down by query, page, country, device, search appearance and date, and filter by search type, such as web, image or video. How much of it you can actually see depends on where you look:

• ·The Performance report in the web interface shows up to 1,000 rows per table. On a site with thousands of queries or pages, you see the top of the list and nothing below it.
• ·The Search Analytics API returns up to 25,000 rows per request and lets you page through more. Google's documentation also caps it at 50,000 rows per day for each search type, sorted by clicks.
• ·Google's BigQuery bulk export is not affected by that daily row limit. Google describes it as most useful for large sites with tens of thousands of pages, or of queries a day.
• ·In the interface, the API and the BigQuery export alike, anonymized queries are left out of the query rows. Google defines them as very rare queries, not issued by more than a few dozen users over two to three months. Your totals still include their clicks and impressions, but no tool can show you the queries themselves.

Why keep Search Console data past 16 months?

Sixteen months covers one year-over-year comparison and a few months more. That is enough to compare this month with the same month last year, and not enough for anything longer, such as:

• ·Comparing this year with two years ago, or following a query or a section of your site across several years.
• ·Telling a seasonal dip from a real decline when the season you need to check is more than 16 months back.
• ·Looking at traffic before and after a migration, a redesign or a Google core update once that date has aged out of the window.
• ·Keeping a record for clients or stakeholders that does not quietly get shorter every day.

How do you keep Search Console data longer than 16 months?

There are four ways. They differ in setup, in how complete the data is, and in whether they can save the 16 months you already have.

• ·Manual export. In the Performance report, export to CSV or Google Sheets on a schedule. It is free and needs no setup, but each table stops at 1,000 rows, the tables are separate summaries (you cannot later ask which page a query landed on in a given week), and it only works if someone remembers to do it.
• ·The Search Console API. A script pulls one day at a time (the approach Google's documentation recommends) and stores the rows in your own database. It can also save the 16 months still in Search Console, but you need a Google Cloud project, OAuth credentials, a scheduler and somewhere to keep the data.
• ·BigQuery bulk export. This is Google's official answer. A property owner connects Search Console to a Google Cloud project with billing enabled, enables the BigQuery API and gives Search Console's service account access; daily exports then start within 48 hours. It is the most complete record, but it only exports from the day you set it up, with no backfill of the 16 months already in Search Console, and you read it with SQL.
• ·An automatic archive. A service reads the API for you, saves the full 16 months on day one and keeps adding days, with no code or Cloud project on your side. This is what GSC PAP does. It also works alongside BigQuery: BigQuery captures more rows from the day you turn it on, and the archive keeps the 16 months BigQuery never copies.

How does GSC PAP keep your Search Console history?

You sign in with Google and the archive starts by itself. There is no button to press, no Google Cloud project and no code. GSC PAP is read-only and free during the public preview, and you query the archive in plain language from Claude, Cursor or Claude Code.

• ·On sign-in, it backfills the full 16 months Google still has for every property your Google account can read.
• ·After that, a daily job fetches each new day, about four days behind today, because Google's numbers take around three days to settle.
• ·Days older than 16 months stay in your archive after Google deletes them, so from the day you connect, your history keeps growing past 16 months for as long as your account is active.
• ·Questions about stable past data (older than about three days) are answered from the archive at zero Google API quota. Recent days still come live from Google.
• ·The archive stores query, page, country, device and date, with clicks, impressions, CTR and position. It is private to your account.
• ·What it cannot do: bring back days Google deleted before you connected, or show anonymized queries. It reads the same Search Analytics API, so on a very large site it holds what the API exposes, not every row a BigQuery export would.