SEO GSC Wizard MCP

Bing query + page pairs

get_bing_query_page_stats

Read-only

Bing Webmaster Tools query+landing-page pairs for a property, aggregated across the window (clicks, impressions, CTR as a 0-100 percentage, and impression-weighted average position per pair). Shows which query drives each page on Bing, the basis for per-page keyword analysis and cannibalisation checks. Bing has no endpoint that returns these combinations, so they are assembled with one request per top page; pass query to pair from a single query instead, or use get_bing_page_queries for one page's queries. Coverage is bounded by seedLimit and by Bing's own top-value sampling, so totals are a lower bound (truncated says when). Returns notConfigured: true when no Bing Webmaster API key is set up for the property.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max query/page pairs, ranked by clicks then impressions (default 100, uncapped).
`query`	No	Optional. Pair from this single search query (Bing lists the pages that ranked for it) instead of fanning out over the top pages. Use it to answer "which pages compete for this term?".
`endDate`	No	Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). Omit BOTH startDate and endDate to return everything Bing has (roughly the last 6 months). Never pass null or the string "null".
`siteUrl`	Yes
`seedLimit`	No	How many top pages to expand into pairs (default 25, max 100). Each one is a separate Bing request, so raising it widens coverage but is slower and likelier to hit Bing rate limits. Only applies to the page fan-out, so a call that passes `query` uses it only if that path has to fall back to pairing by page.
`startDate`	No	Optional. Window start as YYYY-MM-DD (e.g. 2026-01-01). Omit BOTH startDate and endDate to return everything Bing has (roughly the last 6 months). Never pass null or the string "null".