Use this article to reconnect a Google Business Profile (GBP) that shows as disconnected, clear the Google OAuth Error 400: invalid_request during a GBP Audit, and troubleshoot local rankings that show no data. Each fix below is a self-contained set of steps.
📋 How Local SEO syncing works in Search Atlas
Local SEO in Search Atlas relies on Google APIs, Google Maps indexing, citation aggregators, geolocation data, and asynchronous sync cycles. Because these systems update on their own schedules, short delays between an action and visible results are normal.
- Ranking and review data update on recurring sync cycles, not instantly.
- Some sync jobs can take up to 1 hour to finish after you reconnect.
- Reconnecting a Google account does not delete your historical Local SEO data.
⚠️ Fix a Google Business Profile that shows "Disconnected"
A "Disconnected" status means your Google authorization token expired, your permissions changed, or Google invalidated the connection during a security refresh. While disconnected, rankings stop updating, reviews stop syncing, GBP posts fail, geo-grid scans go stale, and Local SEO reports may show incomplete data.
🔁 Reconnect your GBP account
- Go to Avatar (top-right) → Settings → Integrations → GBP card → View Connected Accounts.
- Click Disconnect, then click Connect Google Account to reconnect fresh.
- Log in with the same Google account that owns or manages the GBP listing.
- Approve all requested permissions, and confirm that Maps and Business Profile permissions are granted.
- Wait 15–30 minutes for synchronization to restart.
- Hard-refresh the dashboard — Windows:
Ctrl + Shift + R, Mac:Cmd + Shift + R.
Note: The initial count of businesses shown in the Connect Account modal may not reflect all your Google Businesses — the full count displays after connection completes.
Note: After reconnecting, you may keep receiving notifications for a few minutes while the system updates your account status. This is normal.
✅ Confirm rankings are flowing again
Go to Left Sidebar → Local → Local SEO Heatmaps (then click the View button for your listing → View Your Local SEO Heatmap), then check the Keyword Ranking Score. Fresh ranking scans appearing again confirm the connection is healthy.
🛠️ If your GBP keeps disconnecting
- Remove the GBP integration completely, then reconnect from scratch and wait for a full sync cycle.
- Contact support if reconnection fails repeatedly, the account reconnects but instantly disconnects, or no Local SEO data returns after 1 hour.
⚠️ Fix Google OAuth "Error 400: invalid_request" during a GBP Audit
When Google rejects the connection as non-compliant with OAuth 2.0 policy and shows Error 400: invalid_request as you start a GBP Audit, your stored Google authorization is no longer valid. Reconnect the account to generate a new, valid authorization.
🔑 Re-authorize your Google account
- Log into Search Atlas and open your Google account connection settings.
- Click Disconnect on the connected Google account.
- Click Connect Google Account and sign in with the Google account that manages the GBP listing.
- Approve all requested permissions to establish a new valid authorization for the GBP Audit.
- Run the GBP Audit again.
If the error persists after reconnecting, contact support — the team can resolve it on the backend, usually within a few minutes. You'll be able to run the GBP Audit once the new authorization is active.
⚠️ Fix local rankings that show "No data"
A geo-grid scan can show no data while it is still processing, when the listing has weak local authority signals, or when the location parameters are configured incorrectly. This most often affects new GBP listings, recently verified businesses, and incorrectly configured geo-grids.
🗺️ Check your listing and address
- Verify your GBP listing is publicly visible on Google Maps.
- Confirm the business address matches exactly across your GBP, Search Atlas, citations, website footer, and schema markup (NAP consistency).
📊 Check your geo-grid settings
- Go to Left Sidebar → Local → Local SEO Heatmaps (then click the View button for your listing).
- Confirm the target city, ZIP/postal code, radius, and keywords are correct.
- Temporarily reduce the scan radius — smaller grids process faster and help isolate visibility issues.
- Trigger a manual scan refresh: click View Your Local SEO Heatmap, then hover over the date area.
Fresh scores appearing on the heatmap confirm the scan completed successfully.
📝 If GBP posts don't appear on Google
If GBP posts created in OTTO aren't showing up on your Google Business Profile, this is typically a sync or permissions issue. Work through these checks in order:
- Verify that OTTO sync is enabled for the GBP listing.
- Check that the connected Google account has GBP posting permissions for the listing.
- Clear your browser cache, or try again in an incognito/private window.
- If posts still don't appear after a full sync cycle, contact support so the team can investigate on the backend.
🗺️ If your business location isn't updating
If your service area or business location doesn't update after a relocation, clear the existing citation data or manually sync the location from your GBP listing, then allow a sync cycle to complete. Underlying sync issues affecting location updates have been fixed recently, so a fresh sync should now apply the new location. If the location still doesn't update, contact support.
🛠️ GBP completion score stuck or not updating
If your GBP completion score appears stuck (for example, at 95%) or won't update, this is a known bug affecting completion scoring. Our engineering team is tracking it, and it does not reflect a problem with your listing or connection. Contact support if you'd like to be notified when the fix is released.
🛠️ If GBP data in reports won't load
If GBP data in your reports shows a loading spinner and won't complete, refresh the page or clear your browser cache. If this persists, contact support.
🎯 You now know how to reconnect a disconnected GBP, clear the OAuth Error 400: invalid_request during a GBP Audit, and troubleshoot empty local rankings. If a fresh reconnection doesn't resolve the error or no data returns after 1 hour, contact Search Atlas support so the team can finish the fix on the backend.