Bing Webmaster Tools

Bing Webmaster Tools is Bing's own report of how your site performs in Bing: clicks, impressions, click-through and average position, plus the pages Bing could not read. RankX AI syncs it nightly, refreshes it on demand with Sync now, and charges no credits for any of it, because the Bing Webmaster Tools API is free. It is available on every plan.

It is the Bing counterpart to Search Console, and it is worth connecting for a reason Search Console cannot cover: Bing's index is what Microsoft Copilot answers from, so Bing is the only place you can see whether a page is reachable there at all.

RankX AI also tells Bing about your pages. Every article RankX AI publishes live is announced to Bing automatically, and you can submit URLs to Bing for crawling yourself. Everything else RankX AI does with Bing is reading.

What connecting Bing gets you

Four things, and all four are free to read:

Performance. Clicks, impressions, click-through and average position for the Website, broken down by search term or by page.

Drill-down. For one page, the Bing searches that drove it. For one search, the pages Bing showed. Both directions, on demand.

Crawl issues. Pages Bing could not read or was told not to read: server errors, 404s, DNS failures, timeouts, malware flags, and pages blocked by robots.txt.

Keyword ideas. Related search terms, with the impressions Bing itself recorded for them.

RankX AI also compares what it reads from Bing against what it already knows about your site, which produces findings no single connection could. See what Bing shows that Search Console cannot.

Bing reports weekly, and Search Console reports daily

This is the difference that changes how you read every figure on the screen, so it comes before the figures themselves.

Bing's search and page statistics are weekly. Microsoft's own API reference for the query statistics method says it plainly: the data is updated every week. Search Console's equivalent is daily.

So RankX AI offers a window in whole weeks, not days: 4, 12, 26 or 52, with 12 as the default. A "last 30 days" selector over a weekly grain has only two possible behaviours and both are wrong. It can round, in which case your total stops matching the sum of the rows underneath it, or it can cut a week in half, in which case the number is simply incorrect.

Two smaller consequences follow, and both are deliberate:

The week boundary is read from your data, never assumed. Microsoft publishes no guarantee about which day a Bing week ends on. RankX AI selects from the week endings that actually exist in your rows rather than generating a cadence, so nothing breaks silently the day Bing changes its bucketing.

A short history is labelled as short. If you ask for 12 weeks and Bing has reported three, the header says three. "Last 12 weeks" printed over three weeks of data is a false denominator, and every rate on the screen divides by it.

Bing reports two average positions and Google reports one

Bing sends average impression position, which is where your listing sat each time it was shown, and average click position, which is where it sat when someone actually clicked it. These answer different questions. They are not comparable to each other, and neither is comparable to Search Console's single blended figure.

Average click position is often empty, and that is not a fault. Bing reports no click position for a search that earned no clicks, and on a site with modest Bing traffic that is most search-and-week pairs. RankX AI therefore resolves which basis your data actually supports rather than picking one in advance, and captions every position figure with which one it is showing. A number labelled only "average position" invites exactly the comparison that should not be made.

Bing's crawl issues are a point-in-time observation

The crawl issues list carries the date Bing captured it, and RankX AI shows that date beside it rather than presenting the list as current.

Microsoft's own documentation states that it may take a few days before a fixed issue disappears from this list. So a page you repaired this morning can legitimately still be here, and quoting the capture date is the difference between a report that is right and one that looks wrong a week later.

A page in this list is a page Bing could not read. Since Copilot answers from Bing's index, it is also a page no Microsoft assistant can cite, whatever else is true about it.

An empty crawl issues list is a real answer, not a missing one. RankX AI draws nothing at all rather than a card of dashes, and it distinguishes "we looked and your site has none" from "we could not look". Those are different claims and only one of them is about your website.

Keyword ideas are Bing impressions, not search volume

The figures beside a keyword idea are impressions Bing itself recorded. They are not Google search volume, and they are not a demand estimate.

Bing is a minority of most sites' search traffic, so treat a figure here as a lower bound on interest in a term rather than as its size. For Google-side volume, ad competition and cost per click, use keyword research instead, which is priced.

Submitting URLs to Bing

RankX AI tells Bing about your URLs in two ways, and both cost no credits.

Publishing announces live URLs automatically. When RankX AI publishes a Content Studio article live, to WordPress or to a Shopify blog, or updates one that is already live, it sends the article's address to Bing through your Bing connection. There is nothing to set up beyond connecting Bing, and an announcement never holds up or fails the publish itself.

