Full storage and historical data
Full storage imports a property’s final daily Search Console data and keeps it in the workspace. This page explains what is stored, how the import runs, the statuses and quotas, and what stored history does and does not do today.
✓ Checked in the workspace code · 4 October 2026
Two ways a property can be loaded
Dashboard Management controls which properties appear on your main dashboard and whether each one also has full storage. A property can be shown in two ways:
| Mode | How the data arrives |
|---|---|
| Dashboard (live API) | the property appears on the home dashboard and its data is requested directly from Google Search Console |
| Full storage | the workspace imports the daily Search Console data and keeps it in its own storage |
The page shows two counters: dashboard properties used out of 10, and full-storage properties used out of 5.
What full storage keeps
- Granularity: final daily rows by date, query, page, country and device, so one stored day holds the query × page detail.
- Search type: Web only.
- Only final data. The importer takes a day only once Google marks it final, which is about two days behind the calendar.
- Row limit. Google returns at most 25,000 rows per request; the importer pages through them. A day that still reaches Google’s limit is counted as an “API-limited day”.
How the import works
- First import: up to the last 16 months of final days.
- Then daily: each new final day is added after it becomes final.
- One property at a time: imports run in a queue, so a new property can wait.
- Growth: history grows up to 10 years; older days are removed.
- Turning it off: the stored data is kept for 30 days and then deleted. Turning it back on within that time resumes from the stored days.
Reading the status
| Status | Meaning |
|---|---|
| Off | no storage for this property |
| Queued | waiting for its turn |
| Importing | days are being fetched; progress shows how far it has gone |
| Synced | up to the newest final day |
While a property imports, the row shows the next day to fetch, the number of rows stored and the number of API-limited days, and any error.
The properties table
- Columns: Dashboard (checkbox), Property, Full storage, Permission Level, Google Account and Reports.
- Buttons: a search box, “Clean up inaccessible” (removes saved preferences for properties you can no longer access), “Include all”, “Exclude all” and a copy button for the table.
- Permission levels: Owner (full control), Full User (can view all data), Restricted (view-only access) and Unverified (pending verification) follow Search Console permissions.
Bing properties are in a separate Beta table: only Bing properties that also exist in connected Search Console are available for reports.
Which reports use the stored history
At the time of writing, the report pages request their data from Search Console live. The stored history is imported and kept per property, ready for features that read it, but the reports themselves do not yet draw from it. When a report states its data source and date window, trust that label rather than the existence of a stored history.
Stored rows are designed to be aggregated without early rounding: position is weighted by impressions, which differs from a plain average of daily positions.
Which properties to store
- Start with the properties you analyse most. Five fit in the storage quota.
- Prefer sites whose long-term history matters for trends, forecasts and migrations.
- Leave small or inactive sites on the live API. They do not need a copy.
If something looks wrong
| Symptom | Cause and fix |
|---|---|
| Storage badge says “Unavailable” | the storage service is not available on this deployment |
| A property stays Queued | imports run one property at a time; wait for the one in progress |
| Many API-limited days | large property: Google returns a capped number of rows per day, so stored days may be partial |
| No more room for storage | the quota is 5 properties; turn off storage for another one first |
Full storage, answered
How much history is stored?
Up to 16 months on the first import, then every new final day, up to 10 years.
What happens when I turn storage off?
The data is kept for 30 days and then deleted.
Why is yesterday missing?
Only final days are stored, and Google finalizes data a couple of days late.
Does storage change my reports?
Not at the moment: reports read Search Console live.
Continue
Next, see workspace and properties and dates, comparisons and data delay.