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

Search: Do not show "Private Events" in search results and do not list publicly on search engines #118

Open
mariobehling opened this issue Dec 22, 2020 · 4 comments · Fixed by fossasia/open-event-frontend#6127

Comments

@mariobehling
Copy link
Member

Testing the search shows that events that are defined as "Private Events" in wizard step 2 show up in search results of the site here https://eventyay.com/explore and on public search engines.

Screenshot from 2020-12-22 23-59-36

But: Events that are set to "Private Event" should not be showing up on search results of the website and they should not be listed on search engines, e.g. controlled by robots.txt or other means. Please change the implementation accordingly.

@geekcheeky
Copy link

can i work on this issue

@iamareebjamal
Copy link
Member

Search Engine point remaining

@maze-runnar
Copy link

maze-runnar commented Jun 1, 2021

@mariobehling

You should not use a robots.txt file as a means to hide your web pages from Google Search results. This is because, if other pages point to your page with descriptive text, your page could still be indexed without visiting the page. If you want to block your page from search results, use another method such as password protection or a noindex directive.

If your web page is blocked with a robots.txt file, it can still appear in search results, but the search result will not have a description and look something like this.

https://developers.google.com/search/docs/advanced/robots/intro

@mariobehling mariobehling transferred this issue from fossasia/open-event-frontend Jun 24, 2021
@ayushnau
Copy link

i wonder why I am not seeing anything but Create Next App page. Please clarify

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

Successfully merging a pull request may close this issue.

5 participants