Technical SEO · April 22, 2026 · 6 min read
IndexNow vs. XML Sitemaps: Why Real-Time Indexing Beats Waiting for Googlebot
Most SEO tools submit a sitemap and hope for the best. IndexNow tells Bing and Yandex about your new content the instant it publishes. Here's how the protocol works, which search engines support it, and why we built it into every FluxWriter post.
By FluxWriter Team
The problem with relying on sitemaps
An XML sitemap is a passive document. You publish a post, ping the sitemap, and then wait — sometimes hours, often days — for a crawler to revisit, parse the file, queue the URL, and finally fetch it. For news, product launches, and time-sensitive SEO experiments, that delay is a real cost.
What IndexNow actually does
IndexNow is a tiny open protocol. You POST a JSON payload to a participating search engine's endpoint with the URL(s) you just published or updated, plus a key file you host on your domain to prove ownership. The engine acknowledges within milliseconds and queues a near-immediate fetch.
A minimal request:
POST https://api.indexnow.org/indexnow
Content-Type: application/json
{
"host": "example.com",
"key": "abc123...",
"keyLocation": "https://example.com/abc123....txt",
"urlList": ["https://example.com/blog/new-post"]
}
That's it. No sitemap diff, no crawl budget guesswork.
Who actually honors it
- Bing — yes, fully.
- Yandex — yes, fully.
- Seznam, Naver — yes.
- Google — officially "evaluating" since 2021. In practice: not yet.
If your traffic is Google-dominant, IndexNow is complementary, not a replacement. But Bing market share for AI-assistant referrals (Copilot, ChatGPT search) has grown enough in 2025–2026 that ignoring it is leaving traffic on the table.
How we wired it into FluxWriter
Every published post fires an IndexNow ping as part of the publish step, with the same key file we generate when you connect a new site. There's nothing to configure — if your site is connected, your posts get pinged.