## **⚠️ What the error means**

When Atlas Agent returns **PRECONDITION\_FAILED** and says Google Search Console is not connected for this account, it cannot use Search Console data for the site it is working on. The agent stops instead of guessing. A property that looks active in Site Metrics, including a domain property such as **sc-domain:eladhamdistributors.com**, does not always mean the agent has a usable connection for that same site.

## **📊 Why Site Metrics can still look connected**

Site Metrics and Atlas Agent do not check the connection in exactly the same way. Site Metrics can keep showing a property that was connected earlier, while the agent requires a current authorization on the Search Atlas site you selected. The usual causes are:

- The Google account that owns or can access the Search Console property is not the account currently authorized in Search Atlas.
- The property is linked to a different site record than the one Atlas Agent is using.
- A domain property is connected, but the agent site is a different host, protocol, or URL-prefix property.
- The Google permission was removed, expired, or was not granted for Search Console when the account was connected.
- The connection was updated recently and has not finished syncing.

You do not add a separate Search Console product inside Google. You do need the correct Google user, the correct property, and that property selected on the same Search Atlas site.

## **📍 Where to Find It**

**UI path:** Settings → Integrations

## **🛠️ Checks before you reconnect**

1. Open the site in Search Atlas that Atlas Agent is using, not only the Site Metrics view.
2. Confirm the connected property is the one you expect, such as the domain property for eladhamdistributors.com.
3. In Google Search Console, confirm that the same Google user can open that property and that it is not limited to a different domain or URL prefix.
4. If you manage more than one Search Atlas site, make sure the agent task is running on the site where this property is selected.

## **🔗 How to restore access**

1. In Search Atlas, open the site and go to the Google Search Console connection used by that site.
2. Disconnect the current Google connection for that site if one is shown.
3. Connect again and sign in with a Google account that has access to the domain property.
4. Approve the requested Google permissions, including access to Search Console data.
5. Select the matching property, such as **sc-domain:eladhamdistributors.com**, and save it to this site.
6. Wait a few minutes for the sync to finish, then run Atlas Agent again on the same site.

If the property is correct but the agent still reports that Search Console is not connected, repeat the connection once. A second authorization refreshes an expired or partial grant. No extra manual mapping is required beyond selecting that property on the site the agent uses.

## **✅ After the connection is fixed**

Atlas Agent should stop returning this precondition error and should be able to read the connected property. Site Metrics may update on its own schedule, so a short delay is normal. If metrics look current but the agent still fails, the site selected for the agent is still not the site that holds the active property.

## **💬 When to contact support**

If you confirmed the Google user can open the property, selected that same property on the agent site, and the error remains after a fresh connection and a short wait, contact support. If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.