About this plugin
Transer 多言語ページ翻訳 connects your WordPress site to the transer.io server-side translation API. The engine is built around sites whose original content is written in Japanese, and sites in other languages are supported as well. Why a Japanese-first engine matters General-purpose translation tools treat Japanese as one language among many. Japanese source text has structural habits that break those tools, and the engine behind this plugin is built around them: Japanese-era dates : Reiwa, Heisei and Showa dates are resolved to the correct Gregorian year rather than being transliterated or dropped. Kana-heavy sentences : Text written largely in hiragana is ambiguous to morphological analysis. The engine disambiguates word boundaries instead of guessing at them. Decorative markup : Japanese sites often split words across <span> tags for styling. The engine reads through that markup so a single word is not translated as several fragments. The full HTML of the page is sent as-is, so context is preserved across the whole document rather than being lost sentence by sentence. The translated page is then rendered server-side, and multilingual SEO tags such as hreflang and canonical are generated automatically. Sites written in other languages are supported too: 16 recommended languages, including English, Chinese and Korean, can be set as the source language, and every editing feature works the same way regardless of which one you choose. The Japanese-specific handling described above applies only when the source is Japanese. Editing after translation Machine translation always leaves something you want to change. With this plugin, you fix it on the translated page itself. There is no admin screen to open and no page to hunt for: click the wording that looks wrong, and that is what you edit. Direct editing : Click any text to open a panel showing the Japanese source above and the translation below. Rewrite the translation and save. Clearing the field restores the AI translation on the next load. Glossary : Register a term once and that wording is used from then on. Manually registered terms always take priority over the AI’s choice. Do not translate : Mark headings, taglines or legal wording that should stay in the original Japanese, whichever language the page is viewed in. Image replacement : Swap banners and other images that have text baked into them for a different image per language. Free accounts include up to 100 direct edits and 50 glossary terms. “Do not translate” and the language-switcher styling have no limit. Image replacement is available on paid plans. Key features Server-side translation : The page is translated before it reaches the browser, so search engines and visitors receive the same finished HTML. Automatic multilingual SEO tags : canonical and hreflang tags are inserted automatically for every contracted language. Automatic language-switcher UI : No shortcode placement required. The language switcher is automatically shown on both the original and translated pages. Translated site search : When a visitor searches in their own language, the keyword is translated into your site’s original language before the search runs, so Japanese content is actually found. Nothing to configure. Multilingual sitemap : Visiting /transer-sitemap.xml dynamically generates a sitemap with per-language hreflang annotations. Editing on the translated page : Rewrite wording, register glossary terms and exclude text from translation without leaving the page. See above for details. No server configuration required : No .htaccess rewriting or web-server rewrite rules are needed. The plugin detects language-prefixed URLs (e.g. /en/about ) during WordPress’s init hook. A transer.io account and API key are required Using this plugin requires a free account and API key from transer.io . The first language is free of charge. External services This plugin connects to transer.io, a third-party server-side translation API operated by Hippotech USA Inc. (the same company that develops this plugin), in order to translate your page content into the languages you configure. What is sent, and when : When a visitor requests a page in a language other than your site’s original language, the plugin captures the full HTML output of that page (via an output buffer) and sends it, together with the requesting hostname, URL path, source language code, and your configured list of contracted languages, to the transer.io translation endpoint ( {configured base_url, default https://api.transer.io}/translate-page ). No request is sent when a page is viewed in the original language. Retrieving your contracted languages : When you save the plugin settings, the plugin sends your hostname and API key to {configured base_url}/contract-langs to retrieve the list of languages contracted on your transer.io account. This request is made only from the settings screen, never from a visitor’s page view. Translating search keywords : When a visitor performs a site search on a translated page, the plugin sends the entered keyword, your hostname, and the language codes to {configured base_url}/search-translate so the keyword can be translated into your site’s original language before the search runs. Only the keyword itself is sent. Authentication : Requests are authenticated using an API key that you obtain yourself from your transer.io account and enter on the plugin’s settings screen. No API key is hard-coded in the plugin. On request failure : If the request to transer.io fails for any reason, the plugin falls back to displaying the original, untranslated page; it never blocks page rendering. Data disclosure : The HTML sent to transer.io reflects the page as rendered by WordPress; it does not include values a visitor may have entered into forms on the page. Terms of Service: https://www.transer.io/terms.html Privacy Policy: https://www.transer.io/privacy.html