Google Search Console AI Agent
Query Search Console data in plain language — the Agent uses mcp-search-console to answer questions about rankings, impressions, clicks, and indexing status.
The full canvas, before you import it
Click any node to see its config.
Click a node to select it — same as the Heym editor; the panel shows its settings.
3 nodes · Free & source-available
Google Search Console AI Agent
Ask plain-language SEO questions and get back search performance data directly from Google Search Console — no dashboard needed.
What this workflow does
- SearchQuery — type a free-text SEO question
- SearchConsoleAgent — an Agent queries GSC through the mcp-search-console MCP server and summarizes the results
- SearchResult — returns the Agent's answer
Use cases
- "Which pages got the most impressions last week?"
- "What queries rank between position 5 and 15 for my site?"
- "Show me pages with high impressions but low CTR"
- "Is
/blog/my-postindexed?" - "List my submitted sitemaps and their status"
- "What are my top queries by clicks over the last 28 days?"
Service account setup (recommended)
- Go to Google Cloud Console → IAM & Admin → Service Accounts
- Create a service account (e.g.
[email protected]) - Enable the Google Search Console API in APIs & Services → Library
- Download a JSON key for the service account (Actions → Manage keys → Add key → JSON)
- In Search Console, go to Settings → Users and permissions → Add user, and add the service account email as a Restricted or Full user
- Base64-encode the key:
base64 < service-account.json | tr -d '\n' - Paste the result into the
GSC_CREDENTIALS_JSON_B64env field on the MCP connection
OAuth alternative
If you prefer OAuth instead of a service account, set GSC_TOKEN_JSON_B64 (your token.json) and GSC_OAUTH_CLIENT_SECRETS_JSON_B64 (your OAuth client secrets) in the env field instead. The bootstrap script supports both authentication methods.
MCP connection setup
Open SearchConsoleAgent, find the mcp-search-console MCP connection, and update:
GSC_CREDENTIALS_JSON_B64— your base64-encoded service account JSON- Update
YOUR_SITE_URLin the system instruction to your verified GSC property URL (e.g.https://example.com/)
Notes
- The Agent is configured read-only: it will not submit sitemaps, delete properties, or make any changes
- The
mcp-search-consolepackage is installed automatically byuv run --with - Requires Python 3.11+ and
uvto be installed on the machine running Heym
How to import this template
- 1Click Import → Copy JSON on this page.
- 2Open your Heym and navigate to a workflow canvas.
- 3PressCmd+V/Ctrl+V— nodes appear instantly.
- 4Add your API keys in the node config panels and click Run.
Discover more automations
- IntegrationReddit Subreddit GET Tool CallLet an Agent call a no-key HTTP GET tool that fetches hot posts from a subreddit JSON feed.
- IntegrationJina Web FetcherFetch clean, LLM-ready text from any URL using the Jina Reader API.
- IntegrationOpen-Meteo Weather SnapshotPull live weather (no API key) from Open-Meteo for any city coordinates — great for travel bots and dashboards.
- IntegrationZenQuotes Random QuoteFetch a random inspirational quote as JSON from the free ZenQuotes API — no API key, ideal for bots and UI demos.
- IntegrationSlack + Postgres MCP Answer AgentAnswer Slack channel questions by letting an Agent query Postgres through MCP, then post the answer back to Slack.
- IntegrationDiscord Incoming WebhookPost a message to a Discord channel with a single HTTP node — structured text input and webhook JSON body.
- IntegrationGoogle Sheets AI EnricherRead new rows from Google Sheets, classify or enrich them with an LLM, and write the results back automatically.
- IntegrationRealtime WebSocket Alert RelayListen to an external WebSocket feed, audit critical events, and forward them to another realtime channel.