LinkedIn lets you publish your profile in more than one language, and the feature is quietly one of the most misread things on the platform. It does not translate anything for you, and it never shows two versions side by side. It creates a second, independent profile that LinkedIn serves to a visitor based on the language their interface is set to.
How the second-language profile actually works
You add it from your own profile: open the edit panel for your intro section and look for the option to add a profile in another language. Pick the language, and LinkedIn opens an empty copy. Empty is the important word. Nothing is pre-filled, nothing is auto-translated, and your original text is left alone. You retype your headline, your About section, your job titles and your job descriptions in the new language.
From that point you have two versions of the same profile under one account. A recruiter browsing with their interface set to Spanish sees your Spanish version. A recruiter using LinkedIn in German, a language you never added, sees your primary version. Visitors also get a small language selector near your name so they can switch manually, but almost nobody touches it. What counts is the version they land on by default.
This is not the Languages section further down your profile, the one where you declare that your English sits at a full professional level. That section is a claim about you. The second-language profile is a second set of words about your work. The two are unrelated, and plenty of people list four languages while having exactly one profile version.
What gets duplicated and what stays shared
Fields that exist separately in each version:
- first and last name, which is useful if you need a different script such as Cyrillic or Japanese
- headline
- About
- job titles and job descriptions in Experience
- degree and field of study in Education
Everything else is shared, and that is the part people get wrong:
- your profile URL. There is no /es or /fr variant. One link resolves to whichever version fits the visitor
- photo, banner, location and contact info
- the Skills list, which is a single pool with no per-language twin
- endorsements and recommendations, which stay in whatever language the writer used
- certifications, licenses, company names and dates
- your posts, comments, Featured section and open-to-work settings
The Skills detail catches most people out. You cannot hold "project management" in one version and "gestion de proyectos" in the other, because there is only one list. Terms that need to work in both languages have to earn their place in the text you fully control: the headline and the descriptions.
Picking your primary language
Your primary language is the fallback everyone lands on. Someone with a Portuguese interface, a visitor arriving from a Google result, a recruiter flicking through a shortlist: unless their language matches a version you wrote, they read the primary.
There is no clean button to swap primary and secondary afterwards, so settle it before you type a word. Two questions usually decide it: where do you want your next role to be, and who makes the hiring call there? Want to be hired in Barcelona by a Spanish company? Primary is Spanish. Living in Barcelona but chasing remote roles at US and UK companies? Primary is English, and Spanish becomes the second version. Where you live matters less than where the decision gets made.
My own bias, for what it is worth: for anyone in Europe who would take an international or remote role, English as primary is the safer default. Local recruiters read English profiles without blinking. The reverse, an English-speaking recruiter landing on a wall of Spanish, ends the visit in four seconds.
Keywords decide who finds you
Recruiters search in the language they work in. A recruiter in Madrid filling a sales role types "comercial" or "responsable de cuentas". One in Manchester types "account executive". Your profile only surfaces for words that are actually written on it, so the vocabulary you choose in each version decides who ever sees you.
Which leads to the rule that prevents the most damage: do not translate job titles, map them. Ask what the equivalent role is called by the people who hire for it locally, then use that, even when it drifts from your official title. A French "responsable grands comptes" is a key account manager, not a "large accounts officer".
The reverse trap is just as common. Plenty of titles should stay in English inside a French or Spanish profile because that is what the local market says out loud: data scientist, product owner, growth marketer, DevOps engineer, customer success manager. Translating those makes you harder to find, not more local. When a market genuinely uses both, a double-barrelled headline works, as in "Chef de projet digital | Digital Project Manager". Do it once, in the headline, and stop there. A profile stuffed with slash-separated synonyms reads like a job board listing.
When it earns its keep, and when it does not
It is worth the effort if business in your market happens in a language other than English and you also want international attention; if you are relocating and need to exist in the target market's language before you arrive; or if your field is language-bound, which covers law, public sector, healthcare, HR, retail, teaching and most local sales roles.
Skip it if your second language is conversational and you would be leaning on machine translation. Skip it if your industry runs in English anyway, which is true for large parts of software, aviation and academic research. Skip it if you are two weeks into an urgent search with no spare hours, because one sharp profile beats two half-written ones.
An abandoned second version is worse than none at all: it is the only version a recruiter in that language will ever see, and it may still be advertising a job you left two roles ago.
Mistakes, and how to keep both versions alive
The classic failure is pasting a machine translation and never rereading it. Translation engines handle grammar and miss register. They will turn a French "formation" into "formation" instead of "training", a "stage" into "stage" instead of "internship", and a punchy Spanish summary into English that sounds like a legal notice. Read every line out loud, or have a native speaker spend ten minutes on it.
The second is asymmetry. A six-paragraph About in the primary and two lines in the secondary means recruiters in that market meet a weaker candidate than the one you built. Match the depth, even if the wording differs.
The third is drift. You change jobs, update the primary, forget the other version, and six months later a recruiter is reading a profile that describes a company you left.
Register matters as well. An English About is expected to carry numbers and outcomes; the same sentences translated literally into French or Spanish read as boasting. Rewrite, do not transpose.
For sync, the routine that works is boring: keep both versions in one document, two columns, block by block. Edit the document first, paste into LinkedIn second, and do both languages in the same sitting. Put a recurring reminder in your calendar for a quarterly read-through. If the profile text is already clean and current, turning it into a formatted CV with a tool like Postulit takes minutes in either language, which is one more reason to keep the source document tidy.
What to do this week
- Decide your primary language using the hiring-decision test, not the language you speak best.
- Write the primary version properly first. A second language on top of a mediocre profile multiplies mediocrity.
- Read ten real job ads in the target market and write down the exact titles they use.
- Create the second version from scratch, using those titles rather than translations of your own.
- Check the shared fields once: skills, URL and certifications get read by both audiences.
- Save both versions in a single two-column document, then set a reminder for the first week of every quarter.
If you cannot see yourself doing step six, do not do steps one through five either. A single well-maintained profile in one language beats a bilingual pair where one half has quietly gone stale.