Query Search Console analytics
query_search_analyticsRuns a Search Console searchAnalytics.query against one of the user's properties. Supports date / query / page / country / device / searchAppearance dimensions, dimension filters, and any of the supported search types (web, image, video, news, discover, googleNews). Use this for ad-hoc questions like "top queries last 28 days" or "page-level performance for /pricing". Eligible requests are served from the GSC Wizard ClickHouse warehouse (longer history, no sampling); requests using searchAppearance, the googleNews type or 3+ distinct dimensions fall back to the live Search Console API. The response dataSource says which path ran. Rows are sorted by clicks, or by date first when date is one of the dimensions. Regex filters use RE2 (no lookahead or backreferences; use excludingRegex to exclude). Returns 100 rows by default: read pagination in the response to see whether the result was truncated, and page through with startRow or ask for more at once with rowLimit. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | No | Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). You do NOT need to know today's date or the latest available date: omit this and the server uses the latest settled Search Console date (data lags ~2-3 days behind today). Never pass null or the string "null". | |
| filters | No | Dimension filters joined with AND. Pass an empty list or omit for no filtering. | |
| siteUrl | Yes | The property URL as returned by list_sites (e.g. "sc-domain:example.com"). | |
| rowLimit | No | Rows to return per call (default 100, max 25000). Large values return a lot of raw rows; prefer paging with startRow. | |
| startRow | No | Rows to skip. Use pagination.nextOffset from a previous call to get the next page. | |
| startDate | No | Optional. Window start as YYYY-MM-DD (e.g. 2026-05-03). You do NOT need to know today's date. Omit BOTH startDate and endDate to analyze the last 28 settled days automatically (Search Console data lags ~2-3 days). Never pass null or the string "null". | |
| dimensions | No | ||
| searchType | No | web |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| rows | No | ||
| endDate | No | ||
| siteUrl | No | ||
| rowCount | No | ||
| startDate | No | ||
| dataSource | No | ||
| dimensions | No | ||
| pagination | No | ||
| searchType | No | ||
| dataMaturity | No | ||
| settledThrough | No | ||
| warehouseLatestDate | No |