Guide : IndexNow
IndexNow is the ouvrir push protocol que instantly indique Bing, Yandex, Naver, Seznam, and Yep quand votre URLs modifier — un submission, shared à travers tout of les. Comment cela fonctionne, how to définir it up, and pourquoi it ne fait pashing pour Google.
Langues
1 indice probant sur cette page
- Outil en ligne associéXML Sitemap Validator
IndexNow is a free, ouvrir push protocol from Microsoft Bing and Yandex (launched Oct 18, 2021; aussi Seznam, Naver, and Yep): vous ping participating engines the instant une URL is ajouté, mis à jour, or deleted, and un submission is shared à travers tout of les. Setup is a clé fichier at votre root plus a simple HTTP OBTENIR (un URL) or POST (up to 10 000). It speeds up discovery and recrawl — it doesn't guarantee indexation and it's pas a ranking lever. Google ne fait pas utiliser IndexNow: it said it voudrait tester the protocol in 2021 and jamais adopted it, so it ne fait pashing pour Google. Garder votre sitemaps; IndexNow is additive, and the Google Indexation API is a separate, narrow outil.
Evidence for this claim IndexNow is a push protocol for notifying participating search engines that URLs were added, updated, or deleted; notification does not guarantee crawling or indexing. Scope: Current IndexNow protocol documentation. Confidence: high · Verified: IndexNow protocol documentation Evidence for this claim Participating engines share submitted IndexNow URLs; Google is not listed as a participating IndexNow search engine. Scope: Current IndexNow participant documentation, distinct from Google's narrow Indexing API. Confidence: high · Verified: IndexNow: Participating search enginesTL;DR — IndexNow is a façon to tell moteur de recherches une page modifié au lieu de waiting pour les to trouver out. Vous ping it une fois and it reaches Bing, Yandex, Naver, Seznam, and Yep tout at une fois. It’s rapide to définir up and free. The big catch: Google doesn’t utiliser it, so it won’t aider vous in Google at tout.
Ce que IndexNow is
Normally, moteur de recherches trouver votre nouveau and mis à jour pages on leur propre schedule — ils follow liens and re-crawl votre site whenever ils obtenir autour to it. IndexNow flips que autour. Au lieu de waiting to be re-crawled, vous send the search engine a rapide message: “this page just changed, come look.” It fonctionne pour pages vous ajouter, mettre à jour, or delete.
The clever partie is ce que Microsoft calls the shared ping: vous submit une URL to un placer, and it’s automatically réussi along to every moteur de recherche que supports IndexNow. Correct now that’s Bing, Yandex, Naver, Seznam, and Yep (the moteur de recherche construit by Ahrefs). Un submission, tout of les notified.
The un chose vous have to know
Google ne fait pas utiliser IndexNow. Back in 2021 Google said it voudrait tester the idea, but it jamais en réalité adopted it. So si votre goal is faster indexation in Google, IndexNow ne fait pashing pour vous. It seulement helps on the engines que participate. A lot of personnes obtenir ce incorrect, so it’s worth repeating: IndexNow is a Bing-and-friends outil, pas a Google outil.
Fait it aider me rank meilleur?
Aucun. IndexNow speeds up discovery — how fast an engine notices votre modifier. It doesn’t faire votre pages rank plus élevé, and it doesn’t guarantee une page obtient indexé. The engine encore decides si lune page is worth keeping. Think of it as ringing the doorbell, pas walking via the door.
Devrait vous bother?
Pour la plupart sites it’s a petit, set-it-and-forget-it win — surtout si vous publish or mettre à jour content souvent (news, product listings, press releases). And si vous utiliser Cloudflare, WordPress with Yoast or Rank Math, Wix, Shopify, or Ahrefs Site Audit, turning it on is basically un click — ceux outils ping IndexNow pour vous automatically. Simplement don’t expect it to do anything pour Google, and don’t drop votre XML sitemap, qui is encore how Google (and everyone sinon) discovers votre pages at scale.
Vouloir the protocol details — the clé fichier, the API calls, the comparison to sitemaps and the Google Indexation API? Switch to the Avancé tab.
Evidence for this claim IndexNow is a push protocol for notifying participating search engines that URLs were added, updated, or deleted; notification does not guarantee crawling or indexing. Scope: Current IndexNow protocol documentation. Confidence: high · Verified: IndexNow protocol documentation Evidence for this claim Participating engines share submitted IndexNow URLs; Google is not listed as a participating IndexNow search engine. Scope: Current IndexNow participant documentation, distinct from Google's narrow Indexing API. Confidence: high · Verified: IndexNow: Participating search enginesTL;DR — IndexNow is an ouvrir push protocol (Microsoft Bing + Yandex, launched Oct 18, 2021; joined by Seznam, Naver, and Yep). Vous host a
{key}.txtfichier at votre root pour verification, alors notify engines on ajouter/mettre à jour/delete via a OBTENIR (un URL) or a JSON POST (≤10 000 URLs). The differentiator is the shared ping — submit une fois, reach every participant. It accelerates discovery and recrawl prioritization; it fait pas guarantee indexation and is pas a ranking signal. Google ne fait pas utiliser IndexNow — it said in Nov 2021 it voudrait “be testing” the protocol and jamais adopted it, so it ne fait pashing pour Google. Garder votre sitemaps; the Google Indexation API is a separate, narrow outil.
Ce que IndexNow en réalité is
IndexNow is the push side of URL discovery. La plupart discovery is pull — engines follow liens and lire votre sitemap on leur propre schedule. IndexNow lets vous proactively tell participating engines que something modifié so ils peut prioritize the (re)explorer. Bing’s propre framing: “Si you’re ajout, updating, or deleting content, IndexNow notifies multiple moteur de recherches of votre content changements as soon as ils se produire.”
It was launched October 18, 2021 by Microsoft Bing and Yandex, and it’s a free, ouvrir protocol — “a free, open-source protocol empowering website owners with unprecedented contrôler over how quickly leur content is découvert,” in Bing’s words. The protocol spec lives at indexnow.org.
Who participates (and who doesn’t)
Participating engines today: Bing, Yandex, Naver, Seznam.cz, and Yep (Ahrefs’ moteur de recherche) — that’s the liste indexnow.org’s homepage credits as offering prise en charge. Parce que Bing powers a chunk of the AI-search ecosystem, feeding Bing’s index via IndexNow peut aussi aider visibility on Copilot, ChatGPT Search, and DuckDuckGo.
As of my July 2026 vérifier, indexnow.org’s FAQ aussi listes a submission endpoint pour
Amazon (indexnow.amazonbot.amazon) alongside Bing, Naver, Seznam.cz, and
Yandex — but the homepage’s propre “support from” line hasn’t been mis à jour to
inclure it. I’d treat Amazon’s participation as newly emerging plutôt que entièrement
confirmed jusqu’à le site is internally consistent à propos de it.
Participating aussi isn’t a promise to explorer or index ce que vous send: indexnow.org’s propre spec is explicit que engines “agree que submitted URLs va be automatically shared” with every autre participant — sharing the ping, pas committing to act on it.
Google n’est pas on que liste. Plus on que ci-dessous — it’s the unique la plupart misunderstood chose à propos de ce protocol.
Comment cela fonctionne
Là are four moving parts: a clé, a clé fichier, the submission, and the shared ping.
1. Generate a clé
A clé is a hexadecimal string (the spec permet 8–128 characters: a–z, A–Z,
0–9, and dashes). It’s ce que ties votre submissions to votre domain. Bing:
“An API key is needed to match the ownership of the domain with submitted URLs.”
2. Host the clé fichier (verification)
Placer a UTF-8 text fichier named {your-key}.txt, containing the clé, at votre site
root (or un autre emplacement vous declare via keyLocation). Engines récupérer it to
confirmer vous contrôler the host avant ils accept anything. Bing: “Host votre UTF-8
clé fichier at the root of votre website.” The indexnow.org spec: the clé fichier is how
“moteur de recherches utiliser ce fichier to confirmer domain ownership avant accepting
IndexNow submissions.” Ce is the whole authentication model — there’s aucun OAuth,
aucun service account, simplement a fichier vous pouvez serve.
Si vous utiliser a non-root keyLocation, its chemin aussi scopes qui URLs que clé
peut cover — ce is a detail personnes miss. Per the indexnow.org spec: “the
emplacement of a clé fichier determines the définir of URLs que peut be inclus with ce
clé.” A clé fichier at example.com/catalog/key.txt peut submit URLs sous
/catalog/ but pas sous /help/. Root placement avoids ce limite entirely,
qui is pourquoi the spec calls it the “strongly recommended” option.
3. Submit URLs — OBTENIR (unique) or POST (bulk)
Pour un URL, a plain HTTP OBTENIR is suffisant:
https://api.indexnow.org/indexnow?url={url-changed}&key={your-key}Pour nombreux URLs, a unique JSON POST carries up to 10 000 of les (“IndexNow supports bulk submission of up to 10,000 URLs per POST request.”):
{
"host": "www.example.org",
"key": "your-key",
"keyLocation": "https://www.example.org/your-key.txt",
"urlList": [
"https://www.example.org/url1",
"https://www.example.org/folder/url2"
]
}Au-delà the 10 000-per-POST cap, indexnow.org doesn’t publish a fixed daily
URL quota — its FAQ dit plainly que it “ne fait pas publicly disclose exact rate
limites, as chaque participating moteur de recherche sets its propre daily submission
thresholds per site.” En pratique, the seulement quota signal you’ll voir is a 429
réponse, pas a documented number to plan autour.
The protocol’s documented réponse codes are worth knowing quand you’re debugging:
200 OK (submitted successfully), 202 Accepted (reçu, but — per
indexnow.org’s spec — “IndexNow key validation pending”, qui the FAQ dit
typically montre up seulement on votre premier submission with a nouveau clé, avant
subsequent requêtes settle back to 200), 400 (bad requête / invalid format),
403 Forbidden (clé pas valid, or the fichier is trouvé but the clé isn’t in it),
422 (URLs don’t belong to the host, or the clé schema doesn’t match), and 429
(aussi nombreux requêtes — treated as potential spam). Bing’s propre get-started page listes
the même définir minus 202.
4. The shared ping — submit une fois, reach every participant
Ce is the fonctionnalité que rend IndexNow worth the trouble. From the spec:
“Chaque endpoint sends votre submission directement to its respective moteur de recherche, and
votre submission va be shared à travers tout IndexNow-enabled moteur de recherches.” Vous
peut hit the global endpoint, api.indexnow.org, or quelconque participant’s endpoint
(Bing’s, Yandex’s, etc.) — the effect is the même. Un submission propagates to
tout of les. Vous don’t maintain a separate integration per engine.
Fait Google utiliser IndexNow?
Aucun. Ce is the partie la plupart pages on the web obtenir incorrect or leave vague, so I vouloir to be exact à propos de it.
Google’s seulement substantive public statement came in November 2021, to Search Engine Land. A Google spokesperson said: “We’re encouraged by fonctionner to faire web exploration plus efficient, and we va be testing the potential benefits of ce protocol.” Remarque the framing — it’s à propos de explorer efficiency and testing, pas a commitment to adopt. Moteur de recherche Journal reported the même statement the même day sous a “will be testing” headline.
Années plus tard, nothing has modifié. Google jamais adopted IndexNow. Yoast, who construire an official IndexNow-capable plugin, put Google’s stance plainly: “Google n’est pas currently participating in ce initiative, citing its very efficient exploration mechanism and its continued improvement.” Wikipedia’s entry likewise notes que as of 2022 Google had pas officially adopted the protocol — and it encore hasn’t.
So: submitting to IndexNow ne fait pashing pour Google indexation or rankings. Don’t
conflate ce with Google’s separate crawl-efficiency fonctionner (Gary Illyes’ “explorer
moins” push) — that’s à propos de Google exploration its propre façon plus efficiently, pas à propos de
adopting IndexNow as the mechanism. Pour Google, votre discovery channels remain
liens, sitemaps (with accurate lastmod), RSS/feeds, and WebSub — the push and
pull mechanisms I walk via on my How Search Fonctionne deck. IndexNow simply
isn’t un of les.
IndexNow vs sitemaps vs the Google Indexation API
Personnes reach pour IndexNow expecting it to replace something. It doesn’t. Ces are three différent outils with three différent jobs:
| IndexNow | XML Sitemaps | Google Indexation API | |
|---|---|---|---|
| Model | Push (notify on modifier) | Pull (engines explorer on schedule) | Push (notify Google) |
| Engines | Bing, Yandex, Naver, Seznam, Yep (shared) | Tout engines, incl. Google | Google seulement |
| Content scope | Tout content types | Tout content types | Seulement JobPosting + BroadcastEvent (livestream) |
| Speed | Near-instant on participants | Days to weeks to be découvert | Near-instant pour eligible content |
| Limite | ≤10 000 URLs per POST (aucun publié daily cap) | ≤50 000 URLs per fichier | ~200 publish requêtes/day (par défaut) |
| Setup | Clé fichier at root + HTTP | XML fichier referenced in robots.txt / GSC | Cloud project + service account |
| Google effect | None | Yes | Yes — but seulement the two allowed schema types |
The takeaways I’d vouloir vous to leave with:
- They’re complementary, pas substitutes. Garder votre sitemaps — that’s how Google and everyone sinon discovers vous at scale. Utiliser IndexNow to accelerate discovery on Bing/Yandex/Naver/Seznam/Yep.
- The Google Indexation API n’est pas “Google’s IndexNow.” It’s officially limited to job postings and livestream video — “Google’s Indexation API officially seulement supports two content types,” as CrawlWP puts it. The “instant indexation” plugins que fire it at ordinary pages are off-policy.
- Pour Google, là is aucun public push API pour ordinary pages. Sitemaps plus bon explorer health is the chemin.
Benefits and limites
The efficiency story is the honest pitch. The canonical justification is Cloudflare’s observation que “53% of this crawler traffic is wasted” — engines re-crawling pages que didn’t modifier. IndexNow attacks exactly que waste by telling engines quand to come back au lieu de making les guess. Bing frames the upside as helping “drive plus relevant trafic to votre site, améliorer search engine rankings, and lower explorer costs,” and in 2025 décrit IndexNow as “becoming foundational to the way search engines keep pace with web changes.”
Où it genuinely helps:
- Fast-changing or time-sensitive content — news, ecommerce inventory and pricing, press releases, anything où minutes matter on Bing.
- Bing-fed AI surfaces — Copilot, ChatGPT Search, DuckDuckGo tout lean on Bing’s index.
Où it doesn’t:
- Google — zero effect, complet arrêter.
- Rankings — it speeds discovery, pas position. Faster exploration ≠ plus élevé ranking.
- Guaranteed indexation — it’s a prioritization signal; the engine encore decides si and quand to index.
Adoption has grown fast — Bing reported “plus que 16 million web sites… publishing over 1,2 billion URLs per day” in August 2022, and “3,5 billion URLs submitted per day” by December 2024, with adopters notamment Shopify, GoDaddy, the Internet Archive, and Condé Nast. (Quelconque plus grand 2026 figures vous voir floating autour are secondary-sourced; I’d treat les as estimates jusqu’à Bing publishes a fresh number.)
How to définir it up (vous probably won’t écrire code)
La plupart personnes jamais touch the raw API — a platform fait it pour vous:
- Cloudflare — un click. Enable Robot d’exploration Hints (Cache → Configuration) and “Cloudflare va prendre care of signaling to ces moteur de recherches quand votre content has modifié via the IndexNow protocol.” Ce was the premier big one-click integration, shipped on launch day.
- WordPress — Yoast SEO Premium (it “va ping IndexNow whenever vous publish or mettre à jour votre content”), Rank Math, Tout in Un SEO, or Microsoft’s official IndexNow plugin.
- Wix, Duda, Shopify — built-in prise en charge.
- Bing Webmaster Outils — manual URL submission tied to IndexNow, plus the IndexNow Insights report.
- Ahrefs Site Audit — the integration I construit (voir the Outils tab). Generate a clé in the explorer config, drop it in the clé fichier, and submit lune pages Site Audit flags as modifié, redirigé, or supprimé.
Si vous are rolling votre propre, voir the Scripts tab pour the réel OBTENIR and POST calls and the key-file setup.
Courant myths
- “IndexNow gets you indexed in Google / boosts Google rankings.” Faux. Google doesn’t consume IndexNow.
- “Faster indexing means higher rankings.” Faux. IndexNow speeds discovery; ranking encore dépend on the usual factors.
- “Google is about to adopt it.” Non pris en charge. It testé it in 2021 and jamais adopted it; its plus tard crawl-efficiency fonctionner is unrelated.
- “IndexNow replaces sitemaps.” Faux. Sitemaps remain essential, surtout pour Google. IndexNow is additive.
- “The Indexing API is Google’s IndexNow for any page.” Faux —
JobPosting+BroadcastEventseulement. - “It guarantees indexing.” Faux. It’s a prioritization signal.
Où ce sits in the bigger picture
IndexNow is the cross-engine push analog of the feed mechanisms Google uses (RSS, WebSub) — même idea (“tell me what changed”), différent participants. It lives in the getting-pages-discovered-faster corner of exploration, alongside the Google Indexation API. Pour the complet pipeline — how discovery, exploration, rendering, and indexation fit ensemble — voir the Exploration hub and the How Search Fonctionne cluster page.
AI summary
A condensed prendre on the Avancé version:
- IndexNow = an ouvrir push protocol (Microsoft Bing + Yandex, launched Oct 18, 2021; aussi Seznam, Naver, Yep). Vous notify engines the instant une URL is ajouté, mis à jour, or deleted au lieu de waiting to be re-crawled.
- The shared ping is the differentiator: submit une fois (to
api.indexnow.orgor quelconque participant) and it propagates to tout participating engines. - Setup: generate a clé → host
{key}.txtat votre root pour verification → OBTENIR (un URL) or JSON POST (≤10 000 URLs, aucun publié daily cap). A non-rootkeyLocationaussi limites qui URL paths que clé peut submit. indexnow.org’s spec documents réponse codes 200/202/400/403/422/429 —202simplement signifie votre premier submission’s clé is encore verifying. - Google ne fait pas utiliser it. Google said in Nov 2021 it voudrait “be testing the potential benefits of ce protocol” and jamais adopted it — IndexNow ne fait pashing pour Google indexation or rankings.
- It accelerates discovery, pas ranking, and doesn’t guarantee indexation — it’s a prioritization signal on participating engines (qui aussi feed Bing-powered AI surfaces comme Copilot, ChatGPT Search, DuckDuckGo).
- Complementary to sitemaps; the Google Indexation API is a separate, narrow outil
(
JobPosting+BroadcastEventseulement). - Facile to enable via Cloudflare (Robot d’exploration Hints), Yoast/Rank Math/AIOSEO, Wix/Duda/Shopify, Bing Webmaster Outils, or Ahrefs Site Audit.
Documentation officielle
Primary-source documentation pour the protocol and its biggest backer.
The protocol
- indexnow.org / Documentation / FAQ — the spec: key-file verification (notamment how a non-root
keyLocationscopes submittable URLs), the OBTENIR/POST endpoints, the 10 000-URL POST limite, the complet200–429response-code table, and the shared-ping behavior.
Bing / Microsoft
- Pourquoi IndexNow — Bing’s overview and the benefits framing.
- How to ajouter IndexNow to votre website (obtenir commencé) — the technical walkthrough: clé generation, hosting the clé fichier, the POST JSON structure, and la réponse codes.
- IndexNow adoption gains momentum (Fabrice Canel, Aug 2022) — the 2022 adoption numbers.
- Regarder How Far We’ve Come: IndexNow Expands Adoption À travers Industries (Dec 2024) — the 3,5B-URLs/day milestone and nouveau adopters.
- IndexNow Drives Smarter and Faster Content Discovery (Canel & Madhavan, May 2025).
- Cloudflare Supports IndexNow via one-click Integration — the CDN one-click story.
Cloudflare
- Robot d’exploration Hints Mettre à jour: Cloudflare Supports IndexNow (Oct 18, 2021) — the one-click integration and the “53% of crawler traffic is wasted” stat.
Quotes from the source
On-the-record statements from the protocol, Bing/Microsoft, Cloudflare, and Google. Chaque lien is a deep lien que jumps to the quoted passage.
The protocol — indexnow.org
- “This key proves ownership of your domain and authenticates your submissions so search engines know they’re coming from an authorized source.” Jump to quote
- “…confirm domain ownership before accepting IndexNow submissions.” Jump to quote
- “IndexNow supports bulk submission of up to 10,000 URLs per POST request.” Jump to quote
- “…your submission will be shared across all IndexNow-enabled search engines.” Jump to quote
- “…agree that submitted URLs will be automatically shared with all other participating search engines.” — the participation requirement; sharing the ping is the commitment, pas exploration or indexation it. Jump to quote
- “…the location of a key file determines the set of URLs that can be included with this key.” — pourquoi a non-root
keyLocationscopes ce que vous pouvez submit. Jump to quote - ”…IndexNow key validation pending.” — ce que a
202on votre premier submission signifie. Jump to quote - “…does not publicly disclose exact rate limits, as each participating search engine sets its own daily submission thresholds per site.” Jump to quote
Bing / Microsoft
- “IndexNow is a free, open-source protocol empowering website owners with unprecedented control over how quickly their content is discovered and displayed in search results.” — Bing Webmaster Outils, Pourquoi IndexNow. Jump to quote
- “Whether you’re adding, updating, or deleting content, IndexNow notifies multiple search engines of your content changes as soon as they happen.” — Bing Webmaster Outils, Pourquoi IndexNow.
- “An API key is needed to match the ownership of the domain with submitted URLs.” — Bing Webmaster Outils, Obtenir commencé. Jump to quote
- “By allowing websites to instantly notify search engines of new, changed, and deleted content, IndexNow accelerates indexing and reduces reliance on traditional crawl schedules.” … “IndexNow is becoming foundational to the way search engines keep pace with web changes.” — Fabrice Canel & Krishna Madhavan, Microsoft AI/Bing, May 19, 2025.
Cloudflare
- “Cloudflare will take care of signaling to these search engines when your content has changed via the IndexNow protocol.”
- “Our observation suggests that 53% of this crawler traffic is wasted.” — Cloudflare, Robot d’exploration Hints Mettre à jour, Oct 18, 2021.
Google — the “testing” statement (and Pourquoi c’est important)
- “We’re encouraged by work to make web crawling more efficient, and we will be testing the potential benefits of this protocol.” — Google spokesperson, Nov 9, 2021, via Moteur de recherche Land (and reported identically by Moteur de recherche Journal). Ce is Google’s seulement substantive public statement on IndexNow — remarque it’s à propos de testing, pas adopting. Lire the coverage
- “Google is not currently participating in this initiative, citing its very efficient crawling mechanism and its continued improvement.” — Yoast, summarizing Google’s stance. Jump to quote
Définir up IndexNow — checklist
A one-time setup, alors it runs on every content modifier:
- Generate a clé — a hex string of 8–128 chars (
a–z,A–Z,0–9, dashes). La plupart plugins/CDNs generate un pour vous. - Host the clé fichier — upload
{your-key}.txt(UTF-8, containing the clé) to votre site root, e.g.https://example.com/{your-key}.txt. Confirmer it renvoie200and montre the clé. Si vous host it anywhere autre que the root, que chemin aussi caps qui URLs the clé peut submit — root avoids the limite. - Pick how you’ll submit — a platform integration (Cloudflare, Yoast, Rank Math, Wix, Shopify, Ahrefs Site Audit, Bing Webmaster Outils) or votre propre API calls.
- Submit on ajouter — ping nouveau URLs as vous publish.
- Submit on mettre à jour — ping URLs quand leur content meaningfully changements.
- Submit on delete / redirection — ping supprimé or redirigé URLs so engines drop the stale version faster.
- Vérifier it’s working — vérifier the IndexNow / IndexNow Insights report in
Bing Webmaster Outils and watch pour non-
200réponses. - Garder votre sitemap — IndexNow is additive; don’t supprimer votre XML sitemap (it’s encore how Google discovers vous).
- Définir expectations — remember ce affecte Bing/Yandex/Naver/Seznam/Yep, pas Google, and it speeds discovery, pas rankings.
The mental models
1. Push vs pull discovery. Discovery se produit two façons. Pull: engines come to vous on leur propre schedule — liens and sitemaps. Push: vous go to les the moment something changements — IndexNow (cross-engine), the Google Indexation API (Google, narrow), and feed mechanisms comme RSS/WebSub. IndexNow is the cross-engine push channel. Si a modifié page isn’t being picked up fast suffisant on Bing, push is the lever.
2. Submit une fois, reach tout (the shared ping).
Vous don’t integrate per engine. Un submission to quelconque participant endpoint (or
api.indexnow.org) fans out to every IndexNow-enabled engine. Construire the
integration une fois; the network fait the distribution.
3. The three jobs, three outils rule.
- Sitemaps = baseline pull discovery pour everyone, notamment Google. Jamais drop les.
- IndexNow = push acceleration pour Bing, Yandex, Naver, Seznam, Yep.
- Google Indexation API = push pour Google, but seulement
JobPosting+BroadcastEvent. Utiliser tout three pour ce que chaque is en réalité pour — none replaces un autre.
4. Discovery ≠ indexation ≠ ranking. IndexNow moves the discovery needle on participating engines. It doesn’t guarantee lune page obtient indexé, and it jamais affecte ranking. Si the goal is “rank better,” IndexNow isn’t the outil; si it’s “obtenir my fresh content noticed on Bing fast,” it is.
Submit URLs to IndexNow
Une fois votre clé fichier is live at the root, submitting is a unique HTTP requête. The shared ping signifie un appel reaches every participating engine.
Unique URL (OBTENIR)
curl "https://api.indexnow.org/indexnow?url=https://www.example.com/changed-page&key=YOUR_KEY"A 200 OK signifie it was accepted. On votre premier submission with a nouveau clé vous may
voir a 202 à la place — l’URL was reçu but the clé is encore being verified;
plus tard submissions typically retourner 200. Autre codes: 400 (bad requête), 403
(clé pas valid, or the fichier is trouvé but the clé isn’t in it), 422 (URLs don’t
belong to the host, or clé mismatch), 429 (rate-limited / treated as spam).
Up to 10 000 URLs (JSON POST)
curl -X POST "https://api.indexnow.org/indexnow" \
-H "Content-Type: application/json; charset=utf-8" \
-d '{
"host": "www.example.com",
"key": "YOUR_KEY",
"keyLocation": "https://www.example.com/YOUR_KEY.txt",
"urlList": [
"https://www.example.com/url1",
"https://www.example.com/folder/url2"
]
}'Submit seulement URLs que en réalité modifié (ajouté, mis à jour, deleted/redirigé) — que
respects the protocol’s intent and avoids 429 spam handling.
Définir up the clé fichier (verification)
The whole auth model is a text fichier at votre root. Generate a clé, alors serve it.
Generate a clé (hex string)
# 32-char lowercase hex key — within the 8–128 char spec (a–z A–Z 0–9 and dashes)
openssl rand -hex 16
# → e.g. 9f8c2a1b4d6e0f37a5c9b8d2e1f04736Créer and host the clé fichier
KEY="9f8c2a1b4d6e0f37a5c9b8d2e1f04736"
printf '%s' "$KEY" > "${KEY}.txt"
# Deploy ${KEY}.txt to your web root so it's reachable at:
# https://www.example.com/9f8c2a1b4d6e0f37a5c9b8d2e1f04736.txtConfirmer it’s reachable
curl -i "https://www.example.com/${KEY}.txt"
# Expect: HTTP/2 200 and a body equal to the keyEngines récupérer ce fichier to confirmer vous contrôler the host avant accepting quelconque
submission. Si vous host it somewhere autre que the root, point to it with
keyLocation in votre POST corps — but remarque que a non-root keyLocation aussi
scopes qui URLs que clé peut submit (a clé fichier at /catalog/key.txt seulement
covers URLs sous /catalog/). Root placement avoids que limite.
Outils to définir up and monitor IndexNow
- Cloudflare — Robot d’exploration Hints — the simplest on-ramp. Flip it on in Cache → Configuration and Cloudflare pings IndexNow pour vous whenever votre content changements. Free, aucun clé management.
- WordPress plugins — Yoast SEO Premium (auto-pings on publish/mettre à jour), Rank Math, Tout in Un SEO, and Microsoft’s official IndexNow plugin.
- Wix / Duda / Shopify — built-in IndexNow prise en charge pour hosted platforms.
- Bing Webmaster Outils — manual URL submission tied to IndexNow plus the IndexNow Insights report to voir what’s being submitted and accepted.
- Ahrefs Site Audit — IndexNow integration — the un I construit. Generate an API clé in the explorer config, paste it into votre root clé fichier, alors ouvrir the “Pages to submit to IndexNow” problème — it surfaces pages with content changements, redirections, or supprimé URLs — and submit les (or pick votre propre). Parce que Yep is Ahrefs’ participating moteur de recherche, the même submissions aussi feed Ahrefs’ propre index.
- Roll votre propre — voir the Scripts tab pour the OBTENIR/POST calls and key-file setup si you’d plutôt hit the API directement.
Ressources utiles
My connexe writing & fonctionner
- Ahrefs’ IndexNow integration (IndexNow, Yep & Ahrefs) — the integration I construit into Site Audit, and how Yep (Ahrefs’ moteur de recherche) obtient données from IndexNow aussi.
- The Beginner’s Guide to SEO technique — où discovery and exploration fit in the bigger picture.
My speaking
- How Search Fonctionne (SlideShare) — my walkthrough of URL discovery, notamment the push/feed mechanisms (RSS, WebSub) Google en réalité uses — utile context pour pourquoi IndexNow is pas un of les. (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)
The protocol & official backers
- indexnow.org — the spec and FAQ.
- bing.com/indexnow — Bing’s overview and getting-started guide.
From others
- Yoast — IndexNow: Ce que c’est and how it benefits vous — clair, plugin-focused, and honest à propos de Google’s non-adoption.
- SEJ — IndexNow Celebrates Two Années With 1,4 Billion URLs Submitted Daily — adoption context.
- CrawlWP — IndexNow vs Google Indexation API vs Sitemaps — the comparison, notamment the Indexation API’s two-content-type limite.
- Wikipedia — IndexNow — history, timeline, and participants.
- Moteur de recherche Land — Google is testing the IndexNow protocol pour sustainability — the principal source pour Google’s Nov 2021 “we will be testing” statement; utile pour understanding the original framing.
- Moteur de recherche Journal — Everything We Know À propos de IndexNow So Far — comprehensive early explainer covering launch details, how the shared ping fonctionne, and integration options.
- Moteur de recherche Land — Bing Webmaster Outils gains nouveau IndexNow Insights report — covers the IndexNow Insights report in Bing Webmaster Outils and ce que it montre.
- Moteur de recherche Roundtable — Fabrice Canel on Sitemaps & the suivant big chose in search (vlog #234) — Bing’s principal IndexNow PM discusses the protocol’s role alongside sitemaps.
- r/TechSEO — the community pour explorer/index/discovery debugging.
Courant IndexNow problèmes
Symptom → probable causer → fix, fondé on la réponse codes Bing documents.
Submission renvoie 403 Forbidden
- Causer 1: the clé fichier isn’t reachable at the root (or the
keyLocationvous declared). - Causer 2: the clé fichier is reachable, but its contents don’t match the
keyvous submitted. - Fix:
curl -i "https://www.example.com/{your-key}.txt"and confirmer vous obtenir200with a corps that’s exactly the clé, aucun supplémentaire whitespace or HTML wrapper. Re-upload si the fichier is manquant or le contenu is incorrect.
Submission renvoie 422
- Causer: l’URLs in
urlListdon’t belong to thehostvous declared, or the clé doesn’t match the host/schema you’re submitting pour. Si you’re en utilisant a non-rootkeyLocation, ce aussi fires quand a submitted URL falls outside the clé file’s propre chemin — a clé hosted at/catalog/key.txtcan’t cover URLs sous/help/. - Fix: vérifier que every URL in the payload shares the même host as
host(and protocol —https://www.example.comvsexample.comsanswwware différent hosts). Un clé fichier covers un host (and, pour non-root placement, un chemin prefix); submit chaque subdomain’s URLs with que subdomain’s propre clé.
Premier submission with a nouveau clé renvoie 202 au lieu de 200
- Causer: pas an error.
202signifie l’URL was reçu but the moteur de recherche is encore verifying the clé contre votre clé fichier. - Fix: nothing to do — resend plus tard or simplement wait; subsequent submissions with
the même, now-verified clé typically retourner
200.
Submission renvoie 400
- Causer: malformed requête — bad JSON, manquant requis field (
host,key,urlList), or a clé outside the 8–128 char hex/dash spec. - Fix: validate the JSON corps and the clé format avant sending. Pour the OBTENIR formulaire, confirmer l’URL is correctement encoded.
Submission renvoie 429
- Causer: aussi nombreux requêtes in a short window — treated as potential spam.
- Fix: seulement submit URLs que en réalité modifié (ajouté/mis à jour/deleted), batch les into fewer POSTs au lieu de un OBTENIR per URL, and back off avant retrying.
Vous submitted successfully but Google encore hasn’t indexé lune page
- Causer: ce isn’t an IndexNow problem — Google doesn’t consume IndexNow at
tout. A
200from IndexNow seulement confirms Bing/Yandex/Naver/Seznam/Yep accepted the ping. - Fix: pour Google, vérifier votre XML sitemap and utiliser GSC’s Inspection d’URL / Sitemaps report — voir le site’s Sitemap Validator and Recherche Google Console CSV Analyzer outils à la place.
Pages aren’t showing up faster on Bing despite 200 réponses
- Causer: IndexNow is a prioritization signal, pas a guarantee — Bing encore decides si and quand to (re)explorer and index.
- Fix: confirmer the submissions are landing at tout via Bing Webmaster Outils’ IndexNow Insights report. Si they’re accepted but pages encore aren’t updating, the problème is probable explorer/index eligibility (contenu pauvre, noindex, blocked by robots.txt), pas the push itself.
IndexNow Référence rapide
Participants
| Engine | Supports IndexNow? |
|---|---|
| Bing | Yes (co-launched, Oct 18, 2021) |
| Yandex | Yes (co-launched, Oct 18, 2021) |
| Naver | Yes |
| Seznam.cz | Yes |
| Yep (Ahrefs) | Yes |
| Amazon | Listed as a submission endpoint on indexnow.org’s FAQ as of Jul 2026 — pas yet named on the homepage’s propre summary line |
| Aucun — testé in 2021, jamais adopted |
Endpoints and limites
| Valeur | |
|---|---|
| OBTENIR endpoint | https://api.indexnow.org/indexnow?url={url}&key={key} |
| POST endpoint | https://api.indexnow.org/indexnow |
| Bulk limite | ≤10 000 URLs per POST |
| Clé length | 8–128 chars, hex (a–z, A–Z, 0–9) + dashes |
| Clé fichier | {key}.txt, UTF-8, at site root (or declared keyLocation) |
Réponse codes
| Code | Meaning |
|---|---|
200 | Accepted |
202 | Reçu, clé validation pending (typically premier submission seulement) |
400 | Bad requête / malformed |
403 | Clé invalid, or clé fichier doesn’t contain the clé |
422 | URLs don’t belong to the host, or clé/schema mismatch |
429 | Rate-limited — treated as potential spam |
Who to ping vs ce que it fait
| Outil | Push/Pull | Reaches Google? |
|---|---|---|
| IndexNow | Push | Aucun |
| XML Sitemap | Pull | Yes |
| Google Indexation API | Push | Yes — JobPosting/BroadcastEvent seulement |
One-click integrations: Cloudflare (Robot d’exploration Hints), Yoast SEO Premium, Rank Math, Tout in Un SEO, Wix, Duda, Shopify, Bing Webmaster Outils, Ahrefs Site Audit.
Vérifier IndexNow is en réalité working
Proof points pour chaque step of the setup, from clé fichier to confirmed submission.
Clé fichier is live and correct
- Tester to run:
curl -i "https://www.example.com/{your-key}.txt" - Attendu result:
HTTP/2 200with a corps de la réponse that’s exactly the clé string, nothing sinon. - Échec interpretation: a non-
200signifie the fichier isn’t deployed or isn’t at the declared emplacement; a corps que doesn’t match the clé signifie the incorrect fichier got uploaded. - Monitoring window: immediate.
- Rollback trigger: re-upload the correct fichier si the vérifier fails; don’t submit
URLs jusqu’à ce passes, or every submission va
403.
Submission is accepted
- Tester to run: submit un connu URL via the OBTENIR endpoint (voir the Scripts tab) and lire the HTTP status renvoyé.
- Attendu result:
200 OK(or202 Acceptedsi it’s votre premier submission with a nouveau clé — that’s normal, pas a échec, and plus tard submissions devrait settle to200). - Échec interpretation:
403= clé/key-file mismatch;422= URL/host mismatch (or akeyLocationwhose chemin doesn’t cover ce URL);429= rate-limited, back off;400= malformed requête. - Monitoring window: immediate — la réponse comes back synchronously.
- Rollback trigger: fix the spécifique causer per la réponse code (voir the Courant Problèmes tab) and resubmit.
Engine en réalité reçu and processed submissions
- Tester to run: vérifier the IndexNow Insights report in Bing Webmaster Outils.
- Attendu result: submitted URLs listed with an accepted status, matching ce que vous sent.
- Échec interpretation: URLs manquant from the report despite
200réponses suggests a submission vous think went out didn’t (vérifier votre integration’s logs — Cloudflare, Yoast, etc.). - Monitoring window: autoriser a few hours to a day pour the report to reflect recent submissions.
- Rollback trigger: re-verify the clé fichier and resend si a batch is consistently manquant from the report.
Bing en réalité (re)crawled the modifié page
- Tester to run: vérifier votre serveur logs (or a Log Fichier Analyzer run, voir the
site’s Log Fichier Analyzer) pour a
bingbothit on the submitted URL après the ping. - Attendu result: a bingbot requête to l’URL dans hours of the accepted IndexNow submission — faster que its normal recrawl cadence pour que page.
- Échec interpretation: aucun bingbot hit après a reasonable window signifie the submission was accepted but pas yet prioritized, or l’URL is blocked (robots.txt, noindex) from being crawled at tout.
- Monitoring window: hours to a couple of days.
- Rollback trigger: none — ce is a discovery signal, pas a lever vous pouvez force; si exploration encore doesn’t follow, vérifier pour a blocking problème à la place.
Confirming ce changements nothing pour Google (sanity vérifier)
- Tester to run: comparer Google’s explorer/index timing pour a submitted URL (via GSC’s Inspection d’URL or Statistiques d’exploration) contre a contrôler page vous did pas submit to IndexNow.
- Attendu result: aucun measurable difference — Google’s behavior is unaffected by IndexNow submissions soit façon.
- Échec interpretation: si vous do voir a correlation, it’s coincidental (normal explorer variance), pas causal — Google ne fait pas consume IndexNow.
- Monitoring window: several days to a normal explorer cycle.
- Rollback trigger: none — ce tester exists to confirmer expectations, pas to drive a modifier.
Testez vos connaissances: IndexNow
Five rapide questions on ce que IndexNow is, Comment cela fonctionne, and où its limites are.
Journal des modifications
Mis à jour le 18 juil. 2026.
Résumé éditorial et détails enregistrés des changements.Détails des changements
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
Comparaison complète indisponible — aucun instantané antérieur n’a été archivé pour cette révision.