IndexNow or a sitemap.
A sitemap is a list the engine reads; IndexNow is a notification sent to the engine — one pulls, the other pushes, and neither replaces the other.
The two mechanisms approach the same problem from opposite directions: how will the engine learn about a new or changed page? A sitemap leaves a list and waits for the engine to come and read it; IndexNow sends a request and tells it.
Why a sitemap is still needed
A sitemap is not merely a list of addresses: each entry can carry a last-modified stamp, and the engine sets crawl priority partly by it. That is why the stamp has to be real — pulling every address to today on each build is an easy shortcut, but it stops carrying information. If everything is new, nothing is.
On this site the stamp is tied to the page’s content fingerprint and only advances when the output really changes. The map, too, is derived from the list of GENERATED pages rather than from intent — so an address can never appear in the map without being published. We explain how the sitemap is built in a separate guide.
Where IndexNow fits
IndexNow does one thing and does it well: it reports instantly that an address has changed. A notification is not a guarantee of crawling — the engine still weighs it in its own queue — but it gets you into the line instead of waiting for the schedule. On newly published content the difference can be a matter of hours.
Its limit is plain: Google does not use it. So IndexNow speeds up indexing only in the Bing family. In terms of answer-engine visibility that still matters, because some assistants are fed by the Bing index. We cover the details of the protocol and crawl budget on separate pages.
The order
The right order is this: first set up the sitemap so that it comes out of the build, then add the post-deployment notification step. A notification step that runs BEFORE deployment is wasted — the engine comes, looks, and finds the old content. On this site, if the notification tool cannot verify the key file live, it stops honestly and reports an error.
If you want to know how your brand is cited in ChatGPT, Google AI Overviews and Perplexity, our GEO consulting records which questions and engines cite you and builds the prerequisites.
Criterion
Sitemap
Direction Pull — the engine comes and reads
Google support Yes, the primary route
Bing / Yandex Yes
Latency Depends on the engine’s crawl schedule
IndexNow
Direction Push — the site notifies the engine
Google support No — Google does not use this protocol
Bing / Yandex Yes — where the protocol is actually used
Latency Instant notification; crawling still joins a queue
Sitemap
Scope The whole site
Verification robots.txt or the search console
Change information Carries a lastmod stamp
Maintenance Must come out of the build, not kept by hand
IndexNow
Scope Only the addresses submitted
Verification A key file in the root directory
Change information Only says “this address changed”
Maintenance Triggered after deployment
| Criterion | Sitemap | IndexNow |
|---|---|---|
| Direction | Pull — the engine comes and reads | Push — the site notifies the engine |
| Google support | Yes, the primary route | No — Google does not use this protocol |
| Bing / Yandex | Yes | Yes — where the protocol is actually used |
| Latency | Depends on the engine’s crawl schedule | Instant notification; crawling still joins a queue |
| Scope | The whole site | Only the addresses submitted |
| Verification | robots.txt or the search console | A key file in the root directory |
| Change information | Carries a lastmod stamp | Only says “this address changed” |
| Maintenance | Must come out of the build, not kept by hand | Triggered after deployment |
FREQUENTLY ASKED QUESTIONS
Does IndexNow help with Google?
No. Google does not use the IndexNow protocol and follows the sitemap route. The protocol’s home is Bing, Yandex and engines in the same family — and since Copilot citations are fed by the Bing index, it is still worth having.
Do I need both?
A sitemap is needed in every case; IndexNow is an optional accelerator. Without a sitemap IndexNow stays incomplete, because addresses that are never submitted can only be found through the map.
Is the key file secret?
It is not. By protocol the key is published as plain text at the site root, and the engine reads it while verifying the notification. The key being public comes from the protocol’s design: it only proves ownership of the site.