Skip to content
AAA.win
2026-08-12

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.

What changed

01

Confirmed that the exact root-level https://aaa.win/{key}.txt proof returned HTTP 200 without exposing the production key.

02

Observed that a full request carrying keyLocation still returned HTTP 403, while a minimal homepage request using the same production key and omitting keyLocation returned HTTP 202.

03

Removed keyLocation from root-proof submissions to use the default root-directory verification mode; the production key is unchanged and remains server-only.

04

Treats HTTP 202 only as receipt for processing, not proof of crawling or indexing; an automatic full submission followed by an unchanged idempotent rerun remains a deployment gate, so this release does not claim that the full inventory succeeded.

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