Manage, Remove, or Disable GSC Properties

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🗺️ Overview

If you connected your Google account to Search Atlas and see more Google Search Console (GSC) properties than you need, or are encountering an Access Forbidden error on a project, this article explains what to expect and how to get the right help quickly.

🔍 Why Are Multiple GSC Properties Showing?

When you connect a Google account to Search Atlas, the platform may import GSC properties that your Google account has access to. If your Google account has access to several properties, more than one may appear in Search Atlas — even if you only intend to work with one.

You can request removal or management of properties you do not need to keep your workspace tidy.

🗑️ How to Remove or Manage an Unwanted GSC Property

There is no self-serve option to remove or disconnect a GSC property directly from within Search Atlas. Removing a property requires a backend action by our support team, because properties are tied to your connected Google account at the account level and cannot be unlinked from the workspace interface alone.

To have a property removed or disconnected, please have the following information ready when you contact our support team so we can action this for you promptly:

  • The name or URL of the GSC property you want removed or disabled
  • Your account email and workspace name
  • Whether you want the property fully removed or simply hidden from your workspace

Note: Removing a property from Search Atlas does not delete it from Google Search Console. It only disconnects it from your Search Atlas workspace.

🚫 Fixing the "Access Forbidden" Error on Your Project

The Access Forbidden error means your user account does not currently have the required permission level to open a specific project or property. This is a separate issue from GSC property management.

If you encounter this error, here is what you should do:

  1. Confirm with your workspace owner or administrator that your account has been granted access to the relevant project.
  2. Ask the workspace owner to review your role and permissions and update them if necessary.
  3. Once your permissions have been updated, try accessing the project again.

If the error persists after your permissions have been reviewed and corrected, contact our support team. When you reach out, please have the following ready:

  • The name of the project or GSC property showing the error
  • The exact error message you see on screen
  • Your account email and workspace name
  • The name of the workspace owner or administrator who manages your permissions

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.