cogny cliseofirst 15 calls free

google search console from your shell.

Pull Search Analytics rows, inspect a URL’s indexing status, list and submit sitemaps, and group performance by query, page, or country — straight from Bash over the Google Search Console MCP. No Search Console UI, no service account, no API client.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Google Search Console toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Google_Search_Console__tool_get_search_analytics --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Today you open the Search Console UI, set a date range, click into the Performance report, and export a CSV one filter at a time. The CLI returns the exact query/page rows you ask for as JSON you can sort, diff, or feed to an agent. Connect Google Search Console once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Google Search Console tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Google Search Console tools.

Tool names as the Google Search Console MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Google_Search_Console__tool_get_search_analytics

Query clicks, impressions, CTR, and position grouped by dimension.

cogny tools call mcp__Google_Search_Console__tool_get_search_analytics \ --input '{"site_url":"sc-domain:example.com","start_date":"2026-06-01","end_date":"2026-06-14","dimensions":["query"],"row_limit":3}'

example response

{
  "rows": [
    {
      "keys": [
        "running shoes"
      ],
      "clicks": 842,
      "impressions": 19400,
      "ctr": 0.0434,
      "position": 4.2
    },
    {
      "keys": [
        "trail running shoes"
      ],
      "clicks": 311,
      "impressions": 8120,
      "ctr": 0.0383,
      "position": 6.1
    },
    {
      "keys": [
        "best running shoes 2026"
      ],
      "clicks": 188,
      "impressions": 5440,
      "ctr": 0.0346,
      "position": 7.8
    }
  ]
}

mcp__Google_Search_Console__tool_inspect_url
Check a single URL’s indexing status and last crawl.
- cogny tools call mcp__Google_Search_Console__tool_inspect_url \ --input '{"site_url":"https://example.com/","inspection_url":"https://example.com/blog/new-post"}'
example response
```
{
  "indexStatusResult": {
    "verdict": "PASS",
    "coverageState": "Submitted and indexed",
    "lastCrawlTime": "2026-06-12T08:14:00Z",
    "robotsTxtState": "ALLOWED"
  }
}
```
mcp__Google_Search_Console__tool_submit_sitemap
Submit (or resubmit) a sitemap to nudge a recrawl.
- cogny tools call mcp__Google_Search_Console__tool_submit_sitemap \ --input '{"site_url":"https://example.com/","feedpath":"https://example.com/sitemap.xml"}'
example response
```
{
  "status": "success",
  "feedpath": "https://example.com/sitemap.xml"
}
```

03tools list

the rest of the surface.

A sample of the other Google Search Console tools. Run cogny tools list --json for every tool and its input schema.

mcp__Google_Search_Console__tool_list_properties
mcp__Google_Search_Console__tool_get_sitemaps
mcp__Google_Search_Console__tool_delete_sitemap

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Google Search Console CLI?: No — it is the Cogny CLI calling the Search Console MCP over the cogny-mcp-proxy. You connect Google once in Cogny (OAuth handled for you), then call every tool from Bash with no service account or google-api client to manage.
Can I request indexing of a single URL?: No — and neither can any API. tool_inspect_url is read-only, and Google only exposes per-URL "Request Indexing" in the GSC UI. The supported way to nudge a recrawl is tool_submit_sitemap with a sitemap that contains the URLs.
How far back does the data go?: Search Analytics covers up to 16 months of history, typically with a 2–3 day delay. Pass start_date / end_date as YYYY-MM-DD and group by query, page, country, device, or searchAppearance.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

google search console, then a verdict.

Start free All CLIs