More and more shoppers discover products by asking an AI: "which trail shoes under $100 do you recommend?", "where can I buy hypoallergenic dog food?". ChatGPT and Copilot answer those questions with what Bing has indexed. If your catalog isn't current there, a competitor gets the recommendation. IndexNow is the fastest mechanism to prevent that.
The classic indexing model is pull: the search engine's robot visits your site every so often, discovers what changed and re-indexes it. Fine for a blog. For ecommerce it's a structural problem: prices change daily, products go in and out of stock, launches matter most in their first week. Between the real change and the robot's visit, days or weeks can pass — and in that gap the search engine (and the AI that relies on it) answers with stale data: outdated prices, sold-out products, invisible launches.
IndexNow flips the model: push instead of pull. It's an open protocol driven by Microsoft Bing that defines a standard way to tell search engines a URL changed, the moment it changes.
Technically it's simple and elegant:
{key}.txt file published at your domain root) proving the domain is yours.The engine answers "accepted" in milliseconds and schedules re-indexing with priority. There's no instant-indexing guarantee (each engine decides), but the practical difference against waiting for the crawler is days versus minutes.
Here's the point almost nobody connects: ChatGPT uses Bing's index as the base for answering searches with fresh information, including product searches and shopping recommendations — B2C and B2B alike. Copilot is literally Bing with AI on top. Optimizing your presence on Bing stopped being "3% of traffic" and became the gateway to the fastest-growing discovery channel: generative answers. That territory already has a name of its own: GEO, Generative Engine Optimization.
The equation: catalog current on Bing → products visible and correct when the AI answers. IndexNow is the shortest channel between your catalog and that index.
Transparency first:
If your site is a custom build, you can implement the protocol by hand: generate the key, publish the file and fire the POSTs on every change (the official documentation is short).
If your store runs on a platform like Tiendanube, there are two obstacles: the platform doesn't notify IndexNow for you, and it doesn't let you publish the key file at the domain root. That's exactly what IndexNow Connect solves: it listens to every catalog addition, change and removal in real time, submits the URLs to IndexNow for you, and guides you to publish the key on your domain with a free Cloudflare Worker — without touching your store's code or its load times.
No. Google doesn't participate in the protocol: for Google you still rely on your sitemap and classic crawling. IndexNow accelerates Bing and the engines that share its notices — and with them, ChatGPT and Copilot answers.
No. The response confirms the engine received the notice and will prioritize the recrawl. Final indexing still depends on your content's quality and authority.
No: they complement each other. The sitemap is the full inventory engines re-read periodically (pull); IndexNow is the instant notice for each change (push). Best practices for both are in our sitemap guide.
On a custom site you implement the protocol yourself (it's short). On SaaS platforms like Tiendanube, IndexNow Connect automates the whole process: it listens to catalog changes and submits the URLs for you.
Connect your store for free → — free plan with 500 URLs per month, 1-minute setup.