search_console_analytics_compare_periods
Compare search analytics between two date periods to identify performance changes. Returns clicks, impressions, CTR, and position for each period, aligned by shared dimensions.
Instructions
Query Search Console search analytics twice and return both periods side-by-side. Returns {period_1: [rows], period_2: [rows]} where each rows list has the same shape as search_console_analytics_query (keys, clicks, impressions, ctr, position). The tool does NOT diff or merge the periods — the agent must align by the first key in each row. Read-only. Two REST calls are issued per invocation. Defaults: dimensions=['query'], row_limit=100 per period. For a single-period query use search_console_analytics_query.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site_url | Yes | Property identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com'). The property must be verified and accessible to the authenticated Google account. | |
| row_limit | No | Maximum rows per period (default 100, cap 25000). Applied independently to period 1 and period 2. | |
| dimensions | No | Dimensions shared across both periods. Default ['query']. Use ['page'] to compare URL-level changes, ['device'] for device shifts. | |
| end_date_1 | Yes | Period 1 inclusive end date ('YYYY-MM-DD'). Must be >= start_date_1. | |
| end_date_2 | Yes | Period 2 inclusive end date ('YYYY-MM-DD'). Must be >= start_date_2. | |
| start_date_1 | Yes | Period 1 inclusive start date ('YYYY-MM-DD'). Convention: period 1 is the older / baseline window. | |
| start_date_2 | Yes | Period 2 inclusive start date ('YYYY-MM-DD'). Convention: period 2 is the newer / comparison window. |