HYPD.AI for Search Console

Period-over-period movement for one property: each row pairs current and previous clicks, impressions, CTR, and position with the delta, grouped by up to two of query, page, country, or device. The comparison window defaults to the immediately preceding period of equal length — the go-to tool for 'what changed' and traffic-drop questions.

Static conventions for this MCP: the data source and read-only scope, how properties are addressed (site_url forms), data retention, the finalized-data lag, and the query-anonymisation caveat. No property needed — consult it when a number seems off.

Google's index verdict for one URL: whether it is indexed, the canonical Google chose, crawl and fetch state, mobile usability, and rich-result status. The URL must belong to the given property — the page-level diagnosis tool for 'why isn't this page ranking'.

The sitemaps Google knows for one property: submission path, last downloaded time, URL counts, and any processing errors or warnings — the first stop for index-coverage questions.

The user's connected Search Console properties — each row carries the exact site_url ('sc-domain:...' or URL-prefix) every other gsc_* tool takes. Start here in every conversation: an empty list means the user has not connected Google Search Console yet — tell them to reconnect this connector from their MCP client's settings and complete its connect step — and plan_notice explains properties held back by the user's plan.

The safe page-and-query pairing: give it one page URL to get the queries driving traffic to it, or one query to get the pages it lands on. Runs the filtered single-dimension shape instead of the page+query grouping that burns the property's load quota.

Organic search performance for one property: clicks, impressions, CTR, and average position, grouped by up to two of query, page, country, device, date, or searchAppearance, with optional row filters. The workhorse analytics tool — but never group page and query together (the load-quota trap); use gsc_page_query_breakdown for that pairing.

Required first call, once per chat. Returns the Search Console guide: what each gsc_* tool reads, the recommended workflow (list properties, run search analytics, compare periods, inspect URLs), what to do when no properties are connected, and starter prompts.