---
title: "Save Search Console history in a Store"
description: "Preview, sync, check, and maintain local Search Console history with the CLI."
canonical_url: "https://gscdump.com/gscdump-cli/guides/use-data/build-history"
last_updated: "2026-10-03T07:15:31.532Z"
---

# Save Search Console history in a Store

A Store is a local Parquet directory. It lets you query older dates and run Analyzers that need stored data. Google only offers a limited Search Analytics history, so start before older dates leave its API.

## Plan the first sync

Use one Site, such as `example.com`. Keep `web` separate from other search types. The newest Search Console days can change. For comparisons, use final days and equal windows. The [Sync reference](/gscdump-cli/api/sync) lists tables, search types, and quotas.

## Preview and run it

::pre{tabindex="0"}
```bash
gscdump sync --site example.com --full --dry-run
gscdump sync --site example.com --full
```
::

`--full` requests the history Google still serves. A large Site may need several runs. Sync saves progress and resumes. If you need only a window, use `--start`, `--end`, and `--tables` from the reference.

## Check coverage

::pre{tabindex="0"}
```bash
gscdump sync --site example.com --status
gscdump store stats
gscdump query --schema
```
::

::table{tabindex="0"}
| Signal                              | Next check                                                           |
| ----------------------------------- | -------------------------------------------------------------------- |
| Completed dates for required tables | Run a [stored query](/gscdump-cli/guides/use-data/query-and-export). |
| Missing or failed dates             | Run the sync command printed by `--status`.                          |
| A running sync                      | Wait for it to finish before comparing incomplete windows.           |
| No rows for a search type           | Check Site access and Google's available data.                       |
::

A completed sync cannot recover rows Google omits from its API. Do not treat a missing query row as proof the query had zero impressions.

## Repair a gap

`query`, `analyze`, and `report` stop when the Store covers only part of a required window. Use the printed `gscdump sync` command for those dates and tables, then repeat the read. `--live` can ask Google instead for supported reads. One run never mixes live and Store rows.

## Keep history current

Schedule `gscdump sync --site example.com` daily on a persistent machine. Use renewable credentials, and keep the entire Store between runs. Check `sync --status` after failures. A plain sync catches up after a missed run. Start the [growth trends guide](/gscdump-cli/guides/investigate-traffic/growth-trends) after confirming the comparison history. See [Use data](/gscdump-cli/guides/use-data).

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.