Fixes the plugin not translating. The whole finished page is now translated, so custom themes and page builders are covered; missing text is translated in the visitor's browser instead of only being queued, so no page is slowed down and none is left half done; the background queue no longer spends a request per string; and a built-in translator means no API key is needed at all. Update if switching language left the page in the source language, or made it slow.<\/p>","1.0.3":"
Fixes the default language being impossible to select again, shows why a provider refused a request, and releases translations that were produced earlier but held back from visitors. Update if any page stayed in the source language after translating it.<\/p>","1.0.2":"
Fixes page builder content never being translated, the admin area switching to a right-to-left language, and AI translations being held back from visitors on sites with no approval workflow, and a false report that the WordPress AI Client was connected.<\/p>","1.0.1":"
Fixes a language switcher that would not open when placed by shortcode, widget or template tag.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3704121,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3704121,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3704121,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3704121,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1","1.0.3","1.0.4"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3704163,"resolution":"1","location":"assets","locale":"","width":1440,"height":1450},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3704163,"resolution":"2","location":"assets","locale":"","width":1440,"height":1124},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3704163,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3704163,"resolution":"4","location":"assets","locale":"","width":1440,"height":1200},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3704163,"resolution":"5","location":"assets","locale":"","width":1440,"height":977},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3704163,"resolution":"6","location":"assets","locale":"","width":1440,"height":577},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3704163,"resolution":"7","location":"assets","locale":"","width":1440,"height":1330}},"screenshots":{"1":"Add a language and the slug, direction and flag are set for you. Four ways to carry the language in the address, each with a worked example and its search engine trade-off stated plainly","2":"Eight switcher designs, previewed live with your own languages and settings. All keyboard operable and screen-reader labelled","3":"The full screen switcher on the front end, with a search box for sites that offer more than a handful of languages","4":"The SEO screen states what is set up and what still needs attention, and works alongside the SEO plugin you already run","5":"Insights stay in your own database and tell you which pages to translate next","6":"Pin your brand names so a machine never translates them into something else, or force one agreed wording per language","7":"Detection is checked in a stated order, and every option says plainly what it does and why it is on or off by default"}},"plugin_section":[],"plugin_tags":[220668,22323,99,95,2333],"plugin_category":[48],"plugin_contributors":[269519],"plugin_business_model":[],"class_list":["post-365833","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-translation","plugin_tags-language-switcher","plugin_tags-multilingual","plugin_tags-translate","plugin_tags-translation","plugin_category-language-tools","plugin_contributors-idanishrangaiz","plugin_committers-idanishrangaiz"],"banners":{"banner":"https:\/\/ps.w.org\/ozy-translate\/assets\/banner-772x250.png?rev=3704121","banner_2x":"https:\/\/ps.w.org\/ozy-translate\/assets\/banner-1544x500.png?rev=3704121","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/ozy-translate\/assets\/icon-128x128.png?rev=3704121","icon_2x":"https:\/\/ps.w.org\/ozy-translate\/assets\/icon-256x256.png?rev=3704121","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-1.png?rev=3704163","caption":"Add a language and the slug, direction and flag are set for you. Four ways to carry the language in the address, each with a worked example and its search engine trade-off stated plainly"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-2.png?rev=3704163","caption":"Eight switcher designs, previewed live with your own languages and settings. All keyboard operable and screen-reader labelled"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-3.png?rev=3704163","caption":"The full screen switcher on the front end, with a search box for sites that offer more than a handful of languages"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-4.png?rev=3704163","caption":"The SEO screen states what is set up and what still needs attention, and works alongside the SEO plugin you already run"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-5.png?rev=3704163","caption":"Insights stay in your own database and tell you which pages to translate next"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-6.png?rev=3704163","caption":"Pin your brand names so a machine never translates them into something else, or force one agreed wording per language"},{"src":"https:\/\/ps.w.org\/ozy-translate\/assets\/screenshot-7.png?rev=3704163","caption":"Detection is checked in a stated order, and every option says plainly what it does and why it is on or off by default"}],"raw_content":"\n
OZY Translate makes a WordPress site multilingual without metered word counts, per-language upsells, or a monthly subscription. Everything the plugin can do is available to everyone, for free.<\/p>\n\n
Nothing has to be configured for it to translate. A built-in translator that needs no API key and no account handles the site from the moment you add a second language, and a visitor who picks a language sees that page translated straight away rather than waiting for a queue to catch up.<\/p>\n\n
Pages are not slowed down to do it. The page is sent at full speed with every translation the site has stored, and anything new is translated in the visitor's browser a moment after the page appears, then kept, so the next visitor gets it from storage.<\/p>\n\n
When you want the better phrasing a language model gives, bring your own key from a provider you already trust, several of which have generous free tiers. On WordPress 7.0 and later the plugin can also use the AI Client built into WordPress, so whichever provider you have connected under Settings, Connectors just works and this plugin never handles a key. The AI Providers screen decides which translator leads. You can also turn automatic translation off entirely and write every translation by hand through the built-in editors.<\/p>\n\n
Every translated page can be read aloud in the active language using the browser's built-in speech synthesis. No external service, no API key, no per-character cost. Visitors get play, pause, speed, pitch, voice, and accent controls, plus word-level highlighting as the page is read.<\/p>\n\n
This is paired with a wider accessibility toolkit: font size controls, high contrast mode, a dyslexia-friendly font, reduced motion enforcement, skip links, ARIA landmarks, and a correctly maintained OZY Translate targets WCAG 2.1 level AA for everything it renders, and reaches level AAA for contrast in most places. All switcher designs are keyboard operable, expose correct ARIA roles, trap focus in modal contexts, return focus to the trigger on close, announce language changes through a live region, and respect OZY Translate does not phone home, does not include analytics beacons, and does not transmit any data to OZY Solutions. Usage statistics, when enabled, are stored only in your own database. No external service is contacted unless you explicitly configure and enable it.<\/p>\n\n Every request below is made from your server to the named provider. Your visitors are never sent to a third party, and no data is ever sent to OZY Solutions.<\/p>\n\n One service is used without you configuring anything: the built-in translator, described first below. Your visitors' browsers talk only to your own site, never to a translation service: the browser asks your site for the missing translations, and your server contacts the service. It is what lets the plugin translate with no API key, and it is contacted only when you have added a second language, automatic translation is on, and a page is viewed in that language with text that has not been translated yet. It sends the text being translated and nothing else. It can be switched off under AI Providers, and with it off nothing is sent anywhere until you configure a provider of your own.<\/p>\n\n Every other service here is contacted only after you have switched on the feature that uses it and entered your own credentials for it, and only at the moment that feature runs.<\/p>\n\n The built-in translator is used unless you switch it off. The rest you need at most one of, and only if you want a language model to do the translating instead. Manual translation, imports, the string scanner and browser text-to-speech work with none of them.<\/p>\n\n Built-in translator: Google Translate public endpoint<\/strong><\/p>\n\n Built-in translator: MyMemory<\/strong><\/p>\n\n Built-in translator: LibreTranslate<\/strong><\/p>\n\n OpenAI<\/strong><\/p>\n\n Anthropic<\/strong><\/p>\n\n Groq<\/strong><\/p>\n\n Google Gemini<\/strong><\/p>\n\n Mistral AI<\/strong><\/p>\n\n DeepL<\/strong><\/p>\n\n Google Cloud Translation<\/strong><\/p>\n\n Microsoft Translator<\/strong><\/p>\n\n On WordPress 7.0 and later the plugin can use the AI Client built into WordPress instead of any of the above. In that case this plugin makes no request of its own and holds no key: WordPress contacts whichever provider you connected under Settings, Connectors, under that provider's own terms.<\/p>\n\n The listen feature uses the visitor's own browser by default, through the Web Speech API. That is entirely local: no request leaves the site and none of the services below is used. They are alternatives you can switch to, and each returns audio that is then cached in your own uploads directory.<\/p>\n\n ElevenLabs<\/strong><\/p>\n\n Microsoft Azure Speech<\/strong><\/p>\n\n Google Cloud Text-to-Speech<\/strong><\/p>\n\n Amazon Polly<\/strong><\/p>\n\n ExchangeRate-API<\/strong><\/p>\n\n Weglot<\/strong><\/p>\n\n Every other migration importer (WPML, Polylang, TranslatePress, GTranslate, Loco Translate, qTranslate and MultilingualPress) reads your own database directly and contacts nothing.<\/p>\n\n Country detection reads a header your CDN or proxy already sends, such as the CF-IPCountry header from Cloudflare. No lookup service is contacted and no visitor IP address is sent anywhere. Where no such header is present, country detection simply does nothing.<\/p>\n\n If none of the services above is configured, this plugin operates entirely on your own server and contacts nothing.<\/p>\n\n\n No. Every feature is free. If you enable AI translation you pay your chosen AI provider directly for the tokens you use, which on free-tier providers is typically nothing.<\/p><\/dd>\n No. The built-in translator needs no key and no account, and it is on by default, so adding a second language is enough to see the site translated. Entering a key buys you the better phrasing a language model gives, not the ability to translate at all. On WordPress 7.0 and later, if you have already connected an AI provider under Settings, Connectors, the plugin can use the AI Client built into WordPress instead, in which case WordPress keeps the credentials and this plugin never sees a key.<\/p><\/dd>\n No. A page is sent with every translation the site already has, which is a database read, and anything that has no translation yet is translated in the visitor's browser just after the page has appeared. Nothing is held back waiting for a translation service. If you would rather the HTML left the server complete, which search engines prefer on a page nobody has visited yet, choose \"Before the page is sent\" under AI Providers; the first visitor to each page then waits while it happens.<\/p><\/dd>\n No. A page translates itself the first time somebody views it in another language, and the result is stored for everyone after that, so adding a language is all that is required. If you would rather not wait for a first visitor, Content Translation has a \"Translate the whole site\" button that queues everything.<\/p><\/dd>\n Whichever you choose, under AI Providers. By default the built-in translator leads, so nothing is spent until it cannot manage a string. Turn off \"Try the built-in translator before my own providers\" and your own provider translates everything, with the built-in one kept as the safety net behind it.<\/p><\/dd>\n Yes, and it translates without one: the built-in translator handles the site with no key of your own. Manual translation, imports, the string scanner, the visual editor, all switcher designs, and browser-based text-to-speech work with no external service at all.<\/p><\/dd>\n No. Translations are stored in dedicated tables keyed by a hash of the source text. Your original content is never modified.<\/p><\/dd>\n Subdirectory ( Yes. The plugin ships integrations for WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, and WP Fastest Cache, and sets correct lang<\/code> attribute so operating-system screen readers switch pronunciation properly.<\/p>\n\nWhat is included<\/h4>\n\n
\n
Accessibility statement<\/h4>\n\n
prefers-reduced-motion<\/code>. Contrast is measured programmatically on every build, and the build fails if any pairing drops below AA.<\/p>\n\nPrivacy<\/h4>\n\n
External services<\/h3>\n\n
Translation providers<\/h4>\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Spoken audio<\/h4>\n\n
\n
\n
\n
\n
WooCommerce multi-currency<\/h4>\n\n
\n
Migrating away from another plugin<\/h4>\n\n
\n
Country detection<\/h4>\n\n
\n
ozy-translate<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin through the Plugins screen.<\/li>\n\n
Does this cost anything?<\/h3><\/dt>\n
Do I have to enter an API key?<\/h3><\/dt>\n
Does translating slow my pages down?<\/h3><\/dt>\n
Do I have to translate each page by hand?<\/h3><\/dt>\n
Which translator is used if I add a key as well?<\/h3><\/dt>\n
Does it work without an AI provider?<\/h3><\/dt>\n
Will it duplicate my posts?<\/h3><\/dt>\n
Which URL mode should I choose?<\/h3><\/dt>\n
\/es\/page\/<\/code>) is recommended and gives the best search engine results. Cookie-only mode changes no URLs at all, which is convenient but means search engines only ever see your default language.<\/p><\/dd>\nIs it compatible with caching plugins?<\/h3><\/dt>\n
Vary<\/code> headers for CDN edge caching.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n