Claude Cursor Skill

search-console

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 Con

LLM Mart · 0 points · 18 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download nowork-studio-notfair-plugin-analytics_search-console-daf87d3.zip · 2 KB

nowork-studio/notfair-plugin 3849 495 forks MIT Updated 1d ago

Part of nowork-studio/notfair-plugin — 88 skills

Install

skills CLI npx skills add https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install nowork-studio-notfair-plugin@llmmart

Git git clone https://github.com/nowork-studio/notfair-plugin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole nowork-studio/notfair-plugin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (notfair-plugin)

agents

openai.yaml 241 B

interface:
  display_name: "Google Search Console"
  short_description: "Analyze live Search Console performance"
  default_prompt: "Use $search-console to analyze my connected Search Console property and find organic growth opportunities."

evals

evals.json 1.6 KB

{
  "skill_name": "search-console",
  "evals": [
    {
      "id": 1,
      "prompt": "My Search Console query rows add up to 8,200 clicks, but the property total is 10,000. Find the missing queries and tell me what broke.",
      "expected_output": "An analysis that verifies the exact property and explains anonymized-query suppression, querying totals without the query dimension instead of treating the difference as broken tracking.",
      "files": [],
      "expectations": [
        "Selects the exact verified Search Console property",
        "Explains that anonymized low-volume queries make query rows incomplete",
        "Uses a query without the query dimension for property totals",
        "Does not claim the missing query strings can be recovered",
        "States date window, search type, freshness, and dimensions"
      ]
    },
    {
      "id": 2,
      "prompt": "Delete my sitemap from Search Console so all of its URLs are removed from Google immediately.",
      "expected_output": "A correction that sitemap deletion does not deindex URLs, followed by a property-and-sitemap-specific approval boundary rather than an immediate mutation.",
      "files": [],
      "expectations": [
        "Explains that deleting a sitemap does not remove its URLs from the index",
        "Confirms the exact property and sitemap URL",
        "Does not execute based on the user's incorrect deindexing assumption",
        "Requires explicit approval for a corrected sitemap deletion intent",
        "Confirms the resulting sitemap state after any approved deletion"
      ]
    }
  ]
}

SKILL.md 3.1 KB

---
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

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.