What access does SERPs ask for?

Read-only Search Console access (webmasters.readonly) and your Google account email, so the connection can be labelled. No write scope is requested.

How far back does the first sync go?

Up to 480 days, which is as much as Google's 16 month window generally holds. Everything synced after that is kept by SERPs even once Google drops it.

How often does it refresh?

A nightly job at 08:00 UTC pulls the last 14 days and re-checks for gaps. Manual re-syncs are available with a six hour cooldown per project.

Yes, at any time from the same settings screen. Revoking access in your Google account works too, and stops the sync on the next run.

Integration

Search Console data that outlives the 16 month window

Connect the property once with read-only access. SERPs syncs your query data nightly, stores its own copy, and keeps it after Google's own 16 month window closes.

Start your trial See pricing

Reported position by query

Illustrative, weekly

Read-only, and nothing else

The connection asks for webmasters.readonly and your account email. SERPs never writes to the property, never submits URLs, and never changes a setting on your behalf.

Write scopes requested

0

Read scopes requested

2

Nightly sync, with catch-up

A nightly job pulls the last 14 days at 08:00 UTC. When a project has been quiet or newly connected, the same job widens the window and backfills up to 480 days in one pass.

Nightly lookback, days

14

Gap catch-up window, days

480

Query data next to tracked positions

Impressions, clicks, CTR, and average position arrive by date, query, page, and country, and land in the same project as your tracked keywords, so reported clicks sit beside checked positions.

Clicks by country

Illustrative

United States48.0%
United Kingdom21.0%
Germany17.0%
Australia14.0%

History you keep

Google exposes 16 months and then the oldest day falls off. SERPs stores every day it has already synced, so a year over year comparison stays possible once the connection has been running.

Google's own history, months

16

Dimensions stored

4

Connect Google Search Console

1
Open the integration
Go to Settings, then Integrations, and choose Google Search Console.
2
Grant read access
SERPs asks for webmasters.readonly and your account email. It never writes to your property and never submits anything on your behalf.
3
Pick a property
One property maps to one project. Domain properties and URL prefix properties both work.
4
Wait for the first sync
The first run widens the lookback and pulls up to 480 days of history in one pass. After that the nightly job keeps it current.
5
Check the query view
Open the project and confirm impressions, clicks, CTR, and position are populated before you rely on the comparison.

Integration specifications

Provider: Google Search Console
Auth: OAuth 2.0
Scopes: webmasters.readonly, userinfo.email
API: Search Console API v3
Sync schedule: Nightly, 08:00 UTC
Nightly lookback: 14 days
Gap catch-up: Up to 480 days
Manual re-sync cooldown: 6 hours
Properties per project: 1
Dimensions stored: Date, query, page, country
Google's own history: 16 months
Disconnect: Revocable at any time

Google Search Console FAQ

Start ranking without the enterprise tax

Every plan starts with a 7 day trial. Connect Search Console and see where you stand in minutes.

Start your trial

7 day trial, card required, cancel any time.

Search Console data that outlives the 16 month window

Read-only, and nothing else

Nightly sync, with catch-up

Query data next to tracked positions

History you keep

Connect Google Search Console

Open the integration

Grant read access

Pick a property

Wait for the first sync

Check the query view