What is IndexNow?

Classic discovery rests on waiting: the page is published and you wait for the crawler to come by. IndexNow reverses that — the moment the page is published a notification is sent to the engine and the crawler is called.

Setting it up takes three steps: a key is generated, a text file containing that key is placed at the site root, and changed addresses are submitted to an endpoint. The engine verifies that the notification really comes from the site owner by reading the key file from the LIVE site.

That verification also fixes the running order: the notification has to be sent AFTER DEPLOYMENT. If the key file is not published yet, verification fails and the notification is rejected.

The Bing and Yandex family support it; Google does not, and has said so plainly. In the context of answer engines its value comes through Bing — Microsoft’s answer product is fed by the Bing index.

The most common mistake is submitting every address on every deployment. That turns the “this page really changed” signal the notification carries into noise. A correct setup requires a mechanism that knows which page actually changed.

The return varies by type of site. For a frequently updated publication, shortening the discovery delay is a real gain; on a corporate site updated a few times a year the practical benefit is small.

That the key sits openly at the root is not a security hole but the design itself: verification is only possible while the file is public. Someone who knows the key can only send the information “this page changed”, and there is no value in abusing that.

• Generate the key and keep it — generated once, never changed.
• Put the key file at the root — let it come out of the build, so it is not forgotten by hand.
• Notify AFTER deployment — reverse the order and verification fails.
• Submit only what really changed — submitting every address on every build devalues the signal.
• Watch the outcome — notification records appear in the engine’s webmaster panel.

The fourth item is the rule of the protocol most often broken: the information a notification carries is “this page really changed”, and a signal that reports everything turns into a signal that reports nothing.

Calibrating expectations matters: IndexNow speeds up discovery, it does not guarantee indexing. If a page is crawled quickly and found to be poor, it still will not be indexed. For a site with indexing problems the answer is not this protocol but content quality, and that has to be addressed first.

Where the protocol genuinely makes a difference is elsewhere: on large, frequently updated sites it affects when a crawler returns to which address, that is, on the crawl budget side.

If you want to know how your brand is cited in ChatGPT, Google AI Overviews and Perplexity, our GEO consulting records which questions and engines cite you and builds the prerequisites.