You can submit any URLs yourself from the Bing screen, up to 500 in one go.

Both spend Bing's submission allowance, and three things about that allowance matter:

The allowance is Bing's, not ours. RankX AI reads your remaining quota from Bing rather than assuming a number. Bing sets it per site from the site's verified age, its impressions and other signals it holds, so it varies between sites and there is no figure we can publish for yours.

It is shared across every Website on the connection. One Bing account connected to several Websites draws one allowance between them.

Submitting by hand is staff only. An invited client user on an agency workspace can read the Bing screens and cannot submit, because a submission writes to the agency's own Bing account and spends a shared allowance.

What Bing shows that Search Console cannot

One finding on this screen is not available from either engine on its own: a search where you rank well on one engine and poorly on the other.

Search Console cannot produce it at any price, because Search Console holds Google. RankX AI has both, so it can compare a term's Bing position against its Google position and surface the ones that diverge. A term you have already earned on one engine and not the other is usually the cheapest work on the list, because the page exists and the intent is proven.

The Bing screen also raises pages Bing has never shown, searches earning Bing clicks that you are not tracking, and important pages your robots.txt blocks. Each carries a button that turns it into a task on the Tasks board, so a finding can become work rather than staying a number on a screen. Nothing is added to the board unless you ask for it.

What the Bing connection covers

RankX AI's Bing connection shows whether Bing can read a page and how that page performs in Bing search. That is the layer a Microsoft assistant reaches your site through, and a real, checkable answer to "can a Microsoft assistant reach this page at all".

Copilot's own citation report is read in Bing Webmaster Tools. Bing Webmaster Tools has an AI Performance report, launched in public preview on 10 February 2026, which shows how often Copilot and Bing's AI summaries cited your pages. Microsoft publishes no API for it: there is no method for it in the Webmaster API, so no third-party tool reads it, and you open it in Bing Webmaster Tools directly.

For how often the assistants themselves, Microsoft Copilot included, name your brand, see AI visibility.

Connecting Bing Webmaster Tools

Two steps, in the Website's Integrations settings.

The site has to be verified in Bing Webmaster Tools first, which is done in Bing rather than here. If you already have Search Console verified, Bing can import from it.

The first sync runs shortly after you choose the site, and RankX AI syncs nightly after that. To refresh sooner, press Sync now on the Bing connection in the Website's Integrations settings. Anyone who can open the Website can use it.

Disconnecting

Disconnecting removes RankX AI's stored access and deletes the data synced from Bing.

It does not remove the grant at Bing's end, and RankX AI says so rather than implying otherwise: Bing publishes no way for us to revoke a connection on your behalf. To remove it completely, also remove RankX AI from the API access section of your Bing Webmaster Tools account.

When the Bing screen shows no figures

A Bing connection moves through the same states a Google one does, including the easily missed one where the account is connected but no site has been chosen. RankX AI names the state you are in and what to do about it, and it never prints a zero for a connection it cannot read.

Bing adds one state Google does not have: RankX AI reporting that it could not read the connection at all. That is not a verdict about your connection, and no action is offered on it, because every action would act on state that was just read unsuccessfully.

Why traffic data is missing lists every Bing state in full.

One false alarm is specific to Bing and worth knowing before it happens. The current week is incomplete until Bing closes it. Because the grain is weekly, the most recent bucket is a partial week whenever you look at it, and it will rise. That is Bing's reporting rhythm, not a decline.

Driving this from an assistant

Four tools, matching the four kinds of data above: get_bing_performance, get_bing_drilldown, get_bing_crawl_issues and get_bing_keyword_ideas. All four are read-only, all four are free to call, and all four are in the free band of Chat, so an assistant can use them without spending anything.

Each one refuses rather than reporting zero when Bing is not connected, or is connected with no site selected. That refusal names the state, because an agent told "0 clicks" will report a traffic collapse and an agent told "not connected" will tell you to connect it.

"How is my site doing on Bing over the last 12 weeks, and which pages can Bing not read? Quote the date on the crawl issues."

See the tool reference.

Where to go next

• Search Console, for the Google half and the daily grain this one is weekly against.
• Indexing, for whether Google has your pages, which is the same question this screen answers for Bing.
• Why traffic data is missing, for every connection state and what to do about it.
• AI visibility, for how often assistants actually cite you, which Bing does not report.
• The tool reference, to drive all of this from an assistant.

Last updated 1 October 2026