Reaching English-speaking customers in Vienna, Berlin or Zurich

Short answer: People who need an English-speaking provider in a German-speaking city usually search in English and often add the phrase itself: "English speaking dentist Vienna", "therapist in English Berlin". To show up, you need real English pages at their own URLs (not a translate widget), connected to your German pages with hreflang, plus a Google Business Profile description and reviews that mention English service. Don't stuff "English-speaking" into your business name; Google's guidelines don't allow it.

Expats, international students, visiting professionals and tourists are a steady market in Vienna, Berlin, Munich, Zurich and Geneva. They have a specific worry ("will they understand me?") and they search for it directly. The good news for a small business is that this is a narrow, high-intent search, and many competitors serve it badly with a machine-translated page.

How English-speaking customers search

You can't buy a list of their exact queries, but the patterns are easy to observe in Google's autocomplete and in your own Search Console data once English pages exist:

Service + "English speaking" + city: "English speaking gynaecologist Vienna".
Service + "in English": "tax advisor in English Munich", "yoga classes in English Zurich".
Plain English service + city, with no mention of language: "dentist Vienna 1070". These searchers may simply be using an English phone.
Questions: "how to find a doctor who speaks English in Berlin".

Your pages should answer all four: name the service in English, say clearly that you serve clients in English, and mention the city and district.

Scenario 1: a dental practice in Vienna

A hypothetical practice in the 7th district has a German site and an English-speaking dentist. Expat patients are a growing share but rarely find them.

What to build: English versions of the pages that matter for a first visit, not the entire site. Home, the three or four main treatments, "Your first visit", prices or how billing works, and contact. Each at its own URL, such as /en/ and /en/dental-implants/.

Why separate URLs: Google recommends different URLs for each language version rather than switching language with cookies or browser settings, and warns that Google might not find content that changes dynamically. It also determines a page's language from the visible content, and suggests one language per page and avoiding side-by-side translations.

What to say on the English pages: who speaks English (by name), whether reception and paperwork are in English, how appointments and payment work for people new to the Austrian system, and how to get there by U-Bahn. That last part is local knowledge a translation tool won't add.

Scenario 2: a café and bakery in Berlin

Here the customers are walk-ins and the "English" question is about the menu, ordering and the vibe, not paperwork.

What to build: a simple bilingual site where the menu, opening hours and location exist in both German and English. For a small site, a full English mirror is fine because there are only a handful of pages.

Google profile: Google's Business Profile guidelines list service information and descriptors among things a business name must not include, so "Café Linde – English Spoken" breaks the rules. Use the business description instead. Google's help says it can describe what you offer and what makes you special, must stay under 750 characters, and shouldn't include URLs. A line such as "Staff speak English and German; menus available in both" is useful and allowed.

Reviews: you can't choose the language customers write in, but English-speaking regulars who leave English reviews give other expats the reassurance they're searching for. Ask them as you'd ask anyone, without incentives.

Scenario 3: a business coach in Zurich

A solo coach works mostly in English with international professionals, with some German-speaking clients.

What to build: English as the main language of the site, with German versions of the core pages. Because most of the content is English, the English versions are the "originals" and the German pages are the alternates.

Swiss detail: if you also want French for Geneva or Lausanne clients, add it only when you can maintain it properly. Two good languages beat three half-translated ones.

hreflang in plain words

hreflang tags tell Google which pages are language versions of each other, so an English searcher is shown the English page and a German searcher the German one. Google's rules, as of November 2026:

Each language version must list itself and every other version.
The links must point both ways; if two pages don't point to each other, the tags are ignored.
URLs must be fully qualified (including https).
x-default can mark the fallback page for languages you don't cover.

For a Vienna practice, the English implant page would carry:

<link rel="alternate" hreflang="de" href="https://example.at/zahnimplantate/" />
<link rel="alternate" hreflang="en" href="https://example.at/en/dental-implants/" />

and the German page carries exactly the same two lines. Use the language code alone (en, de) unless you genuinely have separate versions for different countries; you're targeting English speakers in Vienna, not people in England.

Also from Google's multilingual guidance: don't automatically redirect visitors to a language version based on what you guess their language is. Give them a visible language switch instead, and let them choose.

Setup checklist

[ ] Pick the pages that matter for a first enquiry and write them in natural English (a fluent human edit if you start from machine translation).
[ ] Give every English page its own URL (for example under /en/).
[ ] Add reciprocal hreflang tags between each German and English pair.
[ ] Add a clear language switch in the header that links page to page, not to the home page.
[ ] Translate titles, meta descriptions, image alt text and form labels, not just body text.
[ ] Make the enquiry or booking form work in English, including confirmation emails.
[ ] Mention English service in your Business Profile description; keep the business name clean.
[ ] Name the English speakers on your team on the relevant pages.
[ ] Add local practicalities: public transport, district, how payment or insurance works for newcomers.
[ ] After a few weeks, check Search Console for English queries and adjust page wording to match.

FAQ

Is Google Translate on my site good enough?

A translate widget doesn't create separate English pages for Google to index, and the quality shows. Use real English pages, even if there are only five of them.

Should I use a separate .com domain for English?

Usually not. A folder on your existing domain (/en/) is simpler to manage and keeps everything under one site. Google's documentation notes that alternate URLs don't need to be on the same domain, but for a small business one domain is easier.

Do I need a second Google Business Profile for English?

No. One location has one profile. Mention English service in the description and let English reviews accumulate naturally.

Will English pages hurt my German rankings?

Not if each language has its own URLs with correct hreflang. They address different searchers.

If your German site needs a handful of English pages that read like they were written in English, show us which services matter most.