Skip to main content
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. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI 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 OneCLI Cloud or with your own client
  • Automatic token injection on Search Console API requests
  • Per-agent, per-tool access to your properties

​
Connect on OneCLI Cloud (one click)

1

Go to Connections

Open the OneCLI dashboard and navigate to Connections > 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 OneCLI, or to use your own Google client on Cloud, see Use your own Google client.

​
Use your own Google client

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

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.You paste the client into Connections > Google Search Console > Custom credentials, under the Redirect URI the guide asks you to register:
OneCLI 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.

Custom credentials for Google Search Console in OneCLI.

Open Connections > Google Search Console, select Connect Google Search Console, pick your Google account, and click Allow.
OneCLI connect window for Google Search Console showing Configuration required and the Configure credentials button.

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 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 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

The properties the connected Google account can access in Search Console.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Open Connections > Google Search Console and connect again. Agents with access use the new connection automatically.