Limits & Pricing
How far back does my data go?
By the GSC PAP team · Updated
Google Search Console itself only retains the most recent 16 months of data. Anything older drops off Google's side and cannot be recovered, even with API access - this is a hard limit Google enforces on every Search Console user, including direct users of the official Google Search Console UI.
GSC PAP solves this with the Personal Archive. When you sign in with Google, it automatically backfills the full 16 months Google still has, for every property your Google account can read. There is no button to press. After that, a daily job fetches each new day, about 4 days behind today because Google's data takes about 3 days to settle. When Google deletes data older than 16 months on its side, your archive keeps it, so your history grows past 16 months from the day you connect. The archive cannot recover data Google deleted before you connected: it protects you from future loss. A manual backfill is still available at /account/archive, but you do not need it.
Queries for stable past data (older than about 3 days) are served from your archive at zero Google API quota, while the most recent days still come from the live Google API. The search_analytics_archive, historical_position_trend and archive_status tools work on the archive directly, so once your archive holds more than 16 months you can ask questions like "show me query trends over the last 24 months", further back than Google's own UI goes.
Related questions
All questionsLimits & Pricing
Is GSC PAP free? What are the limits?
Yes, GSC PAP is completely free during the public preview (v0.x). There is no credit card required, no trial expiration, and no premium feature gate. The only limits are technical ones to protect the service: 60 MCP tool calls per minute and 1,000 per hour per user. These limits are generous - typical AI assistant usage is 5-20 calls per question, so you can ask hundreds of questions per hour without hitting them.
Limits & Pricing
Does GSC PAP use fewer tokens than calling the Search Console API directly?
Yes, about a third fewer. We measured it on 1,000 real rows from three different properties, serialising the same rows two ways: the shape the Search Console API returns, and the compact format our server sends. The raw API response came to 34,044, 34,535 and 36,237 tokens. The same data from GSC PAP came to 22,933, 23,260 and 23,975. That is 33 to 34% fewer tokens for identical numbers, measured with tiktoken cl100k_base.
Privacy & Security
Can other users see my data?
No. Your Search Console data, OAuth tokens, MCP sessions, archive, and tool call history are all isolated to your user account in our database. Every query passes through bearer-token authentication that resolves to a specific user, and every database query scopes results by user_id. There is no UI, API endpoint, or feature that exposes one user's data to another user.
Skip the GCP project. Just sign in. Ready to plug this into Claude or Cursor? Sign in with Google, copy a token, paste a config block. ~60 seconds.
Sign in with Google