Skip to main content
Bing Webmaster Tools is a free service from Microsoft that helps you monitor and maintain your site’s presence in Bing search results. It provides search performance data — clicks, impressions, top queries and pages — as well as crawl statistics and crawl issues for every site you have verified.

Configuring Bing Webmaster Tools as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Bing Webmaster Tools option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The connector authenticates with a single API key. To generate it:
  1. Sign in to Bing Webmaster Tools.
  2. Open Settings → API access → API Key.
  3. Generate the key and copy it.
The following configurations are available:
  • API Key: Your Bing Webmaster Tools API key. The key inherits access to every site verified by the associated account.
  • Start date: (Optional) The earliest date to keep for date-partitioned streams (rank and traffic, queries, pages, and crawl stats). Records before this date are dropped.
The Bing API exposes no server-side date filter, so the start date and the incremental bookmark are applied by the connector after fetching each response.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select all streams or only specific ones.
Tip: You can quickly find streams by typing their names.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster.
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data.
    • Full table: every time the extraction happens, we’ll get the current state of the data.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
To see data in the Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Bing Webmaster Tools and their corresponding fields:
The sites verified in the account, used as the parent for every site-scoped stream.Key fields:
FieldTypeDescription
urlStringThe site URL, starting with http and ending with a /.
is_verifiedBooleanWhether the site has been verified in Bing Webmaster Tools.
authentication_codeStringVerification code issued by Bing for the site.
dns_verification_codeStringDNS verification code issued by Bing for the site.
Daily clicks and impressions per site. Incremental by date.Key fields:
FieldTypeDescription
site_urlStringThe site URL these stats belong to.
dateDateThe day the metrics were measured (Pacific time).
clicksIntegerNumber of clicks from Bing search results that day.
impressionsIntegerNumber of times the site appeared in Bing results that day.
Weekly clicks and impressions for the site’s top search queries. Incremental by date.Key fields:
FieldTypeDescription
site_urlStringThe site URL.
queryStringThe search query term.
dateDateEnd date of the weekly bucket the metrics cover.
clicksIntegerClicks for the query.
impressionsIntegerImpressions for the query.
avg_click_positionNumberAverage position of the site in results that were clicked.
avg_impression_positionNumberAverage position of the site across impressions.
Weekly clicks and impressions for the site’s top pages. The page URL is returned in the query field. Incremental by date.Key fields:
FieldTypeDescription
site_urlStringThe site URL.
queryStringThe page URL the statistics apply to.
dateDateEnd date of the weekly bucket the metrics cover.
clicksIntegerClicks for the page.
impressionsIntegerImpressions for the page.
avg_click_positionNumberAverage position of the page in results that were clicked.
avg_impression_positionNumberAverage position of the page across impressions.
Daily crawl statistics per site. Incremental by date.Key fields:
FieldTypeDescription
site_urlStringThe site URL.
dateDateThe day the crawl stats apply to.
crawled_pagesIntegerPages crawled by Bing.
in_indexIntegerPages currently in the Bing index.
in_linksIntegerInbound links discovered.
crawl_errorsIntegerTotal crawl errors.
code2xxIntegerURLs that returned a 2xx status.
code301IntegerURLs that returned a 301 redirect.
code302IntegerURLs that returned a 302 redirect.
code4xxIntegerURLs that returned a 4xx status.
code5xxIntegerURLs that returned a 5xx status.
all_other_codesIntegerURLs that returned any other status code.
blocked_by_robots_txtIntegerURLs blocked by robots.txt.
contains_malwareIntegerURLs flagged as containing malware.
URLs with crawl issues per site.Key fields:
FieldTypeDescription
site_urlStringThe site URL.
urlStringThe URL the issue applies to.
http_codeIntegerHTTP status code Bing received for the URL.
in_linksIntegerNumber of inbound links to the URL.
issuesIntegerBitmask flag describing the crawl issue type(s) for the URL.

Implementation Notes

  • The connector authenticates with an API key passed as the apikey query parameter against the Bing Webmaster Tools JSON API (https://ssl.bing.com/webmaster/api.svc/json).
  • The sites stream (GetUserSites) is the parent stream; each site URL is passed to the site-scoped streams as the siteUrl parameter, so a single connection covers every verified site.
  • Microsoft JSON dates (/Date(…)/) are converted to ISO-8601 dates.
  • Date-partitioned streams (rank and traffic, queries, pages, crawl stats) replicate incrementally by date. Because the API has no server-side date filter, the start date and incremental bookmark are applied client-side.
  • Every site-scoped record is stamped with the site_url it belongs to.

Skills for agents

Download Bing Webmaster Tools skills file

Bing Webmaster Tools connector documentation as plain markdown, for use in AI agent contexts.