Google Search Console

The Google Search Console integration pulls your organic search keyword data directly into Statalog, so you can see which queries are driving traffic without switching between tools.

What you get

Once connected, a Search tab appears in your Statalog dashboard showing the top search queries that led visitors to your site. For each query you can see:

  • Clicks — the number of times someone clicked through to your site from Google Search
  • Impressions — how many times your pages appeared in search results for that query
  • CTR — click-through rate (clicks ÷ impressions), expressed as a percentage
  • Average position — your mean ranking position across all searches for that query

The table is filterable by page, so you can drill into the keyword profile of any individual URL on your site.

How to connect

  1. Go to Account → Integrations in your Statalog dashboard.
  2. Click Google Search Console and then Authorize with Google.
  3. A Google OAuth consent screen opens. Sign in with the Google account that has access to your Search Console property and grant the requested permissions (read-only Search Console access).
  4. You are redirected back to Statalog. The integration detects your verified GSC properties automatically.
  5. Select the property that matches your site. Statalog supports both domain properties (e.g. sc-domain:example.com) and URL-prefix properties (e.g. https://example.com/).

If you have multiple GSC properties, you can connect different properties to different Statalog sites from the same integration screen.

Data freshness and caching

Google Search Console data has an inherent lag of 2 to 3 days. This is a Google limitation — GSC does not expose real-time search data through its API. The most recent date available is typically two to three days before today.

To avoid hitting GSC API rate limits, Statalog caches the keyword data for 10 minutes. Reloading the Search tab within that window serves the cached response. Cache is per-site and refreshes automatically when it expires.

Token management

After the initial OAuth flow, Statalog stores an access token and a refresh token for your Google account. The access token is short-lived (one hour); it is refreshed automatically using the refresh token before each API call. You do not need to re-authorize unless you revoke access from your Google account's security settings.

How to disconnect

  1. Go to Account → Integrations.
  2. Click Remove next to the Google Search Console connection.
  3. Statalog deletes your stored tokens immediately. No further requests are made to Google on your behalf.

To fully revoke access at the Google level, visit myaccount.google.com/permissions and remove "Statalog" from the list of connected apps.

FAQ

Why don't I see any keyword data? The most common reason is the 2–3 day data lag. If you connected the integration today, data may not appear until tomorrow or the day after. If you still see nothing after three days, confirm that the GSC property is verified and that the Google account you authorized has at least Read & Analyze access to that property.

My site has traffic but Google shows "(not provided)"? The Search tab in Statalog pulls data from GSC directly, so it does not suffer from the (not provided) keyword redaction that affects referrer-based keyword tracking. If a query has fewer than a GSC threshold of impressions it may be grouped or hidden by Google — this is a GSC policy, not a Statalog limitation.

Does this require Google Analytics? No. Statalog connects to Google Search Console independently. You do not need a Google Analytics account, and connecting GSC to Statalog has no effect on any existing Google Analytics setup.

Does the integration see my full website or just part of it? Statalog requests data scoped to the GSC property you select. A domain property covers all URLs and protocols under that domain. A URL-prefix property covers only URLs that begin with the specified prefix. Choose the property that matches how your site is verified in GSC.

Is the Google OAuth token stored securely? Yes. Tokens are encrypted at rest using your application key. They are never logged or exposed in the UI. Only the Statalog backend accesses them when fetching data on your behalf.