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 indispensable
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. How the sitemap is built is written separately.
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 is not a Google strategy but an accelerator for the Bing family. In terms of answer-engine visibility that still matters, because some assistants are fed by the Bing index. The details of the protocol and crawl budget are written separately.
The order
The right order is this: first the sitemap is set up and comes out of the build, then the post-deployment notification step is added. 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.
Criterion
- Direction — Sitemap: Pull — the engine comes and reads · IndexNow: Push — the site notifies the engine
- Google support — Sitemap: Yes, the primary route · IndexNow: No — Google does not use this protocol
- Bing / Yandex — Sitemap: Yes · IndexNow: Yes — where the protocol is actually used
- Latency — Sitemap: Depends on the engine’s crawl schedule · IndexNow: Instant notification; crawling still joins a queue
- Scope — Sitemap: The whole site · IndexNow: Only the addresses submitted
- Verification — Sitemap: robots.txt or the search console · IndexNow: A key file in the root directory
- Change information — Sitemap: Carries a lastmod stamp · IndexNow: Only says “this address changed”
- Maintenance — Sitemap: Must come out of the build, not kept by hand · IndexNow: 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. Not being secret is part of the design rather than a flaw — the key’s job is proof of ownership, not identity.