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

Point "latest version" links to specific page #1085

Closed
uusijani opened this issue Dec 31, 2018 · 4 comments
Closed

Point "latest version" links to specific page #1085

uusijani opened this issue Dec 31, 2018 · 4 comments

Comments

@uusijani
Copy link
Contributor

As discussed in #915 and #517, Google seems to prefer old versions' documentation at the expense of newer ones for some reason. The issue was partly mitigated by the fix for #958, which added prominent links to the latest version on top of old pages.

But these links currently point to the manual root. Ideally, I'd like these links to point directly to the latest version of the specific manual page I'm viewing, if available.

For instance, a search for nextcloud occ (for me at least) currently yields the manual page for version 9 as the top result. The "latest version" link at the top then takes me to the server manual introduction. This means it's still easier for me to navigate to the latest version of the "Using the occ command" page by manually replacing the version number in the current URL with 'stable' (or the latest release number) than to follow the "latest version" link and try to find the page there.

Producing specific links is probably more laborious than the generic top-level-pointing link. For instance, there may no longer be a corresponding page in the stable version. Detecting such cases should be automatable I think, but there may be other issues that aren't.

This will be much less of an issue once the SEO issue is resolved, but I think direct links would still remain useful, as people can still come up with search terms that search engines think correspond to old documentation better than the latest.

@skjnldsv
Copy link
Member

Don't you think we shouold just wait for google to update evrything?
We could also declare the old ones as outdated to google?
Or remove them from the google robots?

Plenty of ways to make sure eople don't land there again :)

@uusijani
Copy link
Contributor Author

uusijani commented Dec 31, 2018

@skjnldsv The points you raise are about SEO, and (from what I linked to above) I believe those issues are already being worked on. In case I was unclear, I'm not arguing for my idea to supplant the SEO work currently in progress, but to augment it.

Obviously, if #915 gets implemented as requested, my issue becomes moot, but from reading the comments there I understand it's not so cut and dried that it will be.

@MorrisJobke
Copy link
Member

But these links currently point to the manual root. Ideally, I'd like these links to point directly to the latest version of the specific manual page I'm viewing, if available.

The problem with this is that it could be due to restructuring of the documentation the pages aren't reachable under the same domain anymore. Thus we didn't made this the default and just redirect to the main page of the newer docs.

@tflidd
Copy link
Contributor

tflidd commented Apr 22, 2022

It was also mentioned in this newer report: #1825

It was fixed in the meantime.

@tflidd tflidd closed this as completed Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants