TranslatePress
With TranslatePress active, its languages become the bio page editor’s tabs, and bio page addresses use TranslatePress’s URL slugs.
Setup#
None. Activate TranslatePress and add its languages. At Link Bio → Settings, Detect automatically uses the first active plugin in this order: WPML, Polylang, TranslatePress, Bogo, WP Multilang, TranslateWP, Linguise. With another multilingual plugin also active, choose TranslatePress directly. See Language Settings.
How languages are read#
From TranslatePress’s settings:
- Translation languages: the list of languages
- URL slugs: the code used in each address, for example
arorfr - Default language: served at the plain address
Language names come from WordPress’s language list, or from PHP for locales WordPress does not list (such as English (United States)).
Addresses#
| Language | Address |
|---|---|
| Default | yoursite.com/links/ |
| Arabic | yoursite.com/ar/links/ |
| French | yoursite.com/fr/links/ |
The folder is whatever you set as the URL slug in TranslatePress → Settings → Languages.
Editor tabs#
One tab per language, each with its own display name, subtitle, bio, links, showcase heading and button text, and SEO fields. The default language is the first tab.
SEO and hreflang#
The language of the request comes from the address, or from TranslatePress. That tab’s SEO fields go to your SEO plugin. On bio pages, TranslatePress’s hreflang links are replaced by the bio page’s, which list only languages with content.
Right to left#
Arabic, Hebrew, Farsi, Urdu and other right-to-left languages are shown right to left.
What TranslatePress is not used for#
Bio page text is stored in the bio page itself, one set per language. It does not go through TranslatePress’s editor and uses no translation credits.