Skip to content
Marketing & occupancy

Multilingual Care Website: Reach More Relatives

Turkish-, Russian- and Arabic-speaking relatives search for care in their language. How care services win trust and enquiries with multilingual core pages.

12 min read AngehörigeMehrsprachigkeitLocal SEOMigrationPflege-Website

In short and in plain language

This article is about a care website in more than one language.

Some families look for care in their own language. For example in Turkish, Russian or Arabic.

Your own area shows which language is worth it. A few key pages are often enough: services, costs, contact and about us.

A button that translates by itself is not enough. A person should check the text. The page should be easy for all to use in every language.

We translate and check the key pages for you.

When care for a parent becomes a topic in a Turkish-, Russian- or Arabic-speaking family, the search rarely begins in German. Relatives type their questions about costs, services and the nearest care provider in the language they speak at home and in which they place their trust. And the need is growing: the share of over-60s with a migration background rises from around 11 percent in 2004 to a projected 24 percent by 2030 (bpb). A care website offered only in German is absent at the decisive moment for a growing part of these families. This article shows how home care services and facilities can build trust and win enquiries with just a few multilingual core pages, instead of losing these families to a competitor who speaks the language.

Key takeaways

  • The share of over-60s with a migration background rises from around 11 percent in 2004 to a projected 24 percent by 2030 (bpb), and around 29 percent of the population in Germany have a migration background (Federal Statistical Office).
  • Whether a Turkish, Russian or Arabic version pays off is decided not by the national average but by your own catchment area: municipal statistics, your client records and the languages of incoming calls show the real need.
  • Three to four core pages suffice: services, costs including the personal contribution and the relief amount of EUR 131 per month (Section 45b SGB XI), contact, and a short about-us page. An honest note marks which content exists only in German.
  • An automatic translation button is not enough: terms such as respite care or personal contribution quickly turn factually wrong by machine. A machine draft saves time, but the published version belongs with a human editor.
  • Technically it rests on separate language directories, clean hreflang including x-default and a switcher that opens the current page rather than the home page. Arabic versions need a mirrored reading direction, and WCAG 2.2 level AA applies in every language (BFSG).

Why relatives search in their family language

Care is an emotional and a financial decision, and both touch people at a vulnerable point. Anyone who wants to see a mother or father well looked after reads closely, compares and wants to be sure they have understood what a provider offers and what it costs. Technical German like uniform personal contribution, respite care or service module is a hurdle even for native speakers. For a relative who speaks Turkish or Russian in daily life, it quickly becomes a wall. She does not leave because the offer is poor but because she stumbles over the language and is unsure whether she has read the small print correctly.

These families are numerous. Around 29 percent of the population in Germany have a migration background (Federal Statistical Office), with Turkey remaining the single most common country of origin (Federal Statistical Office). At the same time, the first generation of immigrants, who arrived in the 1960s and 1970s, is ageing. This is exactly why the number of people needing care who have a migration background is rising markedly (BAMF research report). The caring relatives of that generation are today the target group researching online, and they do so in the language in which they feel secure. Which content these relatives expect anyway is explored in the article on content for relatives on a care website.

The figures at a glance

From around 11 percent (2004), the share of over-60s with a migration background rises to a projected 24 percent by 2030 (bpb). Around 29 percent of the total population have a migration background (Federal Statistical Office). Of 5.69 million people needing care in December 2023, 86 percent, some 4.89 million people, are cared for at home (Federal Statistical Office). A large part of home-based care rests on the shoulders of relatives, and a growing share of these relatives do not search in German.

How large the target group really is

The size of the target group is often underestimated because no statistic lists it as a care market for language X. You have to combine two developments. First the raw figure: 5.69 million people needing care in December 2023, of whom 4.89 million are at home (Federal Statistical Office). Second the demographics of immigration: the guest-worker generation is reaching the age of care, and their children and grandchildren organise it. Where the two curves meet, a regional need arises that a German-only offer does not capture. In districts with a high share of Turkish- or Russian-speaking households, that share can lie well above the average.

The local view matters. A care service does not cover a whole country but a catchment area of a few towns or districts. Whether a Turkish- or Arabic-speaking core page is worthwhile does not depend on the national average but on the population in your own catchment area. A look at the municipal statistics, at your own client records and at the languages in which enquiries already arrive quickly shows which language takes priority. How a service makes itself visible regionally at all is covered by the article on local SEO for care services.

Which languages are worthwhile

Not every language needs to arrive at once. It makes sense to prioritise by the real need in the catchment area, and usually three to four languages cover the largest part. The population of Turkish origin is the largest group of origin (Federal Statistical Office), Russian-speaking families from the group of late resettlers and immigrants are strongly represented in many regions (BAMF research report), and the Arabic-speaking population has grown noticeably since 2015 (Federal Statistical Office). Which of these groups leads in your own town is decided by local reality, not by gut feeling.

