Agent skill

Google Search Console

by VKirill in VKirill/claude-lane-stack

[RU: Google Search Console API, гугл серч консоль, вебмастер гугл, gsc] GSC (Webmasters) API v1 — OAuth 2.0 + service account, searchanalytics.query (dimensions, filter operators, 25k row cap +…

MITAuto-check passedBackend & APIs

Install Google Search Console

skills CLI
$ npx skills add VKirill/claude-lane-stack --skill google-search-console -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install VKirill/claude-lane-stack google-search-console --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lane-stack/skills/google/google-search-console .claude/skills/google-search-console && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
google-search-console
GitHub stars
122
Token cost
~4.9k tokens
SKILL.md length
2,064 words
Files
10 (incl. references)
Skills in repo
49
Repo updated
First seen
Licence
MIT

At a glance

[RU: Google Search Console API, гугл серч консоль, вебмастер гугл, gsc] GSC (Webmasters) API v1 — OAuth 2.0 + service account, searchanalytics.query (dimensions, filter operators, 25k row cap +…

  • Works in 9 steps: URL Inspection 2000/day/property quota —… → 25,000-row hard cap on Search Analytics… → Data freshness lag ~2-3 days. A request… → …
  • URL-prefix vs Domain property
  • SKILL.md covers Version Requirements (May 2026), Usage, Use this skill when and Do not use this skill when, plus 9 more sections
  • Reaches googleapis.com and searchconsole.googleapis.com

What it does

Google Search Console is an agent skill from VKirill/claude-lane-stack. [RU: Google Search Console API, гугл серч консоль, вебмастер гугл, gsc] GSC (Webmasters) API v1 — OAuth 2.0 + service account, searchanalytics.query (dimensions, filter operators, 25k row cap + startRow pagination), urlInspection.index.inspect (2000/day cap), Sites + Sitemaps CRUD, Indexing API for JobPosting/BroadcastEvent only, ~2-3 day data lag. Use when: GSC, search console, webmasters api, urlInspection, URL-prefix vs Domain property. SKIP: Yandex Webmaster (→yandex-webmaster); GA4 (→google-analytics); Bing…

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/errors.md`, `references/indexing-api.md` and `references/integration.md`).

It sits in Backend & APIs, covering Technical SEO, OAuth and OpenID Connect and Web scraping. It works with Google Search Console, Google Analytics, Google Cloud and Python. The repository describes itself as: Multi-agent AI coding factory for one person — Claude Code PM + Codex/Qwen/Grok/Kimi/AGY writers, durable conveyor, auto-merge to main. The licence is MIT.

When your agent uses it

  • URL-prefix vs Domain property
  • Tasks that involve Technical SEO
  • Tasks that involve OAuth and OpenID Connect

Example prompts

  • “/google-search-console”

Requirements

  • Python 3
  • Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. URL Inspection 2000/day/property quota — a naive crawl of all URLs in one go ends in dailyLimitExceeded. Design with a rate limiter and…
  2. 25,000-row hard cap on Search Analytics responses. Without startRow pagination the long tail is silently lost — the classic "where are my…
  3. Data freshness lag ~2-3 days. A request for "today" returns empty / incomplete. Use dataState: "final" (default) or know what all means.
  4. Domain property vs URL-prefix — sc-domain:example.com aggregates all protocols/subdomains; https://www.example.com/ is only that exact…
  5. Service account cannot self-grant. Its email must be added manually in the GSC UI as a user with Restricted or Full permission. The API…
  6. Indexing API trap: the "speed up indexation" myth → ban. Supported types are JobPosting and BroadcastEvent (in VideoObject) only.
  7. searchAppearance dimension cannot be combined with other dimensions in one request — separate call required.
  8. Billing: GSC endpoints are free at reasonable scale, but exceeding QPM/QPD → 429 with reason quotaExceeded or dailyLimitExceeded. Backoff…
  9. OAuth refresh token expiry: tokens in apps stuck in "Testing" mode expire after 7 days — production requires OAuth verification.

What it can do on your machine

Read from SKILL.md and the folder at commit 45fa19e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • googleapis.com
    • searchconsole.googleapis.com
    • indexing.googleapis.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Search Console loads about 4.9k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 159 tokens; SKILL.md has 2,064 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~159
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from VKirill/claude-lane-stack at commit 45fa19e, republished under its MIT licence (© VKirill). 2,064 words, ~4,920 tokens.

Download SKILL.mdSave it as .claude/skills/google-search-console/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
google-search-console
description
[RU: Google Search Console API, гугл серч консоль, вебмастер гугл, gsc] GSC (Webmasters) API v1 — OAuth 2.0 + service account, searchanalytics.query (dimensions, filter operators, 25k row cap + startRow pagination), urlInspection.index.inspect (2000/day cap), Sites + Sitemaps CRUD, Indexing API for JobPosting/BroadcastEvent only, ~2-3 day data lag. Use when: GSC, search console, webmasters api, urlInspection, URL-prefix vs Domain property. SKIP: Yandex Webmaster (→yandex-webmaster); GA4 (→google-analytics); Bing Webmaster (→bing-webmaster); generic Google auth (→google-cloud-auth); SERP scraping (→xmlstock).
stacks
google-search-console, seo, python, nodejs
tags
seo, google, gsc, search-console, indexing, oauth, sitemaps
source
vechkasov-global-skills
risk
high-stakes
<!-- versions:start -->

Version Requirements (May 2026)

Primary pins:

  • Search Console API: v1 (Webmasters v3 endpoints stable; URL Inspection on searchconsole.googleapis.com/v1)
  • Indexing API: v3 (JobPosting + BroadcastEvent only)
  • Python: 3.14.x
  • Node.js: 24.x (Active LTS)

Source of truth: STACK_VERSIONS.md — verified 2026-08-24

<!-- versions:end -->

Usage

Loaded automatically when the description matches the active task. Read only the section you need, then follow the link to the relevant reference file for full detail.

Use this skill when

  • Pull search analytics data (queries, pages, countries, devices, searchAppearance) for content planning, position audits, or client reports.
  • Programmatically check URL index status via urlInspection.index.inspect (verdict, coverageState, lastCrawlTime, googleCanonical vs userCanonical, mobileUsability, AMP, richResults).
  • Submit / delete / list sitemap.xml for an added property (/webmasters/v3/sites/{siteUrl}/sitemaps).
  • Manage sites list (URL-prefix property vs Domain property sc-domain:example.com) and check permission level.
  • Notify Google about a new or deleted page via Indexing API — only for JobPosting or BroadcastEvent. Regular pages will not work and abuse risks revoke.
  • Build a Python (google-api-python-client + google-auth) or Node.js (googleapis) client with service account and automatic 25k-cap pagination.
  • Schedule a daily ETL of search analytics into PostgreSQL — (query, page, country, device, date) → clicks/impressions/ctr/position.
  • Audit indexation on large sites via URL Inspection while respecting the 2000/day/property quota.

Do not use this skill when

  • You need Yandex Webmaster — different provider, different property/sitemap model; → cascade yandex-webmaster.
  • You need GA4 web analytics (sessions, users, events) — GSC only returns Google search data; → cascade google-analytics.
  • You need Bing Webmaster Tools — separate Microsoft API.
  • You need generic Google OAuth2 / service account patterns; → cascade google-cloud-auth.
  • You need true SERP positions with real locale/device — GSC returns averaged impressions/position for queries already discovered; real SERP snapshot → cascade xmlstock.
  • You expect a "list all my indexed URLs" endpoint — Google does not provide one; sample via Sitemaps + URL Inspection.
  • You want to force-index regular pages with Indexing API — abuse-banned, alternative is sitemap + internal links + UI "Request Indexing".

Purpose

Google Search Console API (Webmasters v3 + URL Inspection v1) is the only official channel for Google organic data: queries, clicks, impressions, CTR, position, index status. This skill covers OAuth 2.0 (user + service account), Search Analytics query with filters and 25k pagination, URL Inspection with daily quota, Sites + Sitemaps CRUD, and — separately — Indexing API (with a strict JobPosting/BroadcastEvent warning).

This skill is high-stakes because:

  1. URL Inspection 2000/day/property quota — a naive crawl of all URLs in one go ends in dailyLimitExceeded. Design with a rate limiter and prioritization (new/changed URLs first).
  2. 25,000-row hard cap on Search Analytics responses. Without startRow pagination the long tail is silently lost — the classic "where are my queries?" bug.
  3. Data freshness lag ~2-3 days. A request for "today" returns empty / incomplete. Use dataState: "final" (default) or know what all means.
  4. Domain property vs URL-prefix — sc-domain:example.com aggregates all protocols/subdomains; https://www.example.com/ is only that exact prefix. Mixing them yields wrong numbers.
  5. Service account cannot self-grant. Its email must be added manually in the GSC UI as a user with Restricted or Full permission. The API offers no bootstrap path.
  6. Indexing API trap: the "speed up indexation" myth → ban. Supported types are JobPosting and BroadcastEvent (in VideoObject) only.
  7. searchAppearance dimension cannot be combined with other dimensions in one request — separate call required.
  8. Billing: GSC endpoints are free at reasonable scale, but exceeding QPM/QPD → 429 with reason quotaExceeded or dailyLimitExceeded. Backoff is mandatory.
  9. OAuth refresh token expiry: tokens in apps stuck in "Testing" mode expire after 7 days — production requires OAuth verification.

The skill owns provider-domain knowledge: endpoints, dimension/filter semantics, freshness lag, quotas, and the billing-free-but-quota-limited model. Pure HTTP plumbing belongs in httpx / nodejs. Deeper auth belongs in google-cloud-auth.

Capabilities

Authentication — OAuth 2.0 (user) + Service Account

Two paths: (a) User OAuth 2.0 Authorization Code flow with refresh_token — for apps where the GSC owner logs in; scopes https://www.googleapis.com/auth/webmasters.readonly (read) or webmasters (full, includes sitemap submit). (b) Service Account JWT — for server-to-server; the service account email must be added as a user in the Search Console UI (Settings → Users and permissions → Add user). Without that, the API returns 403 Forbidden or 404 User does not have sufficient permission for site.

Full reference: references/setup.md

Property types — URL-prefix vs Domain

siteUrl comes in two shapes: URL-prefix (https://www.example.com/ — trailing slash mandatory, exact protocol) and Domain (sc-domain:example.com — aggregates all protocols/subdomains, DNS-verified). Their data does not match: a Domain property sees more impressions. For URL Inspection, siteUrl must match the property exactly.

Full reference: references/setup.md

Search Analytics — searchanalytics.query

POST /webmasters/v3/sites/{siteUrl}/searchAnalytics/query. Body: startDate, endDate (YYYY-MM-DD, Pacific Time), dimensions[] (date, hour, query, page, country, device, searchAppearance), type (web/discover/googleNews/news/image/video, default web), aggregationType (auto/byPage/byProperty/byNewsShowcasePanel), dimensionFilterGroups[] (groupType is always and; operators equals/contains/notEquals/notContains/includingRegex/excludingRegex), rowLimit (1-25000, default 1000), startRow (0+), dataState (final/all/hourly_all). Response: rows[].keys[] + clicks, impressions, ctr (0..1), position. Metadata: responseAggregationType, metadata.first_incomplete_date.

Full reference: references/search-analytics.md

25,000-row cap + startRow pagination

Hard cap = 25,000 rows per response. Full export: loop with rowLimit=25000 and increment startRow += 25000 until a response returns fewer rows than the limit (or zero — empty response means end). There is no next-page-token. Without pagination the tail is silently lost beyond the top 25k by clicks.

Full reference: references/search-analytics.md

Data freshness lag (~2-3 days)

Final data appears with a 2-3 day delay (up to 4 for the long tail). dataState: "final" (default) excludes incomplete days. dataState: "all" includes fresh, recomputable rows (fine for "yesterday" dashboards, bad for historical reports). metadata.first_incomplete_date in the response tells you when data may still change. Hourly data: dataState: "hourly_all" + dimensions: ["hour"].

Full reference: references/search-analytics.md

URL Inspection API — urlInspection.index.inspect

POST https://searchconsole.googleapis.com/v1/urlInspection/index:inspect. Body: inspectionUrl, siteUrl (must match the added property; URL-prefix needs trailing /), languageCode (BCP-47). Response is inspectionResult containing: indexStatusResult (verdict, coverageState, robotsTxtState, indexingState, lastCrawlTime, pageFetchState, googleCanonical, userCanonical, sitemap[], referringUrls[], crawledAs), ampResult, mobileUsabilityResult, richResultsResult. Quota: 2000/day/property and 600 QPM/property.

Full reference: references/url-inspection.md

Sites + Sitemaps CRUD

Sites: GET /webmasters/v3/sites (list), GET /sites/{siteUrl} (get), PUT /sites/{siteUrl} (add — attaches site to current user, not verification), DELETE /sites/{siteUrl}. Fields: siteUrl, permissionLevel (siteFullUser/siteOwner/siteRestrictedUser/siteUnverifiedUser). Sitemaps: GET /sites/{siteUrl}/sitemaps (list), GET /sites/{siteUrl}/sitemaps/{feedpath} (get; feedpath URL-encoded), PUT /sites/.../sitemaps/{feedpath} (submit), DELETE (unsubmit). Fields: path, lastSubmitted, lastDownloaded, isPending, isSitemapsIndex, type (sitemap/rssFeed/atomFeed/urlList/patternSitemap/notSitemap), warnings, errors, contents[].

Full reference: references/sites-and-sitemaps.md

Indexing API — JobPosting and BroadcastEvent ONLY

POST https://indexing.googleapis.com/v3/urlNotifications:publish. Body: { "url": "...", "type": "URL_UPDATED" | "URL_DELETED" }. WARNING: Google explicitly states it "can only be used to crawl pages with either JobPosting or BroadcastEvent (embedded in VideoObject)". Using it for regular pages is abuse → revoke and possible manual action. Batch up to 100 sub-requests via multipart.

WARNING: Service account must have Owner role in the GSC property — Full user is insufficient for the Indexing API. Re-share property with SA email as Owner if you get 403.

Full reference: references/indexing-api.md

Quotas — short-window and daily

Search Analytics: 1200 QPM per-site, 1200 QPM per-user, 40,000 QPM + 30,000,000 QPD per-project. URL Inspection: 600 QPM per-site, 2000 QPD per-site, 15,000 QPM + 10,000,000 QPD per-project. Other resources (Sites/Sitemaps): 20 QPS + 200 QPM per-user, 100,000,000 QPD per-project. Exceeding → 429 with reason quotaExceeded / userRateLimitExceeded / dailyLimitExceeded. Exponential backoff is required.

  • Indexing API: 200 calls/day/project (default, raiseable via quota form); 600 QPM/project.

Full reference: references/rate-limits.md

Errors — 400/401/403/404/429/500

400 badRequest — invalid dimensions/dates. 401 authError — expired token, refresh. 403 forbidden — no permission on property or service account not added. 404 — siteUrl unknown to user. 429 — quota, backoff. 500/503 — transient, retry with jitter. Reason codes are in error.errors[].reason.

Full reference: references/errors.md

End-to-end API workflows

Auth bootstrap → Search Analytics query lifecycle → URL Inspection → Sitemaps → Indexing API caveat → Quota management → Daily ETL into PostgreSQL.

Full reference: references/workflow.md

Production clients — Python + Node.js

Drop-in templates: Python with google-api-python-client (service account from JSON), Python with raw httpx + JWT assertion for fine control, Node.js with googleapis. Pagination helper for 25k cap. URL Inspection batch worker with per-property quota tracker. PostgreSQL schema for daily snapshots.

Full reference: references/integration.md

Show full SKILL.md (815 more words)Show less

Quick reference

ResourceEndpoint (base + path)Method
Search Analytics querywebmasters/v3/sites/{siteUrl}/searchAnalytics/queryPOST
Sites listwebmasters/v3/sitesGET
Sites getwebmasters/v3/sites/{siteUrl}GET
Sites addwebmasters/v3/sites/{siteUrl}PUT
Sites deletewebmasters/v3/sites/{siteUrl}DELETE
Sitemaps listwebmasters/v3/sites/{siteUrl}/sitemapsGET
Sitemap getwebmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}GET
Sitemap submitwebmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}PUT
Sitemap deletewebmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}DELETE
URL Inspectionsearchconsole/v1/urlInspection/index:inspectPOST
Indexing APIindexing/v3/urlNotifications:publishPOST
DimensionNotes
dateYYYY-MM-DD (PT)
hourISO-8601, only with dataState hourly_all
querysearch query
pagelanding URL
countryISO 3-letter, lower-case (usa, rus)
deviceDESKTOP/MOBILE/TABLET
searchAppearancefeatures: AMP, RICH_RESULT, VIDEO, ... — cannot combine with other dimensions in one request
Filter operatorBehavior
equals (default)exact match
notEqualsexact exclusion
containssubstring
notContainswithout substring
includingRegexRE2 include
excludingRegexRE2 exclude
Status / ReasonMeaningAction
400 badRequestinvalid dimensions/datescheck formatting
401 authErrortoken expiredrefresh OAuth token
403 forbiddenservice account not added to propertyadd via UI
404siteUrl unknown to userverify, add, or use sc-domain:
429 quotaExceededshort-windowexp backoff
429 userRateLimitExceededper-user QPMbackoff + lower concurrency
429 dailyLimitExceededper-daywait until PT midnight
500 / 503transientretry with jitter

Common mistakes

  • Requesting 100k+ queries without pagination — you get the top 25k and lose the tail. Fix: loop startRow += 25000 until response is empty.
  • Mixing Domain property with URL-prefix in siteUrl — data will not match; URL Inspection returns 404. Fix: copy the string from GSC UI verbatim; Domain needs the sc-domain: prefix.
  • Service account not added in GSC → 403/404. Fix: a human user must add xxx@yyy.iam.gserviceaccount.com as Restricted or Full user in the UI. The API never self-bootstraps.
  • Using Indexing API for regular pages — abuse, may lead to revoke / manual action. Fix: use sitemap + link profile; Indexing API only for JobPosting / BroadcastEvent.
  • Expecting "today" or "yesterday" data in Search Analytics — 2-3 day lag. Fix: either dataState: "all" for fresh incomplete data, or accept the delay.
  • Combining searchAppearance with other dimensions — spec requires a dedicated call. Fix: first request — just searchAppearance to discover values; second — filter by a specific feature.
  • URL Inspection in a loop over 100k URLs with no quota tracking → dailyLimitExceeded within minutes. Fix: 2000/day/property; prioritize new/changed; persist results for N days.
  • Forgetting to URL-encode feedpath in Sitemaps endpoints → 400. Fix: encodeURIComponent("https://example.com/sitemap.xml").
  • Passing country as "US" — it is lower-case 3-letter ISO: "usa". Fix: validate filter format.
  • Relying on permissionLevel: siteUnverifiedUser — that user gets empty API responses. Fix: ensure siteOwner / siteFullUser / siteRestrictedUser.
  • Querying discover or googleNews for a brand-new property — may be empty if Google has not classified the source. Fix: confirm baseline with type: web first.
  • Ignoring when responseAggregationType differs from requested — Google may return byPage instead of auto. Fix: read the response field for analytics correctness.

Red flags — STOP and verify

  • Service account returns 403 on the first request — check the UI: is the SA email added as a property user? Without it the API returns nothing, not even sites.list.
  • Numbers in the API do not match the GSC UI — almost always different date ranges (UI ~ dataState all, API default final), different property types (Domain vs URL-prefix), or missing pagination.
  • dailyLimitExceeded on URL Inspection well before the day ends — no per-property limiter. Stop the worker; recompute around 2000/property.
  • Someone asks you to "speed up indexation via Indexing API" for regular pages — red flag, path to a manual action. Refuse and explain.
  • An OAuth refresh token suddenly stops working — app likely stuck in Testing mode (7-day expiry) or the user revoked access in their Google account → require re-consent.

Behavioral traits

  • Before any bulk URL Inspection — measure quota: N URLs × 2000/day/property.
  • For any "pull all data for period" request — always write the pagination loop, never a single 25k-row call.
  • For service accounts — first confirm the SA email is added in the GSC UI.
  • Distinguish final vs all dataState and explicitly call out the 2-3 day lag.
  • Never propose Indexing API for regular pages — JobPosting / BroadcastEvent only.
  • For Domain property — always write the sc-domain: prefix; never pass https://example.com/ as Domain.

Important constraints

  • HTTP plumbing — use httpx (Python) or node:fetch / googleapis (Node) — never reimplement.
  • OAuth refresh token persistence — Redis/Postgres, never hard-coded.
  • webmasters.readonly scope for read-only; webmasters only when sitemap submit / sites add is genuinely needed.
  • Cache URL Inspection results for 24-72 hours in the database; never re-inspect the same URL more than once a day.
  • country filters — lowercase ISO-3 (usa, not US).
  • device filters — uppercase (MOBILE, DESKTOP, TABLET).
  • Sitemap feedpath — URL-encoded.
  • All lastSubmitted / lastDownloaded timestamps — RFC 3339.
  • yandex-webmaster — Yandex Webmaster API (separate provider, similar task for RU sites).
  • google-analytics — Google Analytics 4 Data API (web analytics, not GSC).
  • xmlstock — true SERP snapshots via parsing (position with geo/device).
  • google-cloud-auth — generic OAuth / service account patterns for all Google APIs.
  • httpx, nodejs — HTTP transport for custom clients.
  • postgresql, redis — persistence for snapshots, refresh tokens, URL Inspection cache.

API Reference

SectionReference
Auth + property setupreferences/setup.md
Search Analytics deep divereferences/search-analytics.md
URL Inspectionreferences/url-inspection.md
Sites + Sitemapsreferences/sites-and-sitemaps.md
Indexing API caveatreferences/indexing-api.md
Errorsreferences/errors.md
Rate limitsreferences/rate-limits.md
End-to-end workflowsreferences/workflow.md
Python + Node clients, DB schemareferences/integration.md

© VKirill, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in plugins/lane-stack/skills/google/google-search-console of VKirill/claude-lane-stack.

  • SKILL.md
  • references/errors.md
  • references/indexing-api.md
  • references/integration.md
  • references/rate-limits.md
  • references/search-analytics.md
  • references/setup.md
  • references/sites-and-sitemaps.md
  • references/url-inspection.md
  • references/workflow.md

Open the folder on GitHubat commit 45fa19e

Compare with similar skills

Google Search Console next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Search Console compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Google Search Console this skillVKirill/claude-lane-stack122—~4.9kAutomated safety check: PassMIT
Google Workspaceericrisco/rsc-harness174—~3.2kAutomated safety check: PassMIT
Ga4 Auth Setupjeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: PassMIT
Search Console ReportLeoYeAI/openclaw-master-skills2.2k—~4.6kAutomated safety check: PassMIT
Google SEO APIsAgriciDaniel/claude-seo19k1 repos~4.2kAutomated safety check: PassMIT
Blog GoogleAgriciDaniel/claude-blog2.3k1 repos~3.3kAutomated safety check: NotesMIT

Similar skills

  • Google Workspace

    ericrisco/rsc-harness

    A skill your agent uses when server-side code reads or writes Gmail, Drive, Calendar, or Sheets with a GCP service account and no human in the OAuth loop: picking the auth mode (app-owned vs…

    174 GitHub stars~3.2k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed
  • Ga4 Auth Setup

    jeremylongshore/tons-of-skills-marketplace

    Configure auth for the GA4 Data API — OAuth user credentials for interactive use, or a service account for automation / CI.

    2.8k GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Search Console Report

    LeoYeAI/openclaw-master-skills

    Generate comprehensive SEO analysis reports from Google Search Console data with PDF export.

    2.2k GitHub stars~4.6k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed
  • Google SEO APIs

    AgriciDaniel/claude-seo

    Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.

    19k GitHub starsUsed in 1 repo~4.2k tokens
    Marketing & SEOAuto-check passed
  • Blog Google

    AgriciDaniel/claude-blog

    Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…

    2.3k GitHub starsUsed in 1 repo~3.3k tokens
    Marketing & SEOAuto-check: notes
  • Junta Leiloeiros

    sickn33/agentic-awesome-skills

    Coleta e consulta dados de leiloeiros oficiais de todas as 27 Juntas Comerciais do Brasil.

    47k GitHub starsUsed in 2 repos~1.6k tokens
    Backend & APIsAuto-check passed

More from VKirill/claude-lane-stack

All 49 skills in this repo
  • UI UX Pro Max

    VKirill/claude-lane-stack

    Lane-stack design + brand intelligence (vendored ui-ux-pro-max).

    122 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • App Architect

    VKirill/claude-lane-stack

    Owner-facing architect for a new app or service. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Browser QA

    VKirill/claude-lane-stack

    Live browser QA + Playwright-compatible replay. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Copy Project Life

    VKirill/claude-lane-stack

    Карта файлов копирайта в .agents/copy/: шаблоны, статусы, цепочка audience→headlines→ux.

    122 GitHub stars~534 tokensUpdated yesterday
    Auto-check passed
  • Copy Research

    VKirill/claude-lane-stack

    Dispatch copy-lead helpers: Tavily, Codex luna/terra, grok/X, OpenCode DeepSeek, Cursor Grok 4.6 medium-fast.

    122 GitHub stars~827 tokensUpdated yesterday
    Auto-check passed
  • Docs Maintain

    VKirill/claude-lane-stack

    Keep living docs/ honest after code changes. An agent skill from VKirill/claude-lane-stack.

    122 GitHub stars~459 tokensUpdated yesterday
    Auto-check passed

Questions about Google Search Console

What does Google Search Console do?

[RU: Google Search Console API, гугл серч консоль, вебмастер гугл, gsc] GSC (Webmasters) API v1 — OAuth 2.0 + service account, searchanalytics.query (dimensions, filter operators, 25k row cap +…. Google Search Console is an agent skill from VKirill/claude-lane-stack.inspect (2000/day cap), Sites + Sitemaps CRUD, Indexing API for JobPosting/BroadcastEvent only, ~2-3 day data lag.

When should I use Google Search Console?

Google Search Console fits situations like: URL-prefix vs Domain property; tasks that involve Technical SEO; tasks that involve OAuth and OpenID Connect.

How do I install Google Search Console in Claude Code?

Run `npx skills add VKirill/claude-lane-stack --skill google-search-console -a claude-code`. Or copy the skill folder (plugins/lane-stack/skills/google/google-search-console in VKirill/claude-lane-stack) into .claude/skills/google-search-console in your project. Claude Code loads it when a task matches its description.

How do I install Google Search Console in Codex?

Run `npx skills add VKirill/claude-lane-stack --skill google-search-console -a codex`. Or copy the skill folder (plugins/lane-stack/skills/google/google-search-console in VKirill/claude-lane-stack) into .agents/skills/google-search-console in your project. Codex loads it when a task matches its description.

Can I use Google Search Console in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VKirill/claude-lane-stack --skill google-search-console -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-search-console, .gemini/skills/google-search-console, .github/skills/google-search-console and .opencode/skills/google-search-console in your project.

What does Google Search Console need to run?

SKILL.md names no scripts, command-line tools or credentials: Google Search Console is instructions for the agent only. Our summary lists: Python 3; Node.js.

Does Google Search Console access the network?

SKILL.md names 3 domains. In commands or code: googleapis.com, searchconsole.googleapis.com and indexing.googleapis.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Google Search Console safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Google Search Console use?

Google Search Console is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Search Console use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 14k tokens, read only when the agent opens those files.

What are the alternatives to Google Search Console?

Skills that share tags, products or a category with Google Search Console: Google Workspace (ericrisco/rsc-harness, 174 stars), Ga4 Auth Setup (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Search Console Report (LeoYeAI/openclaw-master-skills, 2.2k stars) and Google SEO APIs (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Search Console?

VKirill (a GitHub user) maintains it in VKirill/claude-lane-stack, which has 122 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: VKirill/claude-lane-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.