Skip to main content
Connecting Google Search Console (GSC) unlocks the most valuable data Keupera can give you: the actual queries Google sends to your site, with impressions, clicks, CTR, and average position. Once connected, Keupera uses GSC data to power:
  • Analytics → Search Console views (daily stats, top keywords, top pages)
  • Striking distance insights (keywords ranking 11–20 with high impressions)
  • Keyword cannibalisation detection (multiple URLs competing for the same query)
  • Low-CTR opportunities (high-impression pages with poor click-through)
  • Real impressions and click counts on tracked keywords inside the Keywords module.

​
Prerequisites

  • A verified property in Google Search Console.
  • The Google account you use to connect must have at least Restricted access to the property in GSC.

​
Connect GSC

1

Open Settings → Integrations

Inside the Keupera dashboard navigate to Settings → Integrations for the website you want to connect.
2

Click 'Connect' under Google Search Console

The button redirects you through Google’s OAuth consent screen. Keupera requests the read-only webmasters.readonly scope — it can read property data but never modify your GSC setup.
The OAuth flow uses access_type=offline and prompt=consent so Google issues a refresh token. This lets Keupera continue syncing in the background even when you’re logged out.
3

Pick the right property

After authorising, Keupera lists every GSC property the connected Google account can access. Choose the one matching the website you’re configuring and click Save.
The first sync runs immediately and pulls the last 90 days of data. Subsequent syncs run automatically every 24 hours.

​
What gets synced

​
Permissions & privacy

  • Read-only — Keupera only ever requests the webmasters.readonly scope.
  • Refresh tokens are encrypted at rest in Keupera’s database.
  • You can disconnect at any time from Settings → Integrations → Disconnect GSC, which immediately revokes the token and stops future syncs. Already-synced historical data stays in your Keupera analytics.

​
Troubleshooting

  • “No properties found” — make sure the Google account you authorised has access to the property in GSC. Add the account in Search Console under Settings → Users and permissions if needed.
  • Data missing for the last 2–3 days — Google delays GSC data by up to 72 hours. This is a Google-side limitation, not Keupera.
  • Sync errors after a Google password change — refresh tokens can be invalidated. Re-run the Connect flow to issue a new one.

​
API access

Once GSC is connected, the data is also available via the Public API: