Skip to main content
Use Connections to decide which Google accounts HyperGSC can use and which Search Console properties AI clients can read.

​
Connect a Google account

  1. Sign in to HyperGSC.
  2. Open Connections and select Connect Google Account.
  3. Choose the Google account that has Search Console access and complete consent.
  4. Review the discovered properties.
  5. Select the properties you want to expose and choose Save changes.
HyperGSC requests read-only Search Console access. Google credentials stay on the service; AI clients use their own HyperGSC authorization.

​
Choose the correct property

Copy the property identifier from discovery instead of constructing one from a domain. A Domain property and a URL-prefix property are separate reporting boundaries, even when their names look similar. For example, sc-domain:example.com and https://www.example.com/ are not interchangeable. When multiple Google connections expose the same site, research tools can use the returned connection_id to select the intended connection.

​
Refresh property discovery

Use Refresh properties after a site is added in Search Console or your Google access changes. Newly discovered properties are disabled by default; select and save them before using them in an agent. If refresh fails, confirm that the connected Google account still has access. Reconnect when Google authorization has expired or been revoked.

​
Property limits

After a downgrade, reduce an oversized selection before making further Search Console requests. Changing the selection applies to every connected AI client.

​
Disconnect or switch accounts

Disconnect the old connection in HyperGSC when it is no longer needed. This removes its credentials and properties from HyperGSC. Remove the authorization from Google’s third-party access settings if you also want to revoke the Google grant. Authorize a new Google account separately, refresh its properties, and save the intended selection. Then ask your agent to call get_capabilities again. See authentication for client authorization and troubleshooting for error-specific fixes.