If you set the plugin up on its settings screen and no translated pages appeared, this makes them appear. Your settings are kept.<\/p>","2.2.1":"
Fixes a fatal error on the settings screen for sites that took the first 2.2.0 build. Nothing else changes and your settings are kept.<\/p>","2.2.0":"
Shares the right OpenGraph title and description to Facebook, LinkedIn and X, shows variation descriptions and custom attribute values in the visitor's language, and translates WooCommerce products by default on new sites. Your settings are unchanged.<\/p>","2.0.0":"
Adds translated slugs, metadata, menus and WooCommerce, a language switcher, manual overrides, per-language sitemaps, and the option to translate with your own provider key instead of a Zinn Digital\u00ae plan. Your existing settings are carried over.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3731264,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3731264,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3731264,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3731264,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3731264,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"zinn\/language-switcher":{"name":"zinn\/language-switcher","title":"Language switcher"}},"tagged_versions":["2.4.7"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3731264,"resolution":"1","location":"assets","locale":"","width":1100,"height":1000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3731264,"resolution":"2","location":"assets","locale":"","width":900,"height":404},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3731264,"resolution":"3","location":"assets","locale":"","width":1100,"height":1000},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3731264,"resolution":"4","location":"assets","locale":"","width":1100,"height":526}},"screenshots":{"1":"Choosing who pays and which languages to publish.","2":"The language switcher, in six styles.","3":"The manual-override screen.","4":"Per-language sitemaps and Zinn\u00ae Translate turns a WordPress site into a genuinely multilingual one. Each language gets its own web addresses \u2014 It translates what a visitor actually reads, which is more than a page's body text: titles, bodies and excerpts, URL slugs, SEO titles and descriptions, OpenGraph tags, image alt text, categories and tags, navigation menus, your site title and tagline, and \u2014 on a shop \u2014 product names, descriptions, short descriptions, purchase notes, attribute labels and variation descriptions.<\/p>\n\n Two things run, and it is worth knowing which is which.<\/p>\n\n The plugin<\/strong> runs on your site. It lists every translatable string, stores the finished translations in one table on your own server, and swaps the words in while a page renders. It also tells WordPress which language the page is in, so your theme's and WooCommerce's own buttons \u2014 \"Add to cart\", \"Read more\" \u2014 come out in that language too, from the language packs WordPress already publishes.<\/p>\n\n The translation itself<\/strong> is bought from a provider, and you choose which:<\/p>\n\n There is no free translation tier. Machine translation costs money per word, and somebody pays a provider for every one of them \u2014 either through your Zinn Digital\u00ae plan or on your own key.<\/p>\n\n Every translation can be edited by hand, and an edited translation is never overwritten. Re-translating the page leaves your wording exactly as you typed it.<\/p>\n\n A shortcode ( Product names, descriptions, short descriptions, purchase notes, attribute labels, attribute values and variation descriptions. Prices, SKUs and the stored option values that identify a variation are never touched \u2014 translating those would put the wrong item in a basket.<\/p>\n\n This plugin sends the text of your site to a translation provider that you choose and configure<\/strong>. It makes no outbound request at all until you have chosen one and saved a credential for it.<\/p>\n\n What is sent, and when<\/strong><\/p>\n\n No visitor data, analytics, personal data or order data is transmitted.<\/strong> What is sent is the published content of your site, which is already public, plus the credential you saved for the provider you chose.<\/p>\n\n One database table, Uninstalling the plugin drops that table and deletes those settings. Deactivating does not \u2014 so switching the plugin off to test something never destroys translations you have paid for.<\/p>\n\n\n Translation runs in the background. Publishing or updating a page marks its translations out of date and they are remade automatically; editing a page without changing any words costs nothing.<\/p>\n\n\n No. There is no second copy of anything. A translated page is your own page with the words swapped in as it renders, so your content, your permalinks and your editor are untouched.<\/p><\/dd>\n Nothing on your site changes. Translations are already stored on your own server, so pages keep serving in every language. New or edited content is translated on the next background pass.<\/p><\/dd>\n Yes, on the Manual overrides<\/strong> tab. An edited translation is marked as yours and is never overwritten by a later re-translation.<\/p><\/dd>\n They keep working. The untranslated address redirects permanently to the translated one, and if a re-translation ever changes a slug the previous address redirects too.<\/p><\/dd>\n No. It detects Yoast SEO, Rank Math, All in One SEO and SEOPress and translates what they emit through their own filters, rather than printing a second title, description or canonical of its own.<\/p><\/dd>\n No. With your own Google Gemini, DeepL or OpenAI key the plugin works on its own and the provider bills you. A Zinn Digital\u00ae plan is the alternative, not a requirement.<\/p><\/dd>\n\n<\/dl>\n\n\nllms.txt<\/code> addresses, with links to check them."}},"plugin_section":[262246],"plugin_tags":[2993,99,186,2333,286],"plugin_category":[45,48,55],"plugin_contributors":[280285],"plugin_business_model":[],"class_list":["post-377297","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-hreflang","plugin_tags-multilingual","plugin_tags-seo","plugin_tags-translation","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-language-tools","plugin_category-seo-and-marketing","plugin_contributors-zinndigital","plugin_committers-zinndigital"],"banners":{"banner":"https:\/\/ps.w.org\/zinn-translate\/assets\/banner-772x250.png?rev=3731264","banner_2x":"https:\/\/ps.w.org\/zinn-translate\/assets\/banner-1544x500.png?rev=3731264","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/zinn-translate\/assets\/icon.svg?rev=3731264","icon":"https:\/\/ps.w.org\/zinn-translate\/assets\/icon.svg?rev=3731264","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/zinn-translate\/assets\/screenshot-1.png?rev=3731264","caption":"Choosing who pays and which languages to publish."},{"src":"https:\/\/ps.w.org\/zinn-translate\/assets\/screenshot-2.png?rev=3731264","caption":"The language switcher, in six styles."},{"src":"https:\/\/ps.w.org\/zinn-translate\/assets\/screenshot-3.png?rev=3731264","caption":"The manual-override screen."},{"src":"https:\/\/ps.w.org\/zinn-translate\/assets\/screenshot-4.png?rev=3731264","caption":"Per-language sitemaps and llms.txt<\/code> addresses, with links to check them."}],"raw_content":"\n\/fr\/a-propos\/<\/code> alongside \/about\/<\/code> \u2014 with translated URL slugs, the right hreflang<\/code> tags, its own sitemap, and its own llms.txt<\/code> for AI answer engines.<\/p>\n\nWhere the translations happen<\/h4>\n\n
\n
What it does not do<\/h4>\n\n
\n
Corrections that stick<\/h4>\n\n
The language switcher<\/h4>\n\n
[zinn_language_switcher]<\/code>), a block, a widget and a nav-menu item, all the same control. Six styles \u2014 dropdown, inline list, pills, minimal text, flags and names, stacked list \u2014 each with editable colours, spacing, corners and text size. You choose which languages appear, and whether they are named in their own language (Deutsch) or in yours (German). Right-to-left languages are laid out correctly, and the switcher is keyboard-operable with a visible focus ring.<\/p>\n\nSEO<\/h4>\n\n
\n
hreflang<\/code> on every page, with x-default<\/code> and a self-reference.<\/li>\n<html lang><\/code> and dir=\"rtl\"<\/code> where the language needs it.<\/li>\n\/zinn-sitemap-index.xml<\/code>, with xhtml:link<\/code> alternates, announced in robots.txt<\/code> alongside whatever else is there.<\/li>\nhreflang<\/code> rather than fighting it.<\/li>\n<\/ul>\n\nWooCommerce<\/h4>\n\n
External services<\/h3>\n\n
\n
https:\/\/api.zinndigital.com\/v1\/sites\/{site}\/translation\/sources<\/code>, with the site identifier and token you pasted in. It then fetches the finished translations from https:\/\/api.zinndigital.com\/v1\/sites\/{site}\/translation\/bundle\/{locale}<\/code>. Terms: https:\/\/zinndigital.com\/legal\/terms \u2014 Privacy: https:\/\/zinndigital.com\/legal\/privacy<\/li>\nhttps:\/\/generativelanguage.googleapis.com\/v1beta\/models\/{model}:generateContent<\/code> with your key in a request header. Terms: https:\/\/ai.google.dev\/gemini-api\/terms \u2014 Privacy: https:\/\/policies.google.com\/privacy<\/li>\nhttps:\/\/api.deepl.com\/v2\/translate<\/code> (or https:\/\/api-free.deepl.com\/v2\/translate<\/code> for a free key) with your key in a request header. Terms: https:\/\/www.deepl.com\/en\/pro-license \u2014 Privacy: https:\/\/www.deepl.com\/en\/privacy<\/li>\nhttps:\/\/api.openai.com\/v1\/chat\/completions<\/code> with your key in a request header. If you set a different base URL, it goes to that service instead of OpenAI. Terms: https:\/\/openai.com\/policies\/row-terms-of-use \u2014 Privacy: https:\/\/openai.com\/policies\/row-privacy-policy<\/li>\nhttps:\/\/api.wordpress.org<\/code> for the WordPress, theme and plugin language packs for that language, so your theme's own buttons are shown in it. This is the same request WordPress makes when you change the site language yourself.<\/li>\n<\/ul>\n\n\n
https:\/\/api.zinndigital.com\/v1\/connector\/diagnostics<\/code>. You are shown the\nexact payload first, already redacted, and nothing leaves your site until you press send.<\/strong>\nCredentials are excluded by declaration rather than by matching key names, and render as\n [not sent \u2014 credential]. The plugin never sends this on its own initiative.<\/li>\n<\/ul>\n\nWhat this plugin stores on your site<\/h3>\n\n
{prefix}zinn_translations<\/code>, holding one row per translated string: which content it belongs to, which language, the translation, a hash of the source it was made from, and whether you edited it by hand. It also stores your settings, including the API credential you saved.<\/p>\n\n\n
\n
Does it duplicate my posts?<\/h3><\/dt>\n
What happens if the translation service is down?<\/h3><\/dt>\n
Can I correct a translation?<\/h3><\/dt>\n
What happens to my old URLs if I turn on translated slugs?<\/h3><\/dt>\n
Will it clash with my SEO plugin?<\/h3><\/dt>\n
Do I need a Zinn Digital\u00ae account?<\/h3><\/dt>\n
2.4.7<\/h4>\n\n
\n
2.4.6<\/h4>\n\n
\n
2.4.5<\/h4>\n\n
\n
2.4.4<\/h4>\n\n
\n
2.4.3<\/h4>\n\n
\n
2.4.2<\/h4>\n\n
\n
2.4.1<\/h4>\n\n
\n
2.4.0<\/h4>\n\n
\n
2.3.0<\/h4>\n\n
\n
2.2.11<\/h4>\n\n
\n
2.2.10<\/h4>\n\n
\n
2.2.9<\/h4>\n\n
\n
2.2.8<\/h4>\n\n
\n
2.2.7<\/h4>\n\n
\n
2.2.6<\/h4>\n\n
\n
2.2.5<\/h4>\n\n
\n
2.2.4<\/h4>\n\n
\n
2.2.3<\/h4>\n\n
\n
2.2.2<\/h4>\n\n
\n
2.2.1<\/h4>\n\n
\n
2.2.0<\/h4>\n\n
\n
2.1.1<\/h4>\n\n
\n
2.1.0<\/h4>\n\n
\n
2.0.0<\/h4>\n\n
\n
llms.txt<\/code> \/ llms-full.txt<\/code>.<\/li>\n1.1.2<\/h4>\n\n
\n