What the Bot can read
GA4 and Search Console share one Google sign-in in MCP Ads, with a separate permission for each. Once both are connected, the Bot can list your GA4 properties and Search Console sites and choose the right one when you name it.
GA4: a traffic overview, traffic by default channel group, acquisition by source, medium and campaign, top pages, landing pages with engagement and conversions, conversion events, ecommerce totals and item performance, devices, locations, new versus returning users, events, audiences and realtime users. A custom report takes any GA4 dimensions and metrics, and the Bot can list which ones a property accepts. See the GA4 MCP page.
Search Console: search performance by query, page, country, device, search appearance and date; the queries behind a single page; a side-by-side comparison of two periods; sitemaps; and URL inspection for one page’s indexing and crawl status. See the Search Console docs.
Connect it in a minute
Before you paste it, open the MCP Ads dashboard, go to Connect MCP → API keys and create a key. It is shown once, so copy it then. Make one key per Bot, so you can revoke one without breaking the others. Grok Bot's sign-in flow for custom servers does not complete today, which is why the Bot uses the key header; in Grok chat or Grok Build you can instead add a custom connector at grok.com/connectors with the same URL and sign in with the browser.
Then paste this into Grok Bot (connect GA4 and Search Console in the MCP Ads dashboard first):
Connectors in Grok are account-wide, so once MCP Ads is added every Bot you make can use it. The Bot sees only the platforms and ad accounts you connected in MCP Ads, under the same workspace scope as the web app. MCP Ads is a free trial, then $49/month flat; Grok bills its own usage separately. The full setup is on the Grok Bot page and in the quickstart.
- Add a custom MCP connector:
- - Name: MCP Ads
- - URL: https://mcp-ads.com/mcp-slim
- - Header: Authorization: Bearer <paste your mcp_live_ key>
- Then list my GA4 properties and Search Console sites, and tell me which landing page lost the most organic clicks in the last 28 days.
Checks that fit a weekly Bot
Paid landing pages that underperform. Pages that receive paid traffic but convert below the site average are where ad money leaks after the click. Ask for them limited to paid channels, with a minimum session count so a page with nine visits does not top the list.
Queries on the move. The period comparison shows which queries gained or lost clicks and whether it was impressions (demand or ranking) or CTR (the snippet) that changed. A query with rising impressions and a falling CTR usually needs a better title, not more content.
Pages dropping out. When an important page suddenly loses all its impressions, URL inspection tells you whether Google still has it indexed and when it last crawled it.
| Signal | Source | Likely cause to check |
|---|---|---|
| Clicks down, impressions steady | Search Console | Lower CTR: title, snippet or a new result above you |
| Clicks and impressions down | Search Console | Lost rankings or lower demand |
| Impressions gone for one page | URL inspection | Not indexed, redirected or blocked |
| Paid sessions up, conversions flat | GA4 landing pages | Landing page, form or tracking |
Prompts to give the Bot
Keep scheduled prompts specific about the date window, because the two sources update at different speeds.
- “Every Monday at 8, compare Search Console clicks for the 7 days ending 3 days ago with the 7 days before that. Message me the five queries and five pages with the biggest changes, and whether impressions or CTR drove each.”
- “Every Monday, list GA4 landing pages with at least 100 paid sessions last week that converted below the site average.”
- “Every day at 9, check GA4 sessions by channel for yesterday against the same weekday last week, and tell me only if any channel moved by more than 40%.”
- “Inspect https://example.com/pricing and tell me whether it is indexed and when Google last crawled it.”
- “Which queries bring clicks to our pricing page, and at what average position?”
- “Which campaigns in GA4 (by utm_campaign) produced conversions last month?”
What it will not do without you
Almost everything here is reading. The Search Console writes are submitting a sitemap and removing one; the Bot does them when you ask, and removing a sitemap is worth a second look since it changes how Google discovers your pages. The Bot cannot change GA4 configuration, conversion settings or your site.
The Bot sees only the properties and sites your Google login can see and that you connected in MCP Ads.
Honest limits
Search Console data lags by a couple of days, and the latest days are often incomplete. A Bot comparing “this week” that ends yesterday will report a drop that is not real; end the window a few days back.
GA4 and ad platforms count conversions differently, with different attribution and different timing, so their numbers rarely match. GA4 also misses conversions that never touch your site, such as Meta instant-form leads. Average position in Search Console is an average across impressions, so a page ranking first for one query and fortieth for another can show a middling number that describes neither.
