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
npx skills add AceDataCloud/Skills --skill google-search-console -a claude-codeWhat 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.comover the last 28 days. - Is
https://example.com/pageindexed? 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-code2Manually: put the files in place
~/.claude/skills/google-search-console/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/google-search-console/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill google-search-console -a codex2Manually: put the files in place
.agents/skills/google-search-console/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill google-search-console -a cursor2Manually: put the files in place
.cursor/skills/google-search-console/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install AceDataCloud/Skills skills/google-search-console2Manually: put the files in place
.github/skills/google-search-console/SKILL.md1Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill google-search-console -a gemini-cli2Platform CLI
gemini skills install https://github.com/AceDataCloud/Skills --path skills/google-search-consoleManually: put the files in place
.devin/skills/google-search-console/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add AceDataCloud/Skills --skill google-search-console -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.