| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Michael Christofides <michael(at)pgmustard(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: once more: documentation search indexing |
| Date: | 2022-04-14 08:25:50 |
| Message-ID: | 53CEE7A7-56A2-43A7-950E-521135137456@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> On 14 Apr 2022, at 05:35, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Wed, Apr 13, 2022 at 8:19 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>> I can look at overall traffic to docs. From a period from Mar 21 - Apr
>> 13, traffic to docs is up 6.78% vs. Feb 25 - Mar 20. So it seems OK at a
>> high level.
>
> Have you thought about using robots.txt to forbid Google from indexing
> versions of Postgres that are now out of support?
robots.txt won't keep Google from indexing the page, if it's linked to from
anywhere on the web it will still appear in the index and search results.
If we want to keep outdated version away from the search results they need a
noindex attribute in <head>:
<meta name="robots" content="noindex">
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-04-14 16:23:37 | Re: once more: documentation search indexing |
| Previous Message | Peter Geoghegan | 2022-04-14 03:35:23 | Re: once more: documentation search indexing |