How to Use IndexNow to Get Your Content Indexed Faster

Publishing a new article and waiting weeks for it to appear in search results is a familiar frustration. IndexNow eliminates that wait for a significant portion of the search ecosystem — and increasingly, for AI-powered search too.

What is IndexNow?

IndexNow is an open protocol that lets website owners push new and updated URLs directly to participating search engines the moment content changes. Instead of waiting for a crawler to discover your content on its next scheduled visit, you send a notification and the search engine fetches the URL immediately.

Participating search engines include: - Bing (and Bing-powered Copilot) - Yandex - Seznam - Naver

Google has not formally adopted IndexNow, but does operate its own equivalent (the Indexing API — primarily for job postings and live streams, though it reportedly has broader effects for some sites).

Why IndexNow matters beyond speed

The obvious benefit is faster indexing. For news sites and high-velocity content teams, getting indexed hours rather than weeks after publishing is a competitive advantage.

But for SEO and GEO there's a second, less obvious benefit: freshness signals.

Search and AI systems weight recent, frequently-updated content higher for certain query types. By submitting via IndexNow every time you publish or update content, you're sending an explicit freshness signal alongside the crawl request — not just hoping the crawler notices the updated timestamp.

For Bing Copilot specifically, IndexNow submissions directly feed the freshness layer that determines whether AI-generated answers pull from your latest content or a stale cached version.

Setting up IndexNow: step by step

Step 1: Generate your API key

IndexNow requires a simple API key — a random string of at least 8 characters (alphanumeric). Generate one with any random string generator.

Step 2: Publish the key file

Place a text file at the root of your domain named `{your-key}.txt` (e.g., `yourapikey123.txt`). The file should contain only your API key as its sole content.

# Example: /public/a1b2c3d4e5f6g7h8.txt
a1b2c3d4e5f6g7h8

Step 3: Submit URLs via the IndexNow API

Send a POST request to the IndexNow endpoint with your URLs:

POST https://api.indexnow.org/indexnow
Content-Type: application/json

{ "host": "www.yoursite.com", "key": "a1b2c3d4e5f6g7h8", "keyLocation": "https://www.yoursite.com/a1b2c3d4e5f6g7h8.txt", "urlList": [ "https://www.yoursite.com/new-article", "https://www.yoursite.com/updated-article" ] } ```

A 200 response confirms successful submission. A 422 means the URL list is malformed. A 429 means you've hit the rate limit.

Step 4: Integrate into your publishing workflow

The real value of IndexNow comes from automating submissions at publish time — not manually submitting URLs after the fact.

For Next.js / headless CMS setups, fire the IndexNow API call inside your publish route handler, immediately after the CMS webhook confirms the article is live:

// Inside your publish API route
async function notifyIndexNow(urls: string[]) {
  await fetch('https://api.indexnow.org/indexnow', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({
      host: 'www.yoursite.com',
      key: process.env.INDEXNOW_KEY,
      keyLocation: `https://www.yoursite.com/${process.env.INDEXNOW_KEY}.txt`,
      urlList: urls,
    }),
  })
}

Rate limits and best practices

Batch submissions — The API accepts up to 10,000 URLs per submission. Batch your submissions rather than sending one URL at a time.

Submit on update, not on schedule — Don't submit all your URLs on a cron job. Submit when content actually changes. Mass submissions of unchanged URLs are ignored by search engines and can trigger rate limiting.

Include updated content — IndexNow is valuable for updates, not just new articles. If you refresh an old article with new data, submit it via IndexNow to signal the freshness update.

Don't submit staging/preview URLs — Only submit production URLs. Submitting staging URLs can cause indexing issues or, at minimum, waste your submission quota.

IndexNow vs. Google Search Console URL inspection

For Google, the manual URL inspection tool in Search Console can trigger a re-crawl of individual URLs. This is Google's equivalent for one-off submissions.

For automated publishing at scale, IndexNow (for Bing/Copilot) and a structured sitemap with frequent `lastmod` updates (for Google) are the right combination.

*Indexa submits every published article to IndexNow automatically, alongside sitemap pings and Google Search Console notifications — ensuring new content is indexed on all major search engines within hours of publishing.*