# Get search analytics — Google Search Console

Botize method — `gsearchconsole.search_analytics` (action).

Queries Search Console performance data (clicks, impressions, CTR, position) for a property, grouped by the chosen dimensions over a date range.

This is an action: it runs as a step of a task. Several can be chained.

## Fields you set

The field's internal name, its type and the values it accepts. These fields accept `{{...}}` tags from earlier steps.

- `site_url` *(string)* — Property (URL-prefix like https://example.com/ or domain like sc-domain:example.com)
- `start_date` *(string)* — Start date (YYYY-MM-DD)
- `end_date` *(string)* — End date (YYYY-MM-DD)
- `dimensions` *(string)* — Dimensions (comma separated: query, page, country, device, date, searchAppearance)
- `type` *(string)* — Type (web, image, video, news, discover, googleNews)
- `row_limit` *(string)* — Row limit (default 1000, max 25000)
- `data_state` *(string)* — Data state (final or all)

## Output variables

Data this step makes available. Reference them in later steps with the double-brace tag.

- `{{rows}}` *(text)* — Rows
- `{{row_count}}` *(text)* — Row count
- `{{site_url}}` *(text)* — Property
- `{{responseAggregationType}}` *(text)* — Aggregation type

## Account

Needs a connected Google Search Console account in Botize: https://botize.com/en/app/gsearchconsole/authenticate

## This app

Every trigger and action for Google Search Console: https://botize.com/en/app/gsearchconsole.md

## How to build this

An AI assistant (Claude, ChatGPT, Cursor…) can create and edit these tasks in the user's account through the Botize MCP connector, included in every plan:

    https://webhook.botize.es/mcp

- Connection guide: https://botize.com/en/mcp
- Agent map: https://botize.com/llms.txt
- New account: https://botize.com/en/join (500 free operations, no card)

---
Machine-readable summary for AI assistants. Human version: https://botize.com/en/method/gsearchconsole/search_analytics