Re: patch to point search engines at current version of docs

Поиск
Список
Период
Сортировка
От Jonathan S. Katz
Тема Re: patch to point search engines at current version of docs
Дата
Msg-id 251040de-75ac-d732-2167-377a04ef0326@postgresql.org
обсуждение исходный текст
Ответ на patch to point search engines at current version of docs  (adam sah <adam.sah@gmail.com>)
Ответы Re: patch to point search engines at current version of docs
Список pgsql-www
Дерево обсуждения 
Hi Adam,

On 5/11/19 5:58 PM, adam sah wrote:
> Currently, search engines often rank old versions of Postgres
> documentation pages higher than newer versions. This patch should fix
> this by having search engines always prefer the current version of the
> documentation. Users who want old versions can click on the links at the
> top of the page - today, users who want the current version have to do this.
>
> original
>
discussion: https://www.postgresql.org/message-id/CANNMO%2B%2BkxJmaaB7X6hq_8SqcEruySZrF%3DUkcPm-EG1JCKVascw%40mail.gmail.com
>
> more about rel=canonical: https://www.google.com/search?q=rel+canonical+url

Thanks for the suggestion! I remember looking at this with Magnus last
year during the last time this was brought up. I found this page to be
very helpful on the subject:

https://support.google.com/webmasters/answer/139066?hl=en

We also researched what some other open source projects were doing with
respect to their documentation pages to see how they could optimize it.

I believe the strategy you are proposing would involve setting every
anchor tag that is pointing to "/docs/current/.*" to contain the
rel="canonical" attribute. If we went down this path, the better way
would be to use the "<link rel="canonical" ...>" method that is
mentioned, i.e.

<link
  rel="canonical"
  href="https://www.postgresq.org/docs/current/the-doc-page.html"
/>

and put it in the <head> block.

At the time, one drawback we found was that this could end up causing
pages that existed in older, but supported, versions to go missing from
search engines, which is not necessarily great. We may end up deciding
that this doesn't matter, and that the main point is to get people to
the documentation and then they can select the version, but OTOH, this
could end up breaking a lot of people's workflows for how they look for
info in the docs (myself included).

We might be able to incorporate rel="alternate" on the other
documentation version pages to let the crawlers know that alternate
versions exist, but from what I've seen it seems to be restricted to
i18n or media support, and does not seem to take other attributes such
as "versions."

Thanks,

Jonathan
Вложения

В списке pgsql-www по дате отправления: