German On-Page Specifics: Compound Nouns, Umlauts and Formal Address

German-language websites compete in a market where Google handles around 89.6 percent of all search queries in Austria, while Bing reaches around six percent (StatCounter data via Statista, Austria 2024). On-page optimization for this market follows the same technical principles as in English, but it runs into linguistic features that English-language SEO literature barely covers. Compound nouns, umlauts, the ß and the choice of address change how you calculate title budgets, build URLs and send trust signals. This article covers German on-page specifics for a professional B2B audience in the DACH region, with a particular focus on Austria.

Why German on-page optimization needs its own rules

German is, on average, more character-heavy than English. German words are on average significantly longer than their English equivalents, which hits the tightest on-page budget directly: the title tag. A single compound such as Suchmaschinenoptimierung takes up 24 characters before any other word is added. That matters because title tags with 40 to 60 characters achieve an 8.9 percent better average CTR, according to an analysis of around 4 million Google search results (Backlinko, international study). A German title therefore reaches the upper edge of this range sooner than an English one.

At the same time, the German-language competitive field is structurally smaller. According to W3Techs, German is the content language of only about 6 percent of websites (as of October 2026). For Austrian B2B providers, this means that precise German-language on-page work has outsized leverage, because fewer high-quality pages compete for the same search queries. Then there is the conversion factor: according to an international survey of 8,709 consumers in 29 countries, 76 percent prefer products with information in their native language and 40 percent never buy on foreign-language websites (CSA Research, 2020). Language precision therefore has a direct effect on revenue.

Compound nouns and umlauts: how they work in detail

Handling compound nouns: Google handles what is known as compound splitting and largely breaks down German compound words on its own for evaluation. A search for Kanzlei Steuerberatung Wien usually also matches pages that use Steuerberatungskanzlei Wien. So the strategic decision is not whether to join or split words for technical reasons, but which form matches search intent. Check the actual search volume: do people search more often for the separated form (Kanzlei Steuerberatung Wien) or for the compound (Steuerberatungskanzlei Wien)? Use the form with more demand prominently in the title and H1, and the other one in the body text. That way you cover both forms without artificially lengthening the title.

Umlauts in content: In visible text, umlauts have to be spelled correctly: ä, ö, ü and the ß. The ae, oe, ue substitution does not belong in body text, only in technical fields where ASCII safety matters. What matters is meaning: Über and Uber are not the same, and neither are Schön and Schon. If you drop the dots, you risk wrong entity mapping and poorer readability.

Umlauts in URLs and slugs: In URLs, the ae/oe/ue spelling (vowel plus e) has become the standard: Überprüfung becomes ueberpruefung, Größe becomes groesse. Punycode (prefix xn--) is technically possible for internationalized domain names, but in practice it is unreadable and unsuitable for B2B brand communication. For slugs, the rule is: lowercase, ae/oe/ue substitution, ß to ss. In alt texts, image captions and visible anchor texts, on the other hand, you use the real umlauts, because these fields are rendered and read. Make sure your UTF-8 encoding is correct throughout so that ä does not show up as mojibake.

Swiss special case: Swiss Standard German has no ß. It always uses ss: Strasse, not Straße; Grösse, not Größe. If you serve content for de-CH, apply this spelling consistently, or the text will read as if it had been produced abroad.

Title tags, meta descriptions and the choice between Sie and Du

Character versus pixel budget: Google renders titles by pixel width, not character count. A title full of narrow characters fits more text; a title with many wide capital letters and umlauts gets cut off sooner. The international median serves as a guide: according to the Web Almanac 2024, the median title length was 77 characters on desktop and 79 characters on mobile (HTTP Archive, 2024). For German pages with compound nouns, this means a higher truncation risk: a single long noun can run past the visible end. Put the primary keyword and the brand first and avoid filler words.

Avoiding title rewrites: Google replaces titles when it considers the HTML title unsuitable. Still, the HTML title remains the main source: according to Google, content from HTML title tags is used in more than 80 percent of cases for the displayed title link (Google Search Central, 2021). If you want to avoid rewrites, write concise, page-specific titles without keyword stuffing and without truncated compounds that Google could read as incomplete.

Meta descriptions: The meta description is not a ranking factor, but it does affect click-through rate. According to the Web Almanac 2024, only 66.7 percent of desktop pages had a meta description, while 98.0 percent of desktop pages had a title element (HTTP Archive, 2024). That is an easy lever: a hand-written German description with a clear value proposition and the variant of the term people actually search for sets you apart from competitors who leave the field empty or have it filled in automatically.

Form of address as a trust signal: In traditional B2B settings across the DACH region, the formal Sie is common, especially in long-established industries. The informal Du is established in startups, creative agencies and parts of the tech scene, and some B2B providers deliberately use Du as well. Which form fits depends on your target audience and brand positioning. What matters is consistency: switching between Sie and Du within a page or domain looks unprofessional and undermines the trust that E-E-A-T is supposed to build on-page. Decide on the form of address once and apply it across title, description, content and CTAs.

