Someone asks whether your website is available in English. It might be a customer, a partner abroad, or the guests you already serve who do not read German. Saying yes is a decision about every page you have, and about every change you will make to those pages from then on.
This post walks you through that decision on your own site, page by page. You can do all of it with your current site open in one tab and this post in the other.
Which pages have to exist in English?
Every page that makes your case or takes the enquiry. For most Austrian businesses those are the following pages.
The home page, because it is often the first page a visitor sees and where they decide whether to read on.
The service or product pages, because they are what the visitor came to read. A visitor who lands on the English home page, clicks through to your services and finds the page only in German has nothing to read at the moment it matters most.
The contact page, and everything attached to it. The form labels, the error message when a field is missing, the confirmation the visitor sees after sending, and the email your site sends back all belong to the enquiry. An English form that answers in German leaves the visitor unsure whether the message arrived.
If you sell to a specific group, add the page that group arrives on. A hotel needs its rooms and its booking page in English. A firm that works with partners abroad needs the page that describes how that work runs.
Which pages can stay in one language?
Most of the rest, and that is a legitimate choice. A page in good German is more useful to your visitors than a second version that is thin, out of date, or half translated.
Pages that often stay in German are news and blog archives, job listings aimed at the local market, and offers that only apply locally, such as a regional event or a local delivery area. If nobody who reads English would act on a page, the page does not need an English version.
The legal pages, such as the imprint and the privacy policy, are a separate decision. Which language they need is a legal question, so ask the person who drafts them for you.
When a page stays in German, keep the whole page in German. Google’s guidance for multilingual sites recommends a single language for the content and the navigation on each page.

What does the upkeep look like?
Once the second version exists, every change to the site is two changes. A new price, a new opening hour, a new service, a new page, a corrected phone number: each one has to be written in the second language, checked, and published on both sides.
When one half falls behind, the two halves disagree. A visitor who switches language sees the older answer, and has no way to tell which version is right, because nothing on the page says that one of them is older.
The work is easier to plan when you settle these points before the first English page goes live.
- Who writes the second version of each change. One named person, inside your team or outside it. For the writing itself, let AI do the first pass and have a human edit it.
- When a change counts as done. A change is finished when it is live in both languages. If that is the rule, nobody publishes a new price in German and leaves the English page for later.
- Which pages exist twice. Keep a short written list. When someone adds or changes a page, the list tells them whether the other language needs the same change, so nobody has to guess.
Setting up the second language is work too. Each page on your list needs its second version written, the menu needs both languages, and the form needs its labels, messages and replies in both. That is why we already count a second language version as a project of its own when we explain what a company website costs.
How do visitors and search engines know which language they are on?
A visible switch for the visitor. Put it in the same place on every page, and make it land on the same page in the other language. A switch that always sends the visitor back to the home page makes them find their place again. Google’s guidance also recommends against redirecting visitors automatically to a language version based on what you think their language may be, and suggests links to the other language versions of a page.
The page language, for screen readers. Each version declares its language in the page code, so a reading voice pronounces German words in German and English words in English. The W3C, which writes the web accessibility guidelines, notes that this lets screen readers load the correct pronunciation rules. It is a one-time setting, and on a bilingual site it belongs on each language version. Our post on whether your business website has to be accessible covers the rest of that topic.
The alternate-language links, for search engines. Each page carries links that name its counterpart in the other language, in the page code where visitors do not see them. They help Google Search point people to the most appropriate version of a page by language or region. Google’s documentation sets two rules for them. Each language version must list itself as well as all other language versions, and if two pages do not both point to each other, the links are ignored. An extra value called x-default names the page to use when no listed language matches the visitor’s browser setting.
Google’s documentation adds three points about these pages. It does not use the page language setting to detect what language a page is in. It reads the visible content, so the English page has to be in English all the way through. And a translated page is not treated as a duplicate of the original, as long as its main content is translated. Google recommends a separate address for each language version, rather than one address that changes its language through cookies or browser settings.
Should you add the second language?
Answer these questions about your own business before you decide.
Who actually asks for English, and how often? A single request is a different situation from a steady share of guests from abroad. If you can name the people and how they reach you today, you know whom the English pages are for.
Which pages would they arrive on? Write the list. If it is the home page, two service pages and the contact page, the second version is a contained piece of work. If it is everything, it is a second website.
Who writes the second version, and who keeps it current? This is the question that decides it. If you can name the person and they have the time each month, the upkeep is planned work. If nobody can be named, the English half will fall behind.
A short set of English pages for the visitors who need them is a valid result of these questions. So is keeping one language and keeping it complete and current.
How we handle a second language
This site runs in German and English. Every German post points to its English counterpart, each page declares its own language, every page carries the alternate-language links for both versions, and the switch in the header lands on the same post in the other language. When we build a bilingual site, these parts are in the build from the first page. What a website with us includes is set out in our plans.