Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Blacklists #11

Open
imp1sh opened this issue Feb 2, 2024 · 6 comments
Open

Feature Request: Blacklists #11

imp1sh opened this issue Feb 2, 2024 · 6 comments

Comments

@imp1sh
Copy link

imp1sh commented Feb 2, 2024

In wikijs you can set fine grained privileges for sites and paths.
When there are pages that cannot be seen by the public but only by authorized personel, they still appear in the sitemap.xml.
Please offer a environment variable that carries a list of paths that won't appear in the sitemap.

@Philipinho
Copy link
Member

I will create time to work on this.
PRs are welcomed too.

@Philipinho
Copy link
Member

What do you think of tag-based exclusion? I suggest implementing an environment variable that specifies tags for exclusion.

For instance, if you want to exclude pages marked as private or secret, you would set EXCLUDED_TAGS=private, secret in the environment variable.
Then, simply tag any new pages you don't want indexed with private or secret to automatically exclude them from the sitemap.

This method seems more clearer and easier to manage compared to editing paths, as it eliminates the need to update the environment variable each time you create new pages.

@imp1sh
Copy link
Author

imp1sh commented Mar 16, 2024

Usually it's not single pages that are set to private but paths. I'd much rather see an environment variable (list) where the user can set paths that should not be included in the sitemap.xml.

@Philipinho
Copy link
Member

If we have EXCLUDED_PATHS=/path/to/marketing, should it exclude all pages down the path?
For example /path/to/marketing/sales/schedule is excluded too because it is under marketing.

@imp1sh
Copy link
Author

imp1sh commented Mar 18, 2024

If you'd ask me I'd say yes, block everything below a given path, except when there are whitelists that allow it (override). Like it is handled in robots.txt.

@Philipinho
Copy link
Member

I will work on the EXCLUDED_PATHS option soon. Thank you for your input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants