Bing Webmaster Tools Guide: Verification, URL Inspection, and IndexNow
Why Most Site Owners Ignore Bing (and Why That's a Mistake)
Ask a room full of site owners about search tooling and you'll hear the same answer: Google Search Console, maybe Ahrefs, done. Bing Webmaster Tools sits unopened in a forgotten browser tab. That habit costs you traffic. Bing is the default search behind Windows, Edge, and Microsoft Copilot, and its index feeds a meaningful slice of the AI answers people actually read now. If your site isn't in Bing's index, those surfaces simply cite someone else.
The fix is cheap. Bing Webmaster Tools (BWT) is free, open to any site, and most of it can be automated: verify ownership, submit a sitemap, inspect individual URLs, then wire up IndexNow so every new or updated page gets pushed to the search engine instead of waiting to be discovered. This guide walks through the whole chain in the order you'd actually do it, with the official documentation linked and the failure modes called out before you hit them.
Step 1: Sign Up and Verify Ownership
Log in with any Microsoft account at bing.com/webmasters and add your site. BWT supports four verification methods (official docs: Add and Verify site, verified 2026-10-16):
- DNS auto-verification via the Domain Connect standard — BWT detects your DNS provider and inserts the CNAME for you, done in seconds to minutes;
- XML file authentication — upload a BingSiteAuth.xml file to your site root;
- Meta tag authentication — paste a <meta> tag with your verification code into your homepage <head>;
- CNAME record to DNS — add the record manually at your registrar.
For static sites or edge-rendered apps, the XML file or meta tag route is fastest. If you control the domain's DNS, the CNAME is a set-and-forget option. One caveat people learn the hard way: Bing periodically re-validates ownership, so don't delete the verification file or DNS record after the first success.
Already verified in Google Search Console? There's a legitimate shortcut. BWT can import your site directly from GSC — sign in with your Google account, authorize, and the site plus basic configuration carry over. No re-verification ceremony required.
Step 2: Submit Your Sitemap
Once verified, head to the Sitemaps panel and submit /sitemap.xml. Bing's own Webmaster Guidelines (verified 2026-10-16) list exactly four URL discovery channels: IndexNow submissions, XML sitemaps, crawlable internal links, and external links from relevant sites. The sitemap is one channel among four, but it's the cheapest one to get right.
A few rules of thumb. Only include final 200-status canonical URLs — no 301 redirects, no 404s, no parameterized duplicates. After a migration or redesign, refresh the sitemap and resubmit. Large sites should split sitemaps by directory or language rather than dumping tens of thousands of URLs into one file. If you're mid-migration and watching rankings wobble, our earlier guide on surviving a site migration with 301s and sitemaps covers the URL-mapping side in detail.
Step 3: Diagnose Indexing with URL Inspection
Submission isn't a finish line. When a URL stubbornly refuses to show up in Bing results, open URL Inspection (official docs: URL Inspection, verified 2026-10-16). It returns three cards:
- Index card — when the URL was discovered, crawled, and indexed; if it's not indexed, the reason and a suggested fix appear here;
- SEO card — the page scanned against Bing's SEO best practices, with issues color-coded red/yellow/blue for high/medium/low priority, each with a "how to fix" popover;
- Markup card — whether your structured data (microdata, JSON-LD, and friends) parses cleanly.
Then there's the Live URL tab, which sends Bingbot to fetch the page right now and shows you the HTML and HTTP response exactly as the crawler sees it. This is the tool for hunting stale CDN caches and user-agent-dependent output. Note that Live URL does not follow redirects — it reports the redirect and the destination URL, and you inspect that destination yourself. Once things look right, you can request indexing directly from the tool, consuming your daily quota.
Step 4: IndexNow — Stop Waiting to Be Crawled
IndexNow is an open protocol co-founded by Bing and adopted by Yandex, Seznam, and Naver, among others: one submission, multiple engines notified. The mechanics are simple. You host a key file at your site root to prove ownership, then every time content is added, updated, or deleted, you ping the engine's IndexNow endpoint, and Bingbot prioritizes the crawl.
Bing now recommends IndexNow as the primary submission method. The legacy manual URL submission and URL Submission API still work, but the official documentation notes they may be deprecated as IndexNow adoption grows (official docs: URL Submission, verified 2026-10-16).
How to Implement It
- Generate a key: 8–128 hexadecimal characters (a-f, 0-9), one per site;
- Host the key file: put
{your-key}.txtin your site root, containing exactly the key, UTF-8 encoded. This root-location setup is what the protocol docs call Option 1 and what they strongly recommend. Hosting the file in a subdirectory forces you to pass keyLocation on every submission, and the key only covers URLs under that directory; - Send notifications: for a single URL, a plain GET to
https://www.bing.com/indexnow?url=...&key=...; for batches, POST JSON:
POST /indexnow HTTP/1.1
Content-Type: application/json; charset=utf-8
Host: api.indexnow.org
{
"host": "www.example.com",
"key": "your-key",
"keyLocation": "https://www.example.com/your-key.txt",
"urlList": [
"https://www.example.com/url1",
"https://www.example.com/url2"
]
}
Full protocol reference: IndexNow Documentation (verified 2026-10-16). Response codes decode as follows: 200 means received successfully; 202 means accepted with key validation still pending asynchronously; 400 is a malformed request; 403 means the key didn't validate; 422 means the URLs don't belong to the declared host; 429 means you're submitting fast enough to look like spam. Batches cap at 10,000 URLs per request, and every URL must share the key's host. For a worked example of wiring IndexNow into a Cloudflare-hosted Astro site, see our earlier walkthrough on enabling IndexNow on Astro behind Cloudflare.
Integration Options
If your site sits behind Cloudflare, you can flip on automatic IndexNow submissions from the dashboard. WordPress ships an official plugin; Shopify, Joomla, Drupal, and most mainstream platforms have integrations listed on the protocol's site. Teams with a custom publish pipeline — this site runs on Cloudflare Workers — can just POST from a deploy hook, which is the cleanest option. The IndexNow tab inside BWT shows submission volume over time, the source of each submission (self, plugin, CDN), and a near-real-time sample URL list, so you can confirm the integration actually fires.
Step 5: Learn to Read the Dashboards
- Search Performance — impressions, clicks, and average position, drillable by query and by page, close in spirit to GSC's performance report;
- Site Explorer — URL-level analysis: which pages are indexed, which have errors, and what the error types are;
- SEO Reports / Site Scan — site-wide audits grouped by issue type;
- Backlinks — link profile overview with anchor text distribution.
One expectation to calibrate: the tools are free, but Bing guarantees nothing. The official support docs say it plainly — a newly published URL can take weeks to surface, and pages that don't meet quality thresholds simply won't get indexed.
Step 6: Put Bingbot on a Schedule
When a small server can't take the crawl load, Crawl Control lets you set Bingbot's crawl rate hour by hour (official docs: Crawl Control, verified 2026-10-16). Slow it down during your traffic peaks, open it up at night, pick your timezone, or apply one of the presets to generate an inverse pattern automatically. Priority rule worth memorizing: a Crawl-delay directive in robots.txt always overrides the panel setting. Keep the two from fighting each other.
Risks and Limits, Stated Plainly
- IndexNow is notification, not indexation. The engine still decides what to crawl and index by its own criteria. Hammering submissions won't rescue thin pages, and a 429 can trigger anti-spam handling;
- The key is an ownership credential. A leaked key lets anyone submit URLs on your site's behalf. Root directory is fine; a public repo is not;
- Prefer streaming over batch dumps. The official guidelines recommend submitting as content changes rather than accumulating large batches;
- Ownership gets re-validated periodically; deleting the verification file or DNS record cuts off your dashboards;
- robots.txt blocks mean no indexing. Run changes past BWT's robots.txt tester before pushing them live.
FAQ
Is a 202 response from IndexNow a success?
Mostly yes. It means the request was accepted and key validation happens asynchronously, which is the path most normal submissions take. The failures are 400/403/422/429. To confirm a URL actually entered processing, check the IndexNow report inside BWT.
Do I still need a sitemap with IndexNow?
Yes. They solve different problems: the sitemap is the full map, IndexNow is the incremental "this changed" ping. The official guidelines list both as discovery channels, not alternatives.
Does importing from Google Search Console affect my Google setup?
No. Import copies site info and basic configuration into BWT. Your Google account, data, and settings are untouched.
What's the daily URL submission quota?
Manual submission and the URL Submission API each allow 10,000 URLs per domain per day, resetting at midnight UTC, counted at the domain level with subdomains sharing the pool; you can request an increase through a BWT support ticket. IndexNow batches also cap at 10,000 URLs per request.
Indexed in Bing but not showing in search — why?
Run URL Inspection first to confirm index status. Then check whether the page was consolidated under a different canonical URL as duplicate content, whether robots rules block serving, or whether the quality signals are just weak. Being indexed and ranking are separate things.
A Note on Running Two Dashboards
Plenty of teams have both toolsets installed and no idea what each one is for. The short version: GSC covers Google's discovery, indexing, and performance data; BWT covers Bing's. The numbers won't reconcile — impressions and clicks from the same period will differ between the two, because the audiences, geographies, and ranking systems differ. Track them separately and compare each against its own history, not against each other.
As for cadence, fold a BWT review into a monthly routine: check Search Performance for sudden drops, scan Site Explorer for new error pages, and see whether IndexNow submission volume matches actual crawl volume. A crawl rate that sits far below submission volume for months usually points to weak quality signals or a slow site — more diagnostic than the raw index count will ever be.
Wrapping Up
Bing Webmaster Tools is chronically undervalued: free, open, automatable, and plugged into the Edge, Windows, and Copilot surface area. Verify the site, submit the sitemap, wire up IndexNow, and review the URL inspection report once in a while — that's an afternoon of work. After that, the lag between hitting publish and appearing in Bing's index shrinks noticeably. For anyone running content sites or cross-border e-commerce, it's one of the few pieces of infrastructure with an obviously lopsided return on effort.