Heading hierarchy, entities and schema for German content

Heading hierarchy: A clean H1-to-H3 structure guides the reader and is a prerequisite for featured snippets and AI Overviews. It does not happen by itself: according to the Web Almanac 2024, only 70 percent of mobile pages had an H1 element (HTTP Archive, 2024), so around a third go without one. Write German subheadings as complete terms or as questions that match search intent rather than as clipped keywords.

Featured snippet readiness: Paragraph snippets come with a concrete length window. An analysis of 7,854 featured snippets showed that paragraph snippets get cut off at around 320 characters, and a target range of 40 to 55 words is considered helpful (Portent, international study). In German, this budget is harder to meet because compound nouns use up characters faster. Place a precise answer paragraph within this length window directly after a heading phrased as a question.

Keyword and entity research in German: German is a heavily inflected language. Account for singular and plural (Steuerberater, Steuerberatern), declension and synonyms. Regional variants matter most: Austrian German differs from the standard used in Germany in many places. Jänner instead of Januar, Sackerl instead of Tüte, Matura instead of Abitur, Erdäpfel instead of Kartoffeln. If you target an Austrian audience, use the AT variants where users actually search for them and do not blindly adopt the DE variant.

Schema markup on-page: Structured data should carry German-language values and declare the language correctly. Set inLanguage to de-AT when the page is served for Austria. For local providers, LocalBusiness is the central schema type: add the name, an address in Austrian format, opening hours and areaServed. Local entities (district, federal state, city) increase relevance for regional search queries and support recognition in AI systems.

GEO on-page: Generative engines such as AI Overviews, ChatGPT and Perplexity favor citable content. According to the Princeton study on Generative Engine Optimization, the top methods Cite Sources, Quotation Addition and Statistics Addition achieved a relative improvement of 30 to 40 percent on the Position-Adjusted Word Count metric, with the best methods reaching up to 41 percent (Aggarwal et al., 2024, GEO-bench with 10,000 queries). Applied to German content, this means: back up claims with sources, include concrete statistics and write precise, self-contained answer paragraphs that a generative system can quote directly.

Common mistakes in German on-page practice

Umlauts substituted the wrong way: The most common mistake is the ae/oe/ue spelling in visible content or, conversely, real umlauts in the URL slug. Both are the wrong way around. Umlauts belong in the text, the substitution belongs in the slug.

Dots dropped: Shortening Über to Uber changes the meaning and weakens entity recognition. In visible text, there is no reason to do without correct umlauts.

Compound blows the title budget: A title that starts with a 30-character compound leaves little room for brand and differentiation. Plan the character budget deliberately and use the separated variant if it gets searched more often anyway.

Inconsistent form of address: Switching between Sie and Du within the domain is a classic trust leak. Rule it out with a defined tone-of-voice guideline.

Treating DACH as a single market: AT, DE and CH differ in vocabulary and spelling. If you serve content written for Germany unchanged in Austria or Switzerland (for example with ß for Switzerland or Tüte instead of Sackerl for Austria), it comes across as imported.

hreflang missing or wrong: Without correct hreflang, the de-AT, de-DE and de-CH versions of the same content compete for the same snippets and create duplicate content signals across the DACH region.

hreflang, media and measurement

hreflang for the DACH region: If you run several German-language versions, declare them properly with hreflang: de-AT, de-DE and de-CH, plus an x-default. Each version references all the others and itself. This tells Google which version applies to which country and keeps a page written for Germany from capturing Austrian searchers. If you have only one version for the whole region, de or de-AT is enough, depending on your focus.

Image and media optimization: File names should use descriptive German terms, but in slug format with ae/oe/ue substitution: steuerberatung-wien-bilanz.jpg instead of IMG_2381.jpg. Alt texts, by contrast, are rendered and read, so here you use real umlauts and describe the image content in complete German. This serves accessibility and image search at the same time.

Metrics and measurement: Evaluate German on-page work against concrete signals. First, organic CTR relative to position: according to Backlinko, the first result on Google gets 27.6 percent of all clicks and has a ten times higher CTR than position 10 (Backlinko, international study). A below-average CTR at a good position points to a weak or truncated title. Second, the truncation rate: check regularly whether titles and descriptions get cut off in the preview. Third, the rate of title rewrites in Search Console: if your titles are replaced often, that is a signal to rework the wording. Fourth, how often you are cited in AI Overviews and generative engines, as a GEO indicator.

Further reading

German on-page specifics have the most impact when they mesh with the rest of your on-page work: a well-planned heading hierarchy, clean internal linking with German anchor texts, consistent schema markup with de-AT tagging and citable, source-based content for AI Overviews. For Austrian B2B providers, the combined effect is what counts: a precise German-language presence with a consistent form of address and technically correct markup that builds trust in both classic search and generative answer systems and stands out from the small German-language competitive field.