Google does not send a calendar invite. About 16 months after a day lands in Search Console Performance, that day stops appearing in the UI and in the Search Analytics API. Support cannot restore it. Looker Studio cannot invent it. A CSV you never exported cannot be recovered from Google later.
So the useful question is not “does Google delete Search Console data?” — yes. It is when each of your days falls out, and what you copy while the day is still there.
Sibling guides: 16-month limit, year-over-year when the prior year is gone, Best Google Search Console history tools.
The short answer
| Fact | Detail |
|---|---|
| Window | Rolling ~16 months of Performance data |
| What ages out | Clicks, impressions, CTR, position, and query/page/country/device breakdowns for that calendar day |
| Where it disappears | Search Console UI and Search Analytics API (and anything that only reads them live, including Looker Studio’s native connector) |
| Publish lag | New days usually appear ~2–3 days late; recent days keep being revised |
| Recovery | None once Google drops the day |
| Property age cap | If you verified the property four months ago, you never had sixteen months to begin with |
“Delete” here means Google stops serving the day. Your site did not lose the rankings that day produced; you lost the ledger.
How to reason about a specific day
Take a closed calendar day D that already appears in Performance.
- Approximate expiry: D + ~16 months (Google’s window is “about” sixteen months; treat the boundary as a cliff, not a soft fade).
- Until that cliff, the day is still in the live window — UI, API, Looker connector.
- After the cliff, every live reader returns empty for that date. Empty is missing data, not zero traffic.
The free GSC data expiry calculator runs that arithmetic for any day and lists which months of the current window fall out next.
Worked example (illustrative): if today is 6 October 2026, a Performance day from early June 2025 is near the edge of the window. A day from May 2025 is likely already gone. Do not build a board deck that assumes May 2025 still loads from Google.
Publish lag matters for the newest end of the window, not the oldest. On a Wednesday the latest complete day is often Monday. SiteLine’s own imports re-read recent days because Google revises them — same honesty you need in any warehouse.
What is not on the same clock
- Pages / indexing reports — current state, not a 16-month Performance history.
- Sitemaps list — configuration, not click history.
- BigQuery bulk export tables — once a day lands in your dataset, retention is yours (subject to your Cloud policies). That does not resurrect days that never exported.
- Hosted archives — keep what they imported while you subscribe; they cannot invent pre-connect gaps Google never held.
Why month 17 feels sudden
Teams notice deletion when:
- A YoY comparison first requests the prior year and the series goes blank.
- An agency template assumes 24 months of GSC.
- Someone opens Looker Studio after trusting it as “the archive.”
Prevention is boring and effective: copy while Google still holds the day. Options ranked by job:
- Hosted archive — connect once, backfill the overlap Google still has, keep importing. SiteLine is built for this: ~16-month backfill on connect, up to 25k rows/day/report, retention while subscribed, cookieless analytics beside it, read-only MCP for agents.
- Scheduled Search Analytics API pulls — you own the database; you own the on-call.
- BigQuery bulk export — best first-party forward path; pair with a backfill for days before enable. See BigQuery vs hosted.
- UI CSV / Sheets — fine for a slide; weak for retention (export more than 1,000 rows).
Mental model: four jobs under one word
People say “history” and mean four different things.
- Live window — what Google still serves (~16 months).
- Forward archive — days stored from enable day onward.
- Backfill archive — copy of the overlap on connect day, then ongoing imports.
- Recovered past — days already aged out. Nobody sells this honestly.
If a vendor promises to “restore” deleted Search Console days, walk away. If they promise to copy what Google still holds and keep it under a retention policy, that is a real product.
What SiteLine does on this problem
SiteLine connects with webmasters.readonly, backfills up to about sixteen months of what Google still holds (limited by property verification age), then keeps importing. Imported days stay available while you subscribe. Agents query the warehouse over MCP without write tools — no indexing, no sitemap submit.
Start a 7-day trial (no card) · Pricing from $4.99/mo · MCP overview · Connect Search Console
Prefer the agent path on signup: Register with MCP intent.
FAQ
Exact day Google deletes a Performance day?
Google documents a rolling window of about sixteen months, not a public per-day countdown email. Treat the boundary as hard: plan copies before you need month-17 YoY.
Does deletion affect my rankings?
No. Rankings live in Search. Deletion removes your ability to report that day’s clicks and impressions from Google’s live store.
Can I recover a day with the API after it ages out?
No. The API serves the same live window as the UI for Performance history.
What if my property is only six months old?
You have about six months to copy. No tool invents the prior year Google never stored for that property.
Is Looker Studio enough to survive deletion?
No — Looker Studio Search Console limits. Point Looker at a store you control if you want charts of retained days.