Skip to main content
skill CX Codex

google-search-console · acedatacloud — Claude Code skill: what it does

google-search-console pulls Search Console data through API v1: queries, pages, CTR, average position, sitemaps and index status for a single URL.

Apache-2.0 188 installs ★ 17 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add AceDataCloud/Skills --skill google-search-console -a claude-code
Open on GitHub

What google-search-console does

The skill works as a thin client for Search Console API v1. Requests go out through curl and get trimmed with jq. Auth is a bearer token kept in GOOGLE_SEARCH_CONSOLE_TOKEN, scoped webmasters.readonly, so nothing gets written back. No token means 401 and a reinstall of the connection.

On offer: verified properties with their permission levels, search analytics grouped by query, page, country or date (clicks, impressions, CTR, average position), submitted sitemaps with errors and warnings, plus an index check for one URL. Begin with the sites call. The siteUrl it returns is what every later request needs, URL-encoded as https%3A%2F%2Fexample.com%2F or sc-domain%3Aexample.com. A 403 means the token's account has no claim on that property.

Search Console numbers trail reality by about 2–3 days, so keep endDate a couple of days back when you want stable figures. CTR arrives as a fraction between 0 and 1, and position is an average rank where lower is better.

What it helps with

  • pull the top queries by clicks for the last 28 days
  • spot pages whose average position dropped
  • check whether a URL made it into the index
  • read errors and warnings from submitted sitemaps
  • list verified properties with their permission levels

Example prompts for the agent

  • Show the top 10 queries by clicks for sc-domain:example.com over the last 28 days.
  • Is https://example.com/page indexed? Check it in Search Console.
  • Which sitemaps are submitted, and do any of them report errors?

How to install google-search-console

1Skills CLI (Vercel)

npx skills add AceDataCloud/Skills --skill google-search-console -a claude-code

2Manually: put the files in place

~/.claude/skills/google-search-console/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/google-search-console/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about google-search-console

How do I install google-search-console in Claude Code?

Run npx skills add AceDataCloud/Skills --skill google-search-console -a claude-code. The skill lands at ~/.claude/skills/google-search-console/SKILL.md.

What does google-search-console do?

It queries Search Console API v1 with curl and jq: sites, search analytics by query, page, country or date, sitemaps, and URL inspection results.

Why do the most recent dates come back empty?

Search Console data lags roughly 2–3 days, so the latest dates can be partial. Set endDate a couple of days back for numbers that hold still.

Source text

SKILL.md · Apache-2.0
---
name: google-search-console
description: Query Google Search Console via the Search Console API v1 — search analytics (clicks / impressions / CTR / position), sites, sitemaps and URL inspection. Use when the user mentions Search Console, organic search performance, top queries / pages, indexing status, or sitemaps.
when_to_use: |
  Trigger when the user wants Search Console data — top queries or
  pages by clicks / impressions / CTR / position, performance by date
  or country, the list of verified sites, sitemaps, or URL inspection.
  Read-only (`webmasters.readonly`). List sites first to get the
  property URL.
connections: [google/search-console]
allowed_tools: [Bash]
license: Apache-2.0
metadata:
  author: acedatacloud
  version: "1.0"
---

Query **Google Search Console** via `curl + jq`. The user's OAuth bearer token is
in `$GOOGLE_SEARCH_CONSOLE_TOKEN` (scope `webmasters.readonly`); every call needs
`Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN`. Base:
`https://searchconsole.googleapis.com`.

Failures are `{"error":{"code","message","status"}}` — show verbatim. `401` =
re-install. `403` = the token's account doesn't own/verify that site.

```bash
AUTH="Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN"
# Verified sites (siteUrl is the property — URL-encode it in later calls)
curl -sS -H "$AUTH" "https://searchconsole.googleapis.com/webmasters/v3/sites" \
  | jq '.siteEntry[] | {siteUrl, permissionLevel}'
```

## Search analytics

```bash
# Top queries by clicks for the last 28 days. siteUrl must be URL-encoded
# (https%3A%2F%2Fexample.com%2F  or  sc-domain%3Aexample.com).
SITE="https%3A%2F%2Fexample.com%2F"
curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" -d '{
  "startDate":"2026-05-24","endDate":"2026-06-21",
  "dimensions":["query"],"rowLimit":10
}' "https://searchconsole.googleapis.com/webmasters/v3/sites/$SITE/searchAnalytics/query" \
  | jq '.rows[] | {query: .keys[0], clicks, impressions, ctr, position}'
```

Swap `dimensions` for `["page"]`, `["country"]`, `["date"]`, or combine
`["query","page"]`. Add `"dimensionFilterGroups"` to filter by page/country.

## Sitemaps & URL inspection

```bash
# Submitted sitemaps
curl -sS -H "$AUTH" "https://searchconsole.googleapis.com/webmasters/v3/sites/$SITE/sitemaps" \
  | jq '.sitemap[] | {path, lastDownloaded, errors, warnings}'

# Is a URL indexed?
curl -sS -X POST -H "$AUTH" -H "Content-Type: application/json" \
  -d '{"inspectionUrl":"https://example.com/page","siteUrl":"https://example.com/"}' \
  "https://searchconsole.googleapis.com/v1/urlInspection/index:inspect" \
  | jq '.inspectionResult.indexStatusResult | {verdict, coverageState, lastCrawlTime}'
```

## Gotchas

- **Two property shapes:** URL-prefix (`https://example.com/`) vs Domain
  (`sc-domain:example.com`). Use exactly the `siteUrl` from the sites list,
  URL-encoded.
- Data lags ~2–3 days; the most recent dates may be partial/empty — set `endDate`
  a couple days back for stable numbers.
- `ctr` is 0–1, `position` is average rank (lower = better).

© acedatacloud · Apache-2.0 · AceDataCloud/Skills

Similar skills

All skills for SEO and GEO →

google-search-console by other authors comes first.

google-search-console kostja94 The google-search-console skill for Claude Code is a compatibility pointer for Search Console indexing and performance analysis. It points to the Open Analytics successor. CX Codex +1 2,100installs QuerySail: Google Search Console querysail QuerySail: Google Search Console is an MCP server for Claude Code that reads Search Console metrics, compares date ranges, checks URLs and shows sitemap status. It is read-only. CX Codex +1 Google Search Console get-mcp-ads Read-only MCP server with 20 inspection tools for Google Search Console. It tracks organic performance and spots keyword cannibalization across URLs. CX Codex +1 pp-google-search-console user pp-google-search-console — a skill that drives Google Search Console from the terminal: period compare, quick wins, keyword cannibalization and traffic-drop triage. CX Codex +1 527installs Google Search Console MCP scalably-io A read-only MCP server for Google Search Console: properties, Search Analytics, sitemaps, URL inspection. Useful when your agent should read search data inside the project. CX Codex +1 ★ 1repo stars search-console-mcp sudomichael Connects Google Search Console to an MCP client for read-only search data and SEO analysis in chat. Use it to inspect traffic, indexing, and search queries. CX Codex +1 ★ 8repo stars gsc mikusnuz gsc — an MCP server for Google Search Console API and Indexing API: search analytics, index status checks, sitemap submission, and structured data notifications. CX Codex +1 ★ 8repo stars

From the same set67

The whole set →

Project sponsors

Companies that keep this analytics open