🔧 Fix Recurring Google Integration Disconnections

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

What Is Happening?

Some Search Atlas users experience recurring disconnections with Google Search Console (GSC) and Google Business Profile (GBP) integrations. The connection status may flip between Connected and Not Connected repeatedly, even after attempting to reconnect. This is a known issue that may require backend investigation to resolve fully.

Common Triggers

While our team investigates, the following are known factors that can contribute to repeated disconnections:

  • OAuth token expiry or revocation: Google periodically invalidates access tokens, especially if your Google account password changed, two-factor authentication was updated, or third-party app access was revoked in your Google Account settings.
  • Multiple reconnect attempts in one session: Reconnecting more than once without fully completing the auth flow can corrupt stored credentials, causing the status to flip repeatedly.
  • Browser or cache interference: Cached sessions, browser extensions, or cookie blockers can interrupt the OAuth handshake mid-flow, leaving the connection in a broken state.
  • Google Account permissions changed: If the Google Account used to connect lost owner or full access rights to the Search Console property or Business Profile, Search Atlas cannot maintain a valid connection.

What You Can Try

Before escalating to our team, you may attempt the following general steps:

  1. Revoke and re-grant access in your Google Account. Go to myaccount.google.com → Security → Third-party apps with account access, find Search Atlas, and remove it. This clears any corrupted tokens on Google's side.
  2. Clear your browser cache and cookies, or open an incognito / private window. Disable any ad-blocker or privacy extensions for the duration of reconnection.
  3. In Search Atlas, locate your account integrations settings and find the Google Search Console or Google Business Profile connector.
  4. Disconnect the integration completely — do not skip this step even if the status already shows as disconnected. A full disconnect ensures stale credentials are cleared.
  5. Reconnect once. Complete the full Google OAuth flow and grant all requested permissions. Do not click the button multiple times — wait for the redirect to complete fully before taking any other action.

When the Issue Persists — What to Have Ready

If disconnections continue after following the steps above, this issue requires backend investigation by our team. To help us resolve it as quickly as possible, please have the following information ready when you reach out:

  • The email address of the Google Account used for the integration
  • The name of the GSC property or Business Profile affected
  • The approximate date and time the disconnection first occurred or recurred
  • Any error messages displayed during reconnection attempts

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.