Every time you publish or update content, search engines need to discover those changes before they can rank them. Traditionally, that meant waiting for crawlers to find your pages on their own schedule, which could take days or even weeks depending on your site's crawl budget and authority.
IndexNow changes that equation entirely. It's an open protocol co-developed by Microsoft and Yandex that lets you push real-time URL notifications directly to participating search engines the moment content changes on your site. Instead of waiting to be found, you announce yourself.
For marketers, founders, and agencies focused on organic traffic growth, this shift from passive discovery to active notification can meaningfully accelerate how quickly new and updated content enters search indexes. Think of it like the difference between mailing a letter and sending a text message. Both deliver the information, but one arrives in seconds.
This guide walks you through the complete IndexNow integration process for websites in five concrete steps: generating your API key, hosting the verification file, submitting URLs, automating the workflow, and verifying your results. Whether you're running a WordPress site, a custom-built platform, or a headless CMS, the core process is the same.
By the end, you'll have a fully functional IndexNow setup that notifies search engines automatically whenever your content changes, giving your pages a faster path to discovery and ranking.
Step 1: Generate Your IndexNow API Key
Before you can submit a single URL, you need an API key. This key is how participating search engines verify that you actually own the domain you're submitting URLs for. Without it, any submission attempt will be rejected outright.
The key itself has specific technical requirements. It must be an alphanumeric hex string containing only characters in the range [a-z, 0-9], and it must be between 8 and 128 characters in length. No uppercase letters, no special characters, just a clean hex string.
You have two practical options for generating this key.
Option 1: Generate manually. Use any random hex generator tool online. Search for "random hex string generator," set the character length to at least 32 characters for good uniqueness, and copy the output. Paste it into a text file and keep it somewhere safe.
Option 2: Use Bing Webmaster Tools (recommended). Navigate to bing.com/webmasters, sign in with a Microsoft account, and add your site if you haven't already. Once inside, look for the IndexNow option under the "Configure My Site" section in the left navigation. Bing will auto-generate a valid API key for you and even walk you through the next step of hosting the key file. This is the faster path for most users because the key is already formatted correctly and tied to your verified site.
One important clarification: you only need a single API key per domain. That same key works across all IndexNow-compatible search engines, including Bing, Yandex, Seznam.cz, and Naver. When you submit to the shared IndexNow endpoint, the notification propagates to all participating engines simultaneously. You don't need separate keys for each.
Once you have your key, save it in a secure, accessible location. You'll reference it in every API call you make and in the verification file you'll create in the next step. Losing track of it mid-setup is a common source of frustration, so treat it like a password: store it deliberately before moving on.
Quick tip: If you're managing IndexNow for multiple domains, generate a separate key for each domain. Keys are domain-specific, and mixing them up will cause verification failures.
Step 2: Host the Key Verification File on Your Domain
Generating a key is only half the ownership proof. Search engines won't accept your submissions until they can independently verify that the key you're using actually belongs to your domain. They do this by fetching a specific file from your server. If the file is there and matches your key, verification passes. If not, your submissions will return a 403 Forbidden error.
Here's exactly what you need to do.
Create a plain text file and name it after your API key with a .txt extension. If your key is abc123def456, the file should be named abc123def456.txt. The filename must match the key exactly, character for character.
Inside the file, place only the API key string on a single line. No extra spaces before or after it, no line breaks at the end, no formatting of any kind. The file contents should be exactly and only your key. Some text editors add a trailing newline automatically, so double-check this before uploading.
Upload the file to the root directory of your website. The goal is for the file to be publicly accessible at this exact URL: https://yourdomain.com/[your-key].txt. After uploading, open that URL in a browser. If you see only your key string displayed in the browser window, the file is correctly placed and publicly accessible.
For WordPress users: Connect to your server via FTP or SFTP and upload the file to the public_html folder. Alternatively, use the file manager inside your hosting control panel (cPanel, Plesk, etc.) to upload directly. Avoid placing it inside the wp-content or wp-admin directories. It needs to be at the root level.
Common pitfalls to watch for:
File permissions: If the file is uploaded but returns a 403 error when you try to access it in a browser, the file permissions are likely set too restrictively. Set the file to be publicly readable (permission 644 in Unix-style systems).
CMS blocking .txt files: Some CMS configurations or security plugins block direct access to .txt files in the root directory. If you're hitting a 404 despite the file being there, check your .htaccess file or security plugin settings for rules that might be blocking the file type.
Wrong directory: On some hosting setups, the web root isn't public_html. It might be www, htdocs, or another folder. Confirm the correct web root with your hosting provider if you're unsure.
The success indicator here is simple: the URL returns a 200 HTTP status code and displays only your key. Use a tool like httpstatus.io to confirm the status code if you want to be thorough. Once that check passes, you're ready to start submitting URLs.
Step 3: Submit URLs via the IndexNow API
With your key generated and your verification file live, you can now start notifying search engines about your content. The IndexNow API has a single shared endpoint that routes your submissions to all participating search engines at once: https://api.indexnow.org/indexnow.
There are two ways to submit URLs, and choosing the right one depends on your use case.
GET Request (single URL submission): This is the simplest method. You construct a URL with query parameters and send a GET request. The format looks like this:
https://api.indexnow.org/indexnow?url=https://yourdomain.com/your-page&key=your-api-key
Use this method for real-time, single-page updates. When you publish one new blog post or update a single product page, a GET request is the fastest and simplest approach. You can even test it by pasting the URL directly into a browser.
POST Request (batch URL submission): For submitting multiple URLs at once, use a POST request with a JSON body. The structure looks like this:
The JSON body includes four fields: host (your domain without the protocol), key (your API key), keyLocation (optional, the full URL to your key file if it's not at the default root location), and urlList (an array of full URLs you want to submit). A single POST request supports up to 10,000 URLs, making it ideal for site migrations, large content pushes, or full sitemap submissions.
Use the POST method when you're submitting more than a handful of URLs at once. Sending 200 individual GET requests when a single POST would do the same job is inefficient and risks hitting rate limits.
Before you automate anything, test your first submission manually. Tools like Postman or curl make this straightforward. Send a GET request with a single URL you want indexed and check the HTTP response code you get back.
Here's what the response codes mean:
200 OK: URLs received successfully. The search engines have accepted your submission.
202 Accepted: Request received, but some URLs may be invalid. Check your URL list for formatting issues.
400 Bad Request: Something is wrong with your JSON structure. Validate your POST body with a JSON linter before resubmitting.
403 Forbidden: Key verification failed. This usually means the key file from Step 2 is unreachable or the contents don't match. Go back and re-verify that URL.
422 Unprocessable Entity: The URLs you submitted don't match the host specified in your request. Check that your domain is consistent across all fields.
429 Too Many Requests: You've hit the rate limit. Slow down your submission frequency and avoid resubmitting the same URLs repeatedly in a short window.
One important guideline: only submit URLs you genuinely want indexed. Avoid submitting paginated URLs, faceted navigation pages, filtered e-commerce URLs, pages with noindex meta tags, or any URL blocked by robots.txt. Submitting low-quality or blocked URLs wastes your submission quota and can signal poor site hygiene to search engines.
Step 4: Automate Submissions on Publish and Update Events
Manual submissions work for testing, but they defeat the core purpose of IndexNow. The protocol's real value is zero-latency notification: the moment content changes, search engines know about it. Achieving that requires automation.
How you automate depends on your platform.
WordPress: This is the easiest path. Both Rank Math SEO and Yoast SEO Premium support IndexNow natively. Install either plugin, navigate to its settings, enter your API key, and enable automatic submission on publish and update events. From that point forward, every time you publish a new post or update an existing one, the plugin handles the IndexNow submission in the background. Microsoft also maintains an official IndexNow plugin for WordPress if you prefer a standalone solution.
Custom CMS or headless setups: Hook into your CMS's publish webhook or post-save event. The logic is straightforward: when a content item is published or updated, extract the canonical URL for that item, send a POST request to the IndexNow API endpoint with the URL and your key, and log the response code for monitoring purposes. Most modern CMS platforms and headless systems support webhook events natively, so this typically requires minimal custom code.
Static site generators (Next.js, Gatsby, Hugo): Integrate IndexNow submission into your build and deploy pipeline. After a successful deployment, run a post-deploy script that sends the updated URLs to the IndexNow API. If your build process generates a new sitemap, you can parse that sitemap and submit all URLs in a single POST request. This approach ensures every deployment triggers an indexing notification automatically.
Sitemap-based batch automation: For large sites or after a full site rebuild, configure your system to submit all URLs from your sitemap to IndexNow as a batch. Parse your XML sitemap, extract all loc values, and send them in a POST request. This is particularly useful after site migrations, domain changes, or major content restructures where you want search engines to re-crawl everything promptly.
Sight AI's Website Indexing tools include IndexNow integration with automated sitemap updates, handling this entire workflow without requiring custom development. If you're looking to avoid building and maintaining this infrastructure yourself, an all-in-one platform approach removes the engineering overhead entirely.
The success indicator for this step: within minutes of publishing new content, you should be able to see the submitted URL appear in Bing Webmaster Tools under the URL Submission history. If it shows up there with a 200 response, your automation is working correctly.
Step 5: Verify Submissions and Monitor Indexing Performance
Setting up IndexNow is only valuable if you can confirm it's actually working. Verification has two layers: confirming that your submissions are being received, and confirming that submitted URLs are actually getting indexed.
Checking submission history in Bing Webmaster Tools: This is your primary monitoring dashboard for IndexNow. Navigate to Bing Webmaster Tools, select your site, and look for the IndexNow section under "Configure My Site." The URL Submission report shows your submission history, the status of each submission, and any errors returned. Check this regularly in the first few days after setup to confirm everything is flowing correctly.
Key metrics to watch in this report: your overall submission success rate, the ratio of URLs accepted versus rejected, and any recurring error codes. A high rate of 403 or 422 errors after initial setup usually points to a configuration issue rather than a transient problem, so investigate those promptly.
Checking if a URL was actually indexed: Submission acceptance doesn't guarantee immediate indexing. Search engines still evaluate submitted URLs for quality and relevance before adding them to the index. To check whether a specific URL has been indexed in Bing, use the site:yourdomain.com/specific-page search operator directly in Bing. You can also use the URL Inspection tool inside Bing Webmaster Tools for a more detailed view of how Bing sees a specific page.
Tracking Google indexing separately: IndexNow submissions are shared across the IndexNow network, but Google has not confirmed full adoption of the protocol as of the current date. Google's primary indexing mechanism remains its own crawl queue. To track Google indexing, use Google Search Console's URL Inspection tool and the Coverage report. These show whether Google has crawled and indexed your pages, independent of your IndexNow submissions.
Troubleshooting common errors:
403 errors: Your key file is unreachable. Go back to Step 2 and verify the file is publicly accessible at the correct URL with the correct contents and file permissions.
422 errors: The URLs you're submitting don't match the host in your request. Check that your domain is consistent, including whether you're using www or non-www, and that it matches the host field in your POST body exactly.
400 errors: Your JSON body is malformed. Run it through a JSON validator to identify the formatting issue before resubmitting.
Build a simple logging system: Record every IndexNow API call your system makes, along with the response code and timestamp. This audit trail is invaluable for troubleshooting and helps you spot patterns, like a particular content type consistently triggering 422 errors, that would be invisible without logs.
Ongoing optimization: IndexNow works best as part of a broader technical SEO strategy. Review your sitemap health and crawl budget alongside your IndexNow performance. If search engines are accepting your submissions but indexing is still slow, the bottleneck may be on the crawl processing side rather than the discovery side. Pair IndexNow data with your broader SEO dashboard to correlate submission timing with ranking velocity over time.
Putting It All Together: Your IndexNow Checklist
IndexNow integration for websites is one of those technical SEO moves that's genuinely straightforward to implement but delivers compounding value over time. Here's the complete five-step process as a quick reference:
1. Generate your API key using Bing Webmaster Tools or a hex generator, and save it securely.
2. Create a plain text key file named after your key, place it at your domain root, and verify it's publicly accessible at the correct URL.
3. Test manual URL submissions via GET or POST requests to api.indexnow.org/indexnow and confirm you're receiving 200 response codes.
4. Automate submissions by integrating IndexNow into your CMS publish events, deploy pipeline, or sitemap workflow so notifications happen without manual effort.
5. Monitor submission history in Bing Webmaster Tools, track indexing status with URL inspection tools, and maintain a log of all API calls for troubleshooting.
A few things worth keeping in mind as you move forward. IndexNow is a complement to good SEO fundamentals, not a replacement for them. A healthy XML sitemap, well-managed crawl budget, and quality content are still the foundation. IndexNow accelerates discovery; it doesn't compensate for weak content or technical issues that prevent proper indexing.
The real compounding value here comes from automation. Set it up once, and it runs continuously in the background. Every piece of content you publish gets a faster path to discovery without any additional manual effort on your part.
There's also a forward-looking dimension worth noting. As AI-powered search engines increasingly rely on fresh, indexed web content to generate responses, faster indexing directly supports your AI visibility goals. Content that gets indexed quickly is content that AI models can reference sooner.
If you want to go beyond indexing and understand exactly how AI models are talking about your brand across platforms like ChatGPT, Claude, and Perplexity, Sight AI's all-in-one platform combines IndexNow integration, automated sitemap management, and AI visibility tracking in a single workflow. Start tracking your AI visibility today and see exactly where your brand appears across top AI platforms, so you can stop guessing and start optimizing with real data.
