Utill.net

IndexNow API Key Generator

Hex Key File

Generate a random hexadecimal IndexNow API key online for Bing/Yandex URL notifications and key-file setup.

This conversion runs only in your browser — nothing is uploaded.

IndexNow lets your site notify Bing, Yandex, and other engines when URLs change—this hex key proves ownership.

  • Length—
  • Hex0-9a-f

Next steps

  1. Host the key file at https://your-domain/{key}.txt with a body that is exactly the key (hex only).
  2. Include the same key in IndexNow GET/POST URL notification requests.
  3. If you rotate the key later, update the hosted file and every notifier together.

Save this key as a .txt file at your domain root: https://yourdomain.com/{key}.txt

What is this tool?

This IndexNow key generator creates a random hexadecimal API key for the IndexNow protocol. Participating search engines (including Bing and Yandex) accept authenticated URL change notifications so they can recrawl faster after publish, update, or delete events.

The key is not a password for your CMS—it proves that notification requests are authorized by the site owner. In the common setup you host {key}.txt at the domain root with a body that is exactly the hex string, then send the same key in IndexNow GET or POST calls.

Generation uses the browser's cryptographic RNG. The value never leaves your device from this page; you still need to deploy the file and wire notifiers in your stack.

Common use cases

  • Bootstrap IndexNow for a new site, CMS plugin, or static-site deploy hook
  • Rotate a leaked or shared key without guessing hex by hand
  • Produce a compliant 8–128 character key before writing a custom ping script

How to use

  1. Keep the default length (32) or choose 8–128 hex characters with the slider (changing length regenerates).
  2. Copy the key and the recommended {key}.txt file name.
  3. Publish the file so its body is exactly the key (hex only, no BOM or trailing newline preferred by strict checkers).
  4. Configure Bing/Yandex/IndexNow notifiers with the same key, then ping changed URLs after deploy.

Examples

SettingExample key / fileNotes
Length 8 (minimum)a1b2c3d4 → a1b2c3d4.txtShortest IndexNow-allowed hex key.
Length 32 (default)e3b0c44298fc1c149afbf4c8996fb924 → {key}.txt at site rootPractical length for most plugins.
Odd length 94f8a91c2b → 4f8a91c2b.txtLength need not be even; file body must still match exactly.
Length 128 (maximum)128 hex chars → {key}.txtUpper bound; longer values are rejected by the protocol.

Practical pitfalls

  • Key rotation breaks silent notifiers: Regenerating the key without updating every CMS plugin, CI job, and sitemap ping leaves engines rejecting submissions while an old {key}.txt may still look valid to humans.
  • Whitespace or encoding in the file body fails ownership checks—save raw hex only (no Markdown, quotes, or UTF-8 BOM).
  • IndexNow speeds discovery; it does not guarantee ranking or immediate indexing.

References

Last reviewed: 2026-07-27

Frequently asked questions

What is an IndexNow key?
A site-owned hexadecimal string that proves URL update notifications come from your domain. You host it in a key file and include the same value in IndexNow GET/POST requests.
How long should the key be?
IndexNow allows 8 to 128 hex characters. A 32-character key is a practical default for most CMS plugins and deployment scripts.
Where do I host the key file?
Publish a text file whose name is `{key}.txt` and whose body is exactly the key (no extra whitespace), usually at `https://your-domain/{key}.txt`. Some setups use an alternate `keyLocation` URL—follow the IndexNow docs.
What happens if I regenerate or rotate the key?
Engines will reject notifications until the new key file is live and every notifier (CMS plugin, CI job, sitemap ping) uses the new value. Remove or replace the old `{key}.txt` so stale credentials cannot linger.
Is the generated key uploaded?
No. It is created with the browser's cryptographic random number generator and stays on your device.