Integration · Analytics and data
AI agents for Google Search Console
See how a site does in Google Search (clicks, impressions, click-through rate and position by query, page, country or device) and whether Google has indexed a page, signed in with the person's own Google account.
- Actions
- 3
- Read
- 3
- Write
- 0
Actions
What your agents can do in Google Search Console
3 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 3
Look things up. Nothing changes.
List sites
Lists the Search Console properties the person can see, with their permission level.
Query search performance
Reports a site's Google Search performance over a date range.
Inspect a URL
Asks Google what it knows about one page of a site, as the URL Inspection tool does.
Write 0
Create, change or send.
This tool only reads, so nothing in it changes.
Read only
Every action here only reads, so an agent can look things up in Google Search Console but cannot change anything there.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Sign in with Google and approve access (OAuth).
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Google Search Console data
Ask a question in plain words. The agent can list sites, query search performance or inspect a URL in Google Search Console, then answers with what it found.
- 02
Share what it finds in Slack
Give one agent Google Search Console and Slack: it can list sites in Google Search Console and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "List sites" to a workflow, and it runs in Google Search Console the same way every time, with or without an agent.
Works well with
More Analytics and data tools
- Google Analytics4 actionsRun Google Analytics 4 reports (users, sessions, views, conversions by page, source, country …), see who is on a site right now, and find the properties a person can read, signed in with the person's own Google account.
- Mixpanel4 actionsSend events to a Mixpanel project and query event counts, segmentation and saved Insights reports, in the US, EU or India data residency, with a service account.
- Amplitude14 actionsSend events to an Amplitude project and read its analytics: event counts and segmentation, funnels, retention, active users, saved charts, cohorts and one user's activity, in the US or EU data center.
- PostHog5 actionsQuery product analytics with HogQL, list recent events and persons, check which feature flags a user gets, and add annotations, in a PostHog Cloud project (US or EU) with a personal API key.
- Power BI5 actionsList Power BI workspaces and semantic models, refresh a model, push rows into a push dataset and run DAX queries, as the signed-in person.
- Tableau10 actionsFind workbooks, views and published data sources on Tableau Cloud or Tableau Server, read a view's data as CSV, query a published data source with the VizQL Data Service, search content through the Metadata API.
FAQ
Google Search Console and MyDeepAgents
Can MyDeepAgents connect to Google Search Console?
Yes. The Google Search Console connector has 3 actions, all of which only read. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Google Search Console?
Sign in with Google and approve access (OAuth). Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Google Search Console without asking?
No. Every Google Search Console action only reads, so an agent can look things up there but cannot change anything.
Can I use Google Search Console in workflows as well as agents?
Yes. Every Google Search Console action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Google Search Console to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.