[
https://issues.apache.org/jira/browse/FLINK-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691951#comment-16691951
]
Ken Krugler commented on FLINK-9541:
------------------------------------
The use of canonical links should only be for pages that are actually identical
(e.g. stable and 1.6, currently). It looks like the flink.apache.org site is
using them for pages that aren't identical, e.g. all of the top level pages
from past releases (1.4, 1.5, and 1.6) have the same canonical link to the
stable doc version. Here's some info from a top SEO site about this practice...
{quote}
h3. Using rel=canonical on not so similar pages
While I wouldn’t recommend this, you _can_ definitely use rel=canonical very
aggressively. Google honors it to an almost ridiculous extent, where you can
canonicalize a very different piece of content to another piece of content.
However, if Google catches you doing this, it will stop trusting your site’s
canonicals and thus cause you more harm…
{quote}
This might be what's happening (Google ignoring canonicals), as I see
duplicates in search results of pages that have the same canonical link. The
only pages that should have the canonical link are the latest (eg. 1.6
currently) documentation, being mapped to the stable version. But that would
mean doing an update to the older version's pages with a new release. It's also
possible to set up an HTTP response header with the canonical link, see
[https://webmasters.googleblog.com/2011/06/supporting-relcanonical-http-headers.html,]
so maybe that's a better approach.
Finally, I don't think the JavaDocs have canonical links, yes? I haven't looked
into that much, just checked a page.
> Add robots.txt and sitemap.xml to Flink website
> -----------------------------------------------
>
> Key: FLINK-9541
> URL: https://issues.apache.org/jira/browse/FLINK-9541
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
> Reporter: Fabian Hueske
> Priority: Major
>
> From the [dev mailing
> list|https://lists.apache.org/thread.html/71ce1bfbed1cf5f0069b27a46df1cd4dccbe8abefa75ac85601b088b@%3Cdev.flink.apache.org%3E]:
> {quote}
> It would help to add a sitemap (and the robots.txt required to reference it)
> for flink.apache.org and ci.apache.org (for /projects/flink)
> You can see what Tomcat did along these lines -
> http://tomcat.apache.org/robots.txt references
> http://tomcat.apache.org/sitemap.xml, which is a sitemap index file pointing
> to http://tomcat.apache.org/sitemap-main.xml
> By doing this, you can emphasize more recent versions of docs. There are
> other benefits, but reducing poor Google search results (to me) is the
> biggest win.
> E.g. https://www.google.com/search?q=flink+reducingstate
> <https://www.google.com/search?q=flink+reducingstate> (search on flink
> reducing state) shows the 1.3 Javadocs (hit #1), master (1.6-SNAPSHOT)
> Javadocs (hit #2), and then many pages of other results.
> Whereas the Javadocs for 1.5
> <https://ci.apache.org/projects/flink/flink-docs-release-1.5/api/java/org/apache/flink/api/common/state/ReducingState.html>
> and 1.4
> <https://ci.apache.org/projects/flink/flink-docs-release-1.4/api/java/org/apache/flink/api/common/state/ReducingState.html>
> are nowhere to be found.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
