Per-site Google connections (GA4 and Search Console)

Who this is for

Workspace Owners and Admins who want a site's audits to draw on that site's real Google data. The read-only client role does not see this panel at all.

When to use this page

Before you run an intelligence audit for a site, so the run can use the site's actual Search Console queries and GA4 traffic rather than estimates. You connect once per site; every later audit of that site reuses the connection.

Before you start

• The site must exist in your workspace. Add it under Sites (Add Site), or it is created the first time you audit its domain.
• The connection only changes audit output when the audit runs with Intelligence enabled (a Pro or Enterprise feature).
• Your Google account needs access to the property you are connecting (GA4 property or the verified Search Console site).
• The server needs a Google OAuth client configured. If it is not, the cards show "Google OAuth is not configured on the server yet."

In the app

1. Open Sites, then choose a site to reach its detail page.
2. Scroll to the Connections panel. It has two cards: Google Search Console and Google Analytics 4.
3. On a card, choose Connect with Google. A Google sign-in and consent screen opens.
4. Approve access, then return to the site page. Pick the property from the list and choose Save property.
5. Use Test connection to confirm the property returns data. Disconnect removes the stored tokens for that provider.

You can also reach this from the New audit screen: the Google data panel there opens a site's Connections in a new tab (see Run your first audit).

Per-site connections against the workspace Search Console

This panel is per site, which suits an agency auditing many client domains, each maps to its own property. It is separate from the workspace-wide Google Search Console connector on the Integrations page. When both exist for a domain, the per-site connection is used first and the workspace one acts as a fallback.

Common pitfalls

• "Google hasn't verified this app" warning. The data scopes are sensitive, so until the OAuth app completes Google verification, testers see this screen. Choose Advanced, then continue. It is expected for internal use.
• redirect_uri_mismatch. The site callback URL must be registered on the Google OAuth client. This is a one-off server setup, not something the operator can fix in the app.
• No property selected. Search Console falls back to the audited domain, but GA4 needs a property chosen, without one the GA4 card stays inactive.
• Data does not appear in the audit. Confirm the audit ran with Intelligence enabled. A plain audit does not fetch external data.
• Connection stops working after about a week. This happens when the Google OAuth consent screen is left in "Testing"; move it to production so tokens stay valid.

Related

• Sites and reports.
• Run your first audit.
• Integrations for the workspace-level Search Console connector.