Google Search Console

Google strips keywords from referrers, so the query a visitor searched exists in exactly one place: Search Console. This integration imports those queries and joins them to your sessions, so you can rank searches by what happened after the click rather than by clicks alone.

Connect

1. On Property > Integrations, open the Google Search Console tile and click Connect. Authorise with the Google account that has access to the site in Search Console.

2. Pick the Search Console property. SnipForm lists the properties your login can see. Choose the one for this site.

3. First sync. Selecting a property queues the first import. The drawer polls until it completes, then shows the last 7 days of clicks and a link to the Search queries page.

Sync now on the tile queues an immediate pull. Search Console settles its data after about two days, so the most recent days fill in as they finalise; each sync re-pulls recent days and overwrites in place.

Domain property or URL-prefix property?

A SnipForm property spans every subdomain of its domain. A Search Console domain property (sc-domain:example.com) does too, so the two agree. A URL-prefix property (https://www.example.com/) covers one origin only; choose it and the tile tells you plainly that queries are only reported for that origin. Prefer the domain property when you have it.

What is imported

One row per date, query and landing page: clicks, impressions, CTR and average position, exactly as Search Console reports them (in the site’s own day). Rows are keyed deterministically, so Google’s restatements of recent days replace earlier values instead of duplicating them.

This covers Google Search only. Other search engines are not in this data.

How queries are joined to sessions

Search Console stops at the click. Sessions start at the landing page and know nothing about the query. The bridge is the page: both sides know which page the click landed on.

For each page and day, the sessions that landed on that path (channel: organic search, Google) are shared out across the queries that drove clicks to it, in proportion to those clicks:

sessions(query) = sum over pages [ page_sessions x query_clicks / page_clicks ]

The same apportionment gives each query its share of conversions and value.

Caution

These are estimates, and a different kind of number from ad cost. Ad cost reconciles exactly to an invoice; only its distribution is apportioned. Here the total itself is incomplete and the apportionment is inference. The numbers are good for ranking queries by value, which is the decision they exist to support, and not good enough to quote as counts. The Search queries page says so wherever it shows them.

Coverage

Search Console returns top rows only and withholds rare queries for privacy, so the clicks you can see always fall short of your real organic traffic. SnipForm also stores Google’s unwithheld daily click total, which is the honest denominator: the Search queries page shows coverage (known query clicks as a share of total clicks) as a first-class figure rather than implying the list is complete.

Where it shows up

• Property > Search queries: queries ranked by estimated sessions, conversions and value, with coverage for the period, and a drill-down per query into the landing pages behind it.
• The tile’s health checks: connected, site chosen, first sync complete.

Search Console data is not currently exposed through the API or the MCP tools.