Google Search Console integration

Connect Google Search Console to your Clickport site and the search queries that drive Google traffic show up directly inside your Sources panel. You get the keywords, ranking positions, click-through rates, and impressions next to your visit data, with the same date range and filters you already use.

What you see in the dashboard

Once connected, a new GSC sub-tab appears in the Sources panel between Sources and URLs. It lists your top search queries with clicks, impressions, CTR, and average position. Each column is sortable. Long queries truncate with a hover tooltip to show the full text. The Show More button at the bottom appends another 50 keywords per click.

The tab only appears for sites that have an active integration. Sites without Search Console connected won't show the tab, so dashboards stay clean.

How to connect

The setup runs through Google's standard OAuth flow. The integration is per-site, so you connect Search Console for each Clickport site separately. One Google account can be linked to multiple sites.

1. Make sure your site is added and verified in Search Console. Both domain properties (sc-domain:example.com) and URL-prefix properties (https://example.com/) work.
2. In Clickport, open Settings → Integrations for the site you want to connect.
3. Click Connect Google account. You'll be redirected to Google's consent screen.
4. Pick the Google account that owns the Search Console property and grant read-only access. Clickport only requests webmasters.readonly: we can read keyword data, but we cannot modify anything in your Search Console.
5. You're redirected back to Clickport and the property picker opens automatically. Select the property you want to associate with this Clickport site and save.

Picking the right property

Search Console exposes two property types and the picker shows both. The choice matters for how your site URLs match GSC's data:

• Domain property (sc-domain:example.com) covers every subdomain and protocol. If you have www.example.com, example.com, and shop.example.com all serving content, a single domain property captures them all.
• URL-prefix property (https://example.com/) only covers exactly that scheme, host, and path prefix. Cleaner if you only have one canonical hostname.

If your Google account has access to multiple properties for the same domain, the domain property usually gives the most complete data. URL-prefix properties are useful when you only want to attribute keywords from a specific subdirectory or hostname.

Filtering keywords

Active dashboard filters carry into the GSC tab where they map cleanly to Search Console's dimensions:

• Page filter narrows to keywords where the filtered page was the landing page from Google. Search Console doesn't track mid-session navigation, only the page Google linked to in the result. So filtering by /pricing shows keywords that landed visitors on /pricing, not keywords that drove sessions which happened to include /pricing later.
• Country filter uses ISO-3 country codes under the hood (Clickport converts your ISO-2 selection automatically). Multi-country selection ORs across the values.
• Device filter maps to Desktop, Mobile, or Tablet. Multi-device selection ORs.
• Source filter for Google is silently ignored when you're already in the GSC tab (you're looking at Google data by definition).

Other dashboard filters (browser, OS, UTM, custom events) don't translate to Search Console data and trigger a small "not applied to keyword data" notice above the table. Search Console only exposes four dimensions: query, page, country, and device.

Date range mapping

Whatever date range you pick on the dashboard is what gets sent to Search Console. There's no auto-clamping per preset, but a few specifics worth knowing:

• Last 7 days / 30 days / 91 days: ends yesterday, not today. This matches Search Console's natural cadence and avoids the data-lag empty-result trap.
• All Time: from your site's first tracked event to today. Search Console returns up to 16 months of data — anything earlier than that simply isn't there to return.
• Today / Last 24h / Realtime: technically valid but expected to be empty because Search Console data is delayed 24-72 hours. The dashboard shows a "data is delayed" notice rather than an empty list.
• Custom range: passed verbatim. No clamping on either side.

Data freshness and limitations

The data you see in the GSC tab comes live from Google's Search Console API, with a short cache to keep things responsive. A few constraints inherent to Search Console itself:

• 24-72 hour delay. Search Console processes data in batches. Yesterday's queries are usually available; today's are not. This is why our default presets end at yesterday rather than today.
• 16-month retention. Search Console only keeps data for the last 16 months. Asking for older ranges returns empty.
• Keyword sampling. Google samples keyword data heavily. The clicks attributed to specific keywords add up to less than your total Google visitor count — Google withholds long-tail and low-volume queries to protect user privacy. This is the same limitation you see inside Search Console's own interface.
• Clicks-only by default. The keyword list shows queries that produced actual clicks. Queries that earned impressions but no clicks aren't included by Search Console in its query-dimension data. To see impression-only opportunities, use Search Console directly.

Filters and what they mean for SEO

The combination of Clickport's engagement metrics and Search Console's ranking data lets you ask questions neither tool answers on its own:

• Which top-ranking keywords actually engage visitors? Filter by a page that ranks well, then check whether the engagement score in your Sources panel matches the keyword volume. A page ranking position 3 with high impressions but low engagement might indicate a relevance mismatch worth fixing.
• Which keywords drive your highest-converting traffic? Filter by a goal (e.g. signup completed) in your dashboard, switch to the GSC tab — only those keywords whose landing pages converted are highlighted.
• Where are you close to page-one but not quite? Sort by Position ascending, then filter to positions 8-15. Those are keywords where Search Console says you're on the edge of page one. A small content improvement can push you up.

Disconnecting

Click Unlink Google account in the Integrations card to remove the connection. Clickport revokes the token at Google immediately, so we can no longer fetch any data on your behalf. The setting is per-site, so unlinking one site doesn't affect any other site you've connected.

You can also revoke our access from outside Clickport by visiting your Google account permissions page. If you revoke from Google's side, the next dashboard load shows a red banner asking you to reconnect.

Troubleshooting

"Google revoked our Search Console access"

This appears when the refresh token we hold has stopped working. The most common cause is the user manually revoking access from Google's permissions page, but it can also happen if your Google account changed password (Google sometimes invalidates tokens on password changes) or after Google's 50-active-tokens-per-account limit kicks in. Click Reconnect in the banner and walk through the OAuth flow again — that's enough to restore the integration.

"No verified properties found"

The Google account you authorized with doesn't own or have user access to any Search Console property. Open Search Console with that account and either add your site or accept a pending invitation. Make sure ownership verification finishes (HTML file, DNS TXT, or any of Google's other methods) before retrying the Clickport flow.

"Search Console data is delayed 24-72 hours"

The date range you selected starts within the last three days and Search Console returned no rows. This is normal — switch to a range ending at least one full day ago and the data will appear. The default Clickport presets (Last 7 days, Last 30 days, etc.) already end yesterday and don't hit this case.

"Filter not applied to keyword data"

You have a dashboard filter active that Search Console can't honor. Search Console only exposes four dimensions: query, page, country, device. Other filters (browser, OS, UTM source, custom events, etc.) stay applied to your visitor data in other panels, but the GSC tab quietly drops them and tells you which ones it dropped via the small notice.

Privacy and data handling

Clickport stores three things for the Search Console integration:

• Your Google email address (used to display "Connected as ..." in settings).
• A refresh token issued by Google, AES-256-GCM-encrypted at rest with a key that lives in our server environment, never in our database backups or version control.
• The Search Console property you selected.

We never store keyword data — every keyword view is a live query to Google with a short response cache. We never modify your Search Console data: the OAuth scope we request (webmasters.readonly) is explicitly read-only. Unlinking from Settings or from your Google account permissions page revokes our token immediately. See the privacy policy for full details.