public inbox for [email protected]help / color / mirror / Atom feed
Getting better Google search results 7+ messages / 6 participants [nested] [flat]
* Getting better Google search results @ 2006-08-29 04:20 Greg Sabino Mullane <[email protected]> 0 siblings, 2 replies; 7+ messages in thread From: Greg Sabino Mullane @ 2006-08-29 04:20 UTC (permalink / raw) To: [email protected] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. - -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 200608290016 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFE87/LvJuQZxSWSsgRAk/0AJ9k3fokCQEj7aVyuNBnJF8vCrEDzACcDR8K ZVDwn7UHGIvZUHUcCyV62a4= =VwOO -----END PGP SIGNATURE----- ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [pgsql-advocacy] Getting better Google search results @ 2006-08-29 07:56 Magnus Hagander <[email protected]> parent: Greg Sabino Mullane <[email protected]> 1 sibling, 2 replies; 7+ messages in thread From: Magnus Hagander @ 2006-08-29 07:56 UTC (permalink / raw) To: Greg Sabino Mullane <[email protected]>; [email protected]; +Cc: pgsql-www Wouldn't this be better on -www? :-P > 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. Don't we have enough silly domains already? If we want to get rid of those hits, why don't we just add a robots.txt and tell google not to index the old docs at all? (If people *need* hits in the old docs, they can always hit our own search engine for those docs) //Magnus ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Getting better Google search results @ 2006-08-29 10:37 Greg Sabino Mullane <[email protected]> parent: Magnus Hagander <[email protected]> 1 sibling, 0 replies; 7+ messages in thread From: Greg Sabino Mullane @ 2006-08-29 10:37 UTC (permalink / raw) To: [email protected] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Wouldn't this be better on -www? :-P I considered that, but this seems more of an advocacy problem with a technical solution. I thought the wider advocacy audience might have some ideas about it. > Don't we have enough silly domains already? If we want to get rid of > those hits, why don't we just add a robots.txt and tell google not to > index the old docs at all? (If people *need* hits in the old docs, they > can always hit our own search engine for those docs) I considered that, but I would not want to completely eliminate the old docs from Google searching. There's always a chance something useful is there. However, since 99.9% of generic non-version specific searches should *not* hit those pages, it's best to stick those on the "e" in Goooooooooooooooooooooooogle. :) - -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 200608290634 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFE9BhTvJuQZxSWSsgRAjMuAJ9eHXUVE1teHRNVMuH7lKOKxIgG6wCffYak S9CKiT3zI/FitV09LeAKPHs= =CwM6 -----END PGP SIGNATURE----- ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [pgsql-advocacy] Getting better Google search @ 2006-08-29 14:20 Devrim GUNDUZ <[email protected]> parent: Magnus Hagander <[email protected]> 1 sibling, 1 reply; 7+ messages in thread From: Devrim GUNDUZ @ 2006-08-29 14:20 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: Greg Sabino Mullane <[email protected]>; [email protected]; pgsql-www Hello, On Tue, 2006-08-29 at 09:56 +0200, Magnus Hagander wrote: > Don't we have enough silly domains already? Heh. olddocs.postgresql.org veryolddocs.postgresql.org atticdocs.postgresq rarelyuseddocs.postgresql.org ... :) -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/ Attachments: [application/pgp-signature] signature.asc (189B, 2-signature.asc) download ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [pgsql-advocacy] Getting better Google search @ 2006-08-29 15:07 Robert Treat <[email protected]> parent: Devrim GUNDUZ <[email protected]> 0 siblings, 1 reply; 7+ messages in thread From: Robert Treat @ 2006-08-29 15:07 UTC (permalink / raw) To: [email protected]; +Cc: Devrim GUNDUZ <[email protected]>; Magnus Hagander <[email protected]>; Greg Sabino Mullane <[email protected]>; pgsql-www On Tuesday 29 August 2006 10:20, Devrim GUNDUZ wrote: > Hello, > > On Tue, 2006-08-29 at 09:56 +0200, Magnus Hagander wrote: > > Don't we have enough silly domains already? > > Heh. > > olddocs.postgresql.org > veryolddocs.postgresql.org > atticdocs.postgresq > rarelyuseddocs.postgresql.org > ifyouarestillrunningthisversionthedocswonthelpyou.postgresql.org -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: [pgsql-advocacy] Getting better Google search @ 2006-08-29 16:11 Joshua D. Drake <[email protected]> parent: Robert Treat <[email protected]> 0 siblings, 0 replies; 7+ messages in thread From: Joshua D. Drake @ 2006-08-29 16:11 UTC (permalink / raw) To: Robert Treat <[email protected]>; +Cc: [email protected]; Devrim GUNDUZ <[email protected]>; Magnus Hagander <[email protected]>; Greg Sabino Mullane <[email protected]>; pgsql-www Robert Treat wrote: > On Tuesday 29 August 2006 10:20, Devrim GUNDUZ wrote: >> Hello, >> >> On Tue, 2006-08-29 at 09:56 +0200, Magnus Hagander wrote: >>> Don't we have enough silly domains already? >> Heh. >> >> olddocs.postgresql.org >> veryolddocs.postgresql.org >> atticdocs.postgresq >> rarelyuseddocs.postgresql.org >> > > ifyouarestillrunningthisversionthedocswonthelpyou.postgresql.org Let's just shorten that to: youarefscked.postgresql.org Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Getting better Google search results @ 2006-09-04 05:30 Dawid Kuroczko <[email protected]> parent: Greg Sabino Mullane <[email protected]> 1 sibling, 0 replies; 7+ messages in thread From: Dawid Kuroczko @ 2006-09-04 05:30 UTC (permalink / raw) To: Greg Sabino Mullane <[email protected]>; +Cc: [email protected] On 8/29/06, Greg Sabino Mullane <[email protected]> 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 ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2006-09-04 05:30 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2006-08-29 04:20 Getting better Google search results Greg Sabino Mullane <[email protected]> 2006-08-29 07:56 ` Magnus Hagander <[email protected]> 2006-08-29 10:37 ` Greg Sabino Mullane <[email protected]> 2006-08-29 14:20 ` Re: [pgsql-advocacy] Getting better Google search Devrim GUNDUZ <[email protected]> 2006-08-29 15:07 ` Re: [pgsql-advocacy] Getting better Google search Robert Treat <[email protected]> 2006-08-29 16:11 ` Re: [pgsql-advocacy] Getting better Google search Joshua D. Drake <[email protected]> 2006-09-04 05:30 ` Dawid Kuroczko <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox