Translating website server vs. client-side?

GPT4 is quite good for translation.. much better than GPT3.5.. but I wouldn't have the courage to believe in perfect context translation ... ... and GPT4 is not free

AI translations like Google Translate can be a starting point, Anna, but for SEO and user experience, professional translations are worth the investment. Server-side translation can offer a seamless experience and help avoid duplicate content issues, which, if handled correctly with hreflang tags, won't incur penalties by search engines.

Following

1. Always have it checked by a human/native speaker 2. SEO-wise, you will rank much better with server-side solutions for searches in their native language. It's a game changer to enter another market before a competitor or copycat pops up. 3. The metatag indicates that it is a different language to the Google crawlers. If you only change the language on the client site, the content of the crawled site looks identical and doesn't get indexed. I work at inlang.com and we have all the developer tools, a Figma extension and a no-code web editor to solve your problems. Also, feel free to jump into our Discord and ask for help :)

Following

Hi , anna. you can try this js-library. http://translate.zvo.cn/

Hi Anna! 1. I'd never use an AI tool to translate a website, even if its from Google. These tools are good at translating words, but they will break the overall flow of the sentence. It can badly hurt SEO. Always hire a translator or someone who has a good command over both the languages. 2. It really depends. If you want to translate it on server, you need to identify the client's language preferences. This would increase the load on the server if you are translating on a per-request basis. The best thing to do here is cache or pre-generate versions of your page in every language that you want to support. But this might not be feasible if you have too many pages (and its hard to detect the language preferences on the server, you need to use a cookie or ip to resolve the location, its a blind guess on the first render). What you can really do is use a client side solution (such as react-i18n). This will reduce the strain on server but will increase the size of your client bundle, unless you're using a translation service on the client (it has its own downsides of extra latency and network requests) 3. This is not really a problem. Just add a canonical meta tag on every translated page pointing to the main page. Crawlers will understand canonical pages.