Skip to content
AAA.win
2026-08-12

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.

What changed

01

Verified the new root key externally through Microsoft's production validation path with HTTP 200 without exposing the key.

02

Confirmed both the single-URL GET and single-URL POST submission shapes returned HTTP 200.

03

Set the production batch size to 50 and received HTTP 200 for all eight batches covering 386 canonical URLs, with zero retries.

04

Confirmed a second run detected an unchanged inventory and sent no request, preserving the persisted idempotent state.

05

The final production verifier reported 69 passes, zero failures, and one AdSense account warning. IndexNow HTTP 200 records receipt only, not crawling or indexing, and the separately submitted Bing sitemap remains processing.

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