Questions
Short answers to what people ask before installing.
Is Multilify really free?
Yes. Multilify is free and open source under the GPL v2 or later. There are no paid tiers and no upsells, and there is no plan to add either.
Does it call any external services?
No. Your translations live on your own server and the plugin makes no third-party API calls. It sets one first-party cookie, multilify_language, only when a visitor clicks a language in the switcher, so that their choice is remembered.
Will it slow down my site?
The slug lookup is indexed and object-cached, and the cache entry is dropped whenever a slug changes. On a site with a persistent object cache such as Redis, repeat requests skip the database for that lookup.
Which editors are supported?
Gutenberg and the Classic Editor both work. In either one, each language gets a panel below the post with its title, slug and a visual editor for the content. Builders that render from their own stored data, such as Elementor, are not covered, because Multilify translates content that passes through the_content.
What are the requirements?
WordPress 5.8 or newer and PHP 7.4 or newer. No other plugin is required.
Can I move over from WPML or Polylang?
Yes, by hand or with a script. There is no importer, and the migration page says plainly what carries over and what does not.
Which post types can I translate?
Posts and pages by default. Add any other post type, such as a WooCommerce product, with the multilify_post_types filter. Types you do not add keep their normal addresses.
What does a visitor see when a post has no translation?
The default-language text, at the language's address, so a half-finished translation never shows a blank page. Search engines are told: the canonical points at the default address, and that language is left out of the hreflang tags and the sitemap.
What happens to my existing URLs?
The default language keeps the addresses it already has, so nothing you have published moves. If someone opens the default language with its prefix, such as /en/, they are redirected permanently to the address without it.
Can each language have its own slug?
Yes. Each language panel has a slug field. Leave it empty and the post's own slug is used under that language's prefix. If two posts get the same slug in one language, the second one is numbered, the way WordPress numbers duplicates.
Does it work with nested pages?
Yes. A child page keeps its parent in the path, and each parent uses its translated slug when it has one. A page tree that is only partly translated still opens.
Can each language have its own domain?
No. Every language is a prefix on the same domain, such as /tr/. There is no domain or subdomain per language.
Does it redirect visitors by browser language?
Only at the site root, and only for a first-time visitor. A language picked from the switcher wins over the browser, and logged-in users and crawlers are never redirected. The multilify_enable_browser_detection filter turns it off.
Will dates and theme text change language too?
Yes, when the WordPress language pack for that language is installed. Multilify switches WordPress to the matching locale, such as de_DE for de, so dates and the comment form follow the page. Without the pack the site's own language stays.
Does search work in each language?
Yes. A search under a language prefix also matches that language's translated titles and content, and a search form on a language page searches in that language.
Does it help search engines find each language?
Yes. Posts and language home pages get hreflang tags with x-default, only for languages that have text of their own. Each extra language also gets its own sitemap in WordPress' sitemap index.
Does it work behind a page cache or a CDN?
Each language has its own address, so cached pages stay apart. The site root is the one address that can redirect by browser language, and it sends Vary: Accept-Language, Cookie for that reason. If your cache ignores Vary, turn detection off with the multilify_enable_browser_detection filter.
What happens when I delete a language?
Its translations stay in the database, so adding the same code again brings them back. The default language cannot be deleted until another one is the default.
What happens if I deactivate or delete the plugin?
Deactivating removes the plugin's rewrite rules, so the language addresses stop opening, and your translations stay in the database. Deleting the plugin from the WordPress admin removes every translation, its settings and its database index, so copy your translations out first if you want to keep them.
Does it work on multisite?
Yes. Network activation sets up every site, and each site keeps its own language list.
Is the plugin's admin available in my language?
The settings screen and the translation panels ship in English, German, Spanish and Turkish, and WordPress picks the one that matches your admin language.