Skip to content
AAA.win
EN
EnglishEN中文ZH日本語JAEspañolES
SearchSubmit a tool
Menu
2026-08-12

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

What changed

01

Kept the canonical sitemap index ready for separate Bing Webmaster submission and added standards-based IndexNow notifications for published URL changes; Google is not an IndexNow notification target.

02

The first enabled run submits the current canonical URL set, while persisted state limits later runs to new, updated, and removed canonical URLs.

03

Kept canonical segmented sitemaps as the durable discovery source; IndexNow complements them and never replaces sitemap publication.

04

Treats provider acceptance only as notification delivery, not proof of crawling, indexing, ranking, or search visibility.

Version · v4.3.6-indexnow-delivery-verified

Latest releases

IndexNow production delivery verification

Verified production IndexNow receipt with a new key: Microsoft's external proof returned HTTP 200, single-URL GET and POST both returned HTTP 200, and eight batches covering 386 canonical URLs each returned HTTP 200 with zero retries. A second run found the inventory unchanged and sent no request.

IndexNow proof-origin protocol fix

Production Bing validation exposed HTTP 500 at the external root proof because TLS termination was followed by an internal rewrite using the wrong protocol. This release corrects that rewrite boundary, but remains unverified until the external proof returns HTTP 200, the automatic submission runs, a later canary returns HTTP 200, and the idempotent rerun passes.

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

View all releases