Before you start
- A Google account with access to the intended Search Console site properties and permission to manage Sources in Data Weaver.
- Decide which domain or URL-prefix properties to include. Sign in with the Google account that has access to those properties.
Set up the connection
- Open Sources in the target client and connect Google Search Console using the hosted Google authorization flow.
- Choose the site properties explicitly and save. Selecting none syncs none; do not select another client's sites.
- Run Sync and inspect readiness and coverage before asking about search performance.
Permissions requested
- Read access is needed to list accessible sites and read Search Analytics. Data Weaver does not verify sites, change ownership or submit sitemaps.
- Review the permissions on Google's authorization screen and approve access using the Google account that manages your intended Search Console properties.
Data read and actions performed
- The import reads dated search clicks and impressions for selected sites. Supported live questions can read top pages, top queries and date breakdowns.
- These are Search Console observations, not GA4 traffic; provider definitions remain distinct even when displayed alongside web data.
Refresh and sync
- Default scheduled refresh is hourly with manual Sync available. Google reporting delays and quotas can leave the most recent dates incomplete.
Limitations
- Search Console is not a full log of every query or visit. Provider aggregation and omitted data can affect comparisons.
- Selecting multiple sites can aggregate their observations; overlapping domain/URL-prefix properties may describe overlapping traffic. Historical completeness is not guaranteed.
Troubleshooting
- A missing site usually requires checking Google property access or the connected identity. Update the saved site selection after access changes.
- Check date coverage for apparent missing recent results. Reconnect for authorization failures; use sync history and retry status for temporary errors.
Disconnect and delete
- Remove the source connection in Data Weaver to stop its use and initiate remote connection cleanup.
- Separately remove Data Weaver from Google Account third-party connections to revoke the Google grant. Disconnecting is not a blanket deletion of stored reports or answers; contact Data deletion for retained data.
Privacy and help
You stay in control of what you connect. Review how we handle information, request deletion, or contact us.