X-Original-To: pgsql-advocacy-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 203C49FB688 for ; Mon, 4 Sep 2006 03:09:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 22007-02-2 for ; Mon, 4 Sep 2006 03:09:03 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.204]) by postgresql.org (Postfix) with ESMTP id 8EB6E9FB570 for ; Mon, 4 Sep 2006 02:30:51 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id 14so803891nzn for ; Sun, 03 Sep 2006 22:30:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ph2xxGmgJlBMtKS/4LjHnQQuvjLPpN21KQiScmhiVcnCNQanonvJLdW5AKkMCs7n9YIE41n8NRV/rT561CXkVdFR2DnLQjzU9pCKjfPq067Xu6ZyWFpjsO1Mxf1MCtQYQEVd5HnKq8p2AMH8W4RU0r0XcwZFzNJ9tEQTNbbLaZE= Received: by 10.65.93.18 with SMTP id v18mr2641526qbl; Sun, 03 Sep 2006 22:30:48 -0700 (PDT) Received: by 10.65.250.14 with HTTP; Sun, 3 Sep 2006 22:30:48 -0700 (PDT) Message-ID: <758d5e7f0609032230y6dbe1cc6ge7b16337d040fb39@mail.gmail.com> Date: Mon, 4 Sep 2006 07:30:48 +0200 From: "Dawid Kuroczko" To: "Greg Sabino Mullane" Subject: Re: Getting better Google search results Cc: pgsql-advocacy@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.256 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/18 X-Sequence-Number: 9730 On 8/29/06, Greg Sabino Mullane wrote: > I had an idea while discussing the limitations of our searching > on irc with a few folks. As far as Google putting old 7.x and > 6.x documentation results up, why not create a new subdomain > such as oldocs.postgres.org and stick anything older than a > version of two there. We could still link to it, and leave some > redirects in place for old links, but the new subdomain would > ensure that they would have relatively *low* Google results > compared to the more recent docs, which is what we want. Wouldn't it be feasible to add a "see current version" link which would link from all the old versions to the most current one? Say, a page http://www.postgresql.org/docs/7.4/static/ecpg-errors.html ...would have a line in a header: Home → Documentation → Manuals → PostgreSQL 7.4 (See current version) ...where (See current version) would link to: http://www.postgresql.org/docs/current/static/ecpg-errors.html As far as I understand how Google works, this would push the link density towards the current version of PostgreSQL, therefore 8.1 should pop out as top results. Just a thought. :) Regards, Dawid