Bing Webmaster Tools integration
Connect Bing Webmaster Tools to your Clickport site and the search queries that drive Bing traffic show up directly inside your Sources panel. You get the keywords, ranking positions, click-through rates, and impressions next to your visit data, in the same dashboard you already use.
What you see in the dashboard
Once connected, a new Bing sub-tab appears in the Sources panel, between GSC and URLs. It lists your top search queries with clicks, impressions, CTR, and average position. Each column is sortable. Long queries truncate with a hover tooltip that shows the full text. The Show More button at the bottom loads another 50 keywords.
The tab only appears for sites that have an active integration. Sites without BWT connected won't show the tab, so dashboards stay clean.
How to connect
Setup is one-paste, no OAuth dance. Bing Webmaster Tools uses a per-account API key that you generate in your BWT dashboard. The key works for every site verified under that account.
- Add and verify your site at Bing Webmaster Tools. Any of Bing's verification methods works (XML file, meta tag, DNS).
- In BWT, click the gear icon (top right) → Settings → API access. Or open the API access page directly.
- Click API Key → View API Key. Bing displays a 32-character key (or shows a Generate button if you don't have one yet). Copy it.
- In Clickport, open Settings → Integrations for the site you want to connect. On the Bing Webmaster Tools card, click Connect with API key and paste the key.
- If the key is valid, you'll see a dropdown of every site verified under that BWT account. Pick the one matching this Clickport site and save.
After saving, the card switches to a connected state showing which BWT site is linked.
Filtering
BWT's API exposes far fewer filter dimensions than Google's. Most dashboard filters can't translate.
- Page filter works. If you filter the dashboard to a specific page, the Bing tab shows queries that drove Bing clicks to that exact landing page (using BWT's
GetPageQueryStatsendpoint). - Search box inside the Bing tab filters the loaded keywords client-side. Useful for spotting brand variations or long-tail patterns inside a large keyword list.
- Country, device, source, and channel filters from the main dashboard don't apply. BWT's query endpoint doesn't expose those dimensions. Active dashboard filters of these types show as a "filter not applied" notice above the keyword table.
Why date ranges don't apply
You'll notice the Bing tab ignores whatever date range you've picked on the dashboard. It always shows rolling 6-month aggregates. This is a limitation of BWT's API, not a choice we made.
Microsoft's GetQueryStats endpoint returns one aggregate row per query covering the last 6 months. There's no way to pass start/end dates — Bing doesn't accept the parameters. The only date-segmented endpoint, GetRankAndTrafficStats, returns site-wide daily totals but doesn't break down by query, so it can't power a keyword list. There's also GetQueryTrafficStats which returns daily data for one specific query, but using it to populate a list of top keywords would require hundreds of round-trips and Bing would rate-limit the request.
If Microsoft adds date parameters to their query endpoints in a future API release, we'll honor them. For now: rolling 6 months, full site, no slicing.
Coverage across the Bing-indexed search engines
One thing worth getting precise on: BWT click and impression counts are Bing-specific. When DuckDuckGo, Ecosia, or Brave Search sends a visitor to your site, that click happens on those engines' interfaces and isn't counted in your BWT dashboard. Microsoft only sees clicks that originated on Bing.com.
What is shared across all five engines is the index — the underlying database of pages and rankings. DuckDuckGo, Ecosia, Yahoo, and Brave Search all use Bing's index. So when BWT tells you your page ranks #3 for "linen sheets", that ranking is the same on those four engines too, because they're displaying the same results.
Practically: use the queries and rankings from the Bing tab as a leading indicator for all five engines. Use the clicks and impressions as Bing-specific volume metrics. Your full Bing-family search traffic (Bing + DDG + Ecosia + Yahoo + Brave) is still captured in Clickport's regular Sources panel under the respective source names.
SEO use cases
The combination of Clickport's per-page engagement metrics and BWT's keyword data lets you ask questions worth answering:
- Which Bing-family keywords drive your most engaged visitors? Filter to a page that ranks well on Bing and check its engagement score in your Sources panel. A keyword ranking #3 but converting badly tells you the page-keyword fit is off.
- Where are you close to page-one on Bing? Sort the Bing tab by Position ascending and filter to ranks 8-15. Those are the keywords where a content update could push you up. The same content improvement boosts your ranking on DuckDuckGo, Ecosia, Yahoo, and Brave Search simultaneously.
- Which queries does Bing rank you for that Google doesn't? Open the Bing and GSC tabs side by side. Queries that show up only in Bing are opportunities — usually the indexes have different content emphasis.
- Is your DuckDuckGo traffic worth optimizing for? Check the regular Sources panel for DDG volume. If it's meaningful, your Bing rankings are doing the work; the Bing tab tells you which keywords to optimize next.
Disconnecting
Click Unlink BWT in the Integrations card to remove the connection. Clickport deletes the encrypted API key from our database immediately. The setting is per-site, so unlinking one site doesn't affect any other site you've connected.
The API key itself remains valid on Bing's side until you regenerate it in BWT. If you want to fully invalidate the key (because you're rotating credentials, for instance), go to BWT's API access page and click Generate to replace it.
Troubleshooting
"That API key didn't work"
Bing rejected the key. Most common causes: typo or trailing whitespace on paste, or the key was regenerated in BWT after you copied it. Open BWT → API access, click View API Key, copy fresh, and try again. If it still fails, click Generate to make a new key and retry.
"No sites verified under this BWT account"
Your Bing account has no verified properties yet. Add your site at bing.com/webmasters, complete the verification step (XML file, meta tag, or DNS record), wait a few minutes for verification to clear, then retry the connect flow.
"InvalidUrl" or empty page-filter results
Bing's per-page endpoint only knows about pages that have received clicks from Bing-indexed search in the last 6 months. If you filter by a page that's brand new, has no Bing traffic, or has a URL Bing doesn't recognize (canonical mismatch, redirect, etc.), the endpoint returns empty or errors out. Remove the page filter to verify the connection works on the full site view.
"Bing-family source rows auto-jump to the Bing tab — should they?"
By design. Clicking on Bing, DuckDuckGo, Ecosia, Yahoo, or Brave Search as a source filter takes you to the Bing tab because the keyword data there represents the rankings driving traffic from all five engines (Bing's index powers all of them). The Bing tab notice reminds you that click counts are Bing-only.
Privacy and data handling
Clickport stores two things for the BWT integration:
- Your BWT API key, AES-256-GCM-encrypted at rest with a key that lives in our server environment, never in our database backups or version control.
- The BWT site URL you selected.
We never store keyword data — every keyword view is a live query to Bing with a short response cache. We never modify your Webmaster Tools data: the API key only grants read access. Unlinking from Settings deletes the encrypted key immediately. See the privacy policy for full details.