Skip to content

Fix googleability of docs #12466

Closed
Closed

Description

@brson

Googling for Rust documentation gives very inconsistent results, often to very old docs. Newbies often are led astray.

Old description:

This is a topic I haven't paid much attention to, but it's important, and I know our googlability has traditionally been very bad. I don't know at all what needs to be done off hand but it's something we should dedicate some effort to.

Nominating.

Tasks:

Activity

  1. alexcrichton commented on Feb 27, 2014

    @alexcrichton
    Member
  2. pnkfelix commented on Feb 27, 2014

    @pnkfelix
    Contributor

    To clarify, the particular problem that has plagued us is that it is too easy to end up with outdated documentation when googling for help with problems.

  3. pnkfelix commented on Feb 27, 2014

    @pnkfelix
    Contributor

    Assigning 1.0, P-high.

  4. emberian commented on Feb 27, 2014

    @emberian
    Contributor

    I imagine this could be partially alleviated with some well-placed meta tags.

  5. added this to the 1.0 milestone on Feb 27, 2014
  6. Valloric commented on Feb 28, 2014

    @Valloric
    Contributor

    The very first step should be reading Google's Webmaster Guidelines and related documents.

    Also, here's a good doc Google has prepared on sensible SEO things webmasters can do.

    I imagine this could be partially alleviated with some well-placed meta tags.

    Here's a really nice video on the topic of meta tags and their usefulness by Google's Matt Cutts: https://www.youtube.com/watch?v=RBTBEfd7z_Y

  7. adrientetar commented on Mar 11, 2014

    @adrientetar
    Contributor

    The DNS issue is #4394.

  8. self-assigned this
    on Aug 1, 2014
  9. brson commented on Aug 1, 2014

    @brson
    ContributorAuthor

    @Valloric thank you for those helpful links.

  10. brson commented on Aug 1, 2014

    @brson
    ContributorAuthor

    I've started a task list in the OP.

    I did some basic searches for Rust datatypes in a private window today and the results looked good to me. I'm not sure if there's a whole lot we need to do.

    Google is preferring the 'shorthand' doc urls, not the ones with version numbers in them.

    I intend to run www.rust-lang.org through Google's various webmaster tools to see if it has any suggestions.

  11. Valloric commented on Aug 2, 2014

    @Valloric
    Contributor

    Google is preferring the 'shorthand' doc urls, not the ones with version numbers in them.

    Well, you are using robots.txt to prevent Google from indexing the old API docs.

  12. 17 remaining items

  13. brson commented on Sep 11, 2014

    @brson
    ContributorAuthor

    Nominating for removal from 1.0. Not critical. Worst problems are solved.

  14. assigned and unassigned on Sep 11, 2014
  15. Valloric commented on Sep 11, 2014

    @Valloric
    Contributor

    @brson Have you made sure you aren't serving the same page content from two different URL structures without canonical annotations? http://doc.rust-lang.org/master/std/index.html and http://doc.rust-lang.org/std/index.html show the same page for me. As I mentioned previously, I recommend looking at this Google support doc on canonical URLs.

    In your case, making sure one of those pages uses <link rel="canonical" href="[canonical page url]" /> would be a good idea.

    Even better, make one of those URLs 301 to the other or better still, have just one URL structure for getting to the content.

  16. brson commented on Sep 11, 2014

    @brson
    ContributorAuthor

    @Valloric No, I have not.

  17. Valloric commented on Sep 12, 2014

    @Valloric
    Contributor

    @brson Consider fixing that before you get tons of people searching for Rust docs. It's always a good idea to have your canonical urls sorted out, for any site.

  18. pnkfelix commented on Sep 18, 2014

    @pnkfelix
    Contributor

    Removing from 1.0 milestone but leaving as P-high. No one wants to block the release on just the issue pointed out by @Valloric 's comment here: #12466 (comment)

  19. removed this from the 1.0 milestone on Sep 18, 2014
  20. removed their assignment
    on Mar 12, 2015
  21. brson commented on Jul 14, 2016

    @brson
    ContributorAuthor

    Closing in favor of specific linked bugs.

  22. added a commit that references this issue on Jul 25, 2022
  23. added a commit that references this issue on Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions