What IndexNow Is
IndexNow is a protocol that lets you tell participating search engines that a URL has changed, instead of waiting for a crawler to discover it. A submission is a single HTTP request containing your URLs and a key that proves you control the domain.
That is the entire mechanism. There is no dashboard to log into and no quota to manage, which is why the setup is genuinely short and why so few sites bother to do it.
Why It Matters for AI Citation
ChatGPT search leans on the Bing index. Bing supports IndexNow. That chain is the whole reason this protocol is worth an hour of your time in 2026, and it is a connection most SEO advice still does not draw.
The shortest path from publish to citeable
If a page is not in the Bing index, it is not available to be cited by the assistants that read from it. IndexNow removes the discovery delay from that path, which is frequently the longest part of it.
Google Does Not Participate
Be clear about this so you do not build the wrong expectation. Google does not use IndexNow. Your sitemap and Search Console remain the mechanism for Google coverage, and nothing here replaces them.
This is a Bing and Yandex protocol with a valuable side effect. That side effect happens to matter more in 2026 than the protocol itself did when it launched.
Setting It Up in Four Steps
Generate a key
A random hexadecimal string. It is not a secret in the security sense, it is a proof of control, so treat it as a public identifier rather than a credential.
Host the key file at your domain root
A plain text file whose name is the key and whose contents are the key. This is how the receiving engine verifies that whoever is submitting URLs actually controls the domain.
Send a submission when something changes
One request listing the changed URLs and the key. A single URL or a batch, both work the same way.
Confirm you get an accepted response
An immediate acknowledgement means the submission was well formed. It does not mean the page is indexed, which is a separate decision made on merit.
Automating It Properly
The version of this that keeps working is the one nobody has to remember. Tie the submission to the act of publishing, so that a deploy which changes content fires the request without a human deciding to.
On a static site the natural trigger is the build finishing and the sitemap changing. Watch the sitemap for real changes rather than firing on every deploy, because a deploy that touched only styling has nothing to announce.
What It Does Not Do
It does not force indexing
Submission removes the discovery delay. It does not overrule a decision not to index. A page that would not have earned a place still will not get one.
It does not help with Google
No participation, no effect. Treat any tool that implies otherwise with suspicion.
It does not fix a blocked crawler
If your robots.txt or CDN refuses the crawler, announcing a URL to it changes nothing. Check access first.
The third one is worth checking before you invest any time here, because an agent that cannot reach your page will not index it however loudly you announce the URL.
The Mistake That Wastes It
Submitting every URL on every deploy. Bulk resubmitting an unchanged site trains the receiving engine to discount your signals, and the responsiveness you set the protocol up to gain is exactly what you lose.
The rule
Submit what changed, when it changed. A protocol whose value is that it tells the truth quickly stops being valuable the moment it starts telling the same thing repeatedly.