Organic Search Performance
gsc_performanceSearch Console ORGANIC search performance: queries, pages, countries or devices with clicks, impressions, CTR (%) and average position. Organic data, independent of ads.
dimension takes ONE dimension or a COMBINATION separated by commas: query, page, country, device, date (daily series, returned in date order), or page,query. The combination is what answers "which page ranks for which term", so it is the one to use for cannibalisation work — two pages competing on the same query show up as two rows with the same query (issue #295).
sort = clicks | impressions | ctr | position. This matters more than it looks: Search Console ALWAYS returns rows by clicks, and its own orderBy parameter is accepted and then ignored (measured). So a query with 520 impressions and 2 clicks sits far below the cut and CTR work — which is by definition about high-impression, low-click terms — was impossible. The sort is therefore done here, over every row fetched, and rows_scanned tells you how wide that base was (issue #296).
page / query filter to one page or one query (substring match), so "which queries does THIS page get" is one call.
days: lookback days (Search Console data lags 2-3 days, so the newest days may be empty).
start_date / end_date (YYYY-MM-DD) report an exact window instead of days; the reply's period is the range actually used.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| page | No | ||
| sort | No | clicks | |
| limit | No | ||
| query | No | ||
| end_date | No | ||
| site_url | Yes | ||
| dimension | No | query | |
| start_date | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||