Skip to the content
searchboar.

Crawling and indexing

What is IndexNow?

IndexNow is a protocol through which a website can notify participating search engines that a URL was created, changed or removed; the search engine still decides whether to crawl, index or rank it.

Also known as: IndexNow protocol · IndexNow submission

At a glance

  • An accepted notification is not confirmation of indexing.
  • IndexNow and Google’s Indexing API are different systems with different scope.
  • Notifications do not override robots.txt, noindex or an unavailable page.
On this page
Change notifications for new, modified and removed pages arrive at a search engine’s receiving point.
IndexNow reports URL changes to participating engines; a notification does not guarantee indexing.

What does a change notification do?

Search engines ordinarily discover URLs through links and sitemaps, then revisit them over time. IndexNow provides another signal: something at this address has changed and may deserve another look.

The notification does not contain the entire webpage or directly rewrite the search engine’s index. A new guide, a modified product or a removed job listing can each produce a URL-change event, but the value of a content update comes from the actual change, not from the number of notifications sent.

How is a submission verified?

The IndexNow documentation describes a key and an accessible key file on the website. The protocol supports notifying one or multiple URLs with valid ownership-verification information.

The key file is not a website-administration password. Its purpose is to verify the source of the notification. Even so, the submitting process should be tied to genuine content changes, with invalid or repeated submissions logged. An address on the wrong host does not become valid because its page title looks familiar.

What does a successful response prove?

An accepted request confirms receipt of the notification. It does not establish completed crawling, indexing or a search position. The page may still be unavailable, duplicated or excluded from indexing.

Keep the submitted URL, event, time and response separate from subsequent search-status checks. A dashboard that turns “notification accepted” into “successfully indexed” claims more than its evidence supports.

An example: removing a service

Imagine a repair business ending its on-site appliance service. It first decides whether the old page has a genuinely suitable replacement or should be removed without a successor.

The business implements the appropriate HTTP status code and corrects its own navigation. It then notifies participating search engines of the change through IndexNow.

The submission log can show that the notice was accepted. It cannot establish that the old result instantly disappeared from every search engine. The sequence matters: make the website accurate before announcing the change.

How does this relate to sitemaps and Google’s API?

An XML sitemap lists important canonical URLs to support discovery. IndexNow is a change-notification channel. They can complement one another, but neither replaces internal navigation or correct page responses.

Google’s Indexing API is separate. Its documented scope covers pages with JobPosting, or BroadcastEvent embedded in VideoObject. That is not general authorization to submit every business blog or glossary page through the API.

When should it become part of a workflow?

Use it when the triggering content events, participating search engines and error-handling process are clear. A CMS integration may automate notifications, but its actual behavior must be verified for the publication paths you use.

For a small, infrequently changing website, useful content, accessible URLs and internal links remain the foundation. IndexNow can supplement that foundation; it does not buy priority or bypass a search engine’s decisions.

Sources

  1. IndexNow: protocol documentation
  2. Google Search: Indexing API scope
  3. Google Search Console: Page indexing report