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

README.md: Add step that explains how to use the sitemap.xml properly #92

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

refeed
Copy link
Member

@refeed refeed commented Sep 10, 2022

Followup of 980675c

@rht
Copy link
Contributor

rht commented Sep 10, 2022

Is there a way to automate adding to robots.txt, so that we don't even need to document this?

@refeed
Copy link
Member Author

refeed commented Sep 10, 2022

Umm, I haven't heard such thing existed yet

@rht
Copy link
Contributor

rht commented Sep 10, 2022

This can be quickly tested by committing robots.txt with the sitemap info to a zulip-archive repo root.

@rht
Copy link
Contributor

rht commented Sep 10, 2022

@refeed
Copy link
Member Author

refeed commented Sep 10, 2022

Yes that is possible if the zulip-archive lives right in the root of the URL, e.g. https://example.github.io .

But for github pages especially those that don't use custom domain, most of the case zulip-archive doesn't live in the root of the domain e.g. https://example.github.io/zulip-archive/
In this case, placing a robots.txt here will make it appear in https://example.github.io/zulip-archive/robots.txt which won't be accessed by search engine bots

@rht
Copy link
Contributor

rht commented Sep 10, 2022

The ones with custom domain should work, because that Bootstrap GH pages domain is getbootstrap.com, and they have robots.txt committed in the repo root.

The case where it doesn't work is when the subdomain of the GH pages URL is not the repo name https://example.github.io/zulip-archive/. In this case, then OK, this should be documented. But the rest can be automated.

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 this pull request may close these issues.

None yet

2 participants