Back to Blog
technical#IndexNow#Bing#Indexing#Technical SEO

IndexNow: How to Submit Changed URLs and Check What Happened

By Liwaa BeainiNovember 15, 20263 min read
99Visibility article cover for “IndexNow: How to Submit Changed URLs and Check What Happened” — 99Visibility

IndexNow tells participating search engines that a URL was added, changed or deleted. It is a change notification, not an indexing guarantee or an instruction to cite your business in an AI answer. Set it up once, send meaningful changes, and check what happened after the submission.

This guide separates the setup from the outcome. The protocol details below were checked against the official documentation and FAQ on 15 November 2026.

Before you submit: choose the URL you actually want indexed

Write down the final public address of the page. Check the host, path and canonical. An old URL that redirects, a private preview and the public article are different addresses; sending all three makes your own submission history harder to interpret.

Our recommended submission record has a URL, the change made, the release time, the submission time and the response. That gives you something to investigate when a page stays absent. A success message without the URL or timestamp is a poor debugging record.

Set up the key and send a changed URL

The official protocol uses a public text file to verify the host. Place the key in its verification file on the same host as the submitted pages; a non-root location uses the keyLocation field and has path-scope rules. See the protocol examples before choosing that option.

  1. Check your current integration. If a CMS plugin already handles IndexNow, inspect its configuration and submission history before adding a second sender.
  2. Publish the verification file. Open its public address and inspect the response body. A branded HTML error page with a successful HTTP status is not a valid key file.
  3. Pick a meaningful change. Use a newly published page or one with a real correction. Avoid sending an unchanged site simply to create activity.
  4. Send the notification and record the response. Use the official endpoint or your established CMS integration.

The following is a worked request using fictional values. Replace the host, key and URL with your own verified setup:

curl --request POST 'https://api.indexnow.org/indexnow'   --header 'Content-Type: application/json; charset=utf-8'   --data '{
    "host": "www.example.com",
    "key": "example-indexnow-key-12345678",
    "urlList": ["https://www.example.com/guides/new-page"]
  }'

The documentation permits up to 10,000 URLs per POST. It distinguishes 200 success, 202 received with key validation pending, 400 malformed request, 403 invalid key, 422 URLs outside the allowed host or key scope, and 429 throttling.

Accepted is the start of the check

The IndexNow FAQ explicitly says submission does not guarantee indexing. Each engine makes its own decision. Keep an XML sitemap for discovery, and notify IndexNow about changes rather than repeatedly resending unchanged pages.

After a submission, work through three separate questions:

QuestionEvidence to keepWhat it does not establish
Did the endpoint accept it?Request timestamp and responseThe page entered an index
Could a crawler retrieve the page?Verified request and returned contentThe engine chose to index it
Is the page indexed or cited?The engine's inspection/report or a captured answerYour submission caused that outcome

For our own troubleshooting workflow, check that the public page loads and review the engine's URL inspection. A separate AI crawler access check can investigate AI-agent permissions; it does not establish Bingbot access or index status. If access fails, investigate the response before sending the same URL again. Our own indexing investigation explains why a published page and an indexed page must be counted separately.

Does IndexNow make ChatGPT cite you?

We have no evidence that an accepted IndexNow notification causes a ChatGPT citation. Microsoft's AI Performance announcement describes IndexNow as a way to notify participating engines about changes. That is narrower than a promise about any particular answer.

For a useful release check, record the corrected page, the notification and any later observed answer independently. If AI still quotes an old price, save the answer and its cited URL. That gives you a concrete fact to fix rather than a reason to keep pressing Submit. Use the GEO checklist to separate access problems from answer problems.

Method and limits: documentation review, 15 November 2026. The example was not submitted. No crawl-speed experiment, indexing-time benchmark or citation-lift claim is made.

Share

Want more of our research in Google Search and AI Mode? Add us as a preferred source.

Add 99Visibility as a preferred source on Google

Can AI crawlers reach your site?

Your free audit requests your site as each AI crawler, reads robots.txt bot by bot, and shows every place your firewall disagrees with it.

Start for Free

Related Articles