Weave
Sign InSign Up
View as .md ↗
Google Search Console

Google Search Console | Get Advanced Search Analytics

MCP server · Marketing · google.com · 4 categories · 10 tools

Powered by Advanced GSC ↗

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.

gsc_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.

Tool Input

siteUrlstringrequired— The Search Console property, exactly as it appears in Search Console — either an absolute URL-prefix property (e.g. https://www.example.com/, including any trailing slash) or a domain property (sc-domain:example.com). Forwarded verbatim, never normalized; use gsc_list-properties to see the connected account's exact property identifiers. If the connected Google account cannot verify this property, the partner returns no data rather than an error.(min length: 1)
startDatestring(date)— Start of the date range (YYYY-MM-DD). Must be provided together with endDate. Omit both for the partner's default window.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$)
endDatestring(date)— End of the date range (YYYY-MM-DD). Must be provided together with startDate.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$)
dimensionsarray— Which dimensions to break results down by (e.g. query, page). Omit to use the partner's default grouping (observed: a single `query` dimension).(min items: 1)
[]string(enum: "query", "page", "country", "device", "date", "searchAppearance")
dataStatestring— `all` includes Google's freshest, not-yet-finalized data; `final` returns only finalized rows. Omit for the partner's default.(enum: "all", "final")
searchTypestring— Restrict results to one Google search surface. Omit for web search.(enum: "web", "image", "video", "news")
pageFilterstring— Restrict results to a single page URL, matched per filterOperator.(min length: 1)
queryFilterstring— Restrict results to a single query string, matched per filterOperator.(min length: 1)
countryFilterstring— Restrict results to one country, as an ISO 3166-1 alpha-3 code (e.g. USA).(pattern: ^[A-Z]{3}$)
deviceFilterstring— Restrict results to one device type.(enum: "DESKTOP", "MOBILE", "TABLET")
filterOperatorstring— How pageFilter/queryFilter match. Defaults to equals.(enum: "equals", "contains", "notEquals", "notContains")
rowLimitinteger— Maximum rows to return (up to 25,000). Start with a smaller rowLimit and narrow with dimensions/filters/dataState for exploratory queries; raise it only once you know how much data you need.(>= 1, <= 25000)
startRowinteger— Zero-based row offset for pagination.(>= 0)
sortBystring— Which metric to sort rows by.(enum: "clicks", "impressions", "ctr", "position")
sortDescendingboolean— Sort descending when true, ascending when false. Only meaningful together with sortBy.

Tool Output

siteUrlstringrequired— The Search Console property.
startDatestring— Start of the reporting window (YYYY-MM-DD).
endDatestring— End of the reporting window (YYYY-MM-DD).
dimensionsarray— The dimensions the rows are broken down by, in key order.
[]string
sortBystring— The metric the rows are sorted by, when sorted.
sortDirectionstring— Sort direction (e.g. descending), when sorted.
startRownumber— Zero-based offset of the first returned row.
rowCountnumber— Number of rows returned in this page.
totalMatchednumber— Total rows matching the query across all pages.
hasMoreboolean— Whether more rows are available beyond this page.
rowsarrayrequired— The breakdown rows.
[]object
keysarrayrequired— Dimension values for the row, positionally aligned with `dimensions`.
1 field
[]string
clicksnumber— Clicks for the row.
impressionsnumber— Impressions for the row.
ctrnumber— Click-through rate (clicks ÷ impressions).
positionnumber— Average position in search results.

We're Adding More Google Search Console Tools Constantly!

Don't see a specific Google Search Console tool you need? Email [email protected] and we can add it.

Google Search Console Frequently Asked Questions

What does the Get Advanced Search Analytics tool do?

This page documents the Get Advanced Search Analytics tool (gsc_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. It is one of the Google Search Console Search Analytics tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

Why did my request get rejected before it even reached Google?

startDate and endDate must be provided together. Otherwise this tool validates locally and forwards the rest, sort, filter, dataState, dimensions, straight through.

How large a request should I make?

rowLimit can go up to 25,000 rows, but prefer a smaller rowLimit for exploratory queries and narrow with dimensions/filters/dataState before reaching for the maximum.

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 Tools

get-search-analyticsget-performance-overviewcompare-search-periods