IndexNow: Submitting Changed URLs to Search Engines
IndexNow is an open protocol that lets a site tell search engines on its own that a URL has been added, changed or deleted, instead of waiting for a crawler to notice. According to the project's website, it's supported by Microsoft Bing, Naver, Seznam.cz, Yandex and Yep, and a submission sent to one of them is shared with the others. Google isn't on that list. IndexNow doesn't replace your sitemap and isn't meant for sending every URL at once: according to the project's FAQ, you submit only what has changed, and a 200 response only means the search engine received the URL.
What IndexNow Is and Why It Exists
A search engine learns about changes to a page when its crawler comes back, and crawlers don't revisit every URL often. The IndexNow project's website says that without a notification, it can take days to weeks for search engines to discover that content has changed. IndexNow reverses the direction: the site signals that something has changed at a specific URL, and the search engine can fetch that URL sooner instead of looking for changes blindly.
In its simplest form, a submission is a single HTTP request with the page URL and the owner's key. The protocol is open, published under the Creative Commons Attribution-ShareAlike license, and ownership of the host is proven with a key file on the server. It covers three events: adding a new page, updating an existing one and deleting one. That matters, because a deletion or a redirect is also information a search engine should get quickly, so it doesn't keep showing a URL that no longer exists.
IndexNow doesn't decide what gets indexed. The project's FAQ points out that after a submission, the search engine decides for itself whether to fetch the URL, based on its crawl quota, its scheduling and its quality signals, and that a submission doesn't guarantee immediate indexing. Every submitted URL also counts toward the site's crawl quota. The protocol speeds up the discovery of a change, not the evaluation of the page.
Which Search Engines Support IndexNow
The project's website lists Microsoft Bing, Naver, Seznam.cz, Yandex and Yep as supporting IndexNow. The protocol's public file of endpoints currently also includes entries for the Internet Archive and for Amazon's crawler. The mechanism is shared: search engines that adopt the protocol agree to share submitted URLs with the other participants, so a single submission to any endpoint is enough. The FAQ adds that each search engine decides for itself whether to index a submitted URL, so the same page can be indexed by one of them and not by another.
Google isn't on the list of participating search engines and doesn't publicly describe support for the protocol. In its documentation on asking Google to recrawl your URLs, Google points to two routes: a sitemap for many URLs and the URL Inspection tool in Search Console for individual pages, with the caveat that a request doesn't guarantee inclusion in results, either quickly or at all, and that crawling itself can take anywhere from a few days to a few weeks. Google also has the Indexing API, but it isn't Google's version of IndexNow. According to Google's documentation, it's only for pages with job postings and livestreams, as we explain in our article on the Google Indexing API.
Key, File and Response: How a Submission Works
The IndexNow documentation requires the owner to prove that the host belongs to them. That's what the key is for: a string of 8 to 128 characters made of letters, digits and dashes, stored in a text file on the server. The recommended option is a file named after the key in the site's root directory. When a search engine receives a submission, it fetches that file and checks that it contains the key. You can also put the file deeper in the site, but then the key only covers URLs in that part of the site, and the documentation strongly recommends the root.
A single URL is submitted with a plain GET request carrying the URL and the key as parameters. Many URLs at once go in a POST request with a JSON list, up to 10,000 URLs per request. Read the responses literally. A 200 only means the search engine received the URL. A 202 means the URL was accepted, but key validation is still pending. A 403 means the key isn't valid, for example because the file is missing or doesn't contain the key. A 422 means the URLs don't belong to the host or the key doesn't match the schema, and a 429 means too many requests, which the documentation describes as potential spam.
A 403 here means the same thing it means in any HTTP response: the server understood the request but refuses it. We explain how that same status code can stop AI crawlers at the network edge in our article on 403 Forbidden and AI crawlers. With IndexNow, the most common cause is a key file that doesn't return a 200 at the expected URL.
What to Submit Through IndexNow and What Not To
The project's FAQ is specific on this. You submit URLs where content has been added, updated or deleted: new articles and products, changes in prices and availability, removed pages. You also submit URLs that now redirect, and URLs that return a 404 or a 410, so the search engine can update its index. You don't submit every minor layout change or cosmetic fix, and a URL submitted again should wait at least five minutes and carry a meaningful change.
IndexNow isn't meant for sending every URL on the site at once. The FAQ allows a full submission only after a migration or a redesign, when the whole site really has changed. It also isn't meant for submitting changes made before you adopted the protocol: for those, the project points to a sitemap with accurate last-modified dates. The conclusion is simple: the sitemap is the full inventory of URLs, and IndexNow is the running update on what has changed since last time.
The most common mistake comes from mixing up those two roles. A plugin or script that sends the entire sitemap on every publish turns IndexNow into a second sitemap. It submits hundreds of URLs that haven't changed, uses up the crawl quota and pushes the site toward 429 responses. A submission should contain only the URLs that actually changed, and that requires knowing what was there before.
IndexNow, Bing, Copilot and ChatGPT
Microsoft connects IndexNow with AI search in two places. The documentation for Copilot in organizations describes how, with web search turned on, Copilot generates a query, sends it to the Bing search service and builds its answer from the results (managing web search in Microsoft Copilot). In a February 2026 post introducing the AI Performance report in Bing Webmaster Tools, Microsoft states that IndexNow helps keep information fresh in search and in AI answers, so that AI systems reference the latest version of a page. That's the vendor's statement, not a documented mechanism or a measured effect.
ChatGPT calls for more caution. OpenAI's crawler documentation doesn't mention Bing, and the documented gate to ChatGPT search is the OAI-SearchBot crawler and whether it can access the page. So we don't assume that an IndexNow submission or being in Bing's index translates into what ChatGPT shows. If your goal is ChatGPT search, the thing to check is whether OAI-SearchBot can actually reach your pages.
What Counts as Changed: How We Handle It on This Site
This site submits to IndexNow only the URLs that are new, changed or deleted since the previous submission. A script handles it, running automatically after a successful deployment: it waits for the new version to roll out across the network, compares the live site with the saved state and sends only the difference. The state after each submission is committed to the repository, so the history of that file doubles as a log of submissions.
The most interesting decision is what "changed" means. We don't use the last-modified dates from the sitemap, because some pages deliberately don't have one, and those include some of the most frequently edited ones. Instead, the script computes a fingerprint from the title, the description, the canonical URL and the text of the page's main content. A change to the site-wide header or footer alone is deliberately not submitted: otherwise every footer fix would mean resubmitting the whole site, which is exactly what the project's FAQ advises against.
Before comparing, the script runs positive controls: the key file has to respond live and contain the key, the sitemap has to be reachable, and the homepage has to produce a valid fingerprint. If any of them fails, the result is a blind measurement with its own exit code, and no submission goes out. If the difference covers more than 25% of the URLs, the script refuses and waits for a human decision, because a change that large needs a look first: it may be a real redesign, but it may also be a measurement error.
What We Look for in an IndexNow Audit
In audits, we regularly see plugins that send the entire sitemap through IndexNow after every publish, and key files that stopped returning a 200 after a template change or a site move. We also see sites where IndexNow was supposed to replace the sitemap. That's why we start the review with what actually goes out and when, not with whether the protocol is turned on.
The key file. We check that it returns a 200 at the URL implied by the submission, without a redirect, and that it contains exactly the key. A file in a subdirectory only covers URLs in that part of the site.
The scope of submissions. We compare the submitted URLs with the changes on the site: whether only new, changed and deleted URLs go out, whether a footer change sends out the whole site, and whether submissions cover a staging version.
Responses. We read the status codes in the submission logs. A 200 isn't proof of indexing, and repeated 403 or 429 responses are a signal to fix the key or the frequency.
The sitemap alongside IndexNow. We check that the sitemap is complete and has accurate dates, because it's the sitemap, not IndexNow, that serves as the full inventory of URLs for search engines, Google included.
Summary
IndexNow is a simple protocol for notifying search engines about added, changed and deleted URLs. It's supported by Microsoft Bing, Naver, Seznam.cz, Yandex and Yep, and a submission reaches all participants. Google isn't on that list, and its Indexing API has a different, narrow scope. Microsoft states that IndexNow helps keep AI answers in its services fresh. For ChatGPT, the documented gate remains access for the OAI-SearchBot crawler.
IndexNow pays off most when you use it the way the project's FAQ describes: only for URLs that have changed, alongside a complete sitemap, with checks on the key file and the responses. We review indexing in Bing and Google as part of our SEO audits. If you want to see what your site actually sends to search engines, request a quote.