## **🔍 What You May Be Experiencing**

If you recently noticed your website traffic data drop suddenly — for example, from 1,000–2,000 daily visits down to around 40 — and you are also seeing a **400 error** when running prompts in the Atlas AI Agent, these two issues share the same root cause: a stale or broken Google Search Console (GSC) integration.

When the GSC connection becomes disconnected or stops syncing correctly, the Atlas AI Agent loses access to your live traffic and performance data. This causes prompt failures and makes your traffic appear to have collapsed inside the platform.

## **⚠️ Common Symptoms**

- Atlas AI Agent returns a **400 error** when you submit a prompt
- Daily website traffic shown in the platform drops dramatically and unexpectedly
- Site Metrics data appears outdated, incomplete, or frozen
- AI Visibility or performance insights seem inaccurate or missing

## **🧩 Why This Happens**

Google Search Console connections can become stale over time due to expired OAuth tokens, permission changes in your Google account, or property mismatches. When this happens, Search Atlas can no longer pull fresh data from GSC. The Atlas AI Agent relies on this data to respond to prompts — and without a valid connection, it returns a 400 error instead of a useful answer.

This is not a problem with your website itself. Your actual traffic has not dropped. The platform simply cannot display or use your data while the GSC connection is broken.

## **✅ How to Fix It – Reconnect Google Search Console**

Follow these steps to disconnect and reconnect your Google Search Console integration:

1. Click your **avatar** in the top-right corner of the platform to open the account menu.
2. Navigate to **Settings → Integrations** — *Note: if your GSC integration settings are housed under a dedicated Integrations or Connected Accounts section visible in your account, navigate there instead.*
3. Locate your **Google Search Console** connection and click **Disconnect**.
4. Once disconnected, click **Connect** (or **Reconnect**) and follow the Google OAuth prompts to sign in and grant permissions.
5. When selecting a property during reconnection, make sure you choose the **exact GSC property** that matches your website — for example, `https://www.yourdomain.com` vs. `http://yourdomain.com`. A property mismatch is a common cause of sync failures.
6. Save your settings and return to **Site Metrics** (left sidebar → **Site Metrics**) to confirm your data is loading correctly.

## **⏳ Data Sync Timeline**

After reconnecting Google Search Console, please allow **24 to 48 hours** for your traffic and performance data to fully resync inside Search Atlas. During this window:

- Traffic numbers may still appear lower than expected — this is normal while the sync catches up.
- The Atlas AI Agent should resume responding to prompts correctly once the connection is validated, though data-dependent answers will improve as the sync completes.
- If you still see a 400 error after 48 hours, proceed to the troubleshooting step below.

## **🔎 Verify Your GSC Property Is Correct**

A common reason reconnection does not resolve the issue is a **property mismatch**. In Google Search Console, the same domain can exist as multiple properties (e.g., with or without `www`, with `http` or `https`). Make sure the property you connect in Search Atlas is:

- The property that is **verified** in your Google Search Console account
- The property that has **active data** — check inside GSC directly to confirm traffic is visible there
- The **primary version** of your domain (the one your visitors actually land on)

## **🤖 About Atlas AI Agent and AI Visibility**

The **Atlas AI Agent** is your in-platform AI assistant that answers questions about your site's SEO performance, traffic trends, keyword rankings, and more. It pulls data in real time from connected sources — including Google Search Console — to generate accurate, personalised answers.

**AI Visibility** is a feature within Search Atlas that tracks how your brand and content appear across AI-generated search results and answer engines. Both features depend on a healthy GSC connection to surface accurate insights. Reconnecting GSC restores full functionality for both.

## **🛠️ Still Seeing a 400 Error?**

If you have completed the reconnection steps and waited 48 hours but the 400 error persists when using the Atlas AI Agent, there may be a permissions issue with your Google account or a configuration problem that requires a manual review.

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.