Retrieve keyword and traffic data from the Bing Webmaster Tools API to complement GSC data
domain: bing-webmaster-tools · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Log in to Bing Webmaster Tools, navigate to API Access, and generate an API key
Authenticate requests by appending ?apikey=YOUR_API_KEY as a query parameter to the base API URL https://ssl.bing.com/webmaster/api.svc
Call the GetQueryStats endpoint to retrieve keyword impression and click data for a site and date range
Call GetCrawlIssues to retrieve Bingbot-detected crawl problems such as DNS failures, connection timeouts, and robots.txt blocks
Map the Bing keyword data against equivalent GSC queries to identify keywords where Bing visibility diverges significantly from Google, indicating potential rendering or indexation issues
Known gotchas
The Bing Webmaster Tools API requires site ownership verification in the Bing Webmaster portal before any API call will return data for that property; unverified sites return empty results, not an error
Bing's keyword data uses Bing's own crawl and ranking signals; a page ranking well in GSC may rank poorly in Bing data due to JavaScript rendering differences, as Bingbot's rendering capabilities differ from Googlebot
API responses use XML by default via SOAP; append the json path prefix (e.g., /json/GetQueryStats) to receive JSON responses, which is easier to parse in most scripting environments
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?