Just putting a feature on the site that links over to the Google Translate version really isn't worth the time, since it clutters up the page, and those transla

Just putting a feature on the site that links over to the Google Translate version really isn't worth the time, since it clutters up the page, and those translations aren't very good. However, despite you saying it isn't an option, if you actually serve good translations through the site that are crawled, that may draw more visitors. If it is a saas app and you want it to be used internationally though, I say go for it and use google translate to attempt to translate labels, etc. that you use. Provide a feedback area so that people can tell you if the translation is bad, if they feed like it. But be aware that there is much more to i18n and i10n than translation (legal, other gov't issues, cultural issues, timezone, character set issues in page and DB, layout differences).