Get Search Console report
Fetch Google Search Console search performance (clicks, impressions, CTR, average position) broken down by query, page, country, or device.
gsc_get_report- Safety
- Read-only
- Plan
- Free
A transparent view of what this integration exposes now, what it costs, which plan it needs, and where a human approval is required.
Updated 1 August 2026 from the public registry.
These rows are projected from the same registry used by the API, workflows, agent, and MCP surfaces. Private or disabled operations cannot appear here.
Fetch Google Search Console search performance (clicks, impressions, CTR, average position) broken down by query, page, country, or device.
gsc_get_reportList the Google Search Console dimensions (query, page, country, device, date, searchAppearance) and metrics (clicks, impressions, ctr, position) available in gsc_get_report.
gsc_fieldsList the Google Search Console sites this connection can access. Use the returned site_url with gsc_get_report.
gsc_select_accountsExplore the complete executable definition before connecting a workspace.
Place GA4 Organic Search rows beside daily Search Console performance for the same 28-day window and produce an executive scorecard. The workflow highlights directional patterns while keeping platform definitions separate and refusing to present correlation as attribution.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportai_analyze_datareport_renderUse explicit brand terms to produce a model-assisted narrative grouping of a bounded Search Console query sample. The report keeps ambiguous examples visible and does not claim exhaustive classification, row preservation, total demand coverage, or market share.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded Search Console country-device aggregate to surface observed market and responsive-search questions while keeping sparse combinations, omitted rows, and causation explicit.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderCombine country-level and country-by-query Search Console views into a geographic demand brief for the returned sample. Country keys and metrics are preserved as reported, while the analysis avoids market-size estimates, location intent assumptions, and unsupported expansion claims.
gsc_select_accountsutil_date_rangegsc_get_reportgsc_get_reportai_analyze_datareport_renderReview current-period Search Console country aggregates to identify where search demand is observed and which localization or market checks deserve validation, without treating volume as revenue or market causation.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderSummarize current-period Search Console device rows and surface observed click, impression, CTR, and position differences for a responsive-search review without claiming a device caused performance changes.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderCompare Search Console performance first by device and then by device plus query to find returned queries whose clicks, CTR, or position differ materially across device categories. The workflow treats those differences as investigation opportunities, not proof of a device-specific experience problem.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview current-period Search Console page aggregates to identify pages with observed clicks, impressions, CTR, and position signals that deserve indexing and content verification.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded Search Console page and query sample to identify observed intent clusters and pages worth investigation, while keeping query evidence, page evidence, and omitted rows explicit.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded current-period Search Console page sample and surface pages with weak CTR, attainable average positions, or meaningful click demand worth protecting. This snapshot does not measure decay or sustained deterioration because it does not query a comparable prior period, and it does not represent every indexed page.
gsc_select_accountsutil_date_rangegsc_get_reportconditionai_analyze_datareport_renderReview current-period Search Console page and search-appearance aggregates to identify pages and features needing markup or snippet validation without claiming eligibility or complete visibility.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview current-period Search Console query aggregates for impression, click, CTR, and position opportunities, with explicit sample limits and no unsupported momentum or ranking claims.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded current-period Search Console query sample and surface high-impression, weak-CTR, and attainable-position opportunities for investigation. This snapshot does not measure momentum, decline, or newly visible demand because it does not query a comparable prior period, and omitted rows remain unknown.
gsc_select_accountsutil_date_rangegsc_get_reportconditionai_analyze_datareport_renderReview current-period Search Console search-appearance aggregates to surface observed rich-result and feature visibility questions, with exact evidence and clear limits around coverage, eligibility, and causation.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderCompare bounded GA4 landing-page traffic rows with Search Console page visibility for the same period, then surface page-level mismatches worth checking. The workflow explicitly treats GA4 sessions and Search Console clicks as different measurements and does not manufacture a cross-platform attribution model.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportconditionconditionai_analyze_datareport_renderCollect separate GA4 channel, source-medium, and campaign views plus a bounded Search Console query-page view for the last seven complete days. The final report summarizes acquisition mix and search demand while keeping channel performance, search visibility, and attribution claims distinct.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportga4_get_reportga4_get_reportgsc_get_reportai_analyze_datareport_renderCompare the operating model or open a workspace and start with a visible requirement check.