Everything in the platform's measurement half — Search Performance, the Analytics dashboards, the optimization loop — runs on data from two Google services. Connecting them is a one-time job per domain, and one credential can cover both.
The shape of the setup
- In Settings → Google Accounts, upload a Google service-account key. That account is the platform's read-only door into your data.
- In Domain Management, open Connect on a domain. Search Console and Analytics each get a card — and Analytics has a "use same as Search Console" shortcut, because one service account covers both in the common case.
- For Search Console: if the domain isn't verified yet, the platform can handle DNS verification (with your DNS provider's API key) or walk you through adding the record manually. Already-verified domains connect instantly.
- For Analytics: an existing property is discovered automatically, or one can be created for the domain if none exists.
Connection status shows live on the domain row — pending, partial, active — and the first sync backfills recent history rather than starting from zero.
What flows in after
| Connection | Fills | Used by |
|---|---|---|
| Search Console | Queries, impressions, clicks, positions | Search Performance page, SEO agents |
| Analytics | Sessions, sources, behavior | Analytics page, optimization runs |
The sync runs daily on a schedule you control (schedules chapter), and store analytics join automatically for builds shipped through the platform.
The shared-property detail that matters: if one Analytics property collects for several of your sites, every query the platform makes is filtered by hostname — your dashboard shows this domain's numbers, never the property's combined totals. That guarantee is structural, not best-effort.
← All posts