google-search-console

Google Search Console API integration with managed OAuth. Query search analytics, manage sitemaps, inspect a URL's index status, and monitor site performance. Use this skill when users want to access Search Console data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Search Console connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Search Console action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Search Console examples; they add no Google Search Console capability - Google Search Console is not an event source, a trigger cannot read Google Search Console data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Before installing, be comfortable using Maton's CLI and OAuth connection for Search Console. For normal Search Console queries, prefer read/list calls. Treat sitemap changes, hosted functions, triggers, destinations, raw API keys, and any external forwarding as higher-risk actions that should only happen after you confirm the exact account, scope, destination, and persistence.