Bing Webmaster Tools and the IndexNow Protocol

The plain-language idea

Every search engine that matters works the same way by default: it crawls your site on its own schedule, discovers your sitemap, and re-crawls pages when it estimates they might have changed. You can nudge that schedule — internal links, a fresh lastmod in your sitemap — but you're still waiting for the engine to come pull your content. For a site that publishes or updates content frequently, that lag is real: a price change, a deleted product, a breaking update can sit stale in search results for hours or days.

IndexNow flips that model. It's an open protocol, launched in 2021 and backed jointly by Microsoft (Bing) and Yandex, that lets you push a single URL notification to search engines the moment something changes — instead of publishing content and hoping the crawler visits soon. It's not a "please crawl me" request; it keys directly into a participating search engine's crawl priority queue.

Bing Webmaster Tools is where this actually starts for most sites, since it's also the site-verification hub IndexNow submissions get checked against.

See it in a real thing: verifying with Bing, then pushing a URL via IndexNow

Bing Webmaster Tools verification (pick one — meta tag, DNS, XML file upload, or importing an existing Google Search Console verification):

<!-- Meta tag method — placed in <head> -->
<meta name="msvalidate.01" content="YOUR_BING_VERIFICATION_CODE" />

# DNS method — a CNAME record pointing at the value Bing gives you.
# Usually the most durable since it lives at the domain level, but can
# take anywhere from minutes to 48 hours to propagate.
_bing-verify.yourdomain.com  CNAME  <value-from-bing>

Once verified, generate a 32-character hex API key, host it as a plain-text file at your domain root (content is just the key itself), and push URL changes directly:

// Single URL — a plain GET request
await fetch(
  "https://api.indexnow.org/indexnow" +
    "?url=https://yourdomain.com/blog/new-post" +
    "&key=a1b2c3d4e5f67890a1b2c3d4e5f67890"
);

// Batch — POST with a JSON body, for many changed URLs at once
await fetch("https://api.indexnow.org/indexnow", {
  method: "POST",
  headers: { "Content-Type": "application/json; charset=utf-8" },
  body: JSON.stringify({
    host: "yourdomain.com",
    key: "a1b2c3d4e5f67890a1b2c3d4e5f67890",
    keyLocation: "https://yourdomain.com/a1b2c3d4e5f67890a1b2c3d4e5f67890.txt",
    urlList: [
      "https://yourdomain.com/blog/new-post",
      "https://yourdomain.com/products/discontinued-item",
    ],
  }),
});

One submission to api.indexnow.org fans out to every participating engine — you don't call Bing and Yandex separately.

Watch out

• IndexNow is push, a sitemap is pull. A sitemap is a big list the engine chooses when to re-read; IndexNow is one HTTP call the instant a URL is created, changed, or deleted. They're complementary — keep the sitemap as the source of truth and use IndexNow for low-latency notification.
• Google is not on the list. This is the single most commonly wrong assumption about IndexNow — it's easy to default-assume "search engines" means Google. Verify support per-engine before promising a result.
• The key file is the actual ownership proof, not the key value alone. What makes the protocol trustworthy is that the key must also be hosted as a retrievable file at a URL on the domain being submitted for — the engine fetches it back to confirm you control that host.
• It covers deletions too, not just new/updated content. Submitting a URL that now 404s or has been noindexed is a legitimate IndexNow call — a signal to deprioritize recrawling it, not only a "here's something new" mechanism.
• This is not the same as Bing Webmaster Tools' manual "Submit URL" button. That's a rate-limited, one-at-a-time UI action; IndexNow is the underlying protocol, automatable from a CI/CD publish hook or a CMS's save event.

Why this matters in interviews

Most frontend developers have submitted a sitemap and never gone further, so explaining the mechanical difference between a pull-based crawl and a push-based notification — and naming IndexNow specifically, with the honest caveat about Google not supporting it — signals you've implemented real indexing infrastructure rather than repeated SEO vocabulary. It's also a good test of whether a candidate overclaims: someone who says "IndexNow gets Google to index instantly" is repeating a myth, not describing the protocol.