IndexNow Payload Builder
Prepare one IndexNow change notification batch before sending it from your own authorized client. Enter an owned host, a temporary key to check its format, and changed URLs. This tool checks the batch in your browser and produces an intentionally incomplete JSON request template. It never submits a request.
Key features
- Check HTTP(S) URLs against one host and reject repeated or malformed rows
- Apply the IndexNow limit of 10,000 URLs per POST batch
- Check optional key-file directory scope before constructing the template
- Keep the temporary key out of results, clipboard output and downloads
- Download a separate unsent submission record with event counts
How to use
- Enter the host you own and a temporary IndexNow key. Optionally enter a custom key-file URL.
- Paste one changed URL per line, using added, updated or deleted before a comma when you need an event label.
- Validate the batch and correct every line-specific error before reviewing the JSON template.
- Replace the key placeholder in your own authorized HTTP client, publish the matching key file, and record the actual response yourself.
Use cases
- Prepare a post-release batch of added and updated product URLs.
- Catch a URL on another subdomain before attempting a notification.
- Review whether a custom key file under /catalog/ covers every changed URL.
- Keep a blank response record for a later manual IndexNow submission.
Frequently asked questions
Does this send URLs to Bing, Naver, or IndexNow?
No. It validates user-supplied rows locally and provides a JSON template only. There is no network submission, search engine response or indexing guarantee. The IndexNow protocol is supported by participating search engines; that alone does not establish Naver support.
Why does the exported JSON contain a key placeholder?
The key input is used only for format and disclosure checks, then cleared. No export, copied template or submission record contains the key. Replace the deliberately invalid placeholder only in your own authorized request client.
How do I prove ownership of the host?
The IndexNow protocol requires a UTF-8 text key file on the host. Its root option uses a file named after the key. A custom keyLocation may be used for a narrower directory, but this tool cannot verify that the file is publicly reachable or contains the key.
Can one POST contain both HTTP and HTTPS URLs?
Yes, if they belong to the same host. IndexNow permits up to 10,000 URLs in one POST and allows both schemes. Non-default ports, credentials, fragments, malformed escapes and URLs on another host are rejected here.
What do added, updated and deleted mean in the template?
They are local labels for your submission record. The IndexNow POST body has host, key, optional keyLocation and urlList; it has no separate event field. A deleted URL is still a URL in the list.
Does a successful IndexNow response mean a URL is indexed?
No. An HTTP 200 means the notification was received; HTTP 202 can mean key verification is pending. Crawling and indexing remain search engine decisions. This tool makes no request and observes neither response.
Privacy
The key is read only for local validation and cleared immediately. It is never placed in React state, localStorage, exported JSON, the clipboard template or the submission record. URLs and host stay in this page until you leave or clear it. Nothing is submitted automatically.
Comments & questions