When you publish new content or update existing pages, search engines need to discover those changes before they can rank them. Traditionally, this meant waiting for crawlers to revisit your site on their own schedule — a process that could take days or even weeks depending on your site's crawl frequency and authority.
IndexNow changes that entirely.
Developed by Microsoft and adopted by Bing, Yandex, and other search engines, IndexNow is an open protocol that lets you instantly notify search engines the moment a URL is created, updated, or deleted. Instead of waiting for a crawler to find the change, you push the notification directly. Think of it like the difference between mailing a letter and sending a text message.
For marketers, founders, and agencies focused on organic traffic growth, this matters because faster indexing means faster ranking signals, faster visibility, and a shorter path from publishing to performance. If you're producing SEO or GEO-optimized content at scale — the kind designed to get your brand mentioned across AI search — delays in indexing are a direct tax on your content ROI.
This guide walks you through the complete setup process for IndexNow on Microsoft Bing: generating your API key, verifying ownership, submitting URLs manually and programmatically, and confirming everything is working. By the end, you'll have a fully functional IndexNow integration that automatically notifies Bing every time your content changes. No more waiting on crawl schedules.
Step 1: Understand What IndexNow Does (and What It Doesn't)
Before you touch a single file, it helps to understand exactly what you're setting up and what to expect from it. IndexNow operates on a push-based notification model. Rather than waiting for a search engine crawler to revisit your site and detect changes, you send a signal directly to the search engine saying: "This URL has changed. Come look at it."
That's a meaningful shift from traditional passive crawling, where search engines decide when to visit your pages based on their own crawl schedules, your site's authority, and internal prioritization algorithms.
What IndexNow does: It notifies participating search engines that a URL has been created, updated, or deleted. It accelerates the discovery process.
What IndexNow does not do: It does not guarantee immediate indexing. It does not guarantee ranking. It signals intent and priority, but the search engine still decides whether and when to crawl and index the submitted URL.
The protocol is currently supported by Microsoft Bing, Yandex, Seznam.cz, Naver, and other members of the IndexNow consortium. You can submit to all participating engines simultaneously by using the shared endpoint at api.indexnow.org instead of a search-engine-specific URL.
One important clarification: Google has not adopted IndexNow for general web URLs. Google operates its own separate Indexing API, which is restricted to specific content types like job postings and live streams. If you're thinking about how to index a website in Google, that requires a different process entirely. Set accurate expectations here: IndexNow is primarily a Bing and Yandex play, not a Google play.
IndexNow is most valuable in specific scenarios: sites that publish frequently, e-commerce stores with constant product or pricing changes, news and blog platforms, and any operation where content freshness directly affects performance.
One common pitfall worth addressing early: IndexNow does not replace your XML sitemap. Your sitemap gives search engines a comprehensive map of your site's structure. IndexNow tells them about real-time changes. They serve different purposes and work best together. If you haven't set up a proper sitemap yet, reviewing XML sitemap best practices before proceeding is worth your time. IndexNow also helps address crawl budget optimization by reducing unnecessary crawling — search engines can prioritize pages you've flagged as changed rather than re-crawling everything blindly.
Step 2: Generate Your IndexNow API Key
Your API key is the credential that proves you own the domain you're submitting URLs for. Every IndexNow submission you make will include this key, and Bing will verify it against a file you host on your domain. Get this right from the start.
The easiest way to generate a key is through Bing Webmaster Tools directly. Navigate to webmaster.bing.com, log in with your Microsoft account, and select your verified site. From there, go to URL Submission, then IndexNow. Bing will generate a key for you automatically and even walk you through the verification file step.
If you prefer to generate a key manually, the IndexNow specification has clear requirements. The key must be at least 8 characters long, alphanumeric, and case-sensitive. Hex characters are recommended for compatibility. In practice, a UUID-style string works perfectly — you can generate one using any standard UUID generator tool online. A key that looks like a1b2c3d4e5f67890a1b2c3d4e5f67890 is exactly the format you want.
A few guidelines for your key:
Keep it random: Do not use your domain name, brand name, or any guessable string. The key's purpose is verification, not memorability.
Save it securely: You'll use this key in two places — the verification file you host on your domain, and every API request you make. Losing it means regenerating and re-verifying, which creates unnecessary downtime in your submission pipeline.
Treat it like a credential: While the key itself is semi-public (it's hosted in a text file on your domain), you should still store it in a secure location like an environment variable or secrets manager rather than hardcoding it in public repositories.
Once you have your key, keep it somewhere accessible. You'll need it in the next step when you create the verification file, and again in Step 4 when you start making API calls.
Step 3: Host Your Key File on Your Domain
This is the verification step that proves to Bing you actually own the domain you're submitting URLs for. The process is simple but the details matter — getting this wrong is the most common reason IndexNow setups fail.
Create a plain text file. Name it exactly your API key string followed by .txt. For example, if your key is a1b2c3d4e5f67890, your file should be named a1b2c3d4e5f67890.txt.
Open that file and add only your API key string as the file's content. Nothing else. No line breaks, no whitespace, no additional text. Just the key.
Upload this file to the root of your domain. The final accessible URL should look like this:
https://yourdomain.com/a1b2c3d4e5f67890.txt
Once it's uploaded, open that URL in a browser. You should see only the key string displayed. If you see anything else, or if the page returns an error, fix it before proceeding.
Platform-specific notes:
WordPress: Upload the file via FTP or SFTP directly to your public_html root directory. Alternatively, several IndexNow plugins handle this automatically during setup.
Webflow: Use the Webflow hosting panel to upload the file as a static asset, then configure a custom route or use the file hosting feature to serve it from the root path.
Shopify: Shopify restricts root-level file hosting. You may need to use a third-party app that handles IndexNow verification, or serve the key file from a subdomain if your store is hosted on a custom domain with more control.
Custom or headless setups: Configure your server or CDN to serve the file at the root path with the correct content type (text/plain).
Two critical checks before moving on. First, confirm the file returns an HTTP 200 status code, not a 301 or 302 redirect. Bing will not follow redirects for key verification. Second, confirm the file is accessible at the root level — hosting it in a subdirectory like /assets/ or /files/ will cause verification to fail. Bing looks specifically at the root.
If you run into broader indexing issues during this process, reviewing common website indexing issues can help you diagnose what's going wrong.
Step 4: Submit URLs to Bing via the IndexNow API
With your key file live and accessible, you're ready to start submitting URLs. IndexNow gives you two submission methods: single URL via GET request, and bulk submission via POST request. Both use the same endpoint.
The Bing-specific IndexNow endpoint is: https://www.bing.com/indexnow
If you want to notify all participating search engines simultaneously with one request, use the shared endpoint instead: https://api.indexnow.org/indexnow
Single URL submission (GET request):
For a quick test or a single page update, send a GET request in this format:
https://www.bing.com/indexnow?url=https://yourdomain.com/your-page&key=yourapikey
You can open this directly in a browser or send it via curl. If everything is configured correctly, you'll get a 200 response and the URL will be queued for crawling.
Bulk URL submission (POST request):
For submitting multiple URLs at once, use a POST request with a JSON body. The structure looks like this:
POST https://www.bing.com/indexnow
Content-Type: application/json
The JSON body should include: host (your domain without protocol), key (your API key), keyLocation (the full URL to your key file — optional but recommended), and urlList (an array of fully qualified URLs to submit).
A complete JSON body example looks like: {"host": "yourdomain.com", "key": "yourapikey", "keyLocation": "https://yourdomain.com/yourapikey.txt", "urlList": ["https://yourdomain.com/page-1", "https://yourdomain.com/page-2"]}
You can submit up to 10,000 URLs per POST request per the official specification. Daily submission limits also apply, so use your quota wisely.
Understanding the response codes:
200: Accepted. URLs received and queued successfully.
202: Accepted, but key verification is still pending. The submission will be processed once verification completes.
400: Bad request. Check your request format and JSON structure.
403: Forbidden. Your key doesn't match what Bing found at the key file URL. Re-check your key file is accessible and contains the correct key string.
422: Unprocessable entity. The submitted URLs don't match the declared host, aren't fully qualified, or contain encoding issues.
429: Too many requests. You've hit the rate limit. Slow down submissions and implement a queue.
One important discipline: only submit URLs that have actually changed. Submitting your entire site every day wastes quota, may trigger rate limiting, and signals low quality to the engine. Submit only what's new or meaningfully updated. For broader context on getting your pages discovered, the guide on submitting your website to search engines covers the full picture beyond just IndexNow.
Step 5: Automate Submissions with Your CMS or Platform
Manual submissions are useful for testing, but they're not a sustainable workflow. The real value of IndexNow comes from automating submissions so every content publish or update triggers a notification without any manual intervention.
Here's how automation looks across common platforms:
WordPress: Microsoft publishes an official IndexNow plugin in the WordPress repository. Install it, enter your API key during setup, and it handles everything from there. Every time you publish a new post, update an existing page, or modify a product, the plugin automatically fires the IndexNow submission. This is the lowest-friction path for WordPress users.
Custom CMS or headless setups: Trigger the IndexNow POST request via a webhook or server-side function that fires on content publish events. A simple curl command executed server-side after a content update is all you need. The pattern is: content is saved, publish event fires, webhook calls a function, function sends the POST request to the IndexNow endpoint with the updated URL in the payload.
A basic curl example for a server-side trigger looks like this:
curl -X POST "https://www.bing.com/indexnow" -H "Content-Type: application/json" -d '{"host":"yourdomain.com","key":"yourapikey","urlList":["https://yourdomain.com/updated-page"]}'
Shopify and e-commerce platforms: Use third-party apps from the Shopify App Store that support IndexNow, or implement a custom script that fires on product updates, price changes, or inventory modifications. For high-frequency e-commerce operations, automating IndexNow on product changes can meaningfully improve how quickly updated pricing or availability appears in search results.
Sight AI's built-in integration: For teams using Sight AI's CMS auto-publishing capabilities, IndexNow submissions are handled automatically when content is published through the platform. The system notifies search engines as part of the publishing workflow, so there's no separate configuration required beyond the initial key setup. This is particularly valuable when you're publishing SEO and GEO-optimized content at scale and need every article indexed as quickly as possible.
Two operational tips worth building in from the start:
Log everything: Record each submission along with the response code, timestamp, and submitted URLs. This audit trail makes troubleshooting significantly easier and helps you track submission patterns over time.
Avoid over-triggering: Don't fire a submission on every minor edit. Implement a debounce or batch delay so that multiple rapid edits to the same page result in one submission, not twenty. This preserves your daily quota for content that actually matters.
Step 6: Verify Your Setup in Bing Webmaster Tools
You've generated your key, hosted your verification file, and started submitting URLs. Now you need to confirm the whole system is actually working as expected. Bing Webmaster Tools is where you close that loop.
Log into Bing Webmaster Tools at webmaster.bing.com and navigate to URL Submission, then IndexNow. This section shows your IndexNow submission history — every URL you've submitted, when it was received, and its processing status.
What you're looking for: submitted URLs appearing in the log with 200 or 202 status codes. A 200 means the URL was accepted and queued. A 202 means it was accepted but key verification was still pending at the time of submission, which typically resolves quickly.
Beyond the submission log, use the URL Inspection tool in Bing Webmaster Tools to check the crawl and index status of specific pages you've submitted. This tells you whether Bing has actually crawled the page since your submission and whether it's been indexed.
Diagnosing common errors:
403 errors in your submission log: Bing couldn't find or verify your key file. Go back to Step 3 and confirm the file is accessible at the root URL, returns HTTP 200 (not a redirect), and contains only the key string with no extra characters.
422 errors: Your submitted URLs have a format problem. Check that all URLs are fully qualified (they must start with https://), that they match the host you declared in your request, and that they don't contain unencoded special characters.
429 errors: You're hitting rate limits. Reduce submission frequency, implement batching, and ensure you're only submitting changed URLs rather than your full URL inventory.
For ongoing monitoring, watch the crawl activity graph in the Bing Webmaster Tools dashboard. You should see spikes in crawl activity that correlate with your IndexNow submissions. If you're submitting URLs but seeing no corresponding crawl activity, something upstream in the pipeline needs attention. Pairing this with a broader SEO performance dashboard gives you a complete view of how indexing activity connects to traffic and ranking outcomes.
What success looks like in practice: submitted URLs appearing in the IndexNow log with 200 or 202 statuses, followed by crawl activity in the dashboard, followed by pages appearing or updating in Bing search results within hours to a few days. The timeline varies based on page authority and content quality, but the signal chain should be visible.
Putting It All Together: Your IndexNow Checklist
You now have everything you need to run a fully functional IndexNow integration. Before you call it done, run through this checklist to make sure nothing was missed:
1. API key generated and saved securely — either via Bing Webmaster Tools or a UUID generator, meeting the minimum 8-character alphanumeric requirement.
2. Key file hosted at the root of your domain — named exactly as your key with a .txt extension, containing only the key string, returning HTTP 200 with no redirects.
3. Test submission sent and verified — a single GET or POST request to the Bing IndexNow endpoint returned a 200 or 202 response.
4. Automation configured — your CMS, webhook, or plugin is set up to trigger submissions automatically on content publish and update events.
5. Submission logging in place — you're recording responses so you can audit and troubleshoot your submission history.
6. Bing Webmaster Tools verified — you can see submitted URLs in the IndexNow log and crawl activity in the dashboard.
A reminder that's worth repeating: IndexNow works alongside your XML sitemap and robots.txt, not instead of them. If you haven't built out a solid sitemap yet, the guide on how to create an XML sitemap is a natural next step. These tools serve different functions and are stronger together.
Faster indexing amplifies the value of high-quality content. Getting indexed quickly only matters if the content is worth ranking. For teams publishing SEO and GEO-optimized content at scale, combining IndexNow automation with a platform like Sight AI creates a compounding advantage: content is created by specialized AI agents, published directly to your CMS, and submitted to search engines automatically — all without manual intervention at each stage.
IndexNow is a straightforward setup with a high-impact payoff. You're removing the single biggest delay between content creation and search visibility. Combined with a consistent content operation and the right tools, that acceleration compounds over time into a meaningful organic traffic advantage.
If you're ready to go further than just faster indexing, Start tracking your AI visibility today and see exactly where your brand appears across ChatGPT, Claude, Perplexity, and other top AI platforms — so you can optimize not just for traditional search, but for the AI-driven discovery that's reshaping how audiences find brands.
