Falang multilanguage for WordPress free WordPress plugin

Falang is a multilanguage plugin for WordPress. It allows you to translate an existing WordPress site to other languages. Falang natively supports WooCommerce (product, variation, category, tag, attribute, etc.) Concept Easy setup Supports all languages supported by WordPress (RTL and LTR) When you add a language in Falang, WP language packages are automatically downloaded and updated Easy to use: Translate Posts, Pages, Menus, Categories from the plugin or linked from the WP interface Translate Posts and Terms permalinks Translate additional plugins like WooCommerce, Yoast SEO, etc. You can use Azure,Yandex,Lingvanex to help you with the translation (Google and DeepPL services may be included in later versions) Displays the default language if the content is not yet translated The Language Switcher widget is configurable to display flags and/or language names Language Switcher can be put in Menu, Header, Footer, Sidebars Image captions, alt text and other media text translation without duplicating the media files Language Code directly in the URL No extra database tables created, no content duplication Very good website speed performance (low impact) Contains translations for IT, FR, DE, ES, NL Falang is not meant for WordPress multisite installations! Falang’s goal is to let you translate everything on your page Taxonomies Menu items Theme and plugin strings Custom fields Page builder content Widgets Shortcode outputs URL slugs WooCommerce products Page title and description Image alt text and captions Also available Falang Q-Importer qTranslateX to Falang Falang for Divi Falang for Divi Falang for Elementor Falang for Elementor Known issues Elementor preview needs to have “Show slug for main language” disabled in Falang Settings When a post/page is restricted to one language, the Blog posts overview hides the post in the other languages. But in the single post view on the frontend you can still choose the other language(s) through the language switcher, resulting in a 404. This will be fixed in the next version.