Google OAuth setup problems

What you’ll need

• The Google account that owns (or has the right role on) the Search Console or Analytics property.
• Access to that account’s third-party app settings, in case you need to clear a stale grant.
• A browser with pop-ups and third-party cookies allowed for the consent flow.

Connecting Google Search Console or GA4 runs a standard OAuth consent flow: Google shows you a consent screen, you approve the requested scopes, and Google redirects back to VisibilityIQ with an authorisation code. Credentials stay inside the connector and are stored encrypted — they’re never logged or exposed. Most setup problems are a wrong account, a denied scope, or a browser that blocked the redirect.

Likely causes

• Wrong Google account. You completed consent with an account that doesn’t hold the property.
• Scope not granted. On the consent screen you unchecked, or Google withheld, a permission VisibilityIQ needs to read the property.
• Redirect blocked. A pop-up blocker, ad blocker, or disabled third-party cookies interrupted the redirect back, so no authorisation code reached us.
• “App not verified” / “Google hasn’t verified this app”. Google shows a caution screen for apps under review. This is informational, not a failure.
• Stale prior grant. An earlier, broken authorisation is still recorded on the account and shadows the new attempt.

How to fix it

1. Start the flow on the right account. From Settings → Connectors, click Sign in with Google. When Google asks which account to use, pick the one that owns the property. If you’re signed into several, choose deliberately rather than accepting the default.
2. Grant every requested scope. On the consent screen, leave all requested permissions checked and approve. If you previously denied one, you must re-consent for it to take effect — a partial grant leaves the connector unable to read data.
3. Clear the path for the redirect. Allow pop-ups and third-party cookies for VisibilityIQ, disable aggressive blockers for the consent step, and don’t close the Google tab until it returns you to the app. If the redirect fails, restart the flow rather than reloading mid-way.
4. Get past “app not verified”. On the caution screen, expand Advanced and choose to continue. This screen reflects Google’s review status, not a problem with your account, and is safe to proceed through for a connector you’re intentionally authorising.
5. Re-authorise from a clean slate. If a prior grant is interfering, open the Google account’s Security → Third-party access, remove VisibilityIQ, then run Connect again. In the app, Disconnect first if the connector is in an error state, so re-consent issues a fresh token.
6. Confirm your role. OAuth can succeed while the account still lacks the right level — GSC needs Owner or Full User, GA4 needs Viewer or higher. Verify the role in the relevant console and reconnect with a sufficient account if needed.

Verify it worked

Back in Settings → Connectors, the connector should read Connected with a recent Last synced timestamp. First data can take up to 24 hours to appear; treat it as a problem only past 48 hours.

Still stuck?

If consent completes but the connector still errors, or “No properties found” persists with the correct account, email support@visibilityiq365.com with the property and the account you used. See also Connector auth errors for the general re-consent flow and Audit shows no issues or empty results when a connected source isn’t producing findings.