Use the Google Search Console CLI from KosmoKrator to call Google Search Console tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Google Search Console can be configured headlessly with `kosmokrator integrations:configure google-search-console`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure google-search-console --set access_token="$GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN" --enable --read allow --write ask --jsonkosmokrator integrations:doctor google-search-console --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Manual OAuth tokenoauth2_manual_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN
Secret secret
yes
Access Token
url
GOOGLE_SEARCH_CONSOLE_URL
URL url
no
API Base URL
Call Google Search Console Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Google Search Console.
google-search-console.gsc_list_sites
Read read
List all sites the authenticated user has access to in Google Search Console. Returns site URLs and permission levels.
Query search performance data from Google Search Console — clicks, impressions, CTR, and average position. Group by dimensions like query, page, country, or device.
The sitemap URL or ID (e.g., "https://example.com/sitemap.xml").
google-search-console.gsc_list_search_analytics
Query search performance data from Google Search Console — clicks, impressions, CTR, and average position. Group by dimensions like query, page, country, or device.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.