Submit URL change notifications to Bing and Yandex via the IndexNow protocol instead of waiting for organic recrawl
domain: indexnow.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an IndexNow key and host it as a UTF-8 text file named {key}.txt at your site's root (or specify a custom keyLocation)
For single URLs, GET or POST to a participating endpoint (e.g. api.indexnow.org, bing.com/indexnow, or yandex.com/indexnow) with url and key parameters
For bulk changes, POST a JSON payload with host, key, keyLocation, and a urlList array (all URLs must share the same host as the key)
Trigger submission automatically from your CMS/publish pipeline on create, update, or delete events rather than batching stale URLs
Check the HTTP response code (200/202 success; 400/403/422/429 indicate key, format, or rate problems) and log failures for retry
Known gotchas
IndexNow is adopted by Bing, Yandex, and several smaller/AI search engines but Google does not consume IndexNow submissions, so it is not a substitute for Search Console sitemap/Indexing API workflows
All submitted URLs must be on the same host as the hosted key file, or the request is rejected
Submitting a URL via IndexNow only asks engines to recrawl it soon; it does not guarantee or expedite indexing decisions
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?