Postream

Loading the index…

Docs: IndexNow

IndexNow

Postream notifies Bing, Yandex and other search engines whenever a post goes live.

When a post version goes live (published now or by the schedule) or is edited after being published, Postream notifies the search engines that use IndexNow (Bing, Yandex, Seznam, Naver…) with its URL on the blog.

  • The notification goes out in the background, with retries, and never delays or blocks publishing.
  • Changing the slug of a published post notifies both the new URL and the old one (which now redirects with 301).

Set up

In the panel, on the site page, in the IndexNow section:

  • Key: generate it in the panel or paste your own (8 to 128 letters, digits or dashes). Without a key, nothing is sent. The key is not a secret: it is public in the file below.
  • Post address in each language: full URL with {slug} (and, if you want, {locale}), on the site's domain or a subdomain. For example, https://blog.example.com/{slug} for pt-BR and https://blog.example.com/en/{slug} for en-US. A language without an address is not notified.

Serve the key on the blog

The search engine only accepts the notification if the URL's host serves, at the root, a text file named after the key containing only the key:

GET https://blog.example.com/0b6c5d6e6f1e4b339a1b3f1d2c3b4a59.txt
200 text/plain
 
0b6c5d6e6f1e4b339a1b3f1d2c3b4a59

In Next.js, just create public/<key>.txt with the key inside. The panel shows the exact address after you save.

  • If the languages are on different hosts (blog.example.com and en.example.com), each host serves the same file.
  • When you change the key, publish the new file before publishing posts: notifications refused because of an unverified key (403) are retried for about 30 hours and then discarded.