Two paths announce our pages to Bing, and one Redis hash keeps them from announcing twice
Nakodo has 76 public pages. You can count them yourself in the sitemap : the home page, the pricing and method pages, and then the content families, like the guides hub and the per-niche pages under /youtubers . Google finds changes on those pages by reading the sitemap when it feels like it. Bing, Yandex, Seznam and Naver will take a push instead: one POST to api.indexnow.org/indexnow with a…
Nakodo's website has 76 public pages, ranging from the homepage and pricing information to content families like guides and niche-specific pages. Unlike Google, Bing, Yandex, Seznam, and Naver rely on a push protocol to discover new content. This protocol involves a single POST request with a host, key, and list of URLs to api.indexnow.org/indexnow. The key is made public by exporting it in a file named key.txt, which is checked in and readable by the engines. A test verifies the key's validity and accessibility.
The framework uses the sitemap to determine which pages have changed, been submitted, or removed. The sitemap entries include a date representing the last content change, rather than the build date. The pendingUrls function identifies changed and removed pages based on the submitted hash and live sitemap. The livePages function fetches the live sitemap using the absolute URL of the sitemap.xml file.
Announcing a newly deployed page sends search engines to a page that redirects to the login form, while reading the live sitemap prevents this issue.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
