To target Germany, Austria and Switzerland with German content, start with one German site and add hreflang de-AT and de-CH versions only when the pages genuinely differ for those countries: different prices or currency, payment methods, offers, legal details or vocabulary. When you do, mark the main version as de (all German speakers), the variants as de-AT and de-CH, add an x-default, and make every version reference all the others, including itself.
This guide covers when one German site is enough, when country variants earn their keep, how to implement hreflang for DACH correctly, and the spelling, vocabulary and pricing differences that justify separate pages.
One German site or separate DACH versions?
A single German-language site can rank in all three countries. Google serves results according to the searcher's language and location, and Austrian and Swiss users read standard German without difficulty. Splitting into versions multiplies maintenance, so it should solve a real problem.
| Situation | Recommended setup |
|---|---|
| Same offers, same prices in euros, little AT or CH traffic | One German site, neutral standard German, hreflang only if you have other languages |
| Same offers but Swiss visitors need CHF prices and TWINT | German site plus a de-CH version of commercial pages |
| Different providers or offers per country (insurance, telecoms, energy, local dating or cam promotions) | Separate de-DE, de-AT and de-CH versions of the affected pages |
| Swiss French- and Italian-speaking audiences matter | Add fr-CH and it-CH alongside de-CH |
You do not have to localise the whole site. A common pattern is to localise only the money pages (comparisons, reviews, pricing pages) and keep general guides as one German version.
Rule of thumb: if you would not change anything on a page for an Austrian or Swiss visitor except the hreflang tag, that page does not need a country version.
hreflang de-DE, de-AT and de-CH explained
Google's documentation on localised versions sets the rules. The value is a language code (ISO 639-1), optionally followed by a region code (ISO 3166-1 alpha-2). You cannot specify a country on its own.
- de: German, for any region. Use it for your main German version so German speakers in Germany, Liechtenstein, Luxembourg, Belgium and elsewhere have a match.
- de-DE, de-AT, de-CH: German for Germany, Austria and Switzerland specifically.
- x-default: the fallback for users whose language or region matches nothing, often a language selector or your main version.
A frequent mistake is publishing de-DE, de-AT and de-CH with no plain de version. German speakers outside those three countries then match none of them and fall back to x-default. Either label your German-German version as de, or add de as an extra annotation pointing to it.
How to implement hreflang for DACH
Hypothetical example for a page with a main German version, an Austrian variant and a Swiss variant, placed in the head of every one of the three pages:
<link rel="alternate" hreflang="de" href="https://example.com/de/vergleich/" />
<link rel="alternate" hreflang="de-AT" href="https://example.com/de-at/vergleich/" />
<link rel="alternate" hreflang="de-CH" href="https://example.com/de-ch/vergleich/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/de/vergleich/" />
- Include every version on every version. Each page lists all alternates, including itself.
- Make links reciprocal. If the Swiss page points to the Austrian page, the Austrian page must point back, or Google may ignore the pair.
- Use canonical URLs. Each version should be self-canonical. Do not canonicalise de-AT and de-CH to the German page, or they will drop out of results.
- Pick one method. HTML link elements, HTTP headers or XML sitemaps all work. Sitemaps are easiest for large sites; do not mix methods inconsistently.
- Do not auto-redirect by IP. Suggest the local version with a banner instead, so users and Googlebot can reach every version.
For the wider multi-language picture, including other languages and CMS setups, see hreflang for multilingual affiliate sites.
URL structure
Subfolders (/de/, /de-at/, /de-ch/) on one domain keep authority together and are the simplest option for most affiliate sites. Separate .de, .at and .ch domains send a stronger local signal but each needs its own links. See SEO for German websites for the trade-offs.
Spelling, vocabulary and pricing differences that justify variants
Switzerland (de-CH)
- No ß. Swiss standard German writes "ss": Strasse, Grösse, gross. This is the most visible marker of a Swiss version.
- Vocabulary. Examples include Velo (bicycle), parkieren (to park), Trottoir (pavement) and grillieren (to grill).
- Currency and number format. Prices in CHF, often written CHF 49.90 or Fr. 49.90, with an apostrophe for thousands (1'299.00).
- VAT and payments. Swiss VAT (8.1% standard rate), TWINT at checkout; see affiliate marketing in Switzerland.
Austria (de-AT)
- Vocabulary. Jänner (January), Paradeiser (tomatoes), Erdäpfel (potatoes), Sackerl (bag).
- Prices and VAT. Euros like Germany, but a 20% standard VAT rate, so VAT-inclusive prices can differ.
- Payments and providers. eps bank transfer, and Austrian providers in regulated verticals; see affiliate marketing in Austria.
Legal and contact details
Legal notices, consumer information and support details can differ by country. A de-AT or de-CH version is a natural place to show the right legal information, local support routes and country-specific terms.
Will near-identical versions cause duplicate content problems?
Not in the sense of a penalty. If de-AT and de-CH pages are almost identical to the German page, Google may treat them as duplicates and choose one to show, but hreflang helps it serve the right one to each country. The more genuinely localised the versions are (currency, spelling, offers, details), the more reliably each will be shown where it belongs.
Check results in Google Search Console with country filters after launch, and look for the wrong version ranking in the wrong country. That usually points to missing return links, conflicting canonicals or versions too similar to tell apart.
DACH hreflang launch checklist
- List the pages that genuinely differ by country and localise only those.
- Decide the URL pattern (/de/, /de-at/, /de-ch/) and keep it identical across page types.
- Label the main version de, add de-AT, de-CH and x-default.
- Generate hreflang from one source, such as your CMS or sitemap, so additions stay reciprocal.
- Make every version self-canonical and indexable.
- Replace IP redirects with a dismissible country suggestion banner.
- Check affiliate links: Swiss and Austrian pages should point to offers and landing pages that serve those countries.
- After launch, review Search Console by country for a few weeks and fix any version showing in the wrong market.
Frequently asked questions
Should my main German version be de or de-DE?
Use de if it is meant for German speakers generally, which is usually the case. Use de-DE only if you also have a separate generic de page or the content is strictly German-specific.
Can I target Austria with hreflang if my site has no Austrian version?
No. hreflang points users to alternative versions; it does not create relevance. Without an Austrian version, your German pages will simply be shown to Austrian users where they are relevant.
Is Swiss German dialect needed for de-CH?
No. Swiss websites are written in Swiss standard German, not dialect. The key changes are ss instead of ß, Swiss vocabulary, CHF prices and local details.
Next steps
If you are still deciding whether Austria or Switzerland deserve their own versions, read the market guides for Austria and Switzerland. For hreflang audits and multilingual tools, browse our webmaster software and services directory, and see the full Germany, Austria and Switzerland section.