Blocklingo

• One post per language, linked in a translation group. Deleting a post never deletes its translations.
• URLs: the default language has no prefix, other languages use /uk/, /de/ and so on. The front page of each language lives at its root.
• Language switcher: a block, the [blocklingo_switcher] shortcode, the blocklingo_language_switcher() template tag, or added to a menu of a classic theme without code.
• Per-language header and footer (block themes): header-uk replaces header on Ukrainian pages.
• Navigation menus and synced patterns per language: a block shows the menu or pattern of the page language.
• Categories, tags and other public taxonomies per language, with their own URLs (/uk/category/novyny/) and hreflang.
• Machine translation in the editor: Google, DeepL, Gemini, Claude, or on WordPress 7.0+ the AI provider set up in Settings > Connectors (no separate key). Block attributes are translated in the browser and re-serialized, so blocks stay valid.
• SEO: Slim SEO, Yoast, Rank Math and SEOPress titles and descriptions are translated; one sitemap with hreflang alternates (Slim SEO); hreflang tags and per-language locale.
• Sync like Polylang: categories and tags, featured image, template, parent and order stay identical across translations.
• WordPress, theme and plugin translation files are installed automatically for every language and kept updated.
• Language strings (like WPML String Translation): texts of the theme and plugins without an official translation are collected while you browse the site (or with “Scan site”) and translated by hand or with machine translation.
• Latin slugs for Cyrillic titles, with a tool that converts existing slugs and redirects the old addresses.
• “Translate everything”: the whole site (pages, posts, categories, tags, menus, header and footer) machine-translated into a language at once, as drafts to review.
• The plugin’s own screens are translatable (Ukrainian included).

External services

Machine translation is optional and off until you choose a provider in Settings > Blocklingo and add your own API key. Only the provider you choose is contacted, and only when you translate (the Translate button, “Translate everything”, “Translate empty” on Language strings, “Test connection”, “Load models”). The plugin sends the texts being translated (page title, excerpt, block texts, SEO fields, menu labels, category names, theme strings), the source and target language, your glossary, style guide and extra instructions, and the page title as context. It sends your API key to that provider to authenticate. Nothing is sent in the background or when visitors browse the site.

• Google Cloud Translation API (translation.googleapis.com), by Google: Terms, Privacy.
• DeepL API (api.deepl.com, api-free.deepl.com), by DeepL SE: Terms, Privacy.
• Google Gemini API (generativelanguage.googleapis.com), by Google: Terms, Privacy.
• Anthropic Claude API (api.anthropic.com), by Anthropic: Terms, Privacy.
• WordPress AI (WordPress 7.0 and later): the plugin does not contact any service itself. It passes the same texts to the WordPress AI Client, which sends them to the provider the site owner set up in Settings > Connectors, under that provider’s terms and privacy policy.

Language files: when you add a language, the plugin asks WordPress to install the official translation files for WordPress, themes and plugins from wordpress.org (the same updates WordPress does itself), Privacy.