Find SEO opportunities in your Search Console data

These five tools look for traffic you could have but do not yet: queries just off page one, pages whose CTR trails their position, and demand you show up for without a page that targets it.

The tools

Every tool that reads a property also takes site_url, so one connection covers every property your Google account can see. Ask for list_properties to get the exact strings: sc-domain:example.com and https://example.com/ are different properties with different data.

quick_wins

Returns queries at positions 4–15 with enough impressions to matter, sorted by the clicks reaching position 3 would add. On a small site the default threshold of 100 impressions can return nothing; ask for a lower one.

Ask: “What am I almost ranking for on sc-domain:example.com?”

Parameter	Default	Note
`days`	28
`min_impressions`	100
`max_position`	15

ctr_opportunities

Pages with plenty of impressions and a click-through rate well under what their average position usually earns. These are the title and meta description rewrites worth doing first.

Ask: “Which pages get seen but clicked far less than their position should earn?”

Parameter	Default	Note
`days`	28
`min_impressions`	500

content_gaps

Queries that already show your site but rank worse than position 20. Google is matching you to the demand without a page that targets it.

Ask: “What do I get impressions for but rank beyond page two?”

Parameter	Default	Note
`days`	90
`min_impressions`	50
`min_position`	20

content_recommendations

Runs quick wins, content gaps and the cannibalisation check together and returns a prioritised list: pages to update, content to create, pages to consolidate.

Ask: “Give me the ten content changes worth making first.”

Parameter	Default	Note
`days`	28
`max_recommendations`	10

topic_cluster_performance

Adds up clicks, impressions, CTR and position for every page whose URL matches a path pattern, and lists the cluster's top five pages and queries.

Ask: “How is everything under /blog/seo/ doing as a group?”

Parameter	Default	Note
`path_pattern`	required	e.g. `/blog/seo`
`days`	28

A real answer

From this hosted instance, run against the author's own site. Shown as it came back; rows are trimmed only where the caption says so.

Asked: “What is k-o.pro almost ranking for? It's a small site, so go down to 5 impressions and position 20.”
quick_wins on the hosted instance, 13 October 2026

{
  "_meta": {
    "source": "Google Search Console API (live data)",
    "tool": "quick_wins",
    "parameters": {
      "days": 90,
      "min_impressions": 5,
      "max_position": 20,
      "site_url": "sc-domain:k-o.pro"
    },
    "note": "All numbers in this response come directly from the Google Search Console API. They are exact values, not estimates. Base your analysis only on this data. Do not invent or assume additional context."
  },
  "data": [
    {
      "query": "canonical check",
      "clicks": 0,
      "impressions": 22,
      "ctr": 0,
      "position": 15.6,
      "opportunity": 2
    }
  ]
}

One query qualifies on a site this size: "canonical check", 22 impressions at an average position of 15.6. The parameters Claude actually passed are in _meta, so the lowered thresholds are on the record rather than implied.

Connect it

Add https://gsc.k-o.pro/mcp to claude.ai or Claude Desktop or to Claude Code, sign in with Google, and ask any of the questions above.

About this page

Built and run by Oleksii Khoroshun, an SEO with nine years in the field who builds tools at k-o.pro. It is a fork of Suganthan's GSC MCP by Suganthan Mohanadasan: the analysis logic and most of the tool set are his design, and this fork adds multi-property access, the remote server and per-user sign-in.

Version 3.8.0 · page updated 13 October 2026 · changelog