Connector · Business and support
A Google Search Console teammate in Slack that reads search data and submits nothing.
Chickpea gives a channel a named AI teammate that holds its own Google Search Console connection. It queries search performance, inspects whether a URL is indexed, and reads sitemap status for the sites an Admin approved. Ask which queries grew last month, or why a page is missing from Google, and the answer comes back in the thread. What people call a Google Search Console Slack integration is usually an alert pushed out when something breaks. This one waits to be asked.
What people ask it.
The teammate is @growth, in #growth. Pick a scenario to watch it play.
| Query | Clicks | Impressions | CTR | Position |
|---|---|---|---|---|
| warehouse inventory software | 2,914 | 61,330 | 4.8% | 4.1 |
| northwind returns policy | 1,802 | 19,441 | 9.3% | 2.6 |
| barcode scanner setup | 1,455 | 48,207 | 3.0% | 8.4 |
| stock count template | 986 | 52,118 | 1.9% | 14.2 |
| inventory api docs | 774 | 10,655 | 7.3% | 5.0 |
Clicks and impressions over a period Read only
@growth how many clicks did the pricing page get last month, and from which queries
@growth clicks and impressions by day for the last 28 days
Reads never need confirmation. The teammate runs one bounded search performance query against a site an Admin selected, grouped by up to five of Google's seven dimensions, and answers with the dates it used. Google returns clicks, impressions, CTR, and average position for each row. A range can cover at most 366 days, so a question about three years comes back as a question rather than a wrong number.
Which queries or pages moved Read only
@growth which queries gained the most clicks this month against last month
@growth which pages lost impressions in the last 28 days, and did their position drop
Each period is its own query, and the arithmetic happens in the thread where both rows are visible. A long answer comes back as a table. One query returns at most 1,000 rows and 256 KB, so a large site is answered top down rather than all at once. Position and impressions are separate columns, which is how the teammate tells a ranking drop from a demand drop.
Whether a URL is indexed, and why not Read only
@growth is the new returns guide indexed yet
@growth why is the pricing page not showing up in Google
The URL inspection capability reads Google's own record for one URL under a selected site: the verdict, the coverage state, whether a robots.txt rule blocks it, whether a noindex rule does, the last crawl time, the canonical Google picked against the one the page declares, and the sitemaps Google knows list it. Google documents this as the version in its index, so the teammate cannot test a live URL.
Sitemap status Read only
@growth when was our sitemap last downloaded, and did it have errors
@growth how many URLs in the blog sitemap has Google indexed
The teammate lists the sitemaps for a selected site, or reads one by its path, and reports what Google returns: whether it is still pending, when it was last submitted and downloaded, the error and warning counts, and the submitted and indexed counts per content type. Google's API can also submit and delete a sitemap. Neither is in the capability list.
On a schedule Applies at once
@growth every Monday at 9am Pacific, post last week's clicks here with the queries that moved most
@growth every Monday at 8am Eastern, post which pages lost the most impressions last week
A schedule saves on the spot. It needs an explicit time zone and runs under the Google Search Console connection of the person who asked. Before each run Chickpea re-reads the teammate, the channel grant, and that connection, and a missing one fails the run with a named reason rather than running it.
Connect it
Five steps, from Admin or from Slack.
You sign in through a page Chickpea serves, never in Slack. The link the teammate posts is good for one action, for one teammate, for 24 hours.
- In Chickpea Admin, open the teammate, then Connections, find Google Search Console, and choose Connect. Or ask in Slack,
@growth connect Google Search Console, and follow the link it posts. - Choose who uses it. Team is one shared Google account that everyone who can use the teammate reads through. Personal means each member signs in as themselves and sees the sites their own account is verified for.
- Choose Continue to sign in. A hosted sign-in opens in a second tab and Google asks you to approve the account. There is no token to paste anywhere in this connector, and nothing goes into Slack. The attempt stays open for 30 minutes. Read the permissions on that screen, because the grant there can be wider than the capabilities the teammate is handed.
- An Admin selects the Search Console sites. Until that is saved the connection stays pending and the teammate is given no Search Console tools at all. Select Choose, tick the sites, then Save access.
- Ask something.
@growth which queries brought the most clicks last monthis a good first question, because every capability on this connector reads and none of them can change a thing.
A connection belongs to one teammate. Giving a second teammate Google Search Console means a second sign-in, with its own consent and its own site selection. Chickpea stores an opaque local handle and a display label for each site, so the site URL never reaches the teammate. The adapter swaps the handle for the real site immediately before the call, and an unknown or unselected handle fails before anything is sent.
A managed connector has no discovered tool list. The teammate is handed a fixed list of capabilities that Chickpea curates, not Google's whole Search Console API. Five cover Google Search Console: read one selected site's permission level and metadata, list its sitemaps, read one sitemap, inspect the index status of a URL under it, and query bounded search performance. Google's API also adds and removes sites and submits and deletes sitemaps. None of those are in the list, and there is no write capability at all. The capability list is in the product source.
Google Search ConsoleBeside Google Search Console
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 connectors.
Google AnalyticsSearch Console has the query and the click, GA4 has what the person did next
AhrefsYour own impressions beside third-party keyword and backlink research
Google AdsPaid and organic for the same query, asked once in the channel
FirecrawlFind out why a page is not indexed, then read the page itself to see what is on it
Questions people ask
Is there a Google Search Console MCP?
Several third-party ones, and this connector uses none of them. Google's Search Console API reference documents four REST resources, Search Analytics, Sitemaps, Sites, and URL Inspection, and no MCP server. The projects that rank for that search are written by other people, and each one runs on a single machine that a desktop client points at. Search Console in Chickpea is a managed connector with a fixed capability list, and nothing in it speaks MCP.
Can it change anything in Search Console?
No. All five Search Console capabilities read, and this connector has no write lane at all. It is one of three in that position, with Google Analytics and Gong. Under the capability list sits a gate that does not consult the model: during a Slack turn Chickpea refuses any managed capability whose effect is not read.
Can it request indexing or submit a sitemap?
No, and the two are different kinds of no. Requesting indexing is not in Google's API at all. It is a button in the URL Inspection tool, and Google says a request does not guarantee the page appears in the index and that a daily limit applies. Submitting a sitemap is in Google's API, and it is absent from Chickpea's capability list, along with deleting a sitemap, adding a site, and removing one. The teammate can tell you a sitemap has errors. You go to Search Console to do something about it.
Why is the connection still pending?
Because nobody has picked the sites yet. Signing in with Google is not enough on this connector. An Admin has to select one or more Search Console sites before the teammate receives any tools. Open the connection row, select Choose, tick the sites, and select Save access.
Which sites can it see?
Only the ones an Admin selected, and only what the connected Google account is verified for. Chickpea stores an opaque local handle and a safe label for each site, so the site URL and the connected-account reference never appear in the teammate's input. Each capability takes one site at a time, so a question about two sites is two reads. A handle that is unknown, removed, or unselected fails before anything is dispatched.
What does bounded mean on this connector?
Limits written into the input schema rather than left to the model. A search performance range can be at most 366 days. It takes up to 5 dimensions from query, page, country, device, date, hour, and search appearance, and search appearance cannot be combined with another. Rows are capped at 1,000, where Google itself allows 25,000, and the starting row at 25,000. Search type is one of web, image, video, news, Discover, and Google News. Every result is capped at 256 KB before it goes back to the model.
How far back can it read?
A year and a day in one query, which is the 366-day cap. A question about a longer stretch is answered in several queries rather than one, and the teammate says which ranges it used. Data state is Google's: final by default, or all if you want the freshest rows, which Google warns are preliminary and can change.
Is this Google's own AI?
No. Chickpea is an open source Slack app you deploy to your own Cloudflare account, and it is not built by Google or affiliated with Google. The teammate reads Search Console as an ordinary connected account and answers in Slack. Whatever Google ships inside Search Console keeps working as it does.
Is the Search Console API free to use?
Google publishes usage limits for it rather than a price. Search Analytics allows 1,200 queries per minute per site and per user. URL inspection allows 2,000 queries per day and 600 per minute per site. Everything else runs at 20 queries per second per user. Those ceilings are far above what a channel asking questions will reach. Chickpea adds no per-seat charge, because you run the deployment and pay your model provider directly.
Can it post a weekly SEO report?
Yes. Ask for it in the channel and name a time zone. The schedule saves on the spot and runs under the Search Console connection of whoever asked for it. Every run re-reads the teammate, the destination grant, and that connection, so a disconnected account stops the report with a named reason instead of posting something stale.
Try it
Give a channel a Google Search Console teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Google Search Console, ask. Apache 2.0, no seats, no metering.
Or run it on Node. The setup guide covers both.
Last checked
Facts on this page were checked against the product and Google Search Console's own pages on September 17, 2026. This page is also available as markdown at /connectors/google-search-console.md.