Marketing connector
Google Search Console connector for governed AI agent access
Connect Google Search Console with an OAuth access token and optional default site URL.
Direct answer
OneQuery supports Google Search Console for governed agent access.
Teams use the Google Search Console connector to give AI agents bounded source API calls for endpoint-specific context while OneQuery keeps credentials centralized, limits access to approved sources, and preserves audit logs for review.
Agent workflow
What this connector enables
Google Search Console becomes an approved OneQuery source instead of a secret copied into an agent prompt, shell session, or model tool. The agent receives a governed access path, and the source credentials stay behind OneQuery.
- Use bounded source API calls for endpoint-specific context for marketing context.
- Keep Google Search Console credentials centralized and out of agent runtimes.
- Review agent access through OneQuery audit history instead of reconstructing direct service usage.
Setup checklist
Prepare the Google Search Console connection
Use google search console credentials and connect the source through the Dashboard and CLI. Keep credentials scoped to the data the agent is allowed to read.
- Create or obtain an OAuth 2.0 access token with the `https://www.googleapis.com/auth/webmasters.readonly` scope.
- Copy the token into `credentials.accessToken`.
- Optionally include `siteUrl` so selector `/searchAnalytics/query` expands to `/sites/<siteUrl>/searchAnalytics/query`.
FAQ
Google Search Console connector questions
What is the OneQuery Google Search Console connector?
The OneQuery Google Search Console connector makes marketing context from Google Search Console available to AI agents through bounded source API calls for endpoint-specific context. Connect Google Search Console with an OAuth access token and optional default site URL.
How do AI agents access Google Search Console through OneQuery?
Agents call OneQuery instead of receiving raw Google Search Console credentials. OneQuery keeps credentials centralized, applies source boundaries, and records access in audit logs while exposing bounded source API calls for endpoint-specific context.
How do I set up the Google Search Console connector?
Prepare google search console credentials and connect Google Search Console from the OneQuery dashboard or CLI. Start with this setup step: Create or obtain an OAuth 2.0 access token with the `https://www.googleapis.com/auth/webmasters.readonly` scope.