🔍 Overview
If your Google Business Profile (GBP) integration keeps disconnecting — even after you successfully reconnect it — you are likely experiencing a Google OAuth token revocation issue. This article explains why this happens, how to identify it, and the steps to resolve it for good.
⚠️ Why Does This Keep Happening?
Search Atlas connects to your Google Business Profile using a secure authentication method called OAuth. Google issues a token (a kind of digital key) that allows the platform to read and write data on your behalf. This token can become invalid for several reasons:
- You revoked platform access in your Google Account security settings — either intentionally or accidentally.
- Your Google password changed, which automatically invalidates all connected app tokens.
- Too many connected apps caused Google to cycle out older tokens.
- Your Google Account was used to connect multiple Search Atlas workspaces, causing token conflicts across accounts.
- Inactivity or a Google-side security review expired the token without warning.
When a token is revoked, Search Atlas loses access silently in some cases, which means scheduled posts and data syncs can fail without an obvious error message. The platform is being updated to display a reconnect banner when this occurs, but in the meantime this article will help you get ahead of the issue.
🛠️ How to Permanently Fix the Disconnection
Follow these steps in order. Skipping steps — especially the Google security cleanup — is the most common reason the problem keeps coming back.
- Remove Search Atlas from your Google Account permissions. Go to myaccount.google.com → Security → Third-party apps with account access. Find Search Atlas and click Remove Access. This clears any corrupted or partial token before you reconnect.
- Sign out of all Google accounts in your browser. If you are signed into multiple Google accounts, token conflicts are common. Use a clean browser session or an incognito window for the next step.
- Sign back in to Search Atlas and navigate to the GBP integration settings. Go to Local → GBP Projects and click Connect GBP Account.
- Authenticate with one Google Account only. When the Google sign-in prompt appears, choose the single Google Account that owns or manages your GBP locations. Do not connect multiple Google Accounts to the same workspace.
- Grant all requested permissions. Search Atlas requires specific scopes to manage your GBP listings and scheduled posts. Declining any permission will result in a partial connection that breaks later.
- Verify the connection status. After reconnecting, confirm that your GBP locations appear in the platform and that their status shows as active. If any location shows a warning or is missing, repeat the steps above using the correct Google Account for that location.
🔄 Consolidating Multiple Google Accounts
A very common cause of recurring disconnections is having GBP locations spread across different Google Accounts while connecting them all to one Search Atlas workspace. Here is how to consolidate cleanly:
- Identify which Google Account is the primary owner of each GBP location you want to manage in Search Atlas.
- If locations are owned by different Google Accounts, use Google Business Profile Manager to add a single shared Google Account as a manager across all locations.
- Once all locations are accessible from one Google Account, reconnect Search Atlas using that single account.
- Remove any old or duplicate Google connections from the Search Atlas integrations settings page before reconnecting.
Using one Google Account as the connection point significantly reduces token conflicts and prevents future disconnections.
📋 How to Check If Your Connection Is Healthy
After reconnecting, use these checks to confirm everything is working correctly:
- Navigate to Local → GBP Projects and confirm each location shows a green active status.
- Create a test scheduled post for one GBP location and verify it publishes at the scheduled time.
- Check your GBP dashboard in Search Atlas to confirm location data is syncing correctly.
- Revisit myaccount.google.com → Security → Third-party apps and confirm Search Atlas appears with full access.
🚫 What to Avoid
- Do not reconnect without first revoking old access in your Google Account. Reconnecting on top of a broken token rarely fixes the underlying issue.
- Do not use a Google Account that has two-factor authentication set up on a device you no longer have access to — this can block the OAuth flow mid-connection.
- Do not connect the same Google Account across multiple Search Atlas workspaces simultaneously, as this can cause tokens to override each other.
💬 Still Experiencing Disconnections?
If you have followed all the steps above and the integration continues to disconnect, our team can review your account's token status and OAuth logs directly. 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.