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

# Let AI Agents Check Indexing in Search Console

> Let SEO agents query clicks and impressions, inspect URLs, and check indexing in Google Search Console. The gateway injects OAuth tokens for every call.

> [!WARNING]
>
> **Per-app Google setup is deprecated.** All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the [Google setup guide](/docs/integrations/google.md). Credentials saved for one Google app apply to all of them.

## Overview

Buckle connects AI agents to Google Search Console through Google's OAuth flow. Agents can query search performance data, inspect individual URLs, and check indexing status. The gateway injects OAuth credentials into requests to the Search Console API automatically.

This is useful for SEO agents that need to monitor search rankings, identify indexing issues, or analyze search traffic patterns.

## What you will set up

* A Search Console connection through Google OAuth, in one click on Buckle Cloud or with your own client
* Automatic token injection on Search Console API requests
* Per-agent, per-tool access to your properties

## Connect on Buckle Cloud (one click)

**1. Open the app**

Open the Buckle dashboard and navigate to **Settings** > **Apps** > **Google Search Console**.

**2. Authorize**

Click **Connect Google Search Console**. You'll go straight to Google: pick your account, review the permissions, and click **Allow**. No Google Cloud setup needed.

On self-hosted Buckle, or to use your own Google client on Cloud, see [Use your own Google client](#self-hosted).

## Use your own Google client

> [!NOTE]
>
> This is for self-hosted Buckle, and for Buckle Cloud when you choose **Custom credentials** instead of one-click. One Google client serves every Google app in Buckle, so you set it up once. If you already did it for another Google app, skip to step 2.

> [accordion] 1. Set up your Google client
>
> Follow the [Google setup guide](/docs/integrations/google.md). It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
>
> You paste the client into **Settings** > **Apps** > **Google Search Console** > **Custom credentials**, under the Redirect URI the guide asks you to register:
>
> ![Buckle Custom credentials card for Google Search Console with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/google-search-console/buckle-custom-credentials-google-search-console.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=111cec56b9c4da88bfdb9992bcdd9ca5)
>
> Custom credentials for Google Search Console in Buckle.

> [accordion] 2. Connect Google Search Console
>
> Open **Settings** > **Apps** > **Google Search Console**, select **Connect Google Search Console**, pick your Google account, and click **Allow**.
>
> ![Buckle connect window for Google Search Console showing Configuration required and the Configure credentials button.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/google-search-console/buckle-connect-google-search-console.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=9256fe2069cfb14978dd16adca0f073d)
>
> The Google Search Console connect window before a Google client is set up.

## What agents can do

* Query search performance data (clicks, impressions, CTR, average position) with custom date ranges
* Break down search data by query, page, country, device, and search appearance
* Inspect individual URLs to check indexing status and crawl details
* Submit URLs for indexing
* List verified sites and properties
* View crawl errors and coverage issues
* Read sitemap submission status
* Check mobile usability issues for specific URLs
* Compare search performance across date ranges

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules.md) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Search Console.

## FAQ

> [accordion] Which properties can the agent see?
>
> The properties the connected Google account can access in Search Console.

> [accordion] Does the agent see my Google token?
>
> No. The token stays in Buckle, and the gateway adds it at the proxy. See [How it works](/docs/how-it-works.md).

> [accordion] How do I reconnect or switch accounts?
>
> Open **Settings** > **Apps** > **Google Search Console** and connect again. Agents with [access](/docs/guides/agent-access.md) use the new connection automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.