Bing URL Submission: Submit URLs Through IndexNow, Fix IndexNow Errors, and Confirm Bing Coverage

Why Bing is worth the ten minutes it takes

Bing gets treated as the engine you set up last, if at all, and that made sense when it was a rounding error. It is not one anymore. Bing powers its own search, DuckDuckGo, Ecosia and a chunk of the answers that Copilot and other AI assistants return, so a page missing from Bing is missing from more places than the name suggests. For a US business audience that increasingly asks an assistant instead of scrolling a results page, that reach is buyer traffic you are leaving on the table.

The other reason is effort. Bing submission is genuinely easy through IndexNow, and once it is wired up it runs on its own. There is very little downside to covering an engine that costs a few minutes to set up and quietly feeds several of the places your buyers now look.

IndexNow is the fast lane, and Google is not on it

IndexNow is the protocol Bing built for exactly this: you notify it the instant a URL is published or changed, and it crawls sooner instead of waiting to rediscover the page. One submission reaches every participating engine, currently Bing, Yandex, Seznam and Naver, and you can send up to 10,000 URLs a day. Push too many too fast and you get a 429, which just means slow down, not that anything is wrong.

The catch worth stating plainly: Google does not participate in IndexNow. Submitting to IndexNow does nothing for your Google coverage, and submitting to Google does nothing for Bing. They are separate systems, which is exactly why running both matters. Bing submission is not a substitute for your Google workflow; it is the half most teams skip.

Submission speeds the crawl, it does not force the index

As with Google, telling Bing about a URL speeds up when it is discovered and crawled. It does not decide whether Bing indexes it. Bing applies its own quality checks, and a thin or duplicate page can be submitted a dozen times and still not be indexed. Any tool that promises guaranteed Bing indexing is selling something that does not exist.

The honest workflow is to submit through IndexNow and your sitemap, then confirm the result and treat any gap as a signal to fix the page rather than resubmit it. That is what keeps Bing submission a white-hat activity: official channels, real confirmation, and no pretending you can override the engine.

Error submitting page to IndexNow: what each response code means

IndexNow answers every submission with an HTTP status code, and the codes are specific enough to tell you exactly what went wrong. Most people never see them because they submit through a plugin that swallows the response and shows a generic failure message. If you are getting "error submitting page to IndexNow" from WordPress, Yoast, RankMath or a CDN integration, the underlying code is one of six, and five of the six are fixable in under ten minutes.

The two that account for most failures are 403 and 422, and they are opposites. A 403 means the key file is the problem: it is missing, it returned a 404, or the file exists but the key inside it does not match the key you sent. A 422 means the key is fine but the URLs are not: you submitted an address that does not belong to the host you claimed, or the key does not match the expected schema. If a submission worked yesterday and fails today, check whether your key file still returns 200, because a CDN rule or a robots block in front of a plain text file at the root is the usual culprit.

A 429 is worth reading differently from the others. It means too many requests, flagged as potential spam, and the fix is not to retry harder. Batch your URLs instead: IndexNow accepts up to 10,000 URLs in a single POST, so a site pushing thousands of pages should be sending a handful of large requests rather than thousands of individual ones. And a 202 is not a failure at all, it means the URL was received and key validation is still pending, so no action is needed.

• 200 OK: URL submitted successfully. Nothing to do.
• 202 Accepted: URL received, IndexNow key validation pending. Not an error.
• 400 Bad request: invalid format. Usually malformed JSON or a bad content type header.
• 403 Forbidden: key not valid. The key file was not found, or the file exists but the key is not in it.
• 422 Unprocessable Entity: the URLs do not belong to the host, or the key does not match the schema.
• 429 Too Many Requests: flagged as potential spam. Batch into fewer, larger submissions.

Where the old Bing Add URL page went, and what replaced it

Searches for Bing AddURL and Bing search submission still lead people to the memory of a public form where anyone could paste a URL and have Bing crawl it. That model is gone across every major engine, for the same reason: an open submission box is a spam pipe. What replaced it in Bing is a two-track system, and the track you should be on depends on volume.

The manual track lives in Bing Webmaster Tools under URL Submission. It requires a verified property, and Bing gives verified site owners a daily allowance measured in the thousands of URLs rather than the ten or twelve Google allows through Request Indexing. For most sites that quota is not the constraint, which makes Bing meaningfully easier to work with than Google on this specific job.

The automated track is IndexNow, and it is the one worth building on. It is a plain HTTP GET or POST, it needs no OAuth and no client library, it accepts up to 10,000 URLs per request, and the same submission reaches Bing, Yandex, Seznam and Naver at once. If you are still submitting URLs to Bing by hand through the web interface, you are doing work an HTTP request does better, and you are doing it once per engine instead of once for all of them.