On the one hand, we would like our content that we publish here on the Hive Blockchain to be found in the search engines. But there is also the flip side of this - namely content that we don't want to have in the search engines. During my work as a web developer, I often come to the point where it is necessary or even common to exclude pages from indexing in the search engine. These include, for example, the legal notice or the privacy policy. These contents are important for the legal aspects of a website but do not offer any valuable content for the search engine and the ranking of the actual page. It is therefore common practice to exclude these pages from indexing when the site is launched. ![image.png](https://files.peakd.com/file/peakd-hive/louis88/Eos1qnqU1TQL72rEKXAydQPqdm82YeNcKpvWpWqBcT9AjDivZuSGJxxiQcdkbEVEhym.png) _{Ideogram V2 Turbo • NONE • 16:9 • Feb 15, 2025 8:48 PM Prompt: "A bot sitting in front of the computer and missing his spam articles listed on the search engine - showing access denied in a warm cozy nightsky environment"} If it's up to me, we should be able to use these functions (and I'm speaking here for all frontends) to exclude content written to the blockchain from indexing based on various criteria. And one thing up front - this has nothing to do with censorship. What I want is that content that is low-quality, spam, scam or simply dangerous for other visitors is not included in the global search engines. Fortunately, most if not all search engines adhere to a standard - **noindex** and **nofollow**. And the whole thing should then look like this in the HTML source code for a blog post/comment etc. that should not be indexed: ``` ``` - noindex → Prevents Google & other search engines from indexing the page. - nofollow → Prevents links on the page from being crawled. ### What content should not be indexed by search engines? A few examples. Again and again I see spam, a lot of spam here on the blockchain... Be it spam content - nonsense content, e.g. for casinos, which has been appearing more frequently recently:

![image.png](https://files.peakd.com/file/peakd-hive/louis88/23tGcJ2PxvgogsWeMW5bEdmEVYyToLZ9fyr9B4UTkVwiPMBQZLHxNc18WTHNteSuHDmh4.png) ![image.png](https://files.peakd.com/file/peakd-hive/louis88/23tGcD8RMBHiH2KfGDqXVM3idZctBZPpyDk7ByDfApoKA8jD9WR5Vjexf2W1mD6ZV6raC.png)

![image.png](https://files.peakd.com/file/peakd-hive/louis88/23t7DYjzFVpZJtrMCXwB6FYs3qZQ4i5kQ7sxvpZENtXWtSUW1nD6rsdDZZjbLg6oZsL6T.png) ![image.png](https://files.peakd.com/file/peakd-hive/louis88/23t7BZDcPySnLiH5bx1bQH9jKFB8s5QrQLhJhcjupC2TcvmjS819CR9hcTnWGCX5jA1au.png)

--- And we especially don't want to see content on our blockchain that is obviously a phishing attack. If someone clicks on a link that came to our blockchain via the search engine, there will be a lot of shouting afterwards. So it should be possible to nip such content in the bud. ![image.png](https://files.peakd.com/file/peakd-hive/louis88/23wqko7C66m3FSu7fiCGqQ1nhQLaebfCt5kg1Y8uvCrnQv1zgy9NmZn2aMC7fqry7c2Ja.png) As there are technical options for blocking content before it is indexed by Google, I am now calling on the larger frontends to comment on this topic and discuss the technical details of whether this feature should be included in the frontends and whether the frontends are prepared to implement it. @peakd / @asgarth @jarvie @ecency / @good-karma hive.blog / @blocktrades / @howo / @quochuy @leofinance @inleo @khaleelkazi What comes directly to my mind is that all articles and comments that have a reputation of less than X, which are known to have already ended up on the blacklists - or can effectively be quickly put on a no-index list manually if downvotes / blacklists are not fast enough - are put on the no-index list. Feel free to join the discussion - all other users are also welcome to join the discussion here. Your opinion? Let us know in the comments. Thank you!