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.
Connect to Google Search Console API to pull real organic search data — traffic trends, ranking positions, impressions, CTR, top queries, and page-level performance.
Install Search Console Connect
$ npx skills add LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-marketing-skills search-console-connect --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/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/search-console-connect .claude/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .claude/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connectType 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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-marketing-skills search-console-connect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/search-console-connect .agents/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .agents/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-marketing-skills search-console-connect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/search-console-connect .cursor/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .cursor/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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/LeoYeAI/openclaw-marketing-skills.git --path skills/search-console-connect--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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-marketing-skills search-console-connect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/search-console-connect .gemini/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .gemini/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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 LeoYeAI/openclaw-marketing-skills search-console-connectInstalls 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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/search-console-connect .github/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .github/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-marketing-skills search-console-connect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/search-console-connect .opencode/skills/search-console-connect && 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-connect" agent skill from https://github.com/LeoYeAI/openclaw-marketing-skills/tree/main/skills/search-console-connect into .opencode/skills/search-console-connect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "search-console-connect", 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-connect- GitHub stars
- 1k
- Used in
- 1 other repo
- Token cost
- ~1.6k tokens
- SKILL.md length
- 564 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Connect to Google Search Console API to pull real organic search data — traffic trends, ranking positions, impressions, CTR, top queries, and page-level performance.
- Works in 4 steps: Google Cloud Console → IAM → Service… → Download JSON key → In Search Console → Settings → Users and… → …
- The user wants to audit SEO with real data
- SKILL.md covers Setup (First Time), Data Pull, Analysis Framework and Output Format, plus 3 more sections
- Calls gcloud and python; reaches googleapis.com
What it does
Search Console Connect is an agent skill from LeoYeAI/openclaw-marketing-skills. Connect to Google Search Console API to pull real organic search data — traffic trends, ranking positions, impressions, CTR, top queries, and page-level performance. Use when the user wants to audit SEO with real data, diagnose traffic drops, find quick-win keywords, or understand what's actually driving (or losing) organic traffic. Enhances seo-audit and ai-seo skills with real GSC data. Triggers on: 'why did my traffic drop', 'what keywords am I ranking for', 'SEO audit with real data', 'Search Console data'…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering SEO audit and AI search optimization. It works with Google Search Console and Google Cloud. The repository describes itself as: 33 battle-tested marketing skills for OpenClaw agents — Powered by MyClaw.ai.
When your agent uses it
- The user wants to audit SEO with real data
- Diagnose traffic drops
- Find quick-win keywords
- Understand whats actually driving (or losing) organic traffic
Example prompts
- “why did my traffic drop”
- “what keywords am I ranking for”
- “SEO audit with real data”
- “/search-console-connect”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Google Cloud Console → IAM → Service Accounts → Create
- Download JSON key
- In Search Console → Settings → Users and Permissions → Add user (service account email, Owner)
- Save key path to .agents/search-console-credentials.json
What it can do on your machine
Read from SKILL.md and the folder at commit ed6b63f. 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
Shell commands in SKILL.md call:
gcloudpython
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
googleapis.com
Also links to:
moz.com
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 Connect loads about 1.6k tokens when it runs. Until then it costs about 149 tokens; SKILL.md has 564 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 564 words (~1,589 tokens).
“You are an SEO analyst with direct access to the user's Google Search Console data. You pull real traffic and ranking data to replace guesswork with evidence — then tell the user exactly what to fix and in what order.”
- name
- search-console-connect
Files
Just SKILL.md in skills/search-console-connect of LeoYeAI/openclaw-marketing-skills.
Open the folder on GitHubat commit ed6b63f
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in LeoYeAI/openclaw-marketing-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Search Console Connect 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 Connect this skillLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~1.6k | Automated safety check: Pass | Custom licence | |
| SEO AuditRyze-AI-Adgent/open-seo-mcp-skills | 4.7k | — | ~663 | Automated safety check: Pass | MIT | |
| Global SEO Growthminhnv0807/ai-business-skills | 609 | — | ~5k | Automated safety check: Pass | MIT | |
| SEONexus-JPF/note-companion | 870 | — | ~2.2k | Automated safety check: Pass | MIT | |
| 32 SEO Growthminhnv0807/ai-business-skills | 609 | — | ~5k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT |
Similar skills
Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
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.
32 SEO Growth
minhnv0807/ai-business-skills
Khi nguoi dung muon tang traffic tu SEO, AI SEO, GEO/AEO, Google, ChatGPT, Perplexity, schema, structured data, llms.txt, programmatic SEO, local SEO, directory submissions, Product Hunt…
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.
GEO-First SEO Audit Tool
zubair-trabzada/geo-seo-claude
Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.
More from LeoYeAI/openclaw-marketing-skills
All 13 skills in this repoAd Creative
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
Email Sequence
LeoYeAI/openclaw-marketing-skills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Paywall Upgrade Cro
LeoYeAI/openclaw-marketing-skills
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Google Ads Connect
LeoYeAI/openclaw-marketing-skills
Connect to Google Ads API to pull real account data — campaign performance, keyword health, wasted spend, search terms, impression share.
Meta Ads Connect
LeoYeAI/openclaw-marketing-skills
Connect to Meta Marketing API to pull real Facebook and Instagram ad data — campaign performance, creative fatigue, audience saturation, ROAS by ad set, frequency analysis, and Learning Phase status.
Related
Works with
Categories
Questions about Search Console Connect
What does Search Console Connect do?
Connect to Google Search Console API to pull real organic search data — traffic trends, ranking positions, impressions, CTR, top queries, and page-level performance. Search Console Connect is an agent skill from LeoYeAI/openclaw-marketing-skills. Connect to Google Search Console API to pull real organic search data — traffic trends, ranking positions, impressions, CTR, top queries, and page-level performance.
When should I use Search Console Connect?
Search Console Connect fits situations like: the user wants to audit SEO with real data; diagnose traffic drops; find quick-win keywords; understand whats actually driving (or losing) organic traffic.
How do I install Search Console Connect in Claude Code?
Run `npx skills add LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a claude-code`. Or copy the skill folder (skills/search-console-connect in LeoYeAI/openclaw-marketing-skills) into .claude/skills/search-console-connect in your project. Claude Code loads it when a task matches its description.
How do I install Search Console Connect in Codex?
Run `npx skills add LeoYeAI/openclaw-marketing-skills --skill search-console-connect -a codex`. Or copy the skill folder (skills/search-console-connect in LeoYeAI/openclaw-marketing-skills) into .agents/skills/search-console-connect in your project. Codex loads it when a task matches its description.
Can I use Search Console Connect 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 LeoYeAI/openclaw-marketing-skills --skill search-console-connect -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-connect, .gemini/skills/search-console-connect, .github/skills/search-console-connect and .opencode/skills/search-console-connect in your project.
What does Search Console Connect need to run?
Going by SKILL.md and its folder, Search Console Connect needs the command-line tools its instructions call (gcloud and python). Our summary lists: Python 3.
Does Search Console Connect access the network?
SKILL.md names 2 domains. In commands or code: googleapis.com; the agent is likely to contact it when it follows the instructions. As links in the text: moz.com. This is read from the text; nothing was executed.
Is Search Console Connect 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 Connect use?
Search Console Connect has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Search Console Connect use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Connect?
Skills that share tags, products or a category with Search Console Connect: SEO Audit (Ryze-AI-Adgent/open-seo-mcp-skills, 4.7k stars), Global SEO Growth (minhnv0807/ai-business-skills, 609 stars), SEO (Nexus-JPF/note-companion, 870 stars) and 32 SEO Growth (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Search Console Connect?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-marketing-skills, which has 1,042 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on June 2, 2026.
Source: LeoYeAI/openclaw-marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.