Skip to content
All connectors
Google Search Console MCP server · Analytics

Ask your AI which searches bring people to your site

Google Search Console already knows which searches bring people to your site. This connector lets you ask it in a sentence, from your own AI assistant, instead of filtering the Performance report by hand: which queries grew, which pages get seen and skipped, and whether last month really dropped.

Connect Google Search Console to Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity, with one connection, on the subscription you already pay for.

Your accounts
  • Search Console
  • PostHog
  • WooCommerce
  • Google Analytics 4Soon
HeyMetra
Your AI assistant
Claude
Which pages lost the most clicks this week compared with last week?
Read Search Console with HeyMetra
/guides/returns lost the most, 340 clicks, after slipping from position 3 to 6 for “return policy template”. It is the page to update first.
Reply to Claude…

Read-only: it cannot change anything in this account.

Who it’s for: SEO & GEO · Agencies · Marketing teams

What you can ask it

Without HeyMetra

Claude
Which pages get search clicks but lose visitors before they sign up?
I can’t see your Google Search Console and PostHog. Download clicks by page and the sign-up funnel and paste it here, and I’ll work it out.

With HeyMetra

Claude
Which pages get search clicks but lose visitors before they sign up?
Read with HeyMetra
/blog/pricing-guide takes 2,900 clicks and converts 0.4%, a fifth of the site average.
Make this a PDF and email it to the team every Monday at 9:00.
  • report.pdfMade by Claude
  • Every Monday at 9:00Claude scheduled task
  • Sent to team@yourcompany.comFrom your own address, with HeyMetra email

Without HeyMetra

ChatGPT
Which pages lost the most search clicks since last month, and did their sign-ups fall too?
I don’t have access to Google Search Console and PostHog. If you export both months of clicks by page and sign-ups by page and share it, I can compare.

With HeyMetra

ChatGPT
Which pages lost the most search clicks since last month, and did their sign-ups fall too?
Read with HeyMetra
/features/reports lost 38% of clicks and 41% of sign-ups; the drop started on the 12th.
Make this a PDF and email it to the team every Monday at 9:00.
  • report.pdfMade by ChatGPT
  • Every Monday at 9:00ChatGPT scheduled task
  • Sent to team@yourcompany.comFrom your own address, with HeyMetra email

Without HeyMetra

Grok
Which queries have high impressions, average position 5 to 15, and a click rate under 1%?
I’m not connected to Google Search Console. Upload the queries report as CSV and I’ll try.

With HeyMetra

Grok
Which queries have high impressions, average position 5 to 15, and a click rate under 1%?
Read with HeyMetra
23 queries; the biggest is “shopify sales report” with 14,000 impressions at position 8.
Email this to the team.
  • Sent to team@yourcompany.comFrom your own address, with HeyMetra email

Without HeyMetra

Perplexity
Did search clicks rise in the weeks our newsletter went out?
I can’t reach your Google Search Console and Zoho Marketing Automation data. Share the send dates and weekly clicks and I’ll look into it.

With HeyMetra

Perplexity
Did search clicks rise in the weeks our newsletter went out?
Read with HeyMetra
Yes: in newsletter weeks clicks were 14% higher on average, mostly on the pages the newsletter linked.
Email this to the team.
  • Sent to team@yourcompany.comFrom your own address, with HeyMetra email

What Google Search Console is

What it reads

Google Search Console reports how your site performs in Google’s organic search results: the queries you rank for, your clicks and impressions, and indexing health. It’s the ground truth for SEO.

Queries

The searches your site showed up for, with the clicks, impressions and average position behind each one, for any finished period Google still keeps.

Pages

Which of your pages earn the impressions, which ones people click, and where a page ranks well but nobody opens it.

Sitemaps and single URLs

What each submitted sitemap reports, and why Google has or has not indexed one specific address you ask about.

What it costs to read Search Console

Pricing

Search Console counts as one connector on your plan, and each property you connect counts as one account, however many searches you ask about. Plans differ in how many accounts you connect and how many people share them, never in which connectors you may use.

  • Starter

    For one person starting with their main account.

    $6$5/mo

    billed monthly $60 billed annually, save 17%

    Try free for 7 daysTry free for 7 days
    • 2 connectors at once
    • 2 accounts across them
    • 1 seat
    • Unlimited conversations
  • Superior

    For teams and agencies with many accounts to connect.

    $49$40.83/mo

    billed monthly $490 billed annually, save 17%

    Try free for 7 daysTry free for 7 days
    • 50 connectors at once
    • Unlimited number of accounts
    • 3 seats
    • Unlimited conversations
  • Enterprise

    For organizations with custom scale and security needs.

    • Custom connectors
    • Custom accounts
    • Custom seats
    • Unlimited conversations

    Contact us

    Contact sales

Frequently asked

Is there an official Google Search Console MCP server?

Not from Google. There are open-source servers you run yourself, such as mcp-server-gsc and gsc-mcp, which need a Google Cloud service account and a config entry in each assistant. HeyMetra is hosted: you sign in with Google once, and the same connection works in Claude, ChatGPT and the other assistants we support, beside your store or CRM accounts.

Does it show AI Overviews or AI Mode separately?

No. Search Console counts appearances in AI Overviews and AI Mode together with ordinary results, and its generative AI report is only in Google's own screen for now. What you can ask about is the long-tail, question-style searches those answers show up on most.

