# Get Search By Page Query

`gsc_get-search-by-page-query` · Google Search Console MCP tool · Search Analytics

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.

## Google Search Console Frequently Asked Questions

**What does the Get Search By Page Query tool do?**

This page documents the Get Search By Page Query tool (`gsc_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. 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.

**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/
- /integrations/gsc/search-analytics/compare-search-periods/
- /integrations/gsc/search-analytics/get-advanced-search-analytics/
- /integrations/gsc/search-analytics/get-performance-overview/
- /integrations/gsc/search-analytics/get-search-analytics/

## Input

- **siteUrl** `string` (required, min length: 1) — 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.
- **pageUrl** `string(uri)` (required) — The absolute page URL to fetch query-level search performance for.
- **days** `integer` (>= 1, <= 90) — How many days of data to fetch, counting back from today. Omit for the partner's default window.
- **rowLimit** `integer` (>= 1, <= 25000) — Maximum number of queries to return (up to 25,000). Omit for the partner's default.

## Output

- **siteUrl** `string` (required) — The Search Console property.
- **pageUrl** `string` (required) — The page the query breakdown is for.
- **startDate** `string` — Start of the reporting window (YYYY-MM-DD).
- **endDate** `string` — End of the reporting window (YYYY-MM-DD).
- **rows** `array` (required) — Per-query performance rows for the page.
  - **[]** `object`
    - **query** `string` (required) — The search query.
    - **clicks** `number` — Clicks for the query.
    - **impressions** `number` — Impressions for the query.
    - **ctr** `number` — Click-through rate (clicks ÷ impressions).
    - **position** `number` — Average position in search results.
- **totals** `object` (required) — Aggregated totals across the returned queries (no position).
  - **clicks** `number` — Total clicks across the returned queries.
  - **impressions** `number` — Total impressions across the returned queries.
  - **ctr** `number` — Aggregate click-through rate.