Overview
If your GSC Performance tool displays a Site is not active error, or your settings are not importing as expected, this guide will help you identify the cause and resolve it. In many cases, this error is temporary and clears on its own.
Step 1: Wait and Refresh First
Before taking any other action, note that this error can be caused by a temporary sync delay or a short-lived authentication issue between Search Atlas and the GSC API. These often resolve on their own.
- Wait a few minutes without making any changes.
- Hard-refresh your browser and check whether the error has cleared.
If the error disappears after a refresh, no further action is needed.
Step 2: Confirm Your GSC Property Is Verified
If the error persists, confirm that the affected property is fully verified inside Google Search Console.
- Open Google Search Console in a new tab.
- Check that the property matching your domain appears in your property list.
- Confirm its status is Verified and that you have Owner or Full User permissions on that property.
If the property is unverified or you have restricted permissions, GSC will not authorise Search Atlas to pull data, which can trigger the Site is not active error.
Step 3: Reconnect Your GSC Integration
If the property is verified in GSC but the error still appears in Search Atlas, the connection between the two platforms may need to be refreshed.
- In Search Atlas, locate the option to manage your GSC connection.
- Disconnect your current GSC account.
- Reconnect by re-authorising with the Google account that holds Owner access to the affected property.
- Once reconnected, return to GSC Performance and allow some time for the data sync to complete before refreshing the page.
Step 4: Re-apply Your Import Settings
If your settings did not import correctly alongside the error, follow these steps after the connection is restored.
- Open the GSC Performance tool from your Search Atlas dashboard.
- Confirm the correct property is selected — make sure it matches the domain showing the error.
- Re-enter any date range, filter, or dimension preferences you had configured.
- Save your settings and verify that data is now loading correctly.
Still Seeing the Error?
If the error persists after completing all steps above, please reach out to our support team. To help us investigate quickly, have the following ready: the affected domain name, the exact error message you are seeing, and the approximate time the issue began.
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.