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.
When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues.
Install Google Search Console Tool
$ npx skills add garrettjsmith/localseoskills --skill google-search-console-tool -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install garrettjsmith/localseoskills google-search-console-tool --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/garrettjsmith/localseoskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/google-search-console-tool .claude/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .claude/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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/garrettjsmith/localseoskills/tree/main/skills/google-search-console-toolType 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 garrettjsmith/localseoskills --skill google-search-console-tool -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install garrettjsmith/localseoskills google-search-console-tool --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/google-search-console-tool .agents/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .agents/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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 garrettjsmith/localseoskills --skill google-search-console-tool -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install garrettjsmith/localseoskills google-search-console-tool --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/google-search-console-tool .cursor/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .cursor/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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/garrettjsmith/localseoskills.git --path skills/google-search-console-tool--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 garrettjsmith/localseoskills --skill google-search-console-tool -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install garrettjsmith/localseoskills google-search-console-tool --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/google-search-console-tool .gemini/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .gemini/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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 garrettjsmith/localseoskills google-search-console-toolInstalls 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 garrettjsmith/localseoskills --skill google-search-console-tool -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/google-search-console-tool .github/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .github/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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 garrettjsmith/localseoskills --skill google-search-console-tool -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install garrettjsmith/localseoskills google-search-console-tool --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/garrettjsmith/localseoskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/google-search-console-tool .opencode/skills/google-search-console-tool && 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-tool" agent skill from https://github.com/garrettjsmith/localseoskills/tree/main/skills/google-search-console-tool into .opencode/skills/google-search-console-tool/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-search-console-tool", 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-tool- GitHub stars
- 121
- Token cost
- ~1.7k tokens
- SKILL.md length
- 856 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues.
- Works in 3 steps: Filter pages by URL containing… → Get clicks, impressions, CTR, average… → Get queries driving traffic to each…
- Wants to know what queries drive traffic to their site
- SKILL.md covers When to Use GSC vs Other Tools, Critical Distinction, Core Workflows and Key Metrics and What They Mean, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Google Search Console Tool is an agent skill from garrettjsmith/localseoskills. When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues. Trigger on "Search Console," "GSC," "what keywords am I getting traffic for," "what queries," "impressions," "click-through rate," "indexing issues," "is my page indexed," or "organic performance."
Its SKILL.md is about 1.7k 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 Programmatic SEO and Local SEO. It works with Google Search Console and Ahrefs. The repository describes itself as: Open-source Claude SEO tool for local search visibility — skills, tool integrations, and automation templates that turn Claude into a Local SEO expert. The licence is MIT.
When your agent uses it
- Wants to know what queries drive traffic to their site
- Which pages are indexed
- Click-through rates
- Organic search performance
Example prompts
- “Search Console,”
- “what keywords am I getting traffic for,”
- “what queries,”
- “/google-search-console-tool”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Filter pages by URL containing "/locations/" or your location page pattern
- Get clicks, impressions, CTR, average position per page
- Get queries driving traffic to each location page
What it can do on your machine
Read from SKILL.md and the folder at commit 405ce20. 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
Google Search Console Tool loads about 1.7k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 856 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 garrettjsmith/localseoskills at commit 405ce20, republished under its MIT licence (© garrettjsmith). 856 words, ~1,659 tokens.
Download SKILL.mdSave it as
.claude/skills/google-search-console-tool/SKILL.md (or your agent's skills folder).- name
- google-search-console-tool
- description
- When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues. Trigger on "Search Console," "GSC," "what keywords am I getting traffic for," "what queries," "impressions," "click-through rate," "indexing issues," "is my page indexed," or "organic performance."
- metadata.version
- 1.0.0
- metadata.author
- Garrett Smith
Google Search Console Tool
GSC has official and community MCP servers available. When connected, use it for ground-truth organic search performance data — this is the only tool that shows ACTUAL clicks and impressions from Google.
When to Use GSC vs Other Tools
| You Need | Use GSC | Use Instead |
|---|---|---|
| Actual clicks and impressions from Google | ✅ Only source of truth | — |
| What queries drive traffic to which pages | ✅ Only source of truth | — |
| Click-through rate per query/page | ✅ Only source of truth | — |
| Average position per query | ✅ Ground truth | Semrush/Ahrefs estimates |
| Is a specific page indexed? | ✅ | — |
| Core Web Vitals per page | ✅ | — |
| Crawl errors and issues | ✅ | Screaming Frog (more detailed) |
| Keyword search volume | ❌ No volume data | Semrush, DataForSEO |
| Competitor keyword data | ❌ Your site only | Semrush, Ahrefs |
| Backlink data | ❌ Very limited | Ahrefs |
| Local pack rankings | ❌ Organic only | Local Falcon |
| Citation data | ❌ | BrightLocal |
Critical Distinction
GSC shows organic search performance only — not map pack, not LSA, not ads. A business can get zero clicks in GSC but rank #1 in the local pack (because map pack clicks don't show in GSC as organic clicks). Always pair GSC data with Local Falcon map pack data for complete visibility.
Core Workflows
Location Page Performance
When: User wants to know how their location pages perform in organic search.
What to pull:
- Filter pages by URL containing "/locations/" or your location page pattern
- Get clicks, impressions, CTR, average position per page
- Get queries driving traffic to each location page
How to interpret:
- High impressions, low clicks (low CTR): Title tag or meta description doesn't compel clicks — rewrite them
- High position (>20), some impressions: You're on page 2-3, close to breaking through — optimize content
- Location page with zero impressions: Page may not be indexed, or keywords don't trigger it
- Impressions for queries you don't have a page for: Content gap — create a page for that query
CTR benchmarks by position (approximate):
| Position | Expected CTR |
|---|---|
| 1 | 25-35% |
| 2 | 12-18% |
| 3 | 8-12% |
| 4-5 | 5-8% |
| 6-10 | 2-5% |
| 11-20 | 0.5-2% |
If CTR is below expected for the position, the title/meta needs improvement.
Local Keyword Discovery
When: User wants to find keywords they're already getting impressions for but not optimizing.
What to pull:
- All queries with impressions, filtered to last 3 months
- Sort by impressions descending
- Look for queries containing city names, "near me," service terms
What to look for:
- Queries with high impressions but position 8+: Optimization targets — these have demand
- Queries with "near me" variations: Confirm GBP is optimized for these services
- Queries you rank for that you didn't expect: New keyword opportunities
- Queries with city names you don't have a page for: Location page gaps
Index Coverage
When: User asks "is my page indexed?" or location pages aren't getting traffic.
What to check:
- URL Inspection for specific pages — are they indexed?
- Index coverage report — any errors affecting location pages?
- Sitemap processing — is the sitemap submitted and processed?
Common issues for local:
- Location pages not in sitemap → add them
- Location pages marked "Discovered – currently not indexed" → thin content, Google didn't find them valuable enough
- Location pages blocked by robots.txt → fix robots.txt
- Location pages with "Duplicate, submitted URL not selected as canonical" → canonicalization issue between similar location pages
Show full SKILL.md (327 more words)Show less
Core Web Vitals
When: User's pages are slow or CWV failing.
What to check:
- CWV report for location pages specifically
- Which pages fail LCP, FID/INP, CLS
- Mobile vs desktop performance
For local: Mobile CWV matters most — local searches are predominantly mobile. If mobile CWV fails, fix it before other optimization.
Content Gap Identification
When: Looking for new content opportunities from actual search data.
What to pull:
- Queries where you have impressions but no dedicated page
- Queries with high impressions but position 15+
- Compare queries to your existing page structure
Example: GSC shows 500 impressions/month for "emergency plumber Orchard Park" but you don't have a page specifically about emergency plumbing in Orchard Park → create one.
Key Metrics and What They Mean
| Metric | What It Is | Local SEO Context |
|---|---|---|
| Clicks | Actual clicks from Google to your site | The number that matters — this is real traffic |
| Impressions | Times your page appeared in search results | Shows demand even if you're not getting clicks |
| CTR | Clicks ÷ Impressions | Low CTR = title/meta issue. Compare to position benchmarks |
| Average Position | Average ranking position for a query | Remember: this is organic only, not map pack |
What to Do Next
| What You Found | Next Action | Skill |
|---|---|---|
| Location pages with low CTR | Rewrite title tags and meta descriptions | local-landing-pages |
| Queries without dedicated pages | Create pages targeting those queries | local-landing-pages |
| Location pages not indexed | Fix technical issues (thin content, canonical, sitemap) | local-seo-audit, screaming-frog-tool |
| CWV failing on mobile | Fix page speed issues | local-seo-audit |
| Good organic performance, want to see map pack too | Run Local Falcon scans | local-falcon-tool |
| Competitor analysis needed | GSC is your-site only — use Semrush for competitor data | semrush-tool |
| Need this in a client report | Include GSC data in performance reports | local-reporting |
Default next step: GSC is the truth layer. Start every performance analysis with GSC data, then supplement with other tools. If GSC shows no impressions for a keyword, either the page doesn't exist, isn't indexed, or doesn't target the keyword properly.
© garrettjsmith, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/google-search-console-tool of garrettjsmith/localseoskills.
Open the folder on GitHubat commit 405ce20
Compare with similar skills
Google Search Console Tool 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 Tool this skillgarrettjsmith/localseoskills | 121 | — | ~1.7k | 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 | |
| Universal SEO AnalysisAgriciDaniel/claude-seo | 19k | — | ~4.9k | Automated safety check: Pass | MIT | |
| SEO Project Setuppetera2c/simple-table | 229 | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
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…
Universal SEO Analysis
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
SEO Project Setup
petera2c/simple-table
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Backlink
yan-labs/yan-skills
A skill your agent uses for backlink work - finding, qualifying, submitting, analyzing or verifying backlinks, directory and blog-comment placements, competitor link sources, anchors, toxic links…
More from garrettjsmith/localseoskills
All 38 skills in this repoGbp API Automation
garrettjsmith/localseoskills
When the user wants to programmatically manage Google Business Profiles at scale via API, automate GBP updates, build GBP management tools, or integrate GBP data into their systems.
Gbp Posts
garrettjsmith/localseoskills
When the user wants to create, schedule, or optimize Google Business Profile posts.
Local Content Briefs
garrettjsmith/localseoskills
Generate complete semantic content briefs for local SEO content — location pages, service pages, blog posts, FAQ content, and pillar pages.
Brief
garrettjsmith/localseoskills
Manages persistent work state (briefs) for local SEO engagements.
Local Content Strategy
garrettjsmith/localseoskills
Build a complete local content strategy from keyword research output.
Local Falcon Tool
garrettjsmith/localseoskills
When the user wants to run a geogrid scan, check existing scan reports, track ranking trends over time, monitor GBP changes via Falcon Guard, or analyze reviews.
Related
Works with
Categories
Questions about Google Search Console Tool
What does Google Search Console Tool do?
When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues. Google Search Console Tool is an agent skill from garrettjsmith/localseoskills. When the user wants to know what queries drive traffic to their site, which pages are indexed, click-through rates, organic search performance, or technical indexing issues.
When should I use Google Search Console Tool?
Google Search Console Tool fits situations like: wants to know what queries drive traffic to their site; which pages are indexed; click-through rates; organic search performance.
How do I install Google Search Console Tool in Claude Code?
Run `npx skills add garrettjsmith/localseoskills --skill google-search-console-tool -a claude-code`. Or copy the skill folder (skills/google-search-console-tool in garrettjsmith/localseoskills) into .claude/skills/google-search-console-tool in your project. Claude Code loads it when a task matches its description.
How do I install Google Search Console Tool in Codex?
Run `npx skills add garrettjsmith/localseoskills --skill google-search-console-tool -a codex`. Or copy the skill folder (skills/google-search-console-tool in garrettjsmith/localseoskills) into .agents/skills/google-search-console-tool in your project. Codex loads it when a task matches its description.
Can I use Google Search Console Tool 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 garrettjsmith/localseoskills --skill google-search-console-tool -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-tool, .gemini/skills/google-search-console-tool, .github/skills/google-search-console-tool and .opencode/skills/google-search-console-tool in your project.
What does Google Search Console Tool need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Search Console Tool is instructions for the agent only.
Does Google Search Console Tool 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 Google Search Console Tool 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 Tool use?
Google Search Console Tool 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 Google Search Console Tool use?
About 1.7k tokens (SKILL.md is roughly 6.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 Tool?
Skills that share tags, products or a category with Google Search Console Tool: Global SEO Growth (minhnv0807/ai-business-skills, 609 stars), SEO (Nexus-JPF/note-companion, 870 stars), 32 SEO Growth (minhnv0807/ai-business-skills, 609 stars) and Universal SEO Analysis (AgriciDaniel/claude-seo, 19k 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 Tool?
garrettjsmith (a GitHub user) maintains it in garrettjsmith/localseoskills, which has 121 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on August 15, 2026.
Source: garrettjsmith/localseoskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.