[
https://issues.apache.org/jira/browse/SOLR-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874944#comment-16874944
]
Alexandre Rafalovitch commented on SOLR-13571:
----------------------------------------------
We could definitely do a sitemap.
But also, we could update the redirect list and see if that makes a lot of
difference. I had a quick look in the infra repo and it seems to be two files:
(solr_id_to_new.map.txt and solr_name_to_new.map.txt). This seems to correspond
to those we generated in SOLR-10595. So perhaps we just need to review those
files for target file name changes (may be 99% same) and ask Infra to refresh
files with new URL base of 8.1.
Also, if we could get access to the Google Webmaster tools, that would be nice.
It can be done by publishing a file to the server, can we do that outside of a
full publication process.
Finally, if we republish 6.6 with additional canonical header pointing to
latest (or 8.1 or whatever), this may also refocus the search ranking. The work
for that would probably be identical to that required to redo the maps.
> 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
