IndexNow — Bing-URL-Submit, Schlüsselprüfung & Statuscodes
Erzeugen Sie einen IndexNow-Schlüssel, laden Sie die .txt herunter, prüfen Sie die Live-Datei und senden Sie geänderte URLs an Bing und teilnehmende Suchmaschinen. Folgen Sie den Schritten, lesen Sie die Status-Tabelle (200 vs 202) und ein JSON-Beispiel — eine Änderungsmeldung garantiert keine Indexierung.
So funktioniert’s
1) Generate a key and download {key}.txt. 2) Host it at your site root (or another path on the same host). 3) Check key so this Worker can fetch and match the body. 4) Paste changed URLs (or sitemap XML), preview the JSON, then Submit. Confirm receipts in Bing Webmaster → IndexNow.
Regeln und Grenzen
Protocol rules for keys, hosts, status codes, and what IndexNow does not promise.
- Key: 8–128 characters from [A-Za-z0-9-]. Option 1 (recommended): host UTF-8 text at https://{host}/{key}.txt containing only the key.
- host in the JSON must equal the hostname of every URL and of keyLocation. www.example.com and example.com are different hosts.
- 200 = received; 202 = accepted with key validation often still pending (Bing/global). A green 202 is not proof the key file works — use Check key.
- Protocol allows up to 10,000 URLs per POST; this page caps at 500 to reduce abuse. Prefer submitting only changed URLs.
- Privacy: URL lists are sent through this site’s Worker to the IndexNow endpoint you choose, then discarded from our side — we do not store them in a content database.
Beispiel
Host www.example.com, key indexnowdemokey01, URL https://www.example.com/page → POST JSON with host, key, keyLocation https://www.example.com/indexnowdemokey01.txt, and urlList. After hosting the .txt, Check key should report HTTP 200 and bodyMatch true before Submit.
Gute Einsatzfälle
- New site or tool launch: deploy the key file, check it, then submit the new URLs from your sitemap.
- Content update: submit only the pages you changed instead of the whole site every time.
- Removed pages: submit URLs that now return 404/410 so engines can recrawl sooner.
HTTP-Statuscodes
What common IndexNow responses mean and what to do next.
| Code | Meaning | Next step |
|---|---|---|
| 200 | OK — URLs received | Optional: confirm in Bing Webmaster IndexNow log |
| 202 | Accepted — key validation may still be pending | Verify the live key file; do not assume success from 202 alone |
| 400 | Bad request — invalid format | Fix JSON/URL encoding and retry |
| 403 | Forbidden — key not valid | Fix key file path, body, or blocking (auth/HTML error) |
| 422 | Unprocessable — URL/host/key schema mismatch | Align host and URLs; check key character rules |
| 429 | Too many requests | Wait and reduce batch frequency |
Frequently asked questions
Ist HTTP 202 ein Erfolg?
Die Anfrage wurde akzeptiert. Bei Bing/global kann die Schlüsselprüfung später folgen. Prüfen Sie zuerst die Schlüsseldatei.
Where do I put the key file?
Preferred: site root as https://your-host/{key}.txt with the key as the only body text. You may use another path on the same host via keyLocation; Option 2 also limits which URL prefixes that key can cover.
Why does www vs non-www matter?
They are different hosts. If URLs use www, the key file must be on www (and the host field must be www). Fix DNS/canonical hosts first if you are unsure.
Garantiert IndexNow Indexierung?
Nein. Es benachrichtigt nur über Änderungen.
Do you store my URL list?
No content database. The Worker forwards your JSON to IndexNow/Bing for the request and does not publish the list as a public page.
Related tools
Fragen oder Feedback
Unklar, kaputt oder etwas fehlt? Schreib unten eine Nachricht — wir lesen jede Notiz zu diesen Tools.
References
Educational webmaster tool only. IndexNow does not guarantee crawl, index, or ranking outcomes. Prefer official IndexNow and Bing docs when policies change.