Query and operate connected Google Search Console properties

by nowork-studio · MIT license · ★ 3,853 on GitHub · updated Sep 24

Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or…

---
name: search-console
description: Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO audits to seo-analysis.
argument-hint: "<property, URL, query, date range, or sitemap>"
---

# Google Search Console

Read `../shared/operating-contract.md`. Use the live connector's instructions and schemas to choose tools for the task. For a full-site SEO audit that also needs crawling and on-page analysis, hand off to `/notfair:seo-analysis` after confirming access.

## Select the exact property

1. Resolve `~~search-console` to the actual Search Console connector and inspect its current tools. Use live property information to identify the intended site.
2. Use the exact verified property form returned by the connector: `sc-domain:example.com` and `https://example.com/` are different properties.
3. Define the search type, complete date window, comparison window, dimensions, and business question. If the platform is missing or unauthorized, direct the user to reconnect the universal NotFair plugin and stop before claiming live data.

## Analyze organic performance

Overview

Read ../shared/operating-contract.md. Use the live connector's instructions and schemas to choose tools for the task. For a full-site SEO audit that also needs crawling and on-page analysis, hand off to /notfair:seo-analysis after confirming access.

Manual install (npx, ZIP)

Claude Codenpx skills add nowork-studio/notfair-plugin --skill search-console -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/nowork-studio/notfair-plugin/tar.gz/5229d2163795 \
  | tar -xz -C ~/.claude/skills --strip-components=2 notfair-plugin-5229d2163795/analytics/search-console

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/bcf85ff87dfa0c118ae6/search-console.zip" -OutFile "$env:TEMP\search-console.zip"; Expand-Archive "$env:TEMP\search-console.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.1 KB
agents/1 file · 241 B
evals/1 file · 1.6 KB

Read the files here

nowork-studio/5229d213 files

SKILL.md3.1 KB

Shared references1SKILL.md reads these from elsewhere in the repo. Not in the ZIP.

operating-contract.mdanalytics/shared/1.3 KB

Get them on GitHub ↗

SKILL.md

Show the full text35 lines

search-console/SKILL.md35 lines · 3.1 KB

PreviewCode

Outline

RawView on GitHub

Google Search Console

Read ../shared/operating-contract.md. Use the live connector's instructions and schemas to choose tools for the task. For a full-site SEO audit that also needs crawling and on-page analysis, hand off to /notfair:seo-analysis after confirming access.

Select the exact property

Resolve ~~search-console to the actual Search Console connector and inspect its current tools. Use live property information to identify the intended site.
Use the exact verified property form returned by the connector: sc-domain:example.com and https://example.com/ are different properties.
Define the search type, complete date window, comparison window, dimensions, and business question. If the platform is missing or unauthorized, direct the user to reconnect the universal NotFair plugin and stop before claiming live data.

Analyze organic performance

Correlate totals, queries, pages, countries, and devices as needed for the question. Choose available reporting capabilities; batch related reads when supported and useful, and use a narrow read for a single property, URL, or sitemap.

Query totals without the query dimension when reconciling property-level clicks and impressions. Anonymized low-volume queries make query rows incomplete by design.
Finalized data normally lags recent dates; label fresh all data as provisional.
Show clicks, impressions, CTR, and average position with their exact dimensions and period. Do not average already-aggregated CTR or position rows naively.
Respect row and historical coverage limits reported by the connector. State when the result is top rows rather than a complete export.
Use URL inspection selectively because its quota is tighter than Search Analytics. Inspection reports index state; it does not request indexing.
Treat ranking movement as evidence, not proof of a specific algorithmic cause.

Lead with the largest material gain or loss, affected queries/pages, evidence-backed hypothesis, confidence, and the next SEO action. Route content rewrites, technical remediation, or full audits to the corresponding SEO skill.

Manage sitemaps safely

Submit or remove a sitemap through a supported capability only after showing the exact verified property and sitemap URL and obtaining approval. Confirm the sitemap belongs to the selected property and is fetchable before submission when possible.

Submission and deletion are reversible counterparts, but deleting a submitted sitemap does not remove its URLs from Google's index. Never describe sitemap submission as an indexing guarantee. Confirm the resulting sitemap state from returned before/after evidence or a fresh list.

1	---
2	name: search-console
3	description: Query and operate connected Google Search Console properties through NotFair MCP. Use for live GSC query or page performance, clicks, impressions, CTR, position, traffic changes, indexing status, URL inspection, sitemap reads or approved sitemap submission/removal, and Search Console MCP setup. Route full-site SEO audits to seo-analysis.
4	argument-hint: "<property, URL, query, date range, or sitemap>"
5	---
6
7	# Google Search Console
8
9	Read `../shared/operating-contract.md`. Use the live connector's instructions and schemas to choose tools for the task. For a full-site SEO audit that also needs crawling and on-page analysis, hand off to `/notfair:seo-analysis` after confirming access.
10
11	## Select the exact property
12
13	1. Resolve `~~search-console` to the actual Search Console connector and inspect its current tools. Use live property information to identify the intended site.
14	2. Use the exact verified property form returned by the connector: `sc-domain:example.com` and `https://example.com/` are different properties.
15	3. Define the search type, complete date window, comparison window, dimensions, and business question. If the platform is missing or unauthorized, direct the user to reconnect the universal NotFair plugin and stop before claiming live data.
16
17	## Analyze organic performance
18
19	Correlate totals, queries, pages, countries, and devices as needed for the question. Choose available reporting capabilities; batch related reads when supported and useful, and use a narrow read for a single property, URL, or sitemap.
20
21	- Query totals without the `query` dimension when reconciling property-level clicks and impressions. Anonymized low-volume queries make query rows incomplete by design.
22	- Finalized data normally lags recent dates; label fresh `all` data as provisional.
23	- Show clicks, impressions, CTR, and average position with their exact dimensions and period. Do not average already-aggregated CTR or position rows naively.
24	- Respect row and historical coverage limits reported by the connector. State when the result is top rows rather than a complete export.
25	- Use URL inspection selectively because its quota is tighter than Search Analytics. Inspection reports index state; it does not request indexing.
26	- Treat ranking movement as evidence, not proof of a specific algorithmic cause.
27
28	Lead with the largest material gain or loss, affected queries/pages, evidence-backed hypothesis, confidence, and the next SEO action. Route content rewrites, technical remediation, or full audits to the corresponding SEO skill.
29
30	## Manage sitemaps safely
31
32	Submit or remove a sitemap through a supported capability only after showing the exact verified property and sitemap URL and obtaining approval. Confirm the sitemap belongs to the selected property and is fetchable before submission when possible.
33
34	Submission and deletion are reversible counterparts, but deleting a submitted sitemap does not remove its URLs from Google's index. Never describe sitemap submission as an indexing guarantee. Confirm the resulting sitemap state from returned before/after evidence or a fresh list.
35