> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bing Webmaster Tools as a data source

> Bring data from Bing Webmaster Tools to Nekt.

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](https://app.nekt.ai/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](https://www.bing.com/webmasters).
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.

<Note>
  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.
</Note>

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](https://docs.nekt.com/get-started/core-concepts/triggers), 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](https://docs.nekt.com/get-started/core-concepts/resource-control).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#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](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

<Warning>To see data in the [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.</Warning>

# Streams and Fields

Below you'll find all available data streams from Bing Webmaster Tools and their corresponding fields:

<AccordionGroup>
  <Accordion title="Sites">
    The sites verified in the account, used as the parent for every site-scoped stream.

    **Key fields:**

    | Field                   | Type    | Description                                                 |
    | :---------------------- | :------ | :---------------------------------------------------------- |
    | `url`                   | String  | The site URL, starting with http and ending with a /.       |
    | `is_verified`           | Boolean | Whether the site has been verified in Bing Webmaster Tools. |
    | `authentication_code`   | String  | Verification code issued by Bing for the site.              |
    | `dns_verification_code` | String  | DNS verification code issued by Bing for the site.          |
  </Accordion>

  <Accordion title="Rank and Traffic Stats">
    Daily clicks and impressions per site. Incremental by `date`.

    **Key fields:**

    | Field         | Type    | Description                                                 |
    | :------------ | :------ | :---------------------------------------------------------- |
    | `site_url`    | String  | The site URL these stats belong to.                         |
    | `date`        | Date    | The day the metrics were measured (Pacific time).           |
    | `clicks`      | Integer | Number of clicks from Bing search results that day.         |
    | `impressions` | Integer | Number of times the site appeared in Bing results that day. |
  </Accordion>

  <Accordion title="Query Stats">
    Weekly clicks and impressions for the site's top search queries. Incremental by `date`.

    **Key fields:**

    | Field                     | Type    | Description                                                |
    | :------------------------ | :------ | :--------------------------------------------------------- |
    | `site_url`                | String  | The site URL.                                              |
    | `query`                   | String  | The search query term.                                     |
    | `date`                    | Date    | End date of the weekly bucket the metrics cover.           |
    | `clicks`                  | Integer | Clicks for the query.                                      |
    | `impressions`             | Integer | Impressions for the query.                                 |
    | `avg_click_position`      | Number  | Average position of the site in results that were clicked. |
    | `avg_impression_position` | Number  | Average position of the site across impressions.           |
  </Accordion>

  <Accordion title="Page Stats">
    Weekly clicks and impressions for the site's top pages. The page URL is returned in the `query` field. Incremental by `date`.

    **Key fields:**

    | Field                     | Type    | Description                                                |
    | :------------------------ | :------ | :--------------------------------------------------------- |
    | `site_url`                | String  | The site URL.                                              |
    | `query`                   | String  | The page URL the statistics apply to.                      |
    | `date`                    | Date    | End date of the weekly bucket the metrics cover.           |
    | `clicks`                  | Integer | Clicks for the page.                                       |
    | `impressions`             | Integer | Impressions for the page.                                  |
    | `avg_click_position`      | Number  | Average position of the page in results that were clicked. |
    | `avg_impression_position` | Number  | Average position of the page across impressions.           |
  </Accordion>

  <Accordion title="Crawl Stats">
    Daily crawl statistics per site. Incremental by `date`.

    **Key fields:**

    | Field                   | Type    | Description                               |
    | :---------------------- | :------ | :---------------------------------------- |
    | `site_url`              | String  | The site URL.                             |
    | `date`                  | Date    | The day the crawl stats apply to.         |
    | `crawled_pages`         | Integer | Pages crawled by Bing.                    |
    | `in_index`              | Integer | Pages currently in the Bing index.        |
    | `in_links`              | Integer | Inbound links discovered.                 |
    | `crawl_errors`          | Integer | Total crawl errors.                       |
    | `code2xx`               | Integer | URLs that returned a 2xx status.          |
    | `code301`               | Integer | URLs that returned a 301 redirect.        |
    | `code302`               | Integer | URLs that returned a 302 redirect.        |
    | `code4xx`               | Integer | URLs that returned a 4xx status.          |
    | `code5xx`               | Integer | URLs that returned a 5xx status.          |
    | `all_other_codes`       | Integer | URLs that returned any other status code. |
    | `blocked_by_robots_txt` | Integer | URLs blocked by robots.txt.               |
    | `contains_malware`      | Integer | URLs flagged as containing malware.       |
  </Accordion>

  <Accordion title="Crawl Issues">
    URLs with crawl issues per site.

    **Key fields:**

    | Field       | Type    | Description                                                  |
    | :---------- | :------ | :----------------------------------------------------------- |
    | `site_url`  | String  | The site URL.                                                |
    | `url`       | String  | The URL the issue applies to.                                |
    | `http_code` | Integer | HTTP status code Bing received for the URL.                  |
    | `in_links`  | Integer | Number of inbound links to the URL.                          |
    | `issues`    | Integer | Bitmask flag describing the crawl issue type(s) for the URL. |
  </Accordion>
</AccordionGroup>

## 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

<Snippet file="agent-skills-intro.mdx" />

<Card title="Download Bing Webmaster Tools skills file" icon="wand-magic-sparkles" href="/sources/bing-webmasters.md">
  Bing Webmaster Tools connector documentation as plain markdown, for use in AI agent contexts.
</Card>