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
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.
Read-only: it cannot change anything in this account.
Who it’s for: SEO & GEO · Agencies · Marketing teams
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
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.
The searches your site showed up for, with the clicks, impressions and average position behind each one, for any finished period Google still keeps.
Which of your pages earn the impressions, which ones people click, and where a page ranks well but nobody opens it.
What each submitted sitemap reports, and why Google has or has not indexed one specific address you ask about.
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.
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 daysMost popular
For a small team running several accounts together.
$19$15.83/mo
billed monthly $190 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor 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 daysFor organizations with custom scale and security needs.
Contact us
Contact salesNot 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.
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.
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.
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.
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.
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.
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.
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.
Google Search Console answers next to the other accounts you connect, in the same chat.
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%).
Connectors
Add your own connectorAdd custom connector
Settings → Customize → Connectors
Security and login
Developer mode
Settings → Security and login → Developer mode → chatgpt.com/plugins
grok.com/connectors
Bring your own MCPNew Connector → Custom
grok.com/connectors → New Connector → Custom
Plugins
Connector → Add MCP connector → RemoteAdd custom
Plugins → Add custom → Connector → Add MCP connector → Remote
$ claude mcp add --transport http heymetra https://mcp.heymetra.com/mcp
Added HTTP MCP server heymetra
> /mcp
✓ heymetra · connected
1[mcp_servers.heymetra]
2url = "https://mcp.heymetra.com/mcp"
$ codex mcp login heymetra
1{
2 "mcpServers": {
3 "heymetra": { "url": "https://mcp.heymetra.com/mcp" }
4 }
5}
1{
2 "mcpServers": {
3 "heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
4 }
5}
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.
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.
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.
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.
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.
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
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.
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.