A Search Console archive for agencies solves a problem that has nothing to do with dashboards: client data keeps dying. Access gets rotated during an offboarding, a contract pauses for six months, a property changes owners, and Google's 16-month deletion runs through all of it, whether anyone is watching or not.
Get early access Free during early access. No card required.
The agency-shaped versions of the problem
- Clients arrive without history. By the time a client signs, the baseline from before their decline has often already expired. You inherit a mystery and 16 months of evidence.
- Churn deletes your work. When a client leaves and access changes hands, your view of their data goes with it. If they come back in a year, you start from nothing.
- There is no MCC for Search Console. Google Ads has manager accounts; GSC has nothing. Preserving data happens per property, or it doesn't happen.
How Month17 handles it
Connect each client property once and the archive runs unattended: a full 16-month backfill on connect, a daily sync after that, and no retention limit. Rows that have been archived stay archived. If a client's OAuth access is later revoked, syncing stops, but the history you collected up to that day remains in your account.
On security, since it's the first question a client will ask: Month17 stores OAuth tokens encrypted at rest in PostgreSQL, using your grant and nothing broader. No passwords change hands, and revoking access is a normal Google account operation the client controls.
Pricing stays flat and predictable: free during early access, then $10 per property per month, which passes through cleanly as a line item per client. There are no tiers to outgrow and no per-seat charges for your team.
Years of client data, queryable by your AI
The archive is served over MCP, so whoever on your team works in Claude Code or Cursor can query any archived property in plain language. "Did this client's March drop come from rankings or CTR?" and "compare their last three Q4s" are prompts, not report requests. The MCP server page shows the setup, which is one config block per analyst.
Start with the clients you'd hate to lose
You don't need to archive the whole roster on day one. Start with the accounts where history matters most: long-tenured clients, anyone recovering from an update, anyone with real seasonality. Every week of delay trims a week off the far end of each client's window, and that part never comes back.