You updated your pricing page an hour ago, but ChatGPT is still quoting last month's numbers. The gap is crawl latency: search engines discover changes on their own schedule, sometimes days later. IndexNow closes that gap by letting you push a notification the moment a URL changes, so Bing and Yandex re-crawl in minutes instead of days. Since Bing's index feeds ChatGPT's web browsing and Microsoft Copilot, faster indexing is a direct lever on how fresh your brand looks inside AI answers.
This guide walks through the full setup: generating a key, hosting the key file, submitting URLs by GET and POST, automating submission on publish, and verifying it actually worked.
Key takeaways
- IndexNow is an open protocol supported by Microsoft Bing and Yandex; one ping notifies every participating engine, and platforms like Cloudflare can submit on your behalf. - It matters for GEO because Bing's index backs ChatGPT web browsing and Microsoft Copilot, so getting fresh pages into Bing quickly improves your odds of being cited with current information. - Setup is three parts: generate a key (hex, 8β128 characters), host it at `https://yourdomain.com/<key>.txt`, then submit URLs to `https://api.indexnow.org/indexnow`. - IndexNow notifies Bing and Yandex, not Google, and it speeds up crawling β it does not guarantee indexing or instant appearance in any AI answer. - The real win comes from automating submission on every publish or update, then verifying with Bing Webmaster Tools.
Step 1: Generate your IndexNow key
Your key is a shared secret that proves you own the site. It must be a hexadecimal string (characters `a`β`f` and `0`β`9`) between 8 and 128 characters long.
Generate one from the command line:
- On macOS or Linux: `openssl rand -hex 16` - With Node: `node -e "console.log(require('crypto').randomBytes(16).toString('hex'))"`
You can also use the key generator inside Bing Webmaster Tools, which will create and register one for you. Save the value; you will reuse it everywhere. A typical key looks like `a1b2c3d4e5f60718293a4b5c6d7e8f90`.
Step 2: Host the key file
Search engines verify ownership by fetching a text file named after your key. Create a file whose name is `<your-key>.txt` and whose entire contents are the key itself, then place it at your site root:
- File: `a1b2c3d4e5f60718293a4b5c6d7e8f90.txt` - Contents: `a1b2c3d4e5f60718293a4b5c6d7e8f90` - Location: `https://yourdomain.com/a1b2c3d4e5f60718293a4b5c6d7e8f90.txt`
Confirm it is publicly reachable before going further:
`curl https://yourdomain.com/a1b2c3d4e5f60718293a4b5c6d7e8f90.txt`
The response body must be exactly the key, served with a `200` status and `text/plain`. If you prefer, you can host the key elsewhere on the domain and point to it with `keyLocation` in the POST payload, but the root path is simplest.
Step 3: Submit a single URL by GET
The fastest way to test is a GET request. Replace the domain and key with yours:
`curl "https://api.indexnow.org/indexnow?url=https://yourdomain.com/blog/new-pricing&key=a1b2c3d4e5f60718293a4b5c6d7e8f90"`
A `200` or `202` response means the submission was accepted. GET is convenient for one-off pings β for example, right after publishing a single post β but it only carries one URL per call.
Step 4: Submit multiple URLs by POST
For batch updates, send a POST with a JSON body to the same endpoint. This is the method to wire into your build or CMS.
`curl -X POST "https://api.indexnow.org/indexnow" -H "Content-Type: application/json" -d '{ "host": "yourdomain.com", "key": "a1b2c3d4e5f60718293a4b5c6d7e8f90", "keyLocation": "https://yourdomain.com/a1b2c3d4e5f60718293a4b5c6d7e8f90.txt", "urlList": [ "https://yourdomain.com/blog/new-pricing", "https://yourdomain.com/products/flagship", "https://yourdomain.com/about" ] }'`
Every URL in `urlList` must belong to the `host` you declare β you cannot submit URLs for a domain you have not verified. Keep batches reasonable (up to 10,000 URLs per request per the protocol) and only submit pages that genuinely changed.
Step 5: Automate submission on publish and update
Manual pings do not scale. The goal is that every publish or meaningful edit triggers a submission automatically.
- CMS webhook: fire a small serverless function on your "post published" or "post updated" event that POSTs the changed URL to `https://api.indexnow.org/indexnow`. - Cloudflare: enable the IndexNow integration in your Cloudflare dashboard so Cloudflare submits URLs from your sitemap and crawl signals on your behalf β no key handling required on your side. - Shopify: use an app or a webhook on `products/update` and `articles/update` to submit the affected product and blog URLs. - Static sites: add a deploy hook in your CI pipeline that reads changed paths from the build and posts them after each deploy.
Only ping on real changes. Re-submitting unchanged URLs repeatedly wastes quota and can look like spam.
Common mistakes
- Key mismatch: the file contents must match the key in your request exactly. A trailing newline or a different case will fail verification. - Wrong host: submitting URLs whose domain does not match the `host` field gets the batch rejected. - HTTP instead of HTTPS: submit the canonical HTTPS URLs your users actually see, not redirects. - Over-submitting: pinging the same pages on a timer, whether or not they changed, is the fastest way to get throttled. - Expecting Google: IndexNow does not notify Google. For Google, rely on the sitemap and normal crawling; IndexNow covers Bing, Yandex, and the AI tools built on Bing.
How to verify
Verification happens on two levels: did the ping land, and did it change anything.
- Confirm acceptance: a `200`/`202` from the API means the request was well-formed and the key resolved. - Check Bing Webmaster Tools: the IndexNow section shows submitted URLs and their status, and the URL Inspection tool shows the last crawl date. If the crawl date moves forward after your ping, it worked. - Watch server logs: look for hits from `bingbot` on the submitted paths shortly after submission.
Getting into Bing quickly is only step one. What actually matters for GEO is whether AI engines then cite the fresh page. This is where GEOly fits in. GEOly is an industry-intelligence GEO data platform: once your updated content is live in Bing, you can track your citation rate and AIGVR (its AI-generated visibility score) across ChatGPT, Copilot, and other engines, and use its citation-source analysis to see which of your URLs AI is actually pulling from. GEOly also integrates with Cloudflare Analytics, so you can line up crawl activity against citation gains. You can start with a free 3-day trial at `app.geoly.ai`. For the fuller picture of what the platform does, see [what GEOly AI is](/blog/what-is-geoly-ai).
For the two sides of crawler strategy β who you let in and how fast they see changes β pair this with [why brands should audit AI crawler access now](/blog/why-brands-audit-ai-crawler-access-now) and the [best practices to increase AI crawling and citations](/blog/best-practices-increase-ai-crawling-citations). If you are also tightening which bots can reach you, see how to [configure robots.txt for AI crawlers](/blog/configure-robots-txt-ai). Guides like this one are published by the [GEOly AI editorial team](/blog/author/geoly-ai).
FAQ
Does IndexNow submit my pages to Google?
No. IndexNow notifies Bing and Yandex. Google runs its own discovery through sitemaps and crawling. Because ChatGPT and Copilot lean on Bing's index, IndexNow is still valuable for AI visibility even without Google support.
Will IndexNow get my content into ChatGPT instantly?
It speeds up crawling, not answering. IndexNow can get a fresh page into Bing within minutes, which is a prerequisite for ChatGPT's browsing to surface it β but whether AI actually cites you depends on relevance, authority, and how extractable your content is, not on the ping alone.
How often can I submit the same URL?
Submit only when a page meaningfully changes. Repeatedly pinging unchanged URLs wastes your quota and can trigger throttling. There is no benefit to re-submitting a static page on a schedule.
Can one key cover multiple subdomains?
Each `host` you submit for must have a reachable key file it can verify against. The simplest approach is to host the key file at the root of each domain or subdomain you plan to submit.
Do I need IndexNow if Cloudflare already handles it?
If you enable Cloudflare's IndexNow integration, Cloudflare submits on your behalf and you do not need to manage keys yourself. Running your own submission on top of that is only worth it when you want precise control over exactly which URLs get pinged and when.

