GTranslate approaches translation through Google’s engine: machine translation of your content into over 100 languages, served either through a subdirectory/subdomain structure with SEO-friendly URLs (the paid tiers) or via a JavaScript widget (free). The paid versions are where the SEO story lives – translated pages get their own URLs, meta tags, and hreflang attributes, and become indexable rather than invisible overlays. That architecture distinction separates GTranslate’s tiers: the free widget translates what visitors see but search engines never index it, while the SEO tiers generate real multilingual pages. Against cloud-editing competitors like Weglot and ConveyThis, GTranslate’s differentiator is the Google Translate engine plus a longer-established free tier.
The 3.x plugin releases show steady refinement: Gutenberg block support for the switcher, accessibility attributes (aria-labels with language codes), keyboard navigation fixes, and form-submission handling with file uploads on translated pages – the unglamorous edge cases that break multilingual sites in practice.
Competitive Features
- 100+ languages – Google Translate engine coverage
- SEO tiers with real URLs – subdirectory/subdomain structure with hreflang and meta tags
- Multiple switcher widgets – flags, dropdown, popup with search (3.0.10)
- Gutenberg block (3.1.1) – native switcher placement in the block editor
- Form handling on translated pages (3.1.1) – file uploads work correctly
- Accessibility attributes (3.1.2) – aria-labels and keyboard navigation
- Free tier available – widget-based translation at no cost
Key Features
- Automatic translation – content translated on the fly
- URL structures – subdirectory (example.com/es/) or subdomain (es.example.com)
- Meta tag translation – titles and descriptions per language (SEO tiers)
- Language switcher options – flags, dropdown, and popup widgets
- Editable translations – manually refine machine output (paid tiers)
- Analytics integration – language-level traffic visibility
- CSS-based flag styling – switcher appearance customization
Comparison with Competitors
GTranslate vs Weglot
| Aspect | GTranslate | Weglot |
|---|---|---|
| Translation engine | Google Translate | Google + DeepL + human editing |
| Visual editing | Limited (paid) | Full in-context editor |
| SEO structure | Subdirectory/subdomain (paid) | Subdirectory/subdomain |
| Billing approach | Lower tiers | Higher, word-based |
| Free tier | Widget-based | Trial |
| Setup complexity | Low | Low |
Bottom line: Weglot delivers better translation quality with visual editing at higher pricing; GTranslate covers more languages cheaper with the Google engine. Budget-driven multilingual sites choose GTranslate; content-quality-driven ones choose Weglot.
GTranslate vs ConveyThis
| Aspect | GTranslate | ConveyThis |
|---|---|---|
| Engine | Google Translate | AI machine translation |
| Language count | 100+ | 120+ |
| Visual editing | Limited | In-context on live site |
| Team translation access | Limited | Lower tiers |
| Database impact | None (served by service on paid) | None (cloud) |
| Free option | Widget only | Limited plan |
Bottom line: ConveyThis offers a more modern editing experience; GTranslate’s track record and pricing win on budget. Both are cloud-served approaches – the choice is editing quality versus cost at your volume.
Recommended Stack – multilingual content needs SEO plumbing: pair GTranslate with Rank Math SEO for hreflang-aware sitemaps and metadata across language versions.
Official Changelog
Version 3.1.2
Release Date: June 24, 2026
- Fixed: Deprecated warning in PHP 8 for paid version users.
- Added: aria-label accessibility attribute for flags with language code, and improved Language codes widget looks.
Version 3.1.1
Release Date: May 20, 2026
- Added: Gutenberg block support.
- Fixed: Keyboard navigation issue in language selectors.
- Improved: Paid version support for form submissions with file uploads on translated pages.
Version 3.0.10
Release Date: April 15, 2026
- New: Widget look – popup with search.
Frequently Asked Questions
Is the free version enough for SEO?
No – the free widget translates what visitors see via JavaScript, but search engines do not index it. SEO requires the paid tiers, which generate real URLs per language with hreflang attributes and translated meta tags.
How does the paid version serve translations?
Through subdirectory (example.com/es/) or subdomain (es.example.com) structures, with pages translated server-side so each language version is a real, indexable URL – not an overlay.
Can I manually correct translations?
Yes, on paid tiers – machine translations are editable, with the corrections persisting for future visitors. The visual editing layer is lighter than Weglot’s but covers the common cases.
Do forms work on translated pages?
Yes – the 3.1.1 release specifically improved paid-version support for form submissions including file uploads on translated pages, a failure point in older translation approaches.
How is this different from WPML or Polylang?
Those are manual translation-management systems – duplicated posts per language, editorial workflows, full control. GTranslate automates with machine translation. No translators on staff means GTranslate; professional multilingual content means WPML or Polylang Pro.
Leave a Reply