FluentC vs TranslatePress.
TranslatePress adds pages, posts, files and menus as you add languages, and its navigation needs manual setup. The FluentC WordPress plugin is listed as adding none of these, and it charges by number of languages instead of a licence plus translation costs. Both support hreflang; with TranslatePress you set it up manually.
FluentC and TranslatePress
| Feature | FluentC | TranslatePress |
|---|---|---|
| How content is priced | Fixed price per site, by number of languages | Fixed licence plus translation cost |
| Annual cost | See the pricing page | From €169, plus translation cost |
| Translation limits | Unlimited | Limited |
| Languages | 128+ languages | 130+ |
| hreflang support | Yes | Yes, set up manually |
| Custom fields translation | Automatic | Manual |
| Taxonomy translation | Automatic | Manual |
| WooCommerce support | Yes | Yes, with a premium upgrade |
| US-based support | Yes | No |
| Increases plugin size | No | Yes |
| Increases language files for all plugins | No | Yes |
| Increases page count | No | Yes |
| Increases post count | No | Yes |
| Increases WordPress file size | No | Yes |
| Manual navigation setup | No | Yes |
| Navigation multiplied for each language | No | Yes |
Compared as of June 14, 2024. TranslatePress details come from its public information and may have changed; check its own site for current plans and features.
This comparison is for WordPress. The table covers the FluentC WordPress plugin and TranslatePress.
Pages, posts and menus per language
The difference is mostly in what happens to your site each time you add a language. The table lists TranslatePress as increasing your page count, post count, plugin size, language files and WordPress file size, and as multiplying navigation for each language, with manual navigation setup. FluentC is listed as doing none of these.
That adds up to management time: with several languages you end up maintaining more pages and menus every time content changes.
Custom fields, taxonomies and hreflang
FluentC translates custom fields and taxonomies automatically. With TranslatePress both are manual. hreflang is supported by both, set up manually in TranslatePress.
WooCommerce and support
WooCommerce support is included in FluentC. For TranslatePress it needs a premium upgrade. The table also lists FluentC support as US-based and TranslatePress support as not.
Cost
TranslatePress is a fixed licence plus translation cost. FluentC prices per site, by number of languages, with unlimited translations; see pricing.
Note: Competitor prices were current when this comparison was written and are for reference only. Check TranslatePress for its current pricing.
Switching
Two articles cover the move in more detail: Moving from TranslatePress to FluentC and Five performance differences between TranslatePress and FluentC.
If your site is not on WordPress, FluentC Domains translates it on a subdomain or country domain without touching the origin site.
More on FluentC and TranslatePress
Five performance differences between TranslatePress and FluentC
Code weight, caching, database storage, caching-plugin compatibility and support, five areas that affect how fast a translated WordPress site loads.
Moving from TranslatePress to FluentC on WordPress
What one review of TranslatePress reports about translation quality and support, and what the FluentC WordPress plugin offers instead.
Start with one language.
Flat price per site, per language. Unlimited translations.