Can it change anything in Search Console?

No. The permission Google shows you on sign-in is read-only, so nothing here can submit a sitemap, remove a URL or change a setting. It reads the reports and nothing else.

Why do my query figures add up to less than the site's total?

Google leaves rare searches out of the query report on purpose, to protect the people who typed them. The named queries are the part of your traffic Google is willing to show word by word. For the site's total, ask for it by page or for the whole site instead.

How far back can I ask?

About sixteen months, which is what Google keeps. An older period is refused by name rather than answered as months with no search traffic, so a quiet stretch in an answer is a real one.

Why is yesterday missing?

Google finishes its search figures about two days late. Only finished days are read, so a question that ends today is answered up to the last complete day, and the answer says which days it covered.

I have a domain property and a URL-prefix property. Which one should I connect?

The one whose figures you already report on. A domain property counts every subdomain and both http and https; a URL-prefix property counts only the address it names. They are different counts, so connect one and do not add them together.

Works well with Google Search Console

Works well with

Search Console tells you who found the site. What they did after the click lives somewhere else: in the events PostHog records, or in the store they bought from. Reading the two together is how a ranking turns into a reason.

Ask it alongside your other accounts.

With your other accounts

Google Search Console answers next to the other accounts you connect, in the same chat.

  • Google Search Console
  • PostHog
  • Email
Perplexity
Which pages get search clicks but lose visitors before they sign up? Email me the list.
Sources: Search Console, PostHog via HeyMetra
Three pages take over 1,500 search clicks a month and turn fewer than 1% into sign-ups. The biggest is your pricing guide.
Sent with HeyMetra email
Email · you@yourcompany.com

Many search clicks, few sign-ups: /blog/pricing-guide 2,900 clicks (0.4%), /features/reports 1,840 (0.7%), /integrations 1,610 (0.9%).

Ask a follow-up

Add HeyMetra to your AI assistant

Connectors

Add your own connectorAdd custom connector

Add custom connector https://mcp.heymetra.com/mcp Add

Settings → Customize → Connectors

Step-by-step setup in Claude →
Setting it up 5 steps. You sign in on the provider, so no password reaches us.

Five short steps, all of them in Google's own screens. The only one that trips people up is the first: Search Console gives access per property, so the Google account you sign in with has to be the one that already sees the site there.

  1. 1

    Check which Google account owns the property

    Open search.google.com/search-console and look at the property list. Connect with the account you see it in. Not a personal account that happens to be signed in, and not the agency account unless the property is listed there too.

    Search Console permissions are per property, not per domain. Being an owner of example.com says nothing about shop.example.com.

  2. 2

    Choose Google Search Console in HeyMetra

    On the Connections screen. There is nothing to copy and no key to generate: this connector uses Google's own sign-in.

  3. 3

    Sign in on Google's screen and grant read access

    Your password stays with Google, and you can revoke HeyMetra's access at any time from your Google account. The permission asked for is read-only, so nothing here submits a sitemap, removes a URL or changes a setting.

    If Google offers an account picker, the account you pick is the one whose properties HeyMetra can see. Picking the wrong one shows an empty list on the next step rather than an error.

  4. 4

    Pick the property

    HeyMetra lists what that Google account can read. A domain property (sc-domain:example.com) covers every subdomain and both http and https; a URL-prefix property covers exactly the address it names. Pick the one whose figures you recognise.

  5. 5

    Add HeyMetra to the assistant you use

    Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity. You paste one address and sign in once. Search Console then answers there, from the live property.

Then add HeyMetra where you ask

When it does not work 5 common problems and how to fix each one.

Most of what looks wrong here is Google being careful rather than the connection failing. A missing property, a site listed twice, a two-day gap at the end of a chart and a query list that does not add up all have a plain cause, and each one is below.

The property list is empty after signing in.
That Google account is not verified for any property. Being able to see a site in Analytics, or owning the domain, is not the same permission.
In Search Console, have an existing owner add this account under Settings → Users and permissions. Full or Restricted both work; read access is all HeyMetra asks for.
The site is in the list twice, with different numbers in each.
A domain property and a URL-prefix property for the same site are two different properties and count different traffic. The domain one includes subdomains and the other protocol.
Connect the one whose figures match what you report on. They are not two views of one number and must never be added together.
Asking about the last two days returns nothing, or a drop.
Google finishes processing search data about two days behind, and HeyMetra asks only for finished data rather than serving a partial day as a fall.
Ask for a period ending three days ago. Every answer says which days it actually covers.
The queries add up to far less traffic than the site's own total.
Google leaves rare searches out of query reports entirely, to protect the privacy of whoever typed them. On one measured site the same month showed 339 impressions by query against 1,244 by page.
Read the query list as the named part of the traffic, not as all of it. The site total is the figure to compare months by.
A question about backlinks, Core Web Vitals or AI Overviews is refused.
Search Console shows those in its own interface and publishes no API for them. Nothing can read them on your behalf.
Those stay in Search Console itself for now. HeyMetra refuses them rather than answering from something adjacent and calling it the same thing.

Find the pages people see in search but skip

Add the property to HeyMetra once, then ask which pages get seen and which get skipped.

Or read the same steps on GitHub: zeisoft/google-search-console-mcp.