IndexNow API key generator
This page makes an IndexNow API key in your browser. Press the button and it produces a random key, the name of the file to publish, what goes in that file and the address it has to be served from. The key is made on your device and is not sent to this site or anywhere else.
Generate an IndexNow key
The key comes from crypto.getRandomValues, the random source built into your browser. By default it is 32 lowercase hexadecimal characters, and the length box accepts anything from 8 to 128. The protocol sets only the range, so 32 is this page's default and not a protocol recommendation.
Without JavaScript, or if you would rather use a terminal, three lines do the same. The first makes 32 hexadecimal characters, the second writes the file, named after the key and holding nothing but the key, and the third prints the key so you can copy it into your submissions:
KEY=$(openssl rand -hex 16)
printf '%s' "$KEY" > "$KEY.txt"
echo "$KEY"What to put in the key file
The file is plain text in UTF-8 and holds the key itself, with nothing else in it. Its name is the key followed by .txt, and the name and the content have to agree exactly. For the placeholder example-key-1234abcd the file is example-key-1234abcd.txt, and its whole content is one line:
example-key-1234abcdThe same key goes into the key field of every submission; the request format shows where. The protocol allows 8 to 128 letters, digits and dashes, so a key from any other source works the same way.
Where to publish it
Serve the file from the root of the hostname it is for, at https://your-hostname/<key>.txt. The protocol also accepts another location on the same hostname when the submission names it in keyLocation, but it strongly recommends the root: a file placed in a folder covers only the addresses under that folder.
Every hostname needs its own file: a key that answers on example.com proves nothing about www.example.com. What the key proves explains why, and why the file is public by design.
Check it before you submit
Publishing is the step that fails quietly: a redirect rule or a framework page can answer in place of the file while the site keeps working for visitors. Request the file the way an engine does, over HTTPS and without following redirects:
curl -si "https://your-hostname/<key>.txt"How to check your IndexNow key file lists the four answers that request can return. Once the file comes back as plain text holding the key, the IndexNow submission tester builds the commands for a first submission of one address, and submitting by hand covers where the key is used.
If your hostname is on Bridge CDN
On Bridge CDN the edge serves the key file at your own hostname, so there is no file to publish by hand, and a key made on this page is for a hostname where you place the file yourself. IndexNow at the edge describes that route.
FAQ
What characters can an IndexNow key contain, and how long should it be?
The protocol allows 8 to 128 letters, digits and dashes and names no best length inside that range. The generator makes lowercase hexadecimal characters, which sit inside the set, and the file name and file content have to match the key exactly.
Is the generated key stored anywhere?
No. Your browser makes the key with crypto.getRandomValues and shows it on the page. The script that does it, /js/tools.js, makes no network request, so nothing is sent to this site or anywhere else. Leave the page or press the button again and the key is gone, so copy it before you do either.
Is the IndexNow key a secret?
No. The key proves control of a hostname by being served from it, and anyone, including every participating engine, has to be able to fetch it. It is public by design, for the reasons on the key file.