gsc
Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps. Use when analyzing search performance, finding optimization opportunities, or checking indexing status.
Best use case
gsc is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps. Use when analyzing search performance, finding optimization opportunities, or checking indexing status.
Teams using gsc should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gsc/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gsc Compares
| Feature / Agent | gsc | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps. Use when analyzing search performance, finding optimization opportunities, or checking indexing status.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Google Search Console Skill Query GSC for search analytics, indexing status, and SEO insights. ## Setup 1. **Credentials**: Uses same OAuth credentials as GA4 skill (stored in `.env`) 2. **Scopes**: Requires `webmasters.readonly` scope on your Google Cloud OAuth consent screen 3. **Access**: Your Google account must have access to the Search Console properties ## Commands ### List Available Sites ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py sites ``` ### Top Search Queries ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py top-queries \ --site "https://www.nutrient.io" \ --days 28 \ --limit 20 ``` ### Top Pages by Traffic ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py top-pages \ --site "https://www.nutrient.io" \ --days 28 \ --limit 20 ``` ### Find Low-CTR Opportunities High impressions but low click-through rate = optimization opportunities: ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py opportunities \ --site "https://www.nutrient.io" \ --days 28 \ --min-impressions 100 ``` ### Inspect URL Indexing Status ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py inspect-url \ --site "https://www.nutrient.io" \ --url "/sdk/web" ``` ### List Sitemaps ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py sitemaps \ --site "https://www.nutrient.io" ``` ### Raw Search Analytics (JSON) ```bash source /Users/admin/clawd/skills/gsc/.env && \ python /Users/admin/clawd/skills/gsc/scripts/gsc_query.py search-analytics \ --site "https://www.nutrient.io" \ --days 28 \ --dimensions query page \ --limit 100 ``` ## Available Dimensions - `query` - Search query - `page` - Landing page URL - `country` - Country code - `device` - DESKTOP, MOBILE, TABLET - `date` - Date ## Metrics Returned - **clicks** - Number of clicks from search - **impressions** - Number of times shown in search - **ctr** - Click-through rate (clicks/impressions) - **position** - Average ranking position ## SEO Use Cases 1. **Content Optimization**: Find high-impression/low-CTR pages → improve titles & descriptions 2. **Keyword Research**: See what queries bring traffic → create more content around them 3. **Technical SEO**: Check indexing status, find crawl issues 4. **Ranking Tracking**: Monitor position changes over time 5. **Sitemap Health**: Verify sitemaps are submitted and error-free ## Notes - Data has ~3 day delay (GSC limitation) - Credentials shared with GA4 skill - URL inspection requires the page to be in the property
Related Skills
Zendesk
Manage Zendesk tickets, users, and support workflows through the Zendesk API. Use when searching tickets, updating support state, checking users, or exporting queue data.
task-orchestrator
Autonomous multi-agent task orchestration with dependency analysis, parallel tmux/Codex execution, and self-healing heartbeat monitoring. Use for large projects with multiple issues/tasks that need coordinated parallel execution.
sysadmin-toolbox
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
salesforce
Query and manage Salesforce CRM data via the Salesforce CLI (`sf`). Run SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and make raw REST API calls.
remotion-best-practices
Best practices for Remotion - Video creation in React
planner
Create structured plans for multi-task projects that can be used by the task-orchestrator skill. Use when breaking down complex work into parallel and sequential tasks with dependencies.
parallel-task
Coordinate plan files by launching multiple parallel subagents for unblocked tasks. Triggers on explicit "/parallel-task" commands.
nutrient-openclaw
OpenClaw-native document processing skill for Nutrient DWS. Use when OpenClaw users need to convert files, extract text or tables, OCR scans, redact PII, watermark PDFs, digitally sign documents, or check credit usage from chat attachments or workspace files. Triggers on OpenClaw tool names (`nutrient_convert_to_pdf`, `nutrient_extract_text`, etc.), "OpenClaw plugin", "Nutrient OpenClaw", and document-processing requests in OpenClaw chats. Files are processed by Nutrient DWS over the network, so use it only when third-party document processing is acceptable. For non-OpenClaw environments, use the universal Nutrient document-processing skill instead.
nudocs
Upload, edit, and export documents via Nudocs.ai. Use when creating shareable document links for collaborative editing, uploading markdown/docs to Nudocs for rich editing, or pulling back edited content. Triggers on "send to nudocs", "upload to nudocs", "edit in nudocs", "pull from nudocs", "get the nudocs link", "show my nudocs documents".
last30days
Research any topic from the last 30 days on Reddit + X + Web, synthesize findings, and write copy-paste-ready prompts. Use when the user wants recent social/web research on a topic, asks "what are people saying about X", or wants to learn current best practices. Requires OPENAI_API_KEY and/or XAI_API_KEY for full Reddit+X access, falls back to web search.
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
google-ads
Query, audit, and optimize Google Ads campaigns. Supports two modes: (1) API mode for bulk operations with the google-ads Python SDK, (2) attached-browser mode for users without API access. Use when asked to check ad performance, pause campaigns or keywords, find wasted spend, audit conversion tracking, or optimize Google Ads accounts.