Free IndexNow Setup: What It Does, and Doesn't Do, for AI Search

IndexNow is a change notification. You send a participating search engine a list of URLs you added, updated or deleted. The engine decides whether and when to crawl them.

That is the whole mechanism. It does not rank pages, it does not submit content to a language model, and it does not guarantee indexing. The IndexNow documentation describes a receipt protocol and never mentions AI, LLMs or Copilot.

The registry at indexnow.org/searchengines.json lists exactly seven consuming endpoints as of its 22 August 2026 fetch:

• Bing
• Yandex
• Seznam
• Naver
• Yep
• Internet Archive
• Amazonbot

Google is absent. So the honest scope is narrow: IndexNow can tell Bing and six others about a change, faster than waiting for their next crawl. For a fuller breakdown of the claims around it, see IndexNow and AI search.

You need no paid tool and no account. You need write access to your site root and a way to send an HTTP request.

1. Generate a key. Create a random string of letters, numbers and dashes that matches the key format in the IndexNow documentation. Hypothetical example: a1b2c3d4e5f6a7b8.
2. Host the key file. Save a plain text file named after the key, containing only the key, at your root. For example https://example.com/a1b2c3d4e5f6a7b8.txt. Open it in a browser and confirm it loads with no redirect or login.
3. Ping one URL. Send a GET request:

curl -i "https://api.indexnow.org/indexnow?url=https://example.com/pricing&key=a1b2c3d4e5f6a7b8"

4. Ping several URLs. Send a POST with a JSON body:

curl -i -X POST https://api.indexnow.org/indexnow -H "Content-Type: application/json" -d '{"host":"example.com","key":"a1b2c3d4e5f6a7b8","keyLocation":"https://example.com/a1b2c3d4e5f6a7b8.txt","urlList":["https://example.com/pricing","https://example.com/about"]}'

5. Automate it. Trigger the request from your CMS or deploy pipeline whenever a page changes. Ping real changes only.

IndexNow does not replace your sitemap. Keep lastmod values accurate in both. The trade-offs are covered in IndexNow vs XML sitemaps.

The status code tells you what happened to the ping, and nothing more.

• 200: the request was received. That is the full meaning.
• 202: accepted, with key validation still pending.
• 400: the request was malformed. Check the URL encoding and JSON.
• 403: the key did not validate. Check the key file loads at the stated location.
• 422: a URL does not belong to the host, or the key does not match.
• 429: you sent too many requests. Slow down.

A 200 is not a crawl, not an index entry and not a citation. To learn whether Bing actually crawled and indexed the page, look in Bing Webmaster Tools. Our guide to setting up Bing Webmaster Tools walks through it, including the AI Performance report that shows grounding queries.

Here is what the evidence supports, stage by stage.

Google surfaces: nothing. Google does not consume IndexNow. Google says a page must be indexed and eligible for a snippet to appear as a supporting link in AI Overviews or AI Mode, and that no special optimization is needed. Googlebot finds changes through its own crawling and your sitemap.

Bing and Copilot: a plausible, unmeasured chain. Microsoft wrote on 10 February 2026 that IndexNow "helps ensure that AI systems reference the most current version of a page." That is an assertion from the protocol's operator, with no study behind it. The chain (IndexNow to Bing index freshness to Bing-backed grounding) has each link documented. Its combined effect has never been measured.

ChatGPT: no documented link. OpenAI says ChatGPT search sometimes partners with other search providers. It does not say IndexNow or Bing freshness affects its answers. Otterly's 2026 test of two AI-generated sites is a warning against assuming it: Bing kept both sites, Copilot cited one heavily, and ChatGPT citations stayed effectively at zero. That was one pair of sites run by a vendor, so read it as a caution, not a law. More on how ChatGPT search works is in OpenAI's web search help page explained.

Be clear about what sits outside IndexNow's reach.

• It can't fix access. If robots.txt blocks bingbot or your firewall returns 403 to crawlers, a ping changes nothing. Access comes first.
• It can't fix rendering. Most AI crawlers other than Googlebot don't execute JavaScript, per Vercel's crawler study. Content that only appears after JavaScript runs stays invisible however often you ping.
• It can't reach retrieval-off answers. When a model answers from training data, no ping reaches it.
• It can't be verified end to end. You see the ping response. You don't see whether an AI engine retrieved or cited the updated page.

The next move: confirm crawlers can fetch your key pages before you automate pings. The ChatGPT page fetch test shows what a crawler actually receives.

IndexNow is a first-party protocol, so the fastest free setup usually lives in tools you already run. Bing Webmaster Tools supports IndexNow and shows submitted URLs alongside crawl and index data. Many CMS platforms and CDNs also offer an IndexNow setting or plugin. Check your platform's settings before writing your own script.

Whichever route you take, judge it by Bing's index reports, not by the ping. And keep expectations honest: IndexNow is free, quick hygiene for Bing and six other endpoints. It is not an AI visibility lever. If you want to see whether AI engines name you today, the free checker on this site runs three buyer questions as a snapshot. To see whether any AI visits turn into traffic, set up AI referral tracking in analytics.