gsc-search-analytics

gsc-search-analytics is a skill for Claude Code from antohins/seo-tools-mcp. It costs 75 tokens per session (1,045 once invoked), scanned A, original, MIT.

A guide for analysing Google search performance with Search Console, Google's service for showing how a site appears in search results. It covers clicks, impressions, rankings, search queries, pages, URL indexing, and sitemaps.

In plain words
What is it for?
Use it to investigate Google search traffic, falling rankings, competing pages targeting the same query, missed search opportunities, indexing status, and sitemap data.
Why use it?
It helps interpret search data without mistaking delayed or incomplete numbers for a real traffic drop. It also explains limits such as the 16-month reporting window and missing low-volume queries.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the gsc plugin — 1 skill shipped together

Good fit Use it to investigate Google search traffic, falling rankings, competing pages targeting the same query, missed search opportunities, indexing status, and sitemap data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/antohins/seo-tools-mcp/gsc-search-analytics
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add antohins/seo-tools-mcp --skill gsc-search-analytics
Clone the repo
git clone --depth 1 https://github.com/antohins/seo-tools-mcp

Made for: Claude Code.

Or install gsc, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gsc-search-analytics

README.md
[![agentmods](https://agentmods.dev/badge/skills/antohins/seo-tools-mcp/gsc-search-analytics/github.svg)](https://agentmods.dev/skills/antohins/seo-tools-mcp/gsc-search-analytics)
Your own site
<a href="https://agentmods.dev/skills/antohins/seo-tools-mcp/gsc-search-analytics"><img src="https://agentmods.dev/badge/skills/antohins/seo-tools-mcp/gsc-search-analytics/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gsc-search-analytics

Your own site · 80×15
<a href="https://agentmods.dev/skills/antohins/seo-tools-mcp/gsc-search-analytics"><img src="https://agentmods.dev/badge/skills/antohins/seo-tools-mcp/gsc-search-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,045 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.01045
Opus 5 $0.00037 $0.00522
Sonnet 5 $0.00015 $0.00209
Haiku 4.5 $0.00007 $0.00104

Measured 11d ago against content hash 507eac2acbe6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

gsc-search-analytics scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/gsc/skills/gsc-search-analytics/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Search Console: как читать данные, не обманываясь

Порядок

  1. gsc_auth_status. Нет токена — gsc_oauth_start → пользователь открывает ссылку → gsc_oauth_finish. Сервис-аккаунт работает, но его почту надо вручную добавить в каждое свойство; OAuth видит все свойства аккаунта сразу.
  2. gsc_list_sites — какие свойства доступны. Свойства бывают двух видов: sc-domain:example.com (домен целиком) и https://example.com/ (URL-префикс, со слэшем на конце). Это разные свойства с разными данными.
  3. Дальше gsc_query с нужными dimensions.

Три вещи, из-за которых цифры «не сходятся»

Свежесть. Данные отстают на 2–3 дня. endDate: сегодня вернёт провал в конце периода, который выглядит как обвал трафика. Для отчётов брать endDate = сегодня минус 3 дня. dataState: 'all' подмешивает свежие неполные данные — годится для «что происходит прямо сейчас», но не для сравнения периодов.

Окно. Глубина — 16 месяцев. Запрос за более ранний период вернёт пустоту, а не ошибку.

Суммы не сходятся по построению. Клики по разрезу query не дадут общую сумму: запросы с малым числом показов Google не отдаёт (anonymized queries). Поэтому «сумма по запросам» и «всего кликов по сайту» — разные числа, и это не баг. Общий итог брать отдельным вызовом без dimensions: ['query'].

Разрезы

  • dimensions: ['query'] — что спрашивают.
  • ['page'] — какие страницы собирают.
  • ['query','page'] — связка; на ней ловится каннибализация: один запрос, несколько страниц.
  • ['date'] — динамика.
  • ['country'], ['device'] — сегменты.

position — усреднённая позиция показа, а не позиция в моменте. Сравнивать её со снятой через xmlstock_serp/xmlriver_serp позицией напрямую нельзя: там слепок выдачи по одному региону и устройству, здесь среднее по всем.

ctr возвращается долей (0..1), не процентом.

Типовые задачи

Просадка трафика. ['date'] за 90 дней → найти точку слома. Затем тот же период в разрезе ['query'] и ['page'] до и после: упало по всем запросам (алгоритм, сезон) или по конкретной группе (потеря конкретных позиций).

Read the full file on GitHub · 71 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 71 lines · 75 tokens per session scan A 507eac2acbe6

Subscribe to this mod's changes

gsc-search-analytics is a skill published in the GitHub repository antohins/seo-tools-mcp (3 stars, last pushed 7d ago), licensed MIT. It adds 75 tokens to every session and 1,045 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.