Skip to content

Allow rustdoc to generate noindex meta tags for a library #41882

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

Closed
skade opened this issue May 10, 2017 · 3 comments
Closed

Allow rustdoc to generate noindex meta tags for a library #41882

skade opened this issue May 10, 2017 · 3 comments
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@skade
Copy link
Contributor

skade commented May 10, 2017

There's currently a problem that when searching for the documentation of a crate in any search engine, chances are you find the documentation of a different project that publishes their full documentation along with all dependencies.

To avoid that, allow rustdoc to generate the following meta tag for all documentation of a library:

<meta name="robots" content="noindex">

This makes most crawlers not index the page. The feature could be implemented behind a flag.

rel="canonical" would be preferably, but the correct URL is hard to derive.

@steveklabnik
Copy link
Member

rel="canonical" would be preferably, but the correct URL is hard to derive.

That's #9461

@steveklabnik steveklabnik added T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. C-enhancement Category: An issue proposing an enhancement or a PR with one. labels May 10, 2017
@skade
Copy link
Contributor Author

skade commented May 10, 2017

Thinking this further through, a blanket "noindex" for dependencies might lead to problems, though, if a project publishes docs for set of crates on the same domain, by just building the topmost one.

@steveklabnik steveklabnik added the T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. label May 18, 2017
@steveklabnik
Copy link
Member

steveklabnik commented Sep 24, 2018

Triage: there's been no comments in two years. Additionally, we did accept an RFC that will fix this issue, and it is being tracked in #44687. Closing as a duplicate of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants