Comparison

IndexNow vs the Google Indexing API

Two protocols that get confused constantly, run by different organisations, reaching entirely different search engines. There is no overlap.

Last reviewed 2026-08-21. We build one of the tools compared here; where another does the job better, this page says so.

Short answer

They are unrelated and do not compete. IndexNow reaches Bing, Yandex, Naver, Seznam, Yep and Amazon. The Google Indexing API reaches Google and officially accepts only JobPosting and BroadcastEvent pages.

So the question is not which to choose. Use IndexNow for the engines that implement it, and for Google use a sitemap plus Search Console. The Indexing API is relevant only if you actually publish job listings or livestream events.

Side by side

IndexNowGoogle Indexing API
Run byOpen protocol, originated by Microsoft and YandexGoogle
ReachesBing, Yandex, Naver, Seznam, Yep, Amazon (and the Internet Archive)Google only
Reaches Google?No: announced a test in Nov 2021, never adoptedYes
Eligible pagesAny URL on a host you controlOfficially JobPosting and BroadcastEvent only
AuthenticationA plain text key file at your domain root. No accountOAuth service account via Google Cloud
Batch sizeUp to 10,000 URLs per request100 URLs per batch request
Failure reporting202 from most engines regardless of key validity; 403 from the four that validate synchronouslyErrors returned directly in the API response
CostFreeFree, with quota

The confusion is worth naming

These two get conflated constantly, and tools encourage it. "instant indexing" is used as a product category covering both, which leaves people believing an IndexNow submission does something at Google. It does not. Google announced it would test IndexNow in November 2021 and has never adopted it; there is a fuller account of that here.

The practical consequence: if your traffic is overwhelmingly from Google, IndexNow will not move it. That is not an argument against using IndexNow (it is free and Bing feeds ChatGPT search, DuckDuckGo and Copilot) but it is an argument against expecting it to fix a Google problem. For those, start with why Google is not indexing the page.

What each one actually does

Both operate on discovery: telling an engine a URL exists or changed, so it does not have to wait to find out by recrawling. Neither operates on indexing. An engine that receives your submission, crawls the page and decides not to index it has behaved exactly as designed. Submission removes a delay; it does not cast a vote.

If a page is not being indexed, submitting it repeatedly changes nothing. Check whether it is indexable first: status, robots.txt, meta robots, X-Robots-Tag and canonical, because a submitted page carrying a noindex is a submission spent on a page you have told them not to keep.

Questions

Is IndexNow the same as the Google Indexing API?

No. They are unrelated protocols run by different organisations, reaching different search engines. IndexNow is an open protocol reaching Bing, Yandex, Naver, Seznam, Yep and Amazon. The Google Indexing API is Google's own authenticated API, and it officially accepts only two page types. Neither reaches the other's engines.

Can I use the Google Indexing API for normal pages?

Officially no. Google documents it as accepting JobPosting and BroadcastEvent pages only. Submitting ordinary pages through it is widely done and widely written about, but it is outside the documented contract, so nothing about its behaviour is promised and nothing about it is supported.

Which one should I use?

Both, for different engines, because they do not overlap. Use IndexNow to tell Bing, Yandex, Naver, Seznam, Yep and Amazon that a URL changed. For Google, use a sitemap and Search Console URL Inspection, and use the Indexing API only if you genuinely publish job postings or livestream events.

Does either one guarantee my page gets indexed?

Neither. Both affect discovery, which is the step where an engine learns a URL exists or changed. Whether it then crawls, indexes and ranks that page stays entirely its own decision about your content. A tool promising indexing rather than discovery is promising something no protocol provides.