Skip to content
Skills Library
Marketing & content · Analysis

google-search-console

/google-search-console

Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance — clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings.

Licence
MIT
Last repository change
09.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance — clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings.

Original author description

Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance — clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings.

How it works

  1. 1. Ground yourself first
  2. 2. Reading Search Console data
  3. 3. Reference real data, don't fabricate
Original SKILL.md headings · 61 lines, 449 words
SKILL.md preview
---
name: google-search-console
description: Analyze Google Search Console (organic search) data through Windsor.ai. Use when the user asks about their site's organic Google Search performance — clicks, impressions, CTR, or average position, broken down by search query, page/URL, country, device, search appearance, or date. Do not use for paid search / Google Ads cost, other webmaster tools (e.g. Bing), web analytics like GA4, or changing Search Console settings.
---

# Google Search Console via Windsor.ai

Windsor.ai pulls live **read-only** Google Search Console data through the Search
Analytics API. The connector id is `searchconsole`. Pass `searchconsole` as the connector on every tool call; the Windsor.ai server
serves all connectors, so it is never implied.

This connector is **read-only** organic-search analytics. It reports Search
Console metrics and dimensions; it does **not** cover paid search or ad cost
(that lives in the Google Ads connector), and it does **not** submit sitemaps or
change any Search Console setting — there are no write actions. If asked to
submit a sitemap or change settings, say that's out of scope here.

Golden rules:

- **Never guess field, site, or option names** — get them from `get_fields`,
  `get_connectors`, and `get_options`. Call those first.
- Read-only connector; there are no live write actions to run.
- Report what the user asked for, concisely.

## 1. Ground yourself first

Call `get_connectors` to see which Search Console sites/properties are connected
(each has an id and usually a name). If none is connected, help the user connect:
`get_connector_authorization_url` (or `get_connector_connect_info` for the auth
type and steps) and give them the setup link — don't describe manual dashboard
navigation. If several sites are connected and the request is ambiguous, ask
which one.

## 2. Reading Search Console data

1. Call `get_fields` for `searchconsole` to get valid field ids. Search Console
   splits into **dimensions** (e.g. query, page/URL, country, device, search
   appearance, date) and **metrics** (clicks, impressions, CTR, average
   position). Use the exact ids returned, not these examples.
2. Call `get_data` with the `fields` you need (dimensions + metrics), the target
   site/`account`(s), and a date range — `date_from`/`date_to` (`"2026-02-01"`)
   or a `date_preset` like `last_7d`, `last_28d`, `last_30d`, `this_month`.
   Add `filters` for conditions (e.g. branded vs non-branded queries, a country).

Common requests → recipe:

- **Search performance overview / trend:** `date` + clicks/impressions/CTR/
  position over a preset range.
- **Top queries or pages:** the query or page dimension + clicks/impressions,
  then rank in your answer.
- **By country/device:** that dimension + the metrics.
- Position is an **average position** (lower is better); CTR is clicks ÷
  impressions. Compute derived figures from returned fields.

Watch out: Search Console data typically lags by **~2–3 days** (very recent days
may be missing or partial) and history is limited to about **16 months**. It is
**organic** search only — there is no cost/spend data. If a field the user wants
isn't in `get_fields`, say so rather than substituting a different metric.

## 3. Reference real data, don't fabricate

On an error (unknown field/connector/site), call the relevant discovery tool and
retry with correct ids, or report the specific error. Never invent click counts,
positions, query strings, or site ids.

Versions

RepositoryScoreLicence
This page · windsor-ai/claude-windsor-ai-plugin100MIT
vkirill/claude-lane-stack100MIT
vibe-md/vibe.md100MIT
superdesigndev/treg100Apache-2.0
AceDataCloud/Skills100Apache-2.0
unempyd/revenueos100MIT

Database snapshot: 13.11.2026 · package version ed6ebc0b172a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100free-google-search-console-gsc-bing
    Free Google Search Console (GSC) for SEO: your own Search Console search analytics, keywords, search rankings, clicks, impressions, URL inspection and Bing Webmaster Tools. Connect Free Google Search Console (GSC) & Bing Webmaster Tools by CrakSEO when the user asks about google…
  • 90google-search-console-country-and-device-performance
    Breaks organic search performance down by country and device, from live Google Search Console data in your Coupler.io workspace — clicks, impressions, click-through rate and average position by market and by phone/desktop/tablet, against the site's own average. Use for "how does…
  • 90search-console
    Free Google Search Console (GSC) for SEO - your own Search Console search analytics, keywords, search rankings, clicks, impressions, URL inspection and Bing Webmaster Tools. Use when the user asks: Which Google search queries bring clicks to my website? Why is my page not…
  • 95gcloud-search-console
    Query Google Search Console (Webmasters) performance data from the CLI using gcloud-issued credentials. Use when the user wants to pull clicks, impressions, CTR, or position data for their sites — e.g. "top queries for example.com", "pages ranking for X", "search performance last week".
  • 100search-console
    ACTIVATE when the user wants to PULL/REPORT Google Search Console data — search rankings, clicks, impressions, CTR, index coverage, Core Web Vitals, sitemap status. Trigger phrases: 'search console', 'GSC', 'search performance', 'clicks and impressions', 'CTR analysis', 'index…
  • 90web-analytics-insights
    Report, rank, compare, and trend web analytics performance across Google Analytics 4 and Google Search Console through Windsor.ai. Use when the user asks about sessions, users, engagement rate, conversions, and revenue from GA4; clicks, impressions, CTR, and average position…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.