## **🔍 Overview**

When running a Google Business Profile (GBP) audit in Search Atlas, you may encounter the following error: **Error 400: invalid\_request**. This is a Google OAuth 2.0 authorization error that occurs when your Google account connection has expired or become invalid. Clearing your cache or signing out will not fix this — the solution is to disconnect and reconnect your Google account directly inside Search Atlas.

## **⚠️ Why This Happens**

Search Atlas uses OAuth 2.0 to securely connect to your Google account and access your GBP data. Over time, this authorization token can expire or be revoked — for example, if you changed your Google password, revoked app permissions, or the token simply timed out. Once the token is invalid, any attempt to run a GBP audit will trigger the **Error 400: invalid\_request** message from Google.

## **🛠️ How to Fix It: Reconnect Your Google Account**

Follow these steps to disconnect and reconnect your Google account to restore GBP audit access.

1. Navigate to the GBP or Local section of Search Atlas where your Google Business Profile projects are listed.
2. Locate the GBP project that is showing the authorization error.
3. Find the Google account connection option for that project — it will indicate that the authorization has expired or is no longer valid.
4. Disconnect or remove the expired Google authorization from the project.
5. Once disconnected, initiate a new Google account connection for the same project.
6. A Google sign-in window will appear. Sign in with the Google account that has access to your GBP listing and grant the requested permissions when prompted.
7. After successfully authorizing, return to your GBP project and relaunch the audit.

The **Error 400: invalid\_request** message should no longer appear and your audit will proceed normally.

## **✅ Confirm the Connection Is Working**

After reconnecting, verify the fix was successful before running a full audit:

- Confirm your GBP location data is loading correctly within the platform.
- Check that your GBP project no longer displays an authorization warning or error status.
- Try running the audit again — if it progresses past the authorization step, the reconnection was successful.

## **🚫 What Will Not Fix This Error**

The following steps are commonly suggested for Google errors but **will not resolve Error 400: invalid\_request** caused by an expired OAuth token:

- Clearing your browser cache or cookies
- Signing out of and back into Search Atlas
- Using a different browser or incognito mode
- Disabling browser extensions

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.