I disagree with the decision to remove robots.txt in #668. I think it may at least remove 404 errors from logs and sitemap.xml can only help with SEO or won't be harmful.
However I am not sure if privacytools.io has more than one page and I was unable to get Jekyll working locally on this PC.
I disagree with the decision to remove robots.txt in #668. I think it may at least remove 404 errors from logs and sitemap.xml can only help with SEO or won't be harmful.
However I am not sure if privacytools.io has more than one page and I was unable to get Jekyll working locally on this PC.
Though as I expected, the sitemap is pretty useless since we have only two pages:
Though as I expected, the sitemap is pretty useless since we have only two pages:
> What's the point of having robots.txt when it simply says "all pages allowed"?
Not having it can spam error.log of the HTTP server, but as you use GitHub pages through CloudFlare, I don't know if anyone would ever see them.
> Though as I expected, the sitemap is pretty useless since we have only two pages:
Would there be any harm in case there would be more pages in the future? I don't know about your plans though.
> Can you verify that the jekyll-sitemap plugin is supported by Github Pages?
Yes, see https://pages.github.com/versions/
I think it may at least remove 404 errors from logs and sitemap.xml can only help with SEO or won't be harmful.
I agree with this. Having it in place doesn't hurt and it can only benefit SEO.
> I think it may at least remove 404 errors from logs and sitemap.xml can only help with SEO or won't be harmful.
I agree with this. Having it in place doesn't hurt and it can only benefit SEO.
jonah
approved these changes 2018-12-19 12:31:01 +00:00
Would there be any harm in case there would be more pages in the future? I don't know about your plans though.
I guess this can be useful when we have links like /it/index.html, /de/index.html etc.
> Would there be any harm in case there would be more pages in the future? I don't know about your plans though.
I guess this can be useful when we have links like `/it/index.html`, `/de/index.html` etc.
This repo is archived. You cannot comment on pull requests.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
jonah
I disagree with the decision to remove robots.txt in #668. I think it may at least remove 404 errors from logs and sitemap.xml can only help with SEO or won't be harmful.
However I am not sure if privacytools.io has more than one page and I was unable to get Jekyll working locally on this PC.
What's the point of having robots.txt when it simply says "all pages allowed"?
I see the point with a sitemap, though.
Though as I expected, the sitemap is pretty useless since we have only two pages:
Can you verify that the
jekyll-sitemapplugin is supported by Github Pages?Good point. Though we don't really need a sitemap.
Regarding robots,
Not having it can spam error.log of the HTTP server, but as you use GitHub pages through CloudFlare, I don't know if anyone would ever see them.
Would there be any harm in case there would be more pages in the future? I don't know about your plans though.
Yes, see https://pages.github.com/versions/
I agree with this. Having it in place doesn't hurt and it can only benefit SEO.
I guess this can be useful when we have links like
/it/index.html,/de/index.htmletc.