GTranslateReviews of gtranslate.io

We used them for five years. Normally good service but for an entire week now we've gotten zero support. They don't read replies, don't reply to the replies, and conviently send answers to questions I didn't have... Even after direct statements seeking what I needed. In this case, they didn't need to do anything but tell me if the plans my host had were sufficient. I never got an answer. They can't read and type 'yes' or 'no'. I need better service than that. In fact the last 'responser' was "let me check it" and then more than 14 hours of silence as of this writing. Not sure what's going on their but they are unreliable. The lead of the entire technical department led the charge in not answering, communicating, and downgrading my level of service and support. Simply amazing. We will be moving. We don't use unsupported software. It'll be hell on our SEO but the pain of separation is worth if...if their purpose is BS. We're moving to Polylang. Higher level of support, and cheaper. One $140 fee versus paying Gtranslate $35 monthly and they won't answer a non-laboring inducing question. JFC. UNPROFESSIONAL!

GTranslate serves as the proxy to malicious traffic

Das eingemeldete Problem mit hreflang tags wurde nach wie vor nicht behoben!

We are posting this factual B2B review as Mane Biotech GmbH. GTranslate’s internal logs confirmed in writing that our software integration was uninstalled on November 27, 2025. Despite this uninstallation, their payment system failed to disconnect our corporate credit card and continued to execute unauthorized monthly debits of $50.00 throughout 2026 on decommissioned infrastructure. When brought to management's attention, customer support refused to process full refunds for the unearned fees, citing internal return policies and requesting technical file uploads on a non-existent server. We have been forced to file formal credit card dispute proceedings (Mastercard Code 4853) with our issuing bank to recover our funds. Warning to corporate buyers: Monitor your recurring credit card statements closely after uninstalling this app, as backend payment tokens may remain active in their billing engine post-deletion.

Unfortunately, I had a very bad experience with this plugin, including the paid version that is supposed to translate URLs and provide better SEO functionality. The translations were consistently very poor and often sounded unnatural or simply incorrect. Much worse, however, was the impact on SEO. Similar to what Thomas Wachsmuth described in his review from July 16, 2025, my websites' SEO performance declined dramatically after using the plugin. I tested it on two different websites, and in both cases things went downhill afterwards. Rankings, indexing and overall organic visibility were negatively affected. I specifically paid for the premium version because I expected features such as translated URLs to improve the multilingual SEO setup, but my experience was exactly the opposite. After what happened with both websites, I personally cannot recommend this plugin, especially if organic search traffic and SEO are important to your business.

I used GTranslate on a fairly large WooCommerce site with **3,000+ products and roughly 700 additional pages, posts, categories, and tags**. We wanted to offer translations in 40+ languages. **I would absolutely NOT recommend doing this on a large self-hosted WooCommerce site.** The biggest problem is the absolutely insane amount of traffic GTranslate generates against your origin. Their translation bots repeatedly crawl the site, and once you start creating thousands of translated URLs, those URLs attract even more crawlers and bots. At its worst, we were seeing **10,000+ requests every 15 minutes**. You can try to control this with Cloudflare, rate limiting, Workers, firewall rules, etc., but then you run into another ridiculous problem: **you start interfering with legitimate visitors trying to use the translations.** Someone visits `website DOT com/fr/` or `fr.website DOT com`, clicks around, and suddenly gets rate-limited because you're desperately trying to stop the translation system from hammering your server. I even switched to the **subdomain configuration**, hoping it would improve caching or reduce the load on the main site. In my experience, it solved basically nothing. ### Translated URLs were another disaster I strongly recommend **NOT enabling URL translation** on a large site. Different languages use different characters, punctuation, quotation marks, encoding, etc., and we ended up with malformed translated URLs and a mountain of 404 errors. Instead of improving SEO, you're now babysitting thousands upon thousands of automatically generated URLs and trying to figure out why Google and other crawlers are finding garbage URLs that don't exist. If you're going to use this service, I would seriously consider leaving URL translation OFF. ### The 24-hour caching is ridiculous One of my biggest problems is that translated content is apparently cached for only **24 hours**. On a site with thousands of pages multiplied across 40+ languages, think about what that means. The crawling doesn't eventually settle down. It just keeps going. **Hit. Hit. Hit. Crawl. Crawl. Crawl. Every single day.** I originally started using GTranslate around two years ago. During the first six months, it was actually okay because the website was much smaller. Then it stopped working properly for roughly six months, apparently because of an issue involving Cloudflare. I basically ignored it until I eventually hired a developer to get everything working again. By that point, our website had grown significantly. That's when GTranslate went from being mildly useful to being an **absolute resource-hogging nightmare**. And before somebody says, "You just need a better server" — **no.** I literally upgraded the server to approximately **3× the previous capacity** trying to accommodate this. We eventually had a server with roughly: **48GB RAM 12 CPU cores** I also upgraded to **Cloudflare Pro**, added **Cloudflare Workers**, configured firewall/rate-limiting rules, and **paid a developer to build custom throttling specifically to control the translation traffic**. All of this because of a translation service. And after all of that? **Same nonsense.** At some point you have to ask yourself why you're spending money on bigger servers, Cloudflare upgrades, Workers, developers, firewall rules, bot mitigation, and troubleshooting just to keep a translation plugin from beating the living hell out of your origin server. Maybe this works wonderfully on Shopify, where the infrastructure and hosting situation is completely different. Maybe it works fine on a small WordPress site with 50 pages and two or three languages. But for a **large, self-hosted WooCommerce store with thousands of products and dozens of languages, I wouldn't touch this again.** My recommendation: **Small website + 1–3 languages?** Probably fine. **Large WooCommerce store + 40+ languages + translated URLs?** Stay far away. After two years of dealing with it, upgrading hardware, upgrading Cloudflare, paying a developer, troubleshooting caching, dealing with broken translated URLs, and watching translation bots relentlessly hammer the site, I've finally had enough. **For a large WooCommerce store, GTranslate became less of a translation service and more of a self-inflicted DDoS attack that I was paying for every month.**

Дорого. И цену поменяли и даже не предупредили. Гугл этот перевод теперь с трудом переваривает и оставляет зачастую только английскую версию перевода, а остальные считает тонким контентом и вышвыривают из поиска.

It's cumbersome to use - it is a huge time and energy drain to do highly necessary corrections to translations.