Re: django i18n and google bots

2007-05-03 Thread cactus
You could maybe check the user agent and return the desired specific content for bots. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegr

Re: django i18n and google bots

2007-05-02 Thread Phil
I've already submitted a sitemap to google. But as Eugene said, and after doing some research today, I'm afraid that the bots are impervious to cookies. This means that I will have to construct URL with a language designator )c: On May 2, 8:12 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >

Re: django i18n and google bots

2007-05-02 Thread [EMAIL PROTECTED]
I don't know if it would help, but if you sign up for the google webmaster tools you can set a preferred site root. Also, submitting a sitemap might help. On May 2, 7:37 am, Eugene Morozov <[EMAIL PROTECTED]> wrote: > I think there's no other solution as to use language designator in > URLs and p

Re: django i18n and google bots

2007-05-02 Thread Eugene Morozov
I think there's no other solution as to use language designator in URLs and placing language links on the main page. There's no way Google or any other bot can crawl the site several times with different cookies or something. Currently I'm redoing site in Django that suffers the same problem and i

Re: django i18n and google bots

2007-05-02 Thread Phil
I have indeed access to my logs, I'll check that and let you know. Many thanks Malcolm. On May 2, 10:32 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2007-05-02 at 08:16 +, Phil wrote: > > Guys, > > > I use the i18n framework of django to offer my site content in two > > languag

Re: django i18n and google bots

2007-05-02 Thread Malcolm Tredinnick
On Wed, 2007-05-02 at 08:16 +, Phil wrote: > Guys, > > I use the i18n framework of django to offer my site content in two > language: French and English. As the language preference is kept in a > cookie, all the URLs of my site are therefore language agnostic. All > is working fine. > > But,