SEO
Nexus-JPF/note-companion
Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence.
Query and operate connected Google Search Console properties through NotFair MCP.
Install Search Console
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nowork-studio/notfair-plugin search-console --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/analytics/search-console .claude/skills/search-console && rm -rf skills-srcUse ~/.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/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .claude/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-consoleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nowork-studio/notfair-plugin search-console --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/analytics/search-console .agents/skills/search-console && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .agents/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nowork-studio/notfair-plugin search-console --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/analytics/search-console .cursor/skills/search-console && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .cursor/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nowork-studio/notfair-plugin.git --path analytics/search-console--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nowork-studio/notfair-plugin search-console --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/analytics/search-console .gemini/skills/search-console && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .gemini/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nowork-studio/notfair-plugin search-consoleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/analytics/search-console .github/skills/search-console && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .github/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nowork-studio/notfair-plugin --skill search-console -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nowork-studio/notfair-plugin search-console --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/analytics/search-console .opencode/skills/search-console && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "search-console" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/analytics/search-console into .opencode/skills/search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
search-console- GitHub stars
- 3.9k
- Token cost
- ~784 tokens
- SKILL.md length
- 376 words
- Files
- 3
- Skills in repo
- 48
- Repo updated
- First seen
- Licence
- MIT
At a glance
Query and operate connected Google Search Console properties through NotFair MCP.
- Works in 3 steps: Resolve ~~search-console to the actual… → Use the exact verified property form… → Define the search type, complete date…
- Page performance
- SKILL.md covers Select the exact property, Analyze organic performance and Manage sitemaps safely
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Search Console is an agent skill from nowork-studio/notfair-plugin. 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.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `agents/openai.yaml` and `evals/evals.json`).
It sits in Marketing & SEO, covering SEO audit and Technical SEO. It works with Google Search Console and Model Context Protocol. The repository describes itself as: Open-source SEO, GEO, and marketing skills for AI agents. The licence is MIT.
When your agent uses it
- Page performance
- Traffic changes
- Indexing status
- Approved sitemap submission/removal
Example prompts
- “/search-console”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Resolve ~~search-console to the actual Search Console connector and inspect its current tools. Use live property information to identify…
- 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…
What it can do on your machine
Read from SKILL.md and the folder at commit 1a53d4e. 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
No URLs in SKILL.md.
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
Search Console loads about 784 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 376 words of instructions outside code blocks.
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 nowork-studio/notfair-plugin at commit 1a53d4e, republished under its MIT licence (© nowork-studio). 376 words, ~784 tokens.
Download SKILL.mdSave it as
.claude/skills/search-console/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- 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
- Resolve
~~search-consoleto 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.comandhttps://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
querydimension 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
alldata 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.
Show full SKILL.md (111 more words)Show less
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.
© nowork-studio, 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 2 other files in analytics/search-console of nowork-studio/notfair-plugin.
- SKILL.md
- agents/openai.yaml
- evals/evals.json
Open the folder on GitHubat commit 1a53d4e
Compare with similar skills
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Search Console this skillnowork-studio/notfair-plugin | 3.9k | — | ~784 | Automated safety check: Pass | MIT | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 18k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 146 | — | ~2.8k | Automated safety check: Pass | None | |
| SEO AuditRyze-AI-Adgent/open-seo-mcp-skills | 4.5k | — | ~663 | Automated safety check: Pass | MIT | |
| Geo Meta Tags Auditthedaviddias/Front-End-Checklist | 74k | — | ~763 | Automated safety check: Pass | MIT |
Similar skills
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.
SEO Coach
akseolabs-seo/seo-coach
Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.
SEO Audit
Ryze-AI-Adgent/open-seo-mcp-skills
Full SEO audit of a site from its real Search Console + GA4 data — indexation health, CTR anomalies, decaying pages, striking-distance keywords, quick wins.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
SEO Checker
hanzili/hanzi-browse
Audit web pages for SEO issues in a real browser. An agent skill from hanzili/hanzi-browse.
More from nowork-studio/notfair-plugin
All 48 skills in this repoBroken Link Checker
nowork-studio/notfair-plugin
Crawls a website with a bundled Python script to find broken internal and outbound links, then reports them by status code with the pages they appear on.
Keyword Research
nowork-studio/notfair-plugin
Finds, scores and groups keywords from a seed term or niche for SEO and AI search content strategies, with intent labels, difficulty estimates and topic clusters.
Meta Tags Optimizer
nowork-studio/notfair-plugin
Writes and improves title tags, meta descriptions, Open Graph and Twitter card tags for click-through, with character counts and A/B test variants.
SEO Audit with Search Console
nowork-studio/notfair-plugin
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
Single-Page SEO Audit
nowork-studio/notfair-plugin
Audits one URL for content quality, E-E-A-T, search intent, on-page and technical signals, and produces a scored report with fixes.
Search Console Content Planner
nowork-studio/notfair-plugin
Turns Google Search Console data into a dated content calendar by finding striking-distance queries and unanswered intent, ready to hand to a writer.
Related
Categories
Questions about Search Console
What does Search Console do?
Query and operate connected Google Search Console properties through NotFair MCP. Search Console is an agent skill from nowork-studio/notfair-plugin. Query and operate connected Google Search Console properties through NotFair MCP.
When should I use Search Console?
Search Console fits situations like: page performance; traffic changes; indexing status; approved sitemap submission/removal.
How do I install Search Console in Claude Code?
Run `npx skills add nowork-studio/notfair-plugin --skill search-console -a claude-code`. Or copy the skill folder (analytics/search-console in nowork-studio/notfair-plugin) into .claude/skills/search-console in your project. Claude Code loads it when a task matches its description.
How do I install Search Console in Codex?
Run `npx skills add nowork-studio/notfair-plugin --skill search-console -a codex`. Or copy the skill folder (analytics/search-console in nowork-studio/notfair-plugin) into .agents/skills/search-console in your project. Codex loads it when a task matches its description.
Can I use 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 nowork-studio/notfair-plugin --skill 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/search-console, .gemini/skills/search-console, .github/skills/search-console and .opencode/skills/search-console in your project.
What does Search Console need to run?
SKILL.md names no scripts, command-line tools or credentials: Search Console is instructions for the agent only.
Does Search Console access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 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 Search Console use?
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 Search Console use?
About 784 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Search Console?
Skills that share tags, products or a category with Search Console: SEO (Nexus-JPF/note-companion, 870 stars), Google SEO APIs (AgriciDaniel/claude-seo, 18k stars), SEO Coach (akseolabs-seo/seo-coach, 146 stars) and SEO Audit (Ryze-AI-Adgent/open-seo-mcp-skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Search Console?
nowork-studio (a GitHub organization) maintains it in nowork-studio/notfair-plugin, which has 3,908 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 1, 2026.
Source: nowork-studio/notfair-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.