🔎 What causes recurring disconnections?
Search Atlas connects to Google using authorization tokens. A connection may appear valid but stop working when Google expires or revokes a token, permissions change, access is removed, or Google temporarily returns an authentication error.
GBP connections can be affected by profile ownership, manager permissions, duplicate locations, or intermittent Google API responses. These issues may occur at any time, including weekends, and do not necessarily mean your credentials are incorrect.
✅ Check the connection status
- For Google Search Console, open the relevant project in Search Atlas and review its integration or connection status.
- For Google Business Profile, open the affected GBP project in Search Atlas.
- Note which property or location is disconnected, the time it happened, and any displayed error message.
- Check whether the issue affects one property or multiple properties connected to the same Google account.
🔐 Confirm Google access
- Sign in to the Google account that owns or manages the affected property.
- Confirm that the account still has the required Search Console or Business Profile permissions.
- Check that the property or location has not been deleted, transferred, renamed, or duplicated in Google.
- For GBP, verify that the account has appropriate access to each affected location, not only to the business group.
🔄 Reconnect the affected service
- Disconnect only the affected Google connection when the platform provides that option.
- Reconnect it using the Google account with confirmed access.
- Approve all requested permissions and select the correct properties or locations.
- Return to the project and confirm that data loads successfully.
Reconnect only once when possible. Repeated reconnect attempts can make it harder to identify whether the issue is caused by permissions, a specific property, or a temporary Google response.
🧪 Collect details for investigation
If the connection disconnects again, record the exact time, your time zone, affected properties or locations, Google account used, and the full error message. Screenshots of the connection status and any failed synchronization are also useful.
Also note whether the issue happens after a password change, permission update, account switch, location transfer, or other Google Business Profile change. This information helps determine whether the failure is token-related, property-specific, or part of a broader service issue.
🛠️ How recurring issues are handled
Some disconnections are caused by recoverable Google authentication responses rather than a permanent loss of access. Search Atlas may need to investigate server logs, token handling, affected profile types, and synchronization behavior to identify the underlying cause. When escalating, please have your project name, affected Google account, exact error message, and the timestamp of the disconnection ready.
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.