IndexNow is one of the few genuinely low effort wins in technical SEO. For a directory that publishes and updates pages constantly, the gap between hitting publish and a search engine noticing can be days. IndexNow closes that gap to minutes on the engines that support it. We use it across the Kings Hospitality Group portfolio, and the value is real, but only if you understand exactly what it does and, more importantly, what it does not do.
What IndexNow actually is
IndexNow is an open protocol, jointly backed by Microsoft Bing and Yandex among others, that lets a website tell search engines that a URL has changed. Instead of waiting for a crawler to rediscover a page on its own schedule, you send a short notification the moment something happens. The engine then prioritises crawling that URL. Crucially, it is a push for discovery, not a request for ranking. You are saying look at this now, not rank this higher.
The protocol is deliberately tiny. You generate a key, host a text file containing that key at your domain root so the engine can verify you own the site, and then send the changed URLs to a single endpoint. That is the whole thing. There is no account to manage and no dashboard, which is part of why it is worth wiring in early.
Setting it up properly
The setup is a one time job and then it runs itself. There are three parts.
- Generate a key. Use a long random string. This key is your proof of ownership, so treat it like a credential even though it sits in a public file.
- Host the key file. Place a text file named after the key at your domain root, containing only the key. When you ping, the engine fetches this file to confirm you control the domain.
- Send the ping. On publish or update, your system sends the changed URL or a small batch of URLs to the IndexNow endpoint along with the key. A success response means the notification was accepted, not that the page was indexed.
We bake this into the publishing pipeline so no one has to remember it. When a page goes live or a meaningful edit ships, the ping fires automatically. This is the same instinct behind how we automate sectioned XML sitemaps for large sites: the moment a human has to remember a technical step, it stops happening reliably.
The discipline that makes it useful
IndexNow is easy to abuse, and abusing it quietly destroys its value. The single rule we hold to is this: ping only canonical URLs that have genuinely changed. Not every URL on the page. Not unchanged pages on a schedule. Not parameter variants or paginated tails. Just the real, indexable page that actually changed, once, when it changed.
The reason is trust. The engines watch whether your pings correlate with real change. A site that fires thousands of pings for pages that are identical to last time teaches the engine to discount the signal, and you lose the very speed you set it up for. We see IndexNow as a promise, and a promise only works if you keep it. That is why the page being pinged must already be one you would stand behind, which ties straight into avoiding the thin page problem before you ever announce a URL.
Where it helps, and where it does not
IndexNow shines in a few specific situations that directories hit constantly. When a new listing or guide publishes and you want it discovered today rather than next week. When a page is removed or goes out of stock and you want it dropped from the index quickly so users do not land on dead content. When a significant update lands on an existing page and you want the engine to recrawl the fresh version.
It does nothing for ranking. A page pinged through IndexNow competes on exactly the same merits as any other page. If the content is thin, the faster crawl just means it gets dismissed faster. We are blunt about this internally because the protocol is so frictionless that people imagine it must be doing more than it is. It is a delivery van, not a marketing department.
The Google question
The most common question we get is whether IndexNow works with Google. The honest answer is that Google has tested consuming the protocol but has not committed to acting on it. So we treat IndexNow as a Bing, Yandex, and Seznam tool, which still matters because that traffic is real and because Bing data increasingly feeds other surfaces. For Google we lean on the reliable classics: clean sitemaps, strong internal linking, and no orphans. If you want the fuller picture of fast discovery, our guide on getting a new site indexed fast covers the whole toolkit, of which IndexNow is one piece.
Common mistakes we see
The first is pinging non canonical URLs. If a page canonicalises elsewhere, announcing it just creates confusion. Send the canonical, never the variant. The second is treating a successful ping as confirmation of indexing. The two hundred response only means the notification was received. Whether the page gets indexed still depends entirely on the page. The third is forgetting the key file. If the key file is missing, moved, or returns the wrong content, every ping silently fails verification and you get nothing while assuming it works.
The fourth, and the one that quietly undermines large sites, is over pinging during a bulk operation. When you import a thousand listings, do not fire a thousand individual pings in a burst that looks like an attack. Batch them sensibly and only include URLs that are genuinely new or changed.
How we use it across the portfolio
For us IndexNow is a small, reliable part of the launch and maintenance routine rather than a headline tactic. It earns its place because it is cheap to run and because faster discovery compounds: the sooner a good page is found, the sooner it can start earning links and traffic that improve the whole site. That compounding mindset runs through our building thesis, where the recurring lesson is that small, honest infrastructure beats clever one off tricks.
Set it up once, wire it into publish, ping only real changes to canonical URLs, and never expect it to do a content team's job. Used that way, IndexNow is exactly what it claims to be: a fast, free way to tell the search engines that listen that something on your site is worth a fresh look.
Across the Kings Hospitality Group portfolio we treat IndexNow as a discovery accelerant, not a ranking lever. Our standing rule is to ping only genuinely changed canonical URLs, never the whole site, so the signal stays honest.
Common questions
Does IndexNow work with Google?
Google has experimented with the protocol but does not commit to acting on it. Bing, Yandex, Seznam and others do consume it, so we use it for them and rely on sitemaps and links for Google.
Can IndexNow get bad pages indexed faster?
No. It only speeds discovery. A thin or duplicate page that gets crawled sooner simply gets ignored or dropped sooner. The page still has to earn its place.
How often should I ping?
Only when a canonical URL is actually created, meaningfully updated, or removed. Pinging unchanged pages wastes the signal and can look like spam.