You are welcome to look around. You will have to register before you can post a message, create a blog, chat live with our members, or add a site to our directory.
The /lang/en/ that is 301'd to the regular language, the 301 is not correct, header checkers show /lang/en/ is being 301'd to www.domain.com/translate/g/en/
Can you show me a link on your page where this happens?
I'm not so concerned about header checkers -- I'm concerned about what happens to real site visitors (and robots!)
Quote:
Originally Posted by davesnake
Also, I have perfect w3 validation, yet translated pages have 90+ errors. I dont understand why as the code should be unchanged.
Ahh... that's a great question! Welcome to the deep underbelly of translation.
Google absolutely stuffs the translated pages with crap. We have to take that crap out in order to reduce the "footprint" of the translated pages that Google can use to automatically penalize them.
In tr_config.php, set write_raw_content to true and then look at the raw translation files. There is an enormous amount of garbage that needs to be cleaned up.
That's what the function GoogleFixup() does.
Of course, that code is complex and can easily be buggy!
If you don't like what GoogleFixup() is doing to your pages, you can add/edit/delete anything in that section of the code. That's where the real magic happens.
Well real visitor goto the right place, I thought robots used headers, so that was my concern. You can enter any /en/ url into a header checker and it 301's to the translate folder.
It looks like the header checker script you are using follows the first 301, but does not follow the next 301. Human visitors (and robots) follow both 301's.