Operate
Integrations
Two Google connections turn Wrenda from a proxy into a measurement loop. Search Console tells you whether an optimization moved impressions and clicks; GA4 tells you how much traffic AI platforms actually send. Both are connected per property under Settings → Integrations.
What each unlocks
| Integration | Unlocks |
|---|---|
| Google Search Console |
|
| Google Analytics 4 |
|
Per property
Integrations are scoped to the property (domain) selected in the dashboard's property switcher. Each property has its own isolated connections, so a tenant with three domains connects Search Console three times — once per domain, each to the matching Search Console site. The Setup completeness checklist tracks GSC and GA per domain.
Connect Google Search Console
Select the property
Pick the domain in the property switcher, then open Settings → Integrations.
Click Connect Google Search Console
You are sent to Google to sign in and grant read access. Use a Google account that has access to the site in Search Console.
Choose the Search Console site
Back in Wrenda, a picker lists the sites that account can see with each one's permission level. Choose the one matching the property (a domain property such as
sc-domain:example.comor a URL-prefix property). You have five minutes to pick before the setup session expires.
The connection card shows the Google account email and the site URL, the connect banners on Page Optimizations and SEO Testing disappear, and the checklist marks Search Console done.
Connect Google Analytics 4
Select the property and click Connect GA4
Same page, same flow: sign in with a Google account that can read the GA4 property.
Choose the GA4 property
Pick the property from the list. Five-minute window, as with Search Console.
Sync
Data starts to appear on the next sync. The connection card has a manual Sync button if you don't want to wait, and the Analytics page shows AI Referrals once data exists.
Disconnecting and re-connecting
Each connection card has a Disconnect action. Disconnecting removes the stored tokens; it doesn't delete the verdicts or referral data already recorded. If Google revokes access (password change, removed permissions, the account leaving the Search Console property), disconnect and connect again.
Troubleshooting
“No sites” after signing in
The Google account you used has no Search Console properties (or no GA4 properties). Add and verify the site in Search Console first, or sign in with an account that already has access, then connect again.
“invalid_state” or “missing_params”
The sign-in was started from a stale tab or completed twice. The state token is single-use and short-lived for security. Start again from Settings → Integrations in one tab.
“Setup session expired”
The property picker waited more than five minutes. Click Connect again; you don't need to re-authorise in Google.
401 on the Search Console callback
Earlier builds returned a 401 when Google redirected back to Wrenda for tenants whose subscription gate was active, because the OAuth callback was checked like a normal dashboard request. This is fixed — callbacks now pass through the gate. If you still see a 401 at the callback step, hard-refresh the dashboard to pick up the current build and try again; if it persists, contact support with the time and your property.
Connected the wrong Google account
Disconnect, then connect again and pick the other account on Google's account chooser.
GA4 connected but AI Referrals is empty
Either there is genuinely no AI-sourced traffic yet, or the property has no data for the period. Widen the date range, press Sync, and check the GA4 property itself shows sessions from sources such as chatgpt.com or perplexity.ai.
Next
See also Analytics for what the AI Referrals report shows.