-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Intentionally degrade SEO for non-latest stable docs #7010
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
Comments
Tomorrow we will be releasing "hidden versions" #6792 https://docs.readthedocs.io/en/latest/versions.html#states That should help with this problem. |
well that was a fast turnaround on that feature 😆 thanks for the link - I agree that definitely should help. when a branch is "inactive" will it also stop showing up in google? |
When a version is inactive, the docs are deleted, so I guess google will stop to show those results? |
oh sorry, I meant "hidden", not inactive |
When a version is hidden it's listed as Disallow in a |
awesome - well it sounds like I can close this and you all deserve a 🍺 :-) |
Happy to share it with you... after the global 🌎 pandemic 😷 , of course 😄 |
Uh oh!
There was an error while loading. Please reload this page.
Details
I have noticed a common problem across many projects that are hosted with readthedocs, particularly those that have been around for quite some time, which is that older versions of the documentation often show up first in search results.
Here is a recent example I ran into with Sphinx's own docs:
As you can see, the 1.5.6 Sphinx documentation, which is many many versions old by now, is the first result. It also seems problematic that the latest stable version is not listed at all, and instead we only find a 4.0 dev version of the pages as well.
So here's my question: would it be possible to add an option to intentionally degrade the SEO for non-latest stable (or
latest/
) documentation builds?I think that this could help improve the confusion around projects that have really old documentation show up (it is helpful to have the "these aren't the latest docs" flags, but I find it is still quite confusing for newcomers to follow them)
The text was updated successfully, but these errors were encountered: