Source evidence

translating blog with multiple languages

Automatic Translator with Google Translate · support · 2026-06-09T22:19:00+00:00

Automatic Translator with Google Translate plugin evidence original source source API

complaintsentiment

mediumseverity

0.81relevance

1replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

corelan unresolved

hi, the main language on my blog is English. some of the posts are in French. (but the content is still recognized as english, so I’m not able to let users choose to translate to english) how can I solve this? Hi, What you’re seeing is normal with the current free version. Automatic Translator works with one original/source language for the page. So if your site language is English, choosing English restores the original page instead of translating the current post into English. That means if some posts are written directly in French on an English site, the plugin can still treat those pages as English-first, so English is not available as a translation target for those posts. Right now, the free version works best when the site content has one consistent source language. On mixed-language sites, this kind of behavior can happen. For now, the best workaround is to keep each post in the site’s main language, or create a separate English version for posts that were originally written in French. We’re also working on a more advanced multilingual setup for a future premium version, which will handle cases like this much better.

Commercial Context

Opportunity

localization content operations

Translate localization QA for keeping translated content, language routing, and localized site operations complete

Buyer: multilingual site owners, agencies, and localization teams

Wedge: detect translate translation gaps, broken language routes, and localized metadata drift

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: translating blog with multiple languages: users show pricing, migration, setup pain that may indicate a product gap.

Evidence quote: Hi, What you’re seeing is normal with the current free version.

Affected feature: restore

pricing migration setup reliable

Plugin

API

Automatic Translator with Google Translate

2.0K active installs · 51.3K downloads · rating 86.0

google translate language switcher translate translation website translator

Comments

1 shown

Pampa Dev 2026-06-10T08:21:00+00:00

Hi, What you’re seeing is normal with the current free version. Automatic Translator works with one original/source language for the page. So if your site language is English, choosing English restores the original page instead of translating the current post into English. That means if some posts are written directly in French on an English site, the plugin can still treat those pages as English-first, so English is not available as a translation target for those posts. Right now, the free version works best when the site content has one consistent source language. On mixed-language sites, this kind of behavior can happen. For now, the best workaround is to keep each post in the site’s main language, or create a separate English version for posts that were originally written in French. We’re also working on a more advanced multilingual setup for a future premium version, which will handle cases like this much better.