Bug 1294225 – Search engines prefer old releases in docs.fedoraproject.org

Bug 1294225 - Search engines prefer old releases in docs.fedoraproject.org

Summary:	Search engines prefer old releases in docs.fedoraproject.org

Status:	NEW

Aliases:	None

Product:	Fedora Documentation
Classification:	Fedora
Component:	docs-requests (Show other bugs)
Sub Component:
Version:	devel
Hardware:	All All

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Nobody's working on this, feel free to take it
QA Contact:	Fedora Docs QA
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-12-25 10:21 EST by Federico Leva
Modified:	2016-06-07 18:14 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Federico Leva 2015-12-25 10:21:26 EST

Whenever I search Fedora documentation in search engines without setting a date interval, I end up in docs for fedora 14 or similar. There should be a way to make search engines prefer the most current version of each documentation page.

It may be appropriate to add <link rel="canonical" from all pages to the most recent version of the same page, if existing; or there could be a directory //docs.fedoraproject.org/en-US/Fedora/latest/ or similar, which would be symlinked to 23/ or whatever is the latest version and would be the target of all links.

More on rel canonical:
* https://googlewebmastercentral.blogspot.com/2013/04/5-common-mistakes-with-relcanonical.html
* https://googlewebmastercentral.blogspot.com/2014/02/faceted-navigation-best-and-5-of-worst.html

Related issues: bug 1284490, bug 1225537, bug 948823, bug 1115469.

Note You need to log in before you can comment on or make changes to this bug.