OZY Translate

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. 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. 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. 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. Voice-first accessibility 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. 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 lang attribute so operating-system screen readers switch pronunciation properly. What is included

• Unlimited languages and unlimited translated content.
• A built-in translator that needs no API key, no account and no billing.
• Whole-page translation, so custom themes, page builders, menus, buttons and forms are all covered.
• Works with the AI Client built into WordPress 7.0, so no API key is needed here either.
• Four URL modes: subdirectory, subdomain, query parameter, and cookie-only.
• Eight language switcher designs, including a searchable full-screen modal grid.
• Text-to-speech in 100+ languages through the browser Web Speech API.
• Accent selection for English, Spanish, French, Portuguese, Arabic, Chinese, and more.
• Translated URL slugs with three storage strategies to suit any site size.
• Hreflang tags, per-language canonicals, per-language XML sitemaps, and translated structured data.
• Native WooCommerce support: products, variations, cart, checkout, and order emails.
• Custom field support through seven adapters, including ACF, Meta Box, CMB2, and Carbon Fields.
• Glossary and do-not-translate rules so brand terms survive translation intact.
• Translation memory, approval workflow, and PO / XLIFF / CSV / JSON import and export.
• A string scanner for theme and plugin strings, with both file and runtime scanning.
• Usage insights, kept entirely in your own database, showing which pages to translate next.
• A/B testing of two wordings, with a winner declared only at 95% statistical confidence.
• Automatic right-to-left layout and CJK typography handling.
• Bulk approve, review, flag and delete, run in the background over a whole language.
• Optional visitor-submitted corrections, held for review and never published automatically.
• One-click migration from eight other translation plugins.
• Language switcher widgets for nine page builders, plus shortcodes and template functions.

Accessibility statement 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 prefers-reduced-motion. Contrast is measured programmatically on every build, and the build fails if any pairing drops below AA. Privacy 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.

1.0.4

• Fixed: switching language did not translate the page. A missing translation was only ever added to a background queue, and that queue translated one string per request to a provider the site had to configure and pay for first. A single page holds hundreds of strings, so visitors saw the source language and kept seeing it, whether or not a key had been entered.
• Changed: missing text is now translated in the visitor's browser just after the page appears, which is how a page with four hundred untranslated strings still loads instantly. The page is sent with everything already stored, the few words that are new fill in a moment later, and because every answer is stored the next visitor needs none of it. Translating before the page is sent is still offered under AI Providers for sites that want complete HTML on a page nobody has visited yet.
• Fixed: a long page was left partly translated. Translating during the render had to stop at a time limit, so everything past it stayed in the source language until the queue caught up. The browser has no such limit and finishes the page.
• Fixed: the background queue spent one request per string, which is why it never caught up on a real site. Strings for the same language now travel together, roughly twenty to a request, and a worker run clears fifty jobs rather than ten.
• Added: a "Translate the whole site" button under Content Translation, which walks every published page, post and product and queues all of it for every language. Nothing requires it, since pages translate themselves when viewed, but it means no visitor has to be the first.
• Changed: the Content Translation screen now says what its percentages mean and that most sites need nothing from it. A page nobody has viewed in a language reads "Not yet" rather than a bare zero.
• Added: a built-in translator that needs no API key and no account. Translation now works as soon as a second language is added. A provider of your own is still used when you add one, and the AI Providers screen chooses which of the two leads.
• Fixed: only post content was ever translated. A custom theme's own markup, a page builder's header and footer, template parts, menus, buttons, form labels and meta descriptions do not travel through any filter a plugin can hook, so they stayed in the source language on every theme and every builder. The finished page is now translated on its way to the browser, which reaches all of it. The language switcher's own list of languages is left alone, as are scripts, styles, preformatted text and anything marked do not translate.
• Fixed: a hidden field's value and a meta tag's content were sent out for translation. Nonces, tokens and viewport declarations are not prose, and translating them wasted provider usage. Only button labels and the handful of meta tags that carry prose are translated now.
• Fixed: a page carrying a large HTML comment, which builders and caching layers both produce, could not be parsed and so was not translated at all.
• Fixed: a translation service that was unreachable cost nineteen failed requests for four strings, with a visitor waiting on each one. A service that cannot be reached is now dropped for the rest of the request and paused for five minutes.

1.0.3

• Fixed: the default language could not be selected again. Once a visitor chose another language the choice was stored in a cookie, and because the default language's address carries no language marker, the cookie overrode it on every later request. Clicking English gave Spanish back, for good. Where the address can carry the language, the address now decides; a stored preference only settles it in cookie-only mode, where there is nothing else to go on.
• Fixed: a provider that refused a request failed silently. The reason was recorded and never shown, so a rejected API key looked identical to the plugin doing nothing. The dashboard now prints the last failure, and says so when the queue has work but has never finished any.
• Fixed: translations produced before 1.0.2 stayed hidden after updating. They were filed as awaiting review by the storage rule 1.0.2 corrected, and fixing that rule only changed new work. Sites that never switched the approval workflow on now have those translations published on update, so pages that were translated already start showing without translating anything again.

1.0.2

• Fixed: Elementor's text widgets were translated through WordPress's widget_text filter, at a point before WordPress had finished processing the text. The same sentence was stored two or three times in encodings that never matched what the visitor saw, and translating it again later doubled it.
• Fixed: every piece of text containing an HTML entity, a URL, an email address, a shortcode or a printf token was queued twice, once with the plugin's own protection placeholders still in it. Providers were being asked to translate placeholder text such as "didnOZYX0Zt", and the result was stored beside the real translation.
• Fixed: pages built with Elementor, Divi, Beaver Builder or Brizy were never translated. Those builders discard post_content and render their own stored layout, and the translation pass ran before them, so it translated something the visitor never sees. The language and the address changed and the page stayed in English. Builder-rendered pages are now translated after the builder has run, and Elementor headers, footers, popups and template parts are translated too.
• Fixed: changing URL mode left the previous mode's language argument on every link built afterwards, producing addresses such as /es-es/?lang=es-es.
• Fixed: the whole administration area switched language and flipped right to left once a right-to-left language such as Urdu or Arabic was added, because the visitor's language was being applied to wp-admin as well. Administration screens now always use the site's own language.
• Fixed: removing a language left the confirmation screen on screen afterwards, reporting the language it had just removed as not configured.
• Added: languages can be removed several at a time. Tick the ones you want, press Remove selected, and choose one redirect strategy for all of them.
• Fixed: AI translations were stored as awaiting review and never shown, on sites that had not switched the approval workflow on. A single diagnostic note from the optional review pass was enough to hold a perfectly good translation back, so pages kept appearing in the source language however many were translated.
• Fixed: the WordPress AI Client was reported as connected on WordPress 7.0 and later even when no connector offered text generation, so the plugin claimed it was ready to translate and then failed on every request.
• Fixed: the dashboard's "place a language switcher" step linked to a screen that does not exist, and counted itself as done whenever any design was selected, which it always is.
• Changed: new installs place a floating switcher and switch automatic translation on, so adding a language is enough to see the plugin working. Nothing is sent anywhere until a provider is connected, and both settings can be turned off.
• Changed: existing sites that never altered these settings are moved to the new defaults on update.

1.0.1

• Fixed: a switcher placed with the shortcode, the widget or a template tag, and left on the site's own design, did not load the script it needs. A modal grid, sliding panel, floating button or mega menu placed that way had nothing to open it.

1.0.0

• Initial release.