google-search-console
Google Search Console API for SEO and indexing data. Use when user mentions "Search Console", "GSC", "search analytics", "impressions/clicks", "keyword rankings", "sitemaps", "URL inspection", or "indexing status".
What this skill does
# Google Search Console
Read Search Console data for verified sites — search analytics (queries, clicks, impressions, CTR, position), sitemaps, and URL inspection (indexing status).
> Official docs: `https://developers.google.com/webmaster-tools/v1/api_reference_index`
---
## When to Use
Use this skill when you need to:
- Pull keyword/page performance: clicks, impressions, CTR, average position
- Check which sitemaps are submitted and their processing status
- Inspect a specific URL's index coverage and crawl status
---
## Prerequisites
- Connect **Google Search Console** under vm0.ai → Settings → Connectors (OAuth).
- The connected Google account must already be a verified owner/user of the property in Search Console.
- The access token is injected as `$GOOGLE_SEARCH_CONSOLE_TOKEN`. Access is read-only (`webmasters.readonly`).
**Base URL:** `https://searchconsole.googleapis.com`
**`siteUrl` formats** — must be URL-encoded in the path:
- URL-prefix property: `https://www.example.com/` → `https%3A%2F%2Fwww.example.com%2F`
- Domain property: `sc-domain:example.com` → `sc-domain%3Aexample.com`
---
## 1. List Verified Sites
Find the exact `siteUrl` values you have access to (use one of these in later calls):
```bash
curl -s "https://searchconsole.googleapis.com/webmasters/v3/sites" --header "Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN" | jq '.siteEntry[] | {siteUrl, permissionLevel}'
```
---
## 2. Query Search Analytics
The core report. Returns rows of metrics grouped by the requested dimensions. Dimensions: `query`, `page`, `country`, `device`, `searchAppearance`, `date`.
Write the request body to `/tmp/gsc_query.json` (top 25 queries by clicks for a date range):
```json
{
"startDate": "2026-05-01",
"endDate": "2026-05-31",
"dimensions": ["query"],
"rowLimit": 25,
"orderBy": [{ "field": "clicks", "descending": true }]
}
```
Then run (replace `<site-url-encoded>` with a value from step 1):
```bash
curl -s -X POST "https://searchconsole.googleapis.com/webmasters/v3/sites/<site-url-encoded>/searchAnalytics/query" --header "Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN" --header "Content-Type: application/json" -d @/tmp/gsc_query.json | jq '.rows[] | {query: .keys[0], clicks, impressions, ctr, position}'
```
**By page instead of query:** set `"dimensions": ["page"]` and read `page: .keys[0]`.
**Filtering** — add a `dimensionFilterGroups` block, e.g. only rows where the page contains `/blog/`:
```json
{
"startDate": "2026-05-01",
"endDate": "2026-05-31",
"dimensions": ["query"],
"dimensionFilterGroups": [
{ "filters": [{ "dimension": "page", "operator": "contains", "expression": "/blog/" }] }
],
"rowLimit": 25
}
```
> Note: Search Console data lags ~2-3 days and the most recent days may be incomplete.
---
## 3. List Sitemaps
See which sitemaps are submitted and whether Google has processed them:
```bash
curl -s "https://searchconsole.googleapis.com/webmasters/v3/sites/<site-url-encoded>/sitemaps" --header "Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN" | jq '.sitemap[] | {path, lastSubmitted, lastDownloaded, isPending, errors, warnings, contents}'
```
### Get a Single Sitemap
`<feedpath>` is the full sitemap URL, URL-encoded:
```bash
curl -s "https://searchconsole.googleapis.com/webmasters/v3/sites/<site-url-encoded>/sitemaps/<feedpath-encoded>" --header "Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN" | jq '{path, lastDownloaded, errors, warnings, contents}'
```
---
## 4. Inspect a URL (Indexing Status)
Check whether a specific URL is indexed, its coverage state, and last crawl time.
Write to `/tmp/gsc_inspect.json` (`siteUrl` here is the raw, un-encoded property; `inspectionUrl` must belong to that property):
```json
{
"inspectionUrl": "https://www.example.com/blog/my-post",
"siteUrl": "https://www.example.com/"
}
```
Then run:
```bash
curl -s -X POST "https://searchconsole.googleapis.com/v1/urlInspection/index:inspect" --header "Authorization: Bearer $GOOGLE_SEARCH_CONSOLE_TOKEN" --header "Content-Type: application/json" -d @/tmp/gsc_inspect.json | jq '.inspectionResult.indexStatusResult | {verdict, coverageState, lastCrawlTime, googleCanonical, indexingState, robotsTxtState}'
```
---
## Notes
- Access is **read-only**: submitting/deleting sitemaps and adding/removing sites require the full `webmasters` scope, which this connector does not request.
- `searchAnalytics/query` caps at `rowLimit` 25000 per request; paginate with `startRow` for larger pulls.
- Use the exact `siteUrl` string returned by step 1 — a trailing-slash or http/https mismatch returns 403.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle 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 analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".