The site generates a key, hosts it as a text file on its own domain to prove ownership, and then sends the changed URLs in a simple HTTP request. One request can carry a single URL or a list.
It is a notification, not a request to be indexed. The search engine still decides whether to crawl the URL, when, and whether to keep it. IndexNow can shorten the time before a change is seen; it cannot make a thin page worth indexing. Not every search engine takes part, so check each engine’s own documentation rather than assuming.
The useful habit is to ping from the same place that knows what changed. A deploy step that sends the sitemap’s URLs, or a publish action that sends the one page that was published, keeps the notifications accurate. Pinging URLs that are noindex, redirected or gone sends the wrong signal, so the list should come from the same rules as the sitemap.
IndexNow does not replace a sitemap. The sitemap is the full list of pages you want indexed; IndexNow is a change log on top of it. Pinging without keeping the sitemap correct gains little, because the crawler still finds the stale URLs through the sitemap and the links.
An example from our own work
Production deploys of audacian.eu ping IndexNow with the sitemap’s URLs, and the sitemap lists only indexable pages, so noindex pages are not announced. Videojam, our own video platform, pings IndexNow when pages are published, as part of the same indexation gate that decides which pages go into its sitemap and llms.txt. In both cases the ping tells participating engines what changed. It does not decide whether they crawl it, and we do not report it as a result on its own.