IndexPine docs
Docs
Integrations
Indexnow

IndexNow

Instantly notify Bing, Yandex, and other participating search engines the moment an article publishes, instead of waiting for their crawler to find it.

IndexNow is a shared protocol — backed by Microsoft Bing, Yandex, Seznam.cz, Naver, and others — that lets a site push a "this URL just changed" signal directly to search engines in real time, instead of waiting for their crawler to revisit on its own schedule. Every time IndexPine successfully publishes an article to your CMS, it pings IndexNow with that article's live URL.

Google does not use IndexNow
IndexNow is a real, useful signal for Bing and Yandex (and anything built on Bing's index), but Google does not currently consume IndexNow pings — Google discovery still runs through normal crawling, your sitemap, and Search Console. Think of IndexNow as a fast lane on top of that, not a replacement for it.

Why it needs a one-time setup

The IndexNow protocol requires a verification key file to be hosted on the exact same domain as the URLs being submitted — that's how a search engine confirms you actually control the site you're pinging on behalf of. Since IndexPine publishes onto your CMS rather than our own infrastructure, we don't have filesystem access to your domain, so this key file has to be hosted by you. It's a one-time step, similar in spirit to connecting Google Search Console or a CMS.

How to connect

  1. In your IndexPine dashboard, go to Settings > IndexNow.
  2. Click "Generate & Verify". IndexPine mints a unique key for your site and shows you the exact file path and content to host.
  3. Create a plain-text file at https://{your-domain}/{key}.txt on your own site, containing nothing but that key.
  4. Click "Verify" (or "Re-verify") — IndexPine fetches that URL back and checks the contents match exactly.
  5. Once verified, every future successful publish on this site automatically pings IndexNow with the new article's URL.
Unverified sites are silently skipped
If the key file isn't hosted yet (or verification hasn't been run), IndexPine simply skips the ping for that publish — it's a no-op, not an error, and it never blocks or fails a publish. You won't see anything indexed faster until verification succeeds.

What actually gets sent

After a successful publish, IndexPine POSTs a single request to the IndexNow API containing your domain, your verification key, the key file location, and the one URL that was just published. The protocol supports batching up to 10,000 URLs per request, but IndexPine sends one URL per publish event, right when it happens.

Troubleshooting

  • Verification keeps failing — confirm the file is reachable at exactly https://{your-domain}/{key}.txt over HTTPS, with no redirects, and that its content is only the key (no extra whitespace, HTML wrapper, or CMS template around it).
  • Verified but nothing seems faster — IndexNow speeds up discovery on Bing/Yandex specifically; it has no effect on Google ranking or indexing timelines.
  • Moved domains or regenerated the key — you'll need to host the new key file and re-verify before pings resume.
PreviousRSS feedNext Zapier, Make & n8n