# Search Analytics

Google Search Console MCP server · 5 tools

Search performance data — clicks, impressions, CTR, and average position — broken down by query, page, country, device, or date, plus period-over-period comparisons. Data typically lags live traffic by about two days.

## Google Search Console Frequently Asked Questions

**What are the Google Search Console Search Analytics tools?**

This page lists the Search Analytics tools in the Google Search Console integration: 5 tools for working with search analytics. Each is exposed through your firm's Weave MCP connection and available to members whose access level permits it.

**Which tool should I use for a quick summary versus a full export?**

gsc_get-performance-overview gives a rolling or explicit-range summary; gsc_get-advanced-search-analytics returns up to 25,000 rows with sorting, filtering, and dataState control for a full export, prefer a smaller row limit unless you need the whole set.

**How do I see what's driving clicks to one specific page?**

gsc_get-search-by-page-query returns the queries driving clicks and impressions to a single page.

**What is the Google Search Console integration?**

The Google Search Console integration connects your firm's Google Search Console account to Weave. Google Search Console is Google's free tool for tracking how your sites perform in Google Search. This integration lets your AI workflows read that data, search traffic and rankings, index coverage and URL inspection, and sitemap status, for the properties your connected Google account can access. It groups 10 tools into 4 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

**How does my firm connect Google Search Console to Weave?**

An admin authorizes a Google account with access to your Search Console properties once, via Google's OAuth consent flow in the Weave console. Every firm member then works through that single connection, there is no per-member Google sign-in.

**Why did a tool return no data for our site?**

Every gsc tool that takes a siteUrl requires the connected Google account to be a verified owner or user of that property in Search Console, if it can't verify the property, the tool returns no data rather than an error. gsc_list-properties is the exception: it takes no input and simply lists every property the connected account can access, so start there to get the right siteUrl.

**Why does the data look a couple of days behind our live traffic?**

Search Console's performance data typically lags live traffic by about two days; that's a Google-side reporting delay, not a Weave sync issue.

**Can these tools change anything in Search Console?**

No. Every gsc tool is read-only, none of them can submit URLs, edit sitemaps, or change any Search Console setting.

## Related
- /integrations/gsc/properties/
- /integrations/gsc/url-inspection/

## Tools

- [Compare Search Periods](/integrations/gsc/search-analytics/compare-search-periods/) — Compare search performance between two date ranges for a Search Console property, to spot period-over-period changes in clicks, impressions, CTR, and position. Data typically lags live traffic by about 2 days. Read-only.

- [Get Advanced Search Analytics](/integrations/gsc/search-analytics/get-advanced-search-analytics/) — Fetch search performance data for a Search Console property with sorting, filtering (page/query/country/device), pagination, and dataState control, returning up to 25,000 rows. Prefer a smaller rowLimit for exploratory queries — see the rowLimit field. Data typically lags live traffic by about 2 days. Read-only.

- [Get Performance Overview](/integrations/gsc/search-analytics/get-performance-overview/) — Fetch a high-level search performance summary for a Search Console property over a date range — either a rolling window (days) or an explicit startDate/endDate pair. Data typically lags live traffic by about 2 days. Read-only.

- [Get Search Analytics](/integrations/gsc/search-analytics/get-search-analytics/) — Fetch search performance data (clicks, impressions, CTR, position) for a Search Console property, optionally broken down by query/page/country/device/date/searchAppearance. Data typically lags live traffic by about 2 days. Read-only.

- [Get Search By Page Query](/integrations/gsc/search-analytics/get-search-by-page-query/) — Fetch the search queries driving clicks/impressions to a single page of a Search Console property. Data typically lags live traffic by about 2 days. Read-only.