COCOS Translate makes your site bilingual without touching your theme or your content structure: it translates your site from its default language into one translation language of your choice. You can change the translation language at any time.<\/p>\n\n
Core features:<\/p>\n\n
gettext<\/code> translation.<\/strong> Theme and plugin strings that pass through __()<\/code> \/ _e()<\/code> are translatable too.<\/li>\n- Machine translation.<\/strong> Google Cloud Translation v2 with your own API key. Translate on demand from the editor, in bulk from the admin, or automatically in the background via WP-Cron. (Other engines are available in COCOS Translate PRO, a separate plugin.)<\/li>\n
- SEO-friendly URLs.<\/strong> The translated pages live under their own path prefix (e.g.
\/fr\/<\/code>). hreflang<\/code> alternate links, x-default<\/code>, translated <html lang><\/code> \/ dir<\/code> and localized permalinks are handled for you.<\/li>\n- Language switcher.<\/strong> Shortcode
[cc_transla_switcher]<\/code>, a widget, a cc_transla_language_switcher()<\/code> template tag, an optional floating switcher and optional nav-menu injection.<\/li>\n- Built-in page cache<\/strong> for anonymous visitors so translated pages are served without re-parsing.<\/li>\n<\/ul>\n\n
External services<\/h3>\n\n
This plugin can send text to an external machine-translation service. It does so only if you choose \"Google Translate\" as the machine-translation engine and enter your own API key under Settings \u2192 COCOS Translate \u2192 Machine translation<\/strong>. With the engine set to \"None\" (the default), the plugin makes no external requests.<\/p>\n\nGoogle Cloud Translation API (v2)<\/strong><\/p>\n\n\n- What it is \/ what it is used for: Google's machine-translation service, used to translate the strings of your site (page text, menu items, widget text and similar) into your translation language.<\/li>\n
- What data is sent and when: the text strings to be translated, the source and target language codes, and your Google API key. This happens when you click the machine-translate button in the visual editor, run a bulk \"Auto-translate\" from the admin, or when automatic background translation (WP-Cron) or translate-on-access is enabled. No visitor personal data is sent \u2014 only the site strings that are missing a translation.<\/li>\n
- Service provider: Google LLC. Terms of Service<\/a> \u00b7 Privacy Policy<\/a> \u00b7 Cloud Privacy Notice<\/a><\/li>\n<\/ul>\n\n
Links to translate.cocos.codes in this readme and in the plugin's admin screens are ordinary hyperlinks; the plugin does not contact that site in the background.<\/p>\n\n
Notes \/ limitations<\/h3>\n\n\n- URL translation uses the sub-directory method (
example.com\/fr\/\u2026<\/code>). Sub-domains and separate domains are not supported.<\/li>\n- On sites with a full-page caching layer in front of PHP, exclude the
?cc-transla-edit<\/code> requests from that cache.<\/li>\n- Very large string tables load into memory per request; let the built-in page cache do its job.<\/li>\n<\/ul>\n\n
COCOS Translate PRO<\/h3>\n\n
This plugin translates your site into one language, with Google Translate on your\nown API key. COCOS Translate PRO<\/strong> (https:\/\/translate.cocos.codes) is a separate\npaid plugin for sites in several languages. It offers:<\/p>\n\n\n- Several translation languages per site.<\/strong><\/li>\n
- One-click AI translation<\/strong> through the COCOS Translate proxy \u2014 Google, DeepL,\nOpenAI, Claude and Gemini with no provider API keys<\/strong> to manage.<\/li>\n
- A monthly AI phrase quota<\/strong> with optional top-up packs.<\/li>\n
- Priority support<\/strong> and automatic updates from translate.cocos.codes.<\/li>\n<\/ul>\n\n
PRO is optional and is distributed from translate.cocos.codes, not from WordPress.org.<\/p>\n\n\n
\n- Upload the
cocos-translate<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- Activate the plugin.<\/li>\n
- Go to Settings \u2192 COCOS Translate<\/strong>, pick your default language and the language to translate your site into.<\/li>\n
- Visit the front end, open the admin-bar Translate Page<\/strong> menu and start translating, or configure a machine-translation engine and run Auto-translate<\/strong> from the admin.<\/li>\n<\/ol>\n\n\n
1.0.5<\/h4>\n\n\n- The plugin now translates your site into one translation language of your choice (Settings \u2192 COCOS Translate \u2192 Languages), changeable at any time.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Maintenance release.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Fix: language-prefixed URLs (e.g. \/it\/, \/de\/) returning a 404 on sub-directory installs \u2014 the language segment is now stripped without WordPress losing the site's own sub-directory.<\/li>\n
- Fix: cached translated pages could be answered with a 502 by some proxies\/CDNs because of an invalid HTTP header name on cache hits.<\/li>\n
- Fix: a stray XML declaration could appear in the served HTML of translated pages.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Compliance: documented the Google Cloud Translation external service (data sent, Terms of Service and Privacy Policy links) in this readme.<\/li>\n
- Fix: the live-translation collector now answers a failed nonce check with an error response instead of a success message.<\/li>\n
- Security: the text sent to the machine-translation engine from the visual editor is now sanitised on the server.<\/li>\n
- The platform moved to a new domain \u2014 plugin URI, update-check host, and every in-admin link (pricing, features, account, changelog) now point at translate.cocos.codes.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Fix: WooCommerce Cart\/Checkout AJAX requests breaking on non-default-language pages.<\/li>\n
- Fix: a self-referential translation loop and corrupted HTML entities that could appear in some translated pages.<\/li>\n
- Fix: the visual editor no longer hides text that was already translated via
gettext<\/code>.<\/li>\n- Fix: the WordPress core admin bar is no longer picked up as translatable content.<\/li>\n
- Improvement: rows in the languages table can now be reordered by drag-and-drop (the order also sets the language-switcher order).<\/li>\n
- Improvement: clearer, more visible outline around translatable text in the front-end editor.<\/li>\n
- Various translation-harvesting fixes and WordPress.org plugin-check compliance fixes (escaping, sanitization).<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First public release of COCOS Translate.<\/li>\n
- Whole-page translation of the rendered HTML - visible text plus alt \/ title \/ placeholder \/ aria-label and SEO meta (description, keywords, Open Graph, Twitter).<\/li>\n
- Live translation of content injected after page load (WooCommerce Cart\/Checkout blocks, Gutenberg-hydrated blocks, AJAX fragments) via a MutationObserver layer that also reports unknown strings.<\/li>\n
- Visual front-end editor: hover translatable text, click the pencil, edit the translation, save.<\/li>\n
gettext<\/code> translation for theme and plugin strings.<\/li>\n- Machine translation with Google Cloud Translation v2 (your own API key) - on demand from the editor, in bulk, or automatically via WP-Cron.<\/li>\n
- SEO-friendly per-language URLs (
\/fr\/<\/code>, \/de\/<\/code> ...), hreflang<\/code> alternates, x-default<\/code>, translated <html lang><\/code> \/ dir<\/code> and localized permalinks.<\/li>\n- Language switcher: shortcode
[cc_transla_switcher]<\/code>, widget, template tag, an optional floating switcher and nav-menu injection - with bundled SVG country flags.<\/li>\n- Built-in page cache for anonymous visitors.<\/li>\n
- Glossary with \"keep as-is\" terms; numbers handled as variables so \"83 products\" \/ \"90 products\" translate once.<\/li>\n
- Advanced tab with a \"Danger zone\" (delete all translations \/ reset settings).<\/li>\n<\/ul>","raw_excerpt":"Translate your whole WordPress site from the front end \u2014 machine translation, SEO-friendly language URLs and a switcher.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/370016","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=370016"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mstron"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=370016"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=370016"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=370016"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=370016"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=370016"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=370016"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}