noindex tag #2776

New Issue

OVERLORD · 2026-02-05T05:09:46+03:00

OVERLORD commented

2026-02-05 05:09:46 +03:00

Originally created by @Statium on GitHub (May 4, 2022).

Describe the feature you'd like

Add an option in the settings to prohibit indexing even of a public site for search engines.

Describe the benefits this would bring to existing BookStack users

Prevent indexing of inappropriate content.

Can the goal of this request already be achieved via other means?

No

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?

1 to 5 years

Additional context

No response

Originally created by @Statium on GitHub (May 4, 2022). ### Describe the feature you'd like Add an option in the settings to prohibit indexing even of a public site for search engines. ### Describe the benefits this would bring to existing BookStack users Prevent indexing of inappropriate content. ### Can the goal of this request already be achieved via other means? No ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundemental request ### How long have you been using BookStack? 1 to 5 years ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 05:09:46 +03:00

OVERLORD closed this issue

2026-02-05 05:09:57 +03:00

OVERLORD commented

2026-02-05 05:10:01 +03:00

@ssddanbrown commented on GitHub (May 4, 2022):

Hi @Statium,
We already offer controls for this via the following option:
44013721f0/.env.example.complete (L321)
By default Robot access intent will be controlled by your app's public access status but this can be overridden using the option posted above.

We use the robots.txt approach for this functionality, I wouldn't really look to complicate our implementation further with other robot access request techniques without significant reason to do so. The only flaw I can currently see in our existing approach is that it might not take action if using BookStack on a sub-path, but the hoster could just update the robots.txt file on their root-level site instead.

@ssddanbrown commented on GitHub (May 4, 2022): Hi @Statium, We already offer controls for this via the following option: https://github.com/BookStackApp/BookStack/blob/44013721f0d9bd21c8ebe7cf2ae7d39067fe74bb/.env.example.complete#L321 By default Robot access intent will be controlled by your app's public access status but this can be overridden using the option posted above. We use the `robots.txt` approach for this functionality, I wouldn't really look to complicate our implementation further with other robot access request techniques without significant reason to do so. The only flaw I can currently see in our existing approach is that it might not take action if using BookStack on a sub-path, but the hoster could just update the robots.txt file on their root-level site instead.

OVERLORD commented

2026-02-05 05:10:07 +03:00

@ssddanbrown commented on GitHub (May 10, 2022):

Since there's been no further discussion I'm going to close this.

@ssddanbrown commented on GitHub (May 10, 2022): Since there's been no further discussion I'm going to close this.

OVERLORD referenced this issue

2026-02-05 10:23:42 +03:00

[PR #2776] [CLOSED] Fix for CJK works only with keywords that put inside quotation marks #6062

Sign in to join this conversation.