> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apexgenius.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Search Console

> Authorize a Google account and enable the exact Search Console properties available to the private-preview gateway.

Google Search Console is an ApexGenius private-preview connection. It uses Google OAuth and provider-native property resources.

## What you need

* A Google account with access to the intended Search Console property
* Owner, full-user, or restricted-user access appropriate to the operations you want to run
* ApexGenius private-preview access

## Connect Search Console

1. In ApexGenius, open **Connections**.
2. Select **Google Search Console**.
3. Choose **Connect Google Search Console**.
4. Review the Google consent screen and authorize the account.
5. Return to the connection details.
6. Refresh provider resources.
7. Enable only the properties the MCP gateway should expose.

The current preview requests the Search Console read/write scope because the tool catalog can include sitemap operations. A read-only release should use Google's read-only scope instead.

<Warning>
  **Private preview.**

  The ApexGenius Google OAuth application and any required scope verification must be complete before public onboarding. Search Console property permissions and API quotas still apply.
</Warning>

## Official Google documentation

* <a href="https://developers.google.com/webmaster-tools/v1/how-tos/authorizing" target="_blank" rel="noreferrer">Search Console authorization and scopes</a>
* <a href="https://developers.google.com/webmaster-tools/v1/sites/list" target="_blank" rel="noreferrer">List authorized Search Console properties</a>
* <a href="https://support.google.com/webmasters/answer/7687615?hl=en" target="_blank" rel="noreferrer">Search Console users and permissions</a>
* <a href="https://support.google.com/cloud/answer/13463073?hl=en" target="_blank" rel="noreferrer">Google OAuth app verification</a>

Google documentation is authoritative for property permissions, OAuth scopes, verification, and API behavior.