IndexNow
Tell Bing, Yandex, Seznam, Naver and other IndexNow search engines about new, changed or deleted URLs the moment they change.
IndexNow is an open protocol for notifying search engines that a URL changed. One submission from RankParse goes to api.indexnow.org, which shares it with every participating engine (Bing, Yandex, Seznam, Naver and others). RankParse submits to IndexNow only; it does not submit to any other search engine.
| Operation | Endpoint | Credits |
|---|---|---|
| Create an IndexNow key | POST /v1/indexnow/key | 0 |
| Submit URLs | POST /v1/indexnow | 1, refunded on failure |
How it works
Add the website
The host you submit must be one of your RankParse websites, or a subdomain of one. Add it in the dashboard under Sites with Add website. Submissions for any other host fail with indexnow_host_not_a_website.
Get a key
Call POST /v1/indexnow/key?domain=example.com. You get back a key and the exact URL where it must be hosted. The call is free and returns the same key every time for the same host.
Host the key file
Publish a UTF-8 text file containing exactly the key at the key_location from the previous step: https://example.com/<key>.txt. This proves to search engines that you control the host.
Submit URLs
Call POST /v1/indexnow with up to 1000 URLs from that host. On the first submission (and then at most once a day) RankParse fetches the key file to check it before sending.
Keys and hosts
- A key belongs to one workspace and one host, and it is never rotated, so a key file you have published stays valid.
example.comandwww.example.comare different hosts and get different keys. Create the key for the exact host in the URLs you submit, subdomains included.- The key is 32 lowercase hexadecimal characters. Only your workspace can retrieve it.
Key file verification
Before a submission, RankParse requests https://<host>/<key>.txt with a 30 second timeout and requires an HTTP 200 whose body, with leading and trailing whitespace trimmed, equals the key. A file over 4 KB is treated as not a key file. A successful check is cached for 24 hours, so steady-state submissions skip it. If IndexNow later rejects the key (indexnow_key_rejected), the cache is cleared and the next submission checks the file again.
Agents and the approval inbox
In a workspace that uses the approval inbox, a submission made by an AI agent through the RankParse MCP server becomes a proposal you approve, unless your policy for that website allows automatic submission. See Submit URLs.
MCP tools
| Tool | Where | Purpose |
|---|---|---|
provision_indexnow_key | API-key MCP server | Get or create the key for a host (accepts domain, 0 credits). |
submit_indexnow_urls | API-key MCP server | Submit URLs on one host (accepts urls, 1 credit, refunded on failure). In an approval-inbox workspace it can return a pending proposal instead. |
propose_indexnow_submit | API-key MCP server and secure OAuth connector | Ask the user to approve a submission (accepts urls, optional site_id and note). Always goes through the inbox: 0 credits to propose, 1 credit only when it runs. |
The secure OAuth connector cannot call POST /v1/indexnow/key or POST /v1/indexnow; it can only propose. See MCP Server.