Google Search Console gives Stride your impression and click data from traditional search, which provides useful contrast against AI visibility for the same topics. For implemented work, Stride uses only exact page or query alignment and complete, sufficient 28-day before-and-after windows for a non-causal outcome observation.
Why connect it
Strong classic search rankings do not guarantee AI visibility — the two diverge more than people expect, and that divergence is often the most useful thing on the page. A topic where you rank well but are never recommended by AI is a clear, well-defined gap.
Connecting
- Open Dashboard → Settings → Integrations
- Expand Google Search Console and choose Connect
- Sign in with a Google account that has access to the property
- Select the Search Console property that matches this site
Permissions
Stride requests read-only access to Search Console data
(webmasters.readonly). It cannot change your property settings or submit URLs.
When an outcome observation is eligible
Stride waits for a three-day provider-finalization lag before evaluating an implementation. The before and after periods must each contain exactly 28 complete days, bracket the implementation without including its calendar day, and align to the target page or to the recorded target query/prompt. Each window also needs at least 100 impressions.
When those conditions are met, Stride can say search movement was observed after the work. It does not establish that the work caused the movement.
Disconnecting
Disconnecting removes the stored Search Console credentials, cached provider data, and provider-derived proof observations for that connection. Affected proof records show that the integration is unavailable rather than treating missing data as a result. Stride retains only limited non-sensitive aggregate proof status and a disconnect audit marker where needed for integrity, security, or legal records.
Troubleshooting
Property not listed. The Google account you authorized with needs at least read permission on the property in Search Console.
Data looks delayed. Search Console data lags by a couple of days at source; that lag carries through to Stride.