How to Connect Google Search Console to WebSignalytics

GA4 tells you what people do once they land on your site. It has never been able to tell you what they searched for to find you, or whether your site is even showing up for those searches at all — that data lives in a separate, free Google tool called Search Console. Connecting it to WebSignalytics takes about a minute, and once it's connected, that data starts showing up in your Monday report automatically — no separate login, no second dashboard to check.

What Search Console adds that GA4 can't

GA4 can tell you a visitor arrived through organic search. It cannot tell you what they typed to get there — Google withholds search terms from analytics tools entirely. Search Console is the only place that data exists. Once it's connected, your weekly report adds an "Organic search this week" section covering four things: impressions (how often your site appeared in search results), clicks (how many of those impressions turned into a visit), average position (roughly where you tend to rank), and your top search queries for the week.

That combination catches a specific, easy-to-miss pattern: a page can hold its ranking and keep appearing in search — impressions steady or even rising — while the clicks quietly dry up. Looking at GA4 alone, that just looks like "traffic is down" with no visible cause. Looking at Search Console alongside it, the cause is usually right there.

Before you start

You need a Google account that already has a verified property in Search Console for your site — if you've never set Search Console up at all, do that first at search.google.com/search-console (it's free, and verification is usually just confirming a DNS record or an existing GA4/Analytics connection). If you're not sure whether you already have one, it's fine to try connecting anyway — WebSignalytics will tell you if it doesn't find one.

Step 1 — Click "Connect Search Console"

On your WebSignalytics dashboard, you'll see a Connect Search Console prompt if it isn't linked yet. Click it.

Step 2 — Approve the Google consent screen

You'll be sent to Google's own sign-in and consent screen, asking for read-only access to your Search Console data. This is the same trusted Google OAuth flow you used to connect GA4 — WebSignalytics never sees your Google password, and the access it requests is read-only: it can see your search performance, nothing more.

Step 3 — Pick your property, if asked

If your Google account has exactly one verified property, WebSignalytics selects it automatically and you're done. If it has more than one — for example, both a Domain property and a URL-prefix property for the same site, or properties for more than one site — you'll see a short picker listing each one. Choose the property for the site you want reported on.

Step 4 — Confirm it's connected

Back on your dashboard, you should see a "Search Console connected" badge with your property's address. That's it — there's nothing further to configure.

What happens next

Your next Monday report will include the Organic search section alongside everything else — traffic, acquisition, engagement, conversions, and (if you've connected it) AI search visibility. And because WebSignalytics writes in plain language rather than just listing numbers, the report doesn't just show you impressions were up and clicks were flat — it tells you what that combination is likely to mean and what's worth doing about it.

If your organic clicks have been drifting down while your Search Console numbers look fine on their own, that's exactly the disconnect our case study Where Did the Organic Clicks Go? walks through — the difference between a ranking problem and a clicking problem, and why they call for very different fixes.