[
https://issues.apache.org/jira/browse/SOLR-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874548#comment-16874548
]
Jan Høydahl commented on SOLR-13571:
------------------------------------
{quote}I'm not totally against the idea of having a "latest", but I don't quite
get why it can't be a redirect?
{quote}
Today the "latest" redirect hack is not a landing page of its own, and it uses
302 redirect which I believe will not pass on page rank to the target.
Take [https://lucene.apache.org/solr/guide/about-this-guide.html] which now
redirects to [https://lucene.apache.org/solr/guide/8_1/about-this-guide.html].
Now the user will start sharing the 8_1 link and in a few years we have the
same issue that the 8_1 guide has a lot of credit. Since the URL in browser
changes, it is hard to bookmark and copy, so it won't get much use in the wild.
If, on the other hand, we had a
[https://lucene.apache.org/solr/guide/latest/about-this-guide.html] landing
page, we could move the cwiki 301 redirect
([https://cwiki.apache.org/confluence/display/solr/About+This+Guide)] to the
new stable location. I'm not sure though if Google already has moved all the
rank points to the 6_6 HTML url or if moving the redirects again will suddenly
make the /latest/ urls rank high. If the 6_6 guide still has all the points we
could of course redirect all 6_6 links to "latest" as well, but then the 6_6
guide would be unreachable :). To fix that we could re-release the 6_6 guide
under e.g. 6_6_0.
The extra effort if we choose such a model is
* Copy the generated guide twice to release repo, to two different locations
* Make sure page renames are handled, e.g. as I proposed above, to track when
a page that existed before no longer exists in the to-be-published guide, and
then add a redirect for it to the latest version that had that page, or add a
dummy page with a link on it. This would be scripted as part of release process
- make a tool comparing the page tree between two versions.
> Make recent RefGuide rank well in Google
> ----------------------------------------
>
> Key: SOLR-13571
> URL: https://issues.apache.org/jira/browse/SOLR-13571
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Jan Høydahl
> Priority: Major
>
> Spinoff from SOLR-13548
> The old Confluence ref-guide has a lot of pages pointing to it, and all of
> that link karma is delegated to the {{/solr/guide/6_6/}} html ref guide,
> making it often rank top. However we'd want newer content to rank high. See
> these comments for some first ideas.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
