jdMorgan - 6:16 pm on May 2, 2009 (gmt 0)

I don't see anything there that would stop them from translating.

Do check for HTML coding errors on your page though, and be sure that the DOCTYPE line is the first in the document (for example, make sure there's no spurious blank line ahead of it.)

You can re-code/simplify your .htaccess for somewhat better performance with no change to function:

RewriteEngine on
#
RewriteCond %{HTTP_REFERER} !^(http://(www\.)?example\.co\.uk/.*)?$ [NC]
RewriteCond %{REQUEST_URI} !^nohotlink\.
RewriteRule \.(jpe?g¦gif¦png¦bmp¦swf)$ http://www.example.co.uk/images/nohotlink.jpe [NC,R=302,L]

Note that the additional RewriteCond means that you can name your nothotlink image as a .jpg if you want to, without causing a redirection loop. You don't actually need this line, but it might be helpful if you or someone else is likely to 'forget' why you used a filetype of .jpe for this image...

Important: Replace the borken pipe "¦" characters here with solid pipe characters before use; Posting onthis forum modifies the pipe characters.

You should also look into canonicalizing URLs and hostnames on your server. For example, all of the following 15 URLs return your home page, present duplicate content, and thus "compete" with each other for links, "recognition/branding," and ranking:

example.co.uk/
example.co.uk./
example.co.uk:80/
example.co.uk.:80/
www.example.co.uk./
www.example.co.uk:80/
www.example.co.uk.:80/

example.co.uk/index.html
example.co.uk./index.html
example.co.uk:80/index.html
example.co.uk.:80/index.html
www.example.co.uk/index.html
www.example.co.uk./index.html
www.example.co.uk:80/index.html
www.example.co.uk.:80/index.html

All should be 301-redirected to the canonical "www.example.co.uk/" URL. Doing so would also simplify your anti-hotlinking code, since only the one canonical hostname would then be a valid referrer.

Unfortunately, I doubt that anything I posted here will result in a solution, but correcting any DOCTYPE problems and fixing errors in your HTML *might* help.

There is also the possibility that your host has blocked Google's access to your server at the firewall level. Some hosts do this in a badly-conceived attempt to reduce their network traffic. You could try a translation yourself, and see if the server error log file indicate any problems, or ask your host if they firewall Google translation requests (or any others Google requests).

Jim