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.
Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends.
Install Google Search Console
$ npx skills add superdesigndev/treg --skill google-search-console -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install superdesigndev/treg google-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/superdesigndev/treg.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/google-search-console .claude/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .claude/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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/superdesigndev/treg/tree/main/.agents/skills/google-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 superdesigndev/treg --skill google-search-console -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install superdesigndev/treg google-search-console --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/google-search-console .agents/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .agents/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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 superdesigndev/treg --skill google-search-console -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install superdesigndev/treg google-search-console --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/google-search-console .cursor/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .cursor/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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/superdesigndev/treg.git --path .agents/skills/google-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 superdesigndev/treg --skill google-search-console -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install superdesigndev/treg google-search-console --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/google-search-console .gemini/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .gemini/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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 superdesigndev/treg google-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 superdesigndev/treg --skill google-search-console -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/google-search-console .github/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .github/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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 superdesigndev/treg --skill google-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 superdesigndev/treg google-search-console --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/google-search-console .opencode/skills/google-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 "google-search-console" agent skill from https://github.com/superdesigndev/treg/tree/main/.agents/skills/google-search-console into .opencode/skills/google-search-console/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-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
google-search-console- GitHub stars
- 4.9k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 582 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends.
- Works in 4 steps: Recent days are incomplete — do not… → Dimension sums do NOT equal site totals → searchAppearance cannot be combined with… → …
- Answering questions about organic search clicks
- SKILL.md covers 1. Recent days are incomplete…, 2. Dimension sums do NOT equal…, 3. searchAppearance cannot be… and 4. Two API surfaces on one host, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Google Search Console is an agent skill from superdesigndev/treg. Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends. Use whenever answering questions about organic search clicks, impressions, rankings, or index status.
Its SKILL.md is about 1.2k 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. It works with Google Search Console and Google Analytics. The repository describes itself as: OpenRouter for agent tools. Join community here: https://discord.gg/6mQYYfFMAn.
When your agent uses it
- Answering questions about organic search clicks
Example prompts
- “Use the google-search-console skill to trap to avoid when querying Google Search Console through treg — cases where the API returns a confident…”
- “/google-search-console”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Recent days are incomplete — do not report them as a trend
- Dimension sums do NOT equal site totals
- searchAppearance cannot be combined with any other dimension
- Two API surfaces on one host
What it can do on your machine
Read from SKILL.md and the folder at commit 424ab11. 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
Links to these hosts (documentation or services it may open):
developers.google.comsupport.google.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
Google Search Console loads about 1.2k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 582 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 582 words (~1,157 tokens).
“You already know the Search Console API. This file is only the things that return a plausible wrong answer with no error. Verified live on 2026-07-22 against sc-domain:example.com, with each trap confirmed by watching three independent agents.”
- name
- google-search-console
Files
Just SKILL.md in .agents/skills/google-search-console of superdesigndev/treg.
Open the folder on GitHubat commit 424ab11
Compare with similar skills
Google 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 |
|---|---|---|---|---|---|---|
| Google Search Console this skillsuperdesigndev/treg | 4.9k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Blog GoogleAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.3k | Automated safety check: Notes | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 146 | — | ~2.8k | Automated safety check: Pass | None | |
| SEO Googleseranking/seo-skills | 160 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Global SEO Growthminhnv0807/ai-business-skills | 610 | — | ~5k | Automated safety check: Pass | MIT |
Similar skills
Blog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
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 Google
seranking/seo-skills
Direct access to Google's own SEO data via Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, GA4 organic…
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 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.
More from superdesigndev/treg
All 12 skills in this repoAdd OAuth Provider
superdesigndev/treg
Add a provider to treg's OAuth registry (the ones treg holds its own approved app for).
Dev Local
superdesigndev/treg
One-command local dev stack for tools-registry. An agent skill from superdesigndev/treg.
Google Ads
superdesigndev/treg
Traps when running Google Ads through treg — the API requirements and cleanup semantics that cost round-trips or money.
Google Analytics
superdesigndev/treg
Traps to avoid when querying Google Analytics 4 through treg — cases where the GA4 Data API returns a confident wrong answer instead of an error.
Jev Memory
superdesigndev/treg
A skill your agent uses when the user wants Claude Code to remember their preferences across sessions, asks for a memory mod or memory harness for Claude Code, mentions the Jev memory classifier or…
Tools Registry Context
superdesigndev/treg
tools-registry context + doc upkeep. An agent skill from superdesigndev/treg.
Related
Works with
Categories
Questions about Google Search Console
What does Google Search Console do?
Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends. Google Search Console is an agent skill from superdesigndev/treg. Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends.
When should I use Google Search Console?
Google Search Console fits situations like: answering questions about organic search clicks.
How do I install Google Search Console in Claude Code?
Run `npx skills add superdesigndev/treg --skill google-search-console -a claude-code`. Or copy the skill folder (.agents/skills/google-search-console in superdesigndev/treg) into .claude/skills/google-search-console in your project. Claude Code loads it when a task matches its description.
How do I install Google Search Console in Codex?
Run `npx skills add superdesigndev/treg --skill google-search-console -a codex`. Or copy the skill folder (.agents/skills/google-search-console in superdesigndev/treg) into .agents/skills/google-search-console in your project. Codex loads it when a task matches its description.
Can I use Google 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 superdesigndev/treg --skill google-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/google-search-console, .gemini/skills/google-search-console, .github/skills/google-search-console and .opencode/skills/google-search-console in your project.
What does Google Search Console need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Search Console is instructions for the agent only.
Does Google Search Console access the network?
SKILL.md names 2 domains. As links in the text: developers.google.com and support.google.com. This is read from the text; nothing was executed.
Is Google 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 Google Search Console use?
Google Search Console 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 Google Search Console use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 Google Search Console?
Skills that share tags, products or a category with Google Search Console: Google SEO APIs (AgriciDaniel/claude-seo, 19k stars), Blog Google (AgriciDaniel/claude-blog, 2.3k stars), SEO Coach (akseolabs-seo/seo-coach, 146 stars) and SEO Google (seranking/seo-skills, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Search Console?
superdesigndev (a GitHub organization) maintains it in superdesigndev/treg, which has 4,881 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: superdesigndev/treg on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.