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

Google web crawler is finding candidate packages #504

Open
erantapaa opened this issue Jun 8, 2016 · 3 comments
Open

Google web crawler is finding candidate packages #504

erantapaa opened this issue Jun 8, 2016 · 3 comments

Comments

@erantapaa
Copy link

I did a search Google for Data.Vector hackage and the top hit was:

https://hackage.haskell.org/package/vector-0.11.0.0/candidate/docs/Data-Vector.html

As I understand it, candidate packages just for authors to make sure things look alright before committing the upload, so perhaps we don't want those links being collected by search engines?

@gbaz
Copy link
Contributor

gbaz commented Jun 8, 2016

Ick this is a bit tricky. Due to the nature of the paths we can't change robots.txt to disallow them (they share a common prefix with the good paths) and due to the nature of the pages (generated by haddock) its hard to tweak their metadata directly.

I think we'll need something we've intended to have anyway -- a way to have hackage server do a transform/rewrite on generated docs to add some additional html (in this case an additional META directive to disallow crawls). Definitely open to better ideas.

@gbaz
Copy link
Contributor

gbaz commented Feb 25, 2018

Another thought -- why not just relocate the candidate pages so they don't hang off a common prefix? I don't think there's anything that depends on them being in their current locations...

@hvr
Copy link
Member

hvr commented Feb 25, 2018

@gbaz we could relocate them if we put HTTP redirects in place at their old locations to be on the safe side...

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

No branches or pull requests

3 participants