Every time you publish or update a page, search engines need to discover it before it can rank. Traditional crawling is passive: you wait for bots to find your content on their own schedule, which can take days or weeks depending on your site's authority and crawl budget. IndexNow changes that dynamic entirely.
IndexNow is an open protocol jointly developed by Microsoft (Bing) and Yandex, now supported by additional search engines including Seznam.cz and Naver. It lets you proactively notify participating engines the moment a URL changes, so they can prioritize crawling and indexing it immediately rather than waiting for their next scheduled crawl.
For marketers and founders investing in SEO and GEO-optimized content, this matters. Faster indexing means faster ranking signals, faster traffic, and faster feedback on what's working. If you're publishing content regularly and waiting days for it to surface in search results, you're leaving performance data on the table.
This tutorial walks you through the complete IndexNow implementation process, from generating your API key to verifying successful submissions. Whether you're running a WordPress site, a custom CMS, or a headless architecture, the core steps are the same. By the end, you'll have a working IndexNow setup that automatically pings search engines whenever you publish or update content, without manual intervention.
One important note before we dive in: as of 2026, Google has not officially joined the IndexNow consortium, though they have participated in testing. The primary beneficiaries of IndexNow submissions are Bing, Yandex, and other participating engines. For Google indexing, you'll want to complement IndexNow with the Google Indexing API or sitemap submissions via Search Console. Both are covered later in this guide.
Let's get your content discovered faster.
Step 1: Generate Your IndexNow API Key
Think of your IndexNow API key as a digital signature that proves you own the domain you're submitting URLs for. Without a valid key hosted on your domain, search engines will reject your submissions outright. This step is simple, but getting the format right matters.
Your key is a unique alphanumeric string, minimum 8 characters and up to 128 characters long. The format requirements are straightforward: only lowercase letters (a-z), uppercase letters (A-Z), digits (0-9), and hyphens are allowed. No spaces, no special characters, no underscores.
How to generate your key: The easiest method is visiting the official generator at indexnow.org, which produces a properly formatted random key for you. Alternatively, you can generate a UUID or random hex string using any method you prefer. A cryptographically random string is ideal since it reduces the (already low) risk of key collisions. Here are a few quick options depending on your environment:
Using the command line (Linux/Mac): Run openssl rand -hex 32 to generate a 64-character hex string. Trim it to your preferred length if needed.
Using Python: Run import secrets; print(secrets.token_hex(16)) for a 32-character hex string.
Using an online UUID generator: Any UUID v4 generator works. Remove the hyphens if you prefer a clean alphanumeric string, or keep them since hyphens are permitted.
A few practical notes on key management. Generate one key per domain, not per page or per subdomain. If your subdomains are separate properties with different content teams, they can have separate keys, but a single key covers your entire root domain. Save your key somewhere secure and accessible, since you'll reference it in every API call and in the key file you'll host publicly. A password manager or environment variable in your deployment configuration works well.
The key itself isn't a secret in the traditional sense since it will be publicly visible in your hosted key file. What it does is prove that whoever controls the domain also controls the key, establishing trust with the search engine. Understanding how the IndexNow protocol works at a deeper level can help you troubleshoot edge cases as you build out your implementation.
Success indicator: You have a valid random string that meets the format requirements, saved and ready to deploy. Write it down or store it now before moving to Step 2.
Step 2: Host the Key File on Your Domain
Generating a key is only half the equation. Search engines verify domain ownership by fetching a text file from your domain that contains your key. This is the mechanism that prevents anyone from submitting URLs for a domain they don't control.
The setup is simple: create a plain text file named exactly as your API key with a .txt extension. If your key is a1b2c3d4e5f6g7h8, your file should be named a1b2c3d4e5f6g7h8.txt. The file must be publicly accessible at:
https://yourdomain.com/{your-key}.txt
The file contents should contain only your API key string on a single line. Nothing else. No whitespace before or after, no additional text, no BOM characters. Just the key.
Alternative location: If placing a file at your domain root isn't feasible due to server configuration or CMS restrictions, you can also host it at https://yourdomain.com/.well-known/indexnow-{your-key}.txt. Both locations are accepted by the protocol.
Here's how to handle this across common platforms:
WordPress: Upload the key file via FTP/SFTP directly to your public_html folder (or wherever your WordPress root lives). Alternatively, if you're using a plugin like Rank Math or Yoast SEO with IndexNow support, the plugin handles key file creation and hosting automatically when you enter your key in the settings.
Static sites (HTML, Jekyll, Hugo): Place the file in your /public or /dist folder, whichever directory gets served as your web root. It will be included in your next build and deployment.
Next.js: Place the file in your /public directory. Next.js serves everything in /public from the domain root, so the file will be accessible at the correct URL automatically.
Gatsby: Same approach as Next.js. Place the file in the /static folder, which maps to the root of your deployed site.
Custom server (Node.js, Python, etc.): Serve the file as a static asset from your root path, or add a specific route that returns the key string with a text/plain content type and a 200 status code.
Two common pitfalls to watch for. First, some server configurations block or redirect .txt file requests, particularly if you have aggressive redirect rules or a WAF in place. Second, if your CMS rewrites all URLs through a router, a static file at the root may not be served correctly without explicit configuration. If you run into persistent hosting issues, reviewing common website indexing issues can surface additional troubleshooting steps specific to your platform.
Always test by visiting the URL directly in a browser before proceeding. You should see only your key string displayed as plain text, with no HTML wrapper, no error pages, and no redirects.
Success indicator: Navigating to https://yourdomain.com/{your-key}.txt in a browser returns only your key string with a 200 HTTP status code. Use your browser's developer tools or a tool like curl to confirm the status code if needed.
Step 3: Make Your First IndexNow API Call
With your key generated and hosted, you're ready to make your first submission. This is where the protocol earns its simplicity: notifying search engines is a single HTTP request. You don't need a complex integration to get started.
One important design feature of IndexNow: you only need to ping one participating endpoint. The protocol automatically distributes your submission to all participating search engines. So a single call to api.indexnow.org reaches Bing, Yandex, and other consortium members simultaneously.
GET Request: Single URL Submission
For a single URL, a GET request is the fastest way to test. The format is:
https://api.indexnow.org/indexnow?url=https://yourdomain.com/your-page&key={your-key}
You can paste this directly into a browser, run it with curl, or call it from any HTTP client. If your key file is correctly hosted and the URL belongs to your domain, you'll get a 200 or 202 response back.
POST Request: Batch URL Submission
For submitting multiple URLs at once, use a POST request to the same endpoint with a JSON body. This is the format you'll use in automation. The request body looks like this:
{"host": "yourdomain.com", "key": "{your-key}", "keyLocation": "https://yourdomain.com/{your-key}.txt", "urlList": ["https://yourdomain.com/page-1", "https://yourdomain.com/page-2"]}
The keyLocation field is optional if your key file is at the standard root location. Include it if you've used the .well-known path or a non-standard location. The urlList array accepts up to 10,000 URLs per request, making this ideal for large sites doing an initial bulk submission or re-indexing after a major site migration.
Understanding Response Codes
Knowing what the response codes mean saves significant debugging time:
200 OK: URLs were received and accepted successfully.
202 Accepted: URLs were received and queued for processing. This is also a success state.
400 Bad Request: Something is malformed in your request. Check your URL format, ensure it's properly encoded, and verify the JSON structure if using POST.
403 Forbidden: Key mismatch. The search engine fetched your key file and the key doesn't match what you submitted. Double-check that your hosted key file contains exactly the same string as your API call.
422 Unprocessable Entity: The URL you submitted doesn't belong to the domain associated with your key. All submitted URLs must match the domain where your key file is hosted.
429 Too Many Requests: You've hit a rate limit. Slow down your submission frequency and avoid submitting the same URL repeatedly within a short window.
Start with a GET request for a single URL using curl or your browser before building any automation. This validates your setup end-to-end before you invest time in integration work. A 200 or 202 here means everything is wired up correctly. If you're evaluating dedicated IndexNow submission tools to handle this process, testing manually first gives you a baseline to compare against.
Success indicator: You receive a 200 or 202 HTTP response from the IndexNow endpoint for a URL on your domain. Your first submission is complete.
Step 4: Automate Submissions on Publish and Update
Manual pinging defeats the purpose of IndexNow. The real value is instant, automatic notification every time content changes, without anyone having to remember to trigger it. This step is where implementation varies by platform, but the underlying logic is the same everywhere: trigger an IndexNow API call whenever a URL is created or updated.
WordPress
This is the easiest path. Both Rank Math SEO and Yoast SEO have built-in IndexNow support. Enter your API key in the plugin settings, and submissions happen automatically whenever you publish or update a post, page, or custom post type. No custom code required. If you're already using either plugin for SEO, enabling IndexNow is typically a single toggle and a key entry field.
Custom CMS or Headless Architecture
Add an IndexNow API call to your content publishing webhook. Most headless CMS platforms (Contentful, Sanity, Strapi, and others) support outgoing webhooks that fire when content is published or updated. Configure a webhook that triggers a serverless function or a lightweight API endpoint, which then makes the IndexNow POST request with the affected URL.
The function logic is minimal: receive the webhook payload, extract the URL of the changed content, make a POST request to api.indexnow.org/indexnow with your key and the URL, and log the response. A serverless function on Vercel, Netlify Functions, or AWS Lambda handles this cleanly without maintaining dedicated infrastructure. For a deeper look at building this kind of connection, the IndexNow API integration guide covers common patterns across different stack configurations.
Static Site Generators (Next.js, Gatsby, Hugo)
Add an IndexNow submission step to your CI/CD pipeline. After a successful build and deploy, run a script that compares the current sitemap against the previous version, identifies new or changed URLs, and submits them via a POST request. This approach is efficient for large sites because it only submits what actually changed rather than your entire URL inventory on every deploy.
For Next.js specifically, you can also use a post-build script in your package.json that fires after next build completes, reading your generated sitemap and submitting new entries.
Using Sight AI's Indexing Tools
If you'd rather not build and maintain this automation yourself, Sight AI's Website Indexing tools include IndexNow integration with automated sitemap updates built in. The platform handles the submission logic for you, firing IndexNow pings when new content is published and keeping your sitemap synchronized, without requiring custom code or pipeline configuration. For marketers and founders focused on content output rather than infrastructure, this removes the engineering overhead entirely.
Rate limiting note: Avoid submitting the same URL more than once per 24-hour period. Search engines may throttle or ignore repeat submissions for the same URL within a short window. Your automation should be smart enough to deduplicate and only submit URLs that have genuinely changed.
Success indicator: Publishing a new post or page triggers an automatic IndexNow ping without any manual action. Confirm this by publishing a test page and checking your server logs or Bing Webmaster Tools for the corresponding submission entry.
Step 5: Verify Indexing and Monitor Performance
Submitting URLs is only useful if you can confirm they're being processed and indexed. This step closes the loop on your implementation by showing you how to verify that IndexNow is working and how to track its impact over time.
Bing Webmaster Tools
Your primary verification tool is Bing Webmaster Tools. If you haven't already, add and verify your site at bing.com/webmasters. Once verified, navigate to the URL Inspection tool and paste any recently submitted URL. This shows you the URL's current crawl status, last crawl date, and whether it's indexed. You can also submit your website to Bing directly through Webmaster Tools to ensure your domain is fully registered before relying on IndexNow submissions alone.
For a broader view of your IndexNow activity, look under the URL Submission section in Bing Webmaster Tools. This log shows accepted URLs, submission timestamps, and any errors returned for recent submissions. It's the most direct way to confirm that your automated pings are reaching Bing and being processed correctly.
Server Access Logs
After a successful IndexNow submission, Bingbot typically visits the submitted URL within hours rather than days. Check your server access logs for requests from Bingbot's user agent following your submissions. Seeing Bingbot crawl a page shortly after you submitted it is a strong signal that your IndexNow setup is functioning correctly.
Tracking Indexing Speed Over Time
One of the best ways to validate IndexNow's impact is to track how quickly new pages appear in Bing search results before and after implementation. Keep a simple log of publication timestamps and first-indexed timestamps for new pages. The pattern should show a meaningful reduction in the gap between publish and index after IndexNow is active.
Handling Error Patterns
If your submission log shows repeated errors, address them promptly. Repeated 403 errors almost always mean your key file is inaccessible, either blocked by your server, returning a non-200 status, or containing extra whitespace. Revisit Step 2 and confirm the file is serving correctly. Repeated 422 errors indicate a URL and domain mismatch, meaning you're submitting URLs that don't match the domain where your key file is hosted. Check that your automation is pulling the correct domain from your content URLs.
Complementing IndexNow with Google Tools
Since Google isn't a full IndexNow participant, maintain parallel indexing workflows for Google coverage. Submit your XML sitemap via Google Search Console and keep it updated. For high-priority pages, the Google Indexing API can request faster crawling, though it was originally designed for job postings and livestream pages. For most sites, a current sitemap submitted to Search Console combined with strong internal linking is the most reliable Google indexing strategy.
Connecting to Broader SEO Monitoring
Indexing speed is only meaningful in the context of what happens next. Connect your IndexNow activity to your broader SEO performance tracking. Correlate submission timestamps with ranking changes and organic traffic growth to understand which content types benefit most from faster indexing. Tools that combine indexing automation with content performance tracking, including AI visibility monitoring across platforms like ChatGPT and Perplexity, give you a unified view of how your content is performing across both traditional and AI search.
Success indicator: New URLs appear in Bing's index within 24-48 hours of publication, and your Webmaster Tools submission log shows consistent 200 or 202 responses with no recurring errors.
Putting It All Together: Your IndexNow Checklist
You now have everything you need to implement IndexNow from scratch. Here's the complete process as a quick-reference checklist:
1. Generate your API key using indexnow.org or a cryptographically random string generator. Save it securely.
2. Host your key file at https://yourdomain.com/{your-key}.txt containing only the key string. Verify it returns a 200 status in your browser.
3. Make your first API call using a GET request to test the connection. Confirm you receive a 200 or 202 response before building automation.
4. Automate submissions via your CMS plugin, publishing webhook, or CI/CD pipeline so every new or updated URL is pinged automatically.
5. Verify and monitor through Bing Webmaster Tools, server logs, and indexing speed tracking to confirm the setup is working and delivering results.
IndexNow is a powerful layer in your indexing strategy, but it works best as part of a complete approach. Pair it with XML sitemap optimization, regular sitemap submissions to Google Search Console, and crawl budget management for a comprehensive setup. For Google specifically, maintain your sitemap and consider the Indexing API for high-priority content.
If you want to skip the custom development work, Sight AI combines IndexNow automation with content generation and AI visibility tracking in a single platform. You get automated indexing, GEO-optimized content publishing, and visibility into how your brand is being mentioned across AI models like ChatGPT, Claude, and Perplexity, all without stitching together separate tools.
Faster indexing gets your content into search results sooner. But knowing how that content performs across both traditional search and AI platforms is what turns indexing speed into measurable growth. Start tracking your AI visibility today and see exactly where your brand appears across top AI platforms, so you can publish with confidence and optimize what's actually working.
