Read Search Console performance

Read stored organic query performance for the linked Search Console site. Method: GET Path: /projects/{project_id}/ga4/search-console Use the HTTP base for your authorized environment and an Authorization: Bearer header. See authentication and HTTP setup.

Parameters

This table covers the standard read profile. It excludes internal application routes and advanced analysis controls.

Name	Location	Type	Required	Default	Meaning
`project_id`	path	string	Yes	—	Project ID from list_projects. Select the project in the intended workspace and environment.
`start_date`	query	string	No	`"30daysAgo"`	Start of the requested range, as YYYY-MM-DD or a relative value such as 30daysAgo. These reads select a stored snapshot; use resolved_window for the dates actually served.
`end_date`	query	string	No	`"today"`	End of the requested range, as YYYY-MM-DD or today. Check resolved_window rather than treating the requested dates as the served period.
`limit`	query	integer	No	`100`	Maximum stored query rows to return, capped at 5000. The rows remain a top-query subset; use site_totals for whole-site values when returned.

Request example

Set IQRUSH_API_BASE and IQRUSH_ACCESS_TOKEN through secure configuration. Replace project/run IDs and sample selections with values returned by your account. JSON objects and arrays are encoded as query strings.

curl --fail-with-body --silent --show-error --get \
  --header "Authorization: Bearer ${IQRUSH_ACCESS_TOKEN}" \
  --header "Accept: application/json" \
  --data-urlencode start_date=2026-09-01 \
  --data-urlencode end_date=2026-09-30 \
  --data-urlencode limit=100 \
  "${IQRUSH_API_BASE%/}/projects/${IQRUSH_PROJECT_ID}/ga4/search-console"

Read the response

Returns query data with clicks, impressions, CTR, and position where available, along with sync and period context. Inspect gsc_sync_status and gsc_sync_error. The advertised device argument is not applied by the current HTTP route; omit it and do not claim a device-filtered result.

Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

Field	Meaning and use
`linked`	Whether a Google property link exists. A linked property can still lack a Search Console site or usable snapshot.
`rows`	Stored search-query results when available. The unlinked example is not evidence of zero clicks or impressions.

Selected response fields from IQRush Dev. Lists are shortened and project/run IDs are placeholders; this is not the full response.

{
  "project_id": "PROJECT_ID",
  "linked": false,
  "rows": []
}

This observed example has no linked Google property. It demonstrates the unavailable-integration response; it is not a zero-traffic report. MCP equivalent: get_search_console_data. Use the parameters and defaults on this page for HTTP.

Fields when linked data is available

The Dev handler defines the fields below for populated responses. They are not populated in the unlinked example shown here.

Field	Meaning and use
`resolved_window`	Stored Search Console snapshot dates actually served.
`site_totals`	Whole-site clicks, impressions, CTR, and position for that snapshot when available.
`rows_are_top_n_subset`	True identifies the query rows as a selected subset; their sum is not the site total.
`rows[].query`	Search query from the stored subset.
`rows[].clicks`	Clicks for the query in the selected snapshot.
`rows[].impressions`	Impressions for the query in the selected snapshot.
`rows[].ctr`	Stored click-through rate; preserve null when unavailable.
`rows[].position`	Stored average search position; preserve null when unavailable.

If the result is unavailable

Check HTTP status and the response’s error field before using data. A successful empty response does not establish a zero value. Preserve not_available, not_available_reason, unavailable_reason, and linked where returned. Errors and recovery shows observed examples.

Get started

Connect securely

Read measurements

Build dependable integrations

Build reports

Report recipes

Reference

Session and discovery

Visibility measurements

Sources and evidence

Changes and trends

Google data

Pages and report planning

HTTP operations

Read Search Console performance — HTTP

Parameters

Request example

Read the response

Fields to use

Fields when linked data is available

If the result is unavailable

​Parameters

​Request example

​Read the response

​Fields to use

​Fields when linked data is available

​If the result is unavailable

Parameters

Request example

Read the response

Fields to use

Fields when linked data is available

If the result is unavailable