AgentAlley
Submit

Google Search Console

Query and operate connected Google Search Console properties through NotFair MCP.

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/search-console.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit nowork-studio/notfair-plugin/analytics/search-console#main ~/.claude/skills/search-console

For one project only, change the path to .claude/skills/search-console.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Google Search Console

Show the full text35 lines
search-console/SKILL.md35 lines · 3.1 KB
Outline
RawView on GitHub
namedescriptionargument-hint
search-consoleQuery 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.<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

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---
2name: search-console
3description: 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.
4argument-hint: "<property, URL, query, date range, or sitemap>"
5---
6 
7# Google Search Console
8 
9Read `../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 
131. Resolve `~~search-console` to the actual Search Console connector and inspect its current tools. Use live property information to identify the intended site.
142. Use the exact verified property form returned by the connector: `sc-domain:example.com` and `https://example.com/` are different properties.
153. 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 
19Correlate 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 
28Lead 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 
32Submit 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 
34Submission 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 

Discussion

Alternatives

Also in SEO & keywordsSee all 364 in Marketing →
Backlink Profile AnalysisBacklink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.Marketing · MIT/setup-cmsConnect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report.Marketing · MITCore Web Vitals optimizationOptimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".Marketing · MITClaude opus as SEO auditorAct as Claude Opus, an expert SEO auditor, analyzing and optimizing websites for improved search engine performance.Marketing · CC0-1.0

Browse more free Claude skills or everything in Marketing.