Turkish

The population of Turkish origin is the largest group of origin in Germany (Federal Statistical Office). The first generation is reaching the age of care, their families organise it and often research in Turkish.

Russian

Russian-speaking families from the group of late resettlers and immigrants are strongly represented in many regions (BAMF research report). For older relatives, Russian is often the language in which trust is built.

Arabic

The Arabic-speaking population has grown markedly since 2015 (Federal Statistical Office). With its right-to-left reading direction, Arabic adds technical requirements that belong in the plan early on.

The order is a recommendation, not a rule. A service in a town with many Polish- or Vietnamese-speaking families prioritises differently. The principle stays the same: first one language done cleanly and completely, then the next. Three half-finished translations look weaker than one that is complete and comprehensible. If in doubt, start with the language in which most phone enquiries already arrive, because that channel shows the real need more honestly than any forecast.

Which core pages belong in several languages

Maintaining a complete website in four languages is neither necessary nor affordable for a care service. The leverage lies elsewhere: three to four core pages answer the questions that count at the moment of decision. Anyone who translates these pages and clearly marks the rest of the site as continuing in German captures almost all of the benefit without overwhelming the editorial team. What matters is that the translated pages cover the three big questions: what do you offer, what does it cost me and how do I reach you.

  • The services page in the family language: what the provider actually offers, home care or residential, with a plain explanation of the technical terms
  • The cost page: which part the care insurance fund covers and where the personal contribution begins, with the relief amount of EUR 131 per month (Section 45b SGB XI) as a concrete example
  • The contact page with a clear offer: a call back or a consultation slot, and a note that advice is available in the respective language
  • A short about-us page showing that the team includes people who know the language and the cultural expectations
  • A consistent, easy-to-find language switcher on every page, not hidden away in the footer
  • An honest note about which content is only available in German, so no one clicks into a void

The home page and the three core pages are enough as a foundation. Everything else, such as individual guide articles or legal texts, can stay in German at first as long as the transition is clearly marked. How the page structure should be built so that it holds in every language is shown in the article on the structure and layout of a care website.

Real translation instead of machine automation

The biggest mistake is an automatic translation button that turns the site into every language by script. Such tools produce sentences that are almost grammatically correct and still sound wrong, precisely with sensitive care terms. If respite care or personal contribution is machine-translated, the worst case is a factually wrong statement that destroys trust and is legally vulnerable. Care is a field where an imprecise wording about cost reimbursement has real consequences. That is why the core pages belong to a human translator who commands both the language and the care terminology.

FeatureAutomatic translationEdited translation
Technical termsOften literal and wrongCorrect and explained
TrustFeels foreign and mechanicalSounds familiar and personal
Legal safetyErrors on cost and serviceStatements checked and sound
Cultural closenessIgnores expectationsPicks up address and tone
MaintenanceChanges uncontrolledUpdated deliberately
SEODowngraded by search enginesCleanly indexable

That does not mean technical tools have no place. A machine pre-translation can save time as a rough draft, as long as a human then checks it, corrects it and sets the technical terms right. The difference is the review step: the published version must never go online unedited. For the three to four core pages this effort is manageable and one-off, while the effect lasts.

Technical basics: hreflang, language choice and URLs

For search engines to assign the translated pages to the right language and for relatives to land directly in their language, clean hreflang markup is needed. Each language version points to itself and to all other versions of the same page, plus a declaration for the default language. Without this link the versions may compete against each other in the worst case, or the German version appears even when someone explicitly searches in Turkish. The markup belongs in the head of every page and must be consistent across languages.

hreflang in the head of every core page
<link rel="alternate" hreflang="de" href="https://www.pflegedienst-beispiel.invalid/leistungen/" />
<link rel="alternate" hreflang="tr" href="https://www.pflegedienst-beispiel.invalid/tr/hizmetler/" />
<link rel="alternate" hreflang="ru" href="https://www.pflegedienst-beispiel.invalid/ru/uslugi/" />
<link rel="alternate" hreflang="ar" href="https://www.pflegedienst-beispiel.invalid/ar/khadamat/" />
<link rel="alternate" hreflang="x-default" href="https://www.pflegedienst-beispiel.invalid/leistungen/" />

For the URL structure, descriptive directories per language have proven their worth, such as a prefix like /tr/ or /ru/. This is unambiguous for users and search engines and easy to manage. Also important is a language switcher that does not merely show a flag but opens the current page in the target language rather than throwing users back to the home page. Arabic content adds the right-to-left reading direction, which the layout must mirror so that text and controls do not slip. How such requirements can be reliably met on mobile is shown in the article on the mobile care website for relatives.

These mistakes cost visibility

Avoid automatic redirects based on browser language alone, which force users and search engines into one language and make the other invisible. Avoid identical URLs for several languages, because search engines then cannot separate the versions. And avoid a language switcher that always jumps to the home page instead of opening the current page in the new language. Each of these mistakes costs exactly the visibility the translation was meant to create.

Cultural closeness instead of literal sameness

A good translation is more than replacing words. It hits the tone, the form of address and the expectations a target group has of a serious offer. In some cultures a more formal address is a matter of course, in others the emphasis on family and personal care counts more than any list of services. Anyone who takes seriously the relatives' worry that their father or mother will be treated with respect and understanding addresses that worry directly. This is not a marketing phrase but the reason a family chooses a provider.

Trust grows where the language fits

Cultural closeness works in both directions. It convinces relatives looking for a service for their own parents, and at the same time it helps with staff. A provider that appears multilingual and makes diversity visible is more attractive as an employer to care workers with a migration story. How international professionals can be addressed specifically through the website is shown in the article on a careers page for international care workers, and how genuine voices from the team strengthen this effect is covered by the article on employee voices on the careers page.

Accessible and mobile in every language

Multilingualism and accessibility work hand in hand. A large part of caring relatives are already older themselves, read with enlarged text and almost always use a smartphone. A translated page that scrolls horizontally on a phone or whose text cannot be enlarged misses its target group despite correct language. Since June 2025 the German Accessibility Strengthening Act has required an accessible result for many digital offers anyway (BFSG), and the recognised benchmark for this is conformance level AA of WCAG 2.2. Multilingual core pages should meet these requirements in every language, not only in German.

  • Each language version carries the correct lang attribute so screen readers choose the right pronunciation
  • For Arabic content the layout mirrors the right-to-left reading direction fully, not just the text
  • Font sizes and contrasts meet level AA of WCAG 2.2 equally in every language
  • The language switcher is reachable by keyboard and has a visible focus indicator
  • On a smartphone every version stays operable with one hand, without horizontal scrolling
  • Forms and error messages are comprehensible in the translated version too and are announced to screen readers

Anyone who has already implemented these basics cleanly in the German version transfers them to the other languages with manageable effort. How accessibility can be implemented in practice without overloading the editorial team is shown in the article on the accessible care website in practice.

Implementation in the first weeks

You do not have to build everything at once. The order below prioritises by effect per effort: first the one language with the greatest need, first the core pages, then technical cleanliness, then the next language. In this sequence a sound multilingual foundation stands after a few weeks, and from then on it only needs to be kept up to date.

  1. Week 1: check the need in the catchment area, evaluate incoming enquiries by language, decide on a first language
  2. Week 2: have the services page translated and edit the translation for accuracy, explaining technical terms
  3. Week 3: translate the cost page with the personal contribution and the relief amount of EUR 131 (Section 45b SGB XI) and add a date of record
  4. Week 4: translate the contact page and the about-us page, and clearly state the offer of advice in the respective language
  5. Week 5: add a language switcher that opens the current page in the target language, not the home page
  6. Week 6: set the hreflang markup for all versions and lay out the URL structure cleanly per language
  7. Week 7: check accessibility and mobile operation in every language, and test the Arabic version for reading direction
  8. Week 8: have the result proofread in the target language, then tackle the next language on the same pattern

Once the first language stands, the second goes much faster because structure, switcher and technology are already in place. For the underlying basis the care website is the frame, the overview of services provides the content, and how the path from translation to a real enquiry is closed is explored in the article on more enquiries via a care website. We are happy to clarify questions about the concrete implementation for your catchment area in a personal conversation.

Sources

This article is based on data from: the German Federal Agency for Civic Education (bpb, migration and care, share of over-60s with a migration background rising from around 11 percent in 2004 to a projected 24 percent by 2030), the Federal Statistical Office (Microcensus, around 29 percent of the population with a migration background, Turkey as the most common country of origin; care statistics, 5.69 million people needing care in December 2023, of whom 86 percent and thus around 4.89 million people cared for at home), the Federal Office for Migration and Refugees (BAMF research report on care and migration, markedly rising number of people needing care with a migration background) as well as the German Social Code Book XI (Section 45b relief amount, retrieved via the Federal Ministry of Justice legal portal) and the German Accessibility Strengthening Act (BFSG, in force from June 2025). Figures on amounts reflect the status of 14 August 2026 and do not replace individual advice; the binding information on the specific personal contribution is provided by the responsible care insurance fund.

Related Articles

Marketing & occupancy

Assisted Living Websites: Show Apartments and Services

Present apartment type, floor plan and costs separately: how an assisted living offer becomes comparable online and the viewing appointment becomes bookable.

13 min read
Marketing & occupancy

Day-Care Website: Fill Vacant Places Faster

How a day-care website makes free places visible, explains the daily routine and transport and turns relatives' visits into concrete booking requests.

13 min read
Law & data protection

ePA in care: what relatives want to know about access

The ePA in care: what the care service sees, who adds entries, how relatives object or act as representatives, and how a guide page answers these questions.

19 min read