Will Search Console finally exceed the 90 days of history?

Why has this 90-day limitation always existed?

The 90-day window in Search Console has never been officially justified by Google. This constraint forces SEO professionals to regularly export their data if they want to maintain a complete history of performance.

Technically, storing and serving massive volumes of impressions and clicks data comes with a significant infrastructure cost. However, third-party tools like Semrush or Ahrefs maintain much longer histories. The real reason is likely economic and strategic: to push larger sites towards paid solutions.

What does this announced extension actually mean?

Google does not specify the target duration (180 days? A year? Several years?), nor the reports that will be affected. The performance report, coverage data, Core Web Vitals: will it be all or just part?

This lack of details leaves practitioners in the dark. It is impossible to plan the cessation of a home archiving system or third-party solution if the actual scope of the change is unknown.

How does this change the game for historical analysis?

Currently, comparing a period with its N-1 equivalent beyond 45 days becomes impossible without prior export. Analyzing the impact of an algorithm update that occurred three months ago? You already had to have anticipated it.

An extended history would allow for more refined seasonal analyses, detection of long-term trends, and better correlation between SEO actions and results. Especially for e-commerce sites with strong seasonality.

• Quarterly manual exports could become obsolete if the extension exceeds 180 days
• Retrospective analyses will gain in granularity without relying on local archiving
• Correlation with past events (redesign, migration, penalty) will be simplified
• Small structures without data collection infrastructure will be the first beneficiaries
• Year-over-year comparisons could finally be native if Google extends to 12 months

Is this announcement really a surprise?

Not really. Google has already extended certain data windows in the past, particularly on Analytics 4 where raw data is retained for 14 months. This development aligns with the goal of catching up with market standards.

What is more surprising is the complete lack of a timeline. When Google communicates about a feature without a date, experience shows that the delay ranges from a few months to… never. Remember some promises about the expanded Indexing API. [To be verified]

What data will actually be extended?

The announcement refers to “Search Console reports” in the plural. But all reports? The performance report consumes the most resources with its granular impression/click data per URL and query.

I would bet on an extension in multiple phases: first the aggregated metrics (coverage, Core Web Vitals, links), then possibly the performance report. Or it could be a partial extension: 180 days for detail per query/URL, a year for aggregates. Nothing is confirmed. [To be verified]

Should we abandon manual archiving because of this?

No, at least not immediately. As long as we do not know the exact scope and the deployment date, continuing to export your data remains the basic caution. Especially since Google could limit the extension to certain types of accounts or traffic volumes.

Moreover, even with an extended history, there is no guarantee that the interface will allow for mass exports as flexible as a homemade database. API limits (5,000 rows per query on the performance report) are likely to remain unchanged.

What should you do while waiting for this extension?

Continue your regular exports via the API or the manual interface. There is no guarantee on the timeline or on retroactivity: the newly extended data will likely not cover the history prior to deployment.

If you do not yet have an archiving system, now is the time to set up an automated script (Python + Search Console API, or Google Sheets with Apps Script). Even basic, it will help you avoid losing the history of the previous months.

How to adapt your analysis workflow once the extension is deployed?

Once the window is extended, immediately check which reports are affected and to what depth. Test mass exports to see if the API limits change.

Adapt your dashboards and client reports to leverage this historical depth. Year-over-year seasonal analyses will finally become native if Google reaches 12 months. Take advantage of this to refine your correlations between SEO actions and measurable results.

What mistakes should you avoid during this transition?

Do not delete your archives right after the announcement. Wait for the actual deployment and confirm that your pre-extension history remains accessible. Google sometimes has surprises regarding the actual scope.

Also, avoid overestimating the impact: if you are working on recent sites or launches, 90 days are often more than enough. The extension will mainly benefit established sites with several years of history and long-term comparative analyses.

• Maintain regular exports until the scope of the extension is confirmed
• Document the current structure of your archives to facilitate future migration
• Test the API as soon as it is deployed to identify any new limits
• Prepare report templates that make use of extended histories (YoY, long-term trends)
• Anticipate server load if you launch large-scale retroactive analyses
• Train your teams on the new available historical analysis workflows