SurfacedBy already tells you where AI assistants mention your brand. Google Search Console and Google Analytics know something different: which search queries earn you clicks, and what those visitors do once they land. Those numbers used to live in separate tabs from your AI visibility. Now you can connect both to SurfacedBy and read them in the same place, one domain at a time.
What you can connect
From a domain’s Integrations page you connect two Google sources. Search Console pairs your AI visibility with classic search impressions and clicks. Google Analytics 4 overlays AI referrals onto what visitors actually do on the site. Both connect with Google sign-in, and SurfacedBy reads only the property you select.
Why it matters
Organic search and AI answers are two routes to the same page, and most teams measure them in two different tools. Reading them together is where the useful questions surface: which pages win clicks in search but rarely get cited in AI answers, and which prompts you already win in AI that your organic pages have not caught up to. Those are different jobs, and you can only see them when the two data sets sit next to each other.
What Search Console adds
- Organic queries that earn clicks but rarely show up in AI answers: pages that rank in search and have room to win citations.
- Prompts you already win in AI that are not yet organic winners: topics where the AI credit is ahead of the classic SEO.
- Clicks, impressions, average position, and CTR shown next to your tracked prompts, where Search Console reports them.
An illustrative example of the kind of row this surfaces:
| Organic query | Monthly clicks | Avg position | In AI answers |
|---|---|---|---|
| best running shoes for flat feet | 1,240 | 4.2 | No |
| wireless earbuds comparison | 880 | 6.1 | Yes |
| standing desk under 300 | 410 | 3.5 | No |
What Analytics adds
- AI-referred sessions, where Analytics can see the referrer.
- Conversions and revenue on those sessions, where the connected property reports them.
- Visibility movement read next to traffic movement, as a correlation to watch, not a cause to claim.
What neither source can see
Connecting Google adds context; it does not turn either tool into a complete record of AI traffic, and the integration does not pretend otherwise.
- Search Console does not cleanly separate every AI surface. Google’s AI answers ground on the same index as classic search, so some AI-driven impressions are blended into ordinary search data.
- Analytics sees identifiable AI traffic and known referrers, not every AI visit. Some AI traffic arrives with no referrer at all.
- Connecting Google is enrichment, not a requirement. SurfacedBy tracks AI visibility on its own; these sources add the organic and behavioral context around it.
We took apart exactly what each assistant sends to your origin, and where the blind spots are, in our nginx log study of AI traffic versus referral traffic.
How to connect
- Open the domain’s Integrations page.
- Connect Search Console and pick the property for this domain.
- Connect Google Analytics 4 and pick the property.
- Wait for the first sync, then check the status on each card.
If you connected Analytics earlier for AI traffic tracking, Search Console is the other half of the same picture: one shows what AI drives, the other shows what classic search still owns.
A note on timing: we change these integrations often, from customer requests, our own testing, and keeping pace as Google reshapes Search Console and GA4. Treat the screenshots here as how the connect flow looked at launch. If your Integrations page looks different, you are on a newer version.
