Domain Strategy: ccTLD vs Subfolder vs Subdomain

Why domain strategy determines success in DACH

If you run an Austrian B2B company and want to grow beyond the national border, you face a consequential decision early on: How do I structure my domains for multiple countries and languages? The answer determines whether link authority consolidates or splinters, how clearly Google recognizes your geographic targeting, and how expensive operations become.

The market is real. At the start of 2025, Austria had 8.69 million internet users at 95.3% online penetration. Search engine optimization here effectively means Google optimization: in May 2026, Google held around 81.87% of the search engine market in Austria. Your domain strategy therefore has to work for Google above all.

At the same time, the .at ccTLD is an established local signal: nic.at manages over 1.5 million registered .at domains. In the Austrian market, the .at extension is a familiar trust signal dominated by domestic owners: according to a 2018 nic.at analysis, 72.6% of .at domains were held by Austrian owners.

How it works: how Google evaluates geotargeting

Google reads the geographic targeting of a page from several signals. One particularly strong signal is the domain extension. According to Google Search Central, country-code top-level domains provide a strong, clear geotargeting signal to users and search engines, make server location irrelevant, and allow a clean separation of sites. The main drawback: a ccTLD can only ever target a single country.

With generic TLDs (subfolders and subdomains), this strong signal disappears. Google names a shared drawback of these structures: users often can't recognize the geotargeting from the URL alone, because it remains unclear whether "de" refers to the language or the country. You close this gap with hreflang annotations.

Important in practice: Google crawls from a single source. According to the documentation, Google does not vary the crawl source for a site, and most crawls come from the US. The practical consequence is blunt: Google does not discover language and country versions on its own through different crawl locations. You have to declare every variant explicitly, for example through hreflang entries, ccTLDs, or explicit links.

Server location plays a minor role. According to Google, it is a signal, but not a definitive one, because many sites use CDNs or host in countries with better infrastructure. With a ccTLD, location is irrelevant anyway. With gTLD structures, subdomains allow different server locations, while a subdirectory is tied to a single location. In practice, a CDN solves this performance aspect for subfolder structures without shifting the geo signal.

Strategy: decision matrix ccTLD vs subfolder vs subdomain

Three structures, three profiles. Which one fits depends on your resources and goals.

ccTLD (e.g., company.at, company.de): Strongest geo signal, highest local trust, clean separation of markets. The price: every domain starts its authority at zero. Link equity spreads across several domains instead of consolidating. Running, registering, and maintaining multiple ccTLDs creates ongoing costs. This makes sense if you serve a few strategically central markets with a strong local focus and have the budget for separate link building in each country.

Subfolder (company.com/at/, company.com/de/): The recommended standard for most companies in 2026. All country versions share one domain and therefore the entire domain authority. A backlink to any subpage strengthens the whole domain. Lower costs, high scalability, simplest migration when you expand later. The geo signal is weaker than with a ccTLD and has to be offset through hreflang and local signals (language, currency, address, links from local websites). Search Console no longer has a country setting: Google retired the International Targeting report in September 2022.

Subdomain (at.company.com, de.company.com): Google tends to treat subdomains as standalone sites. Authority then fragments much like with ccTLDs, without their strong geo signal. The advantages are the option of different server locations and a technical separation, which can help when tech stacks differ significantly by market. If international SEO is your only concern, a subdomain is rarely the first choice.

The core logic: subfolders consolidate link equity, ccTLDs and subdomains fragment it. If you don't want to build a strong brand per country and care about consolidated authority, subfolders are your best option.

Implementing hreflang correctly

hreflang is the bridge between language and country versions. Even so, adoption is low and the error rate is high. According to the 2022 Web Almanac, only 9.6% of sites on desktop and 8.9% on mobile used hreflang tags. German is rarely annotated: according to the same source, the hreflang value "de" reached 2.2% on desktop and 2.0% on mobile, while x-default stood at 4.0% on desktop and 3.7% on mobile.

Above all, implementation is error-prone. An Ahrefs analysis of 374,756 domains using hreflang found that 67% of them had at least one error. The most common single error was a missing x-default, followed by missing self-referencing tags and references to redirected or broken pages.

Here is how you avoid the typical pitfalls:

Return tags (reciprocity): Every language version has to reference all the others, including itself. If the AT page points to the DE page, the DE page has to point back to the AT page. If the return link is missing, Google ignores the annotation.

x-default: Set an x-default version for users whose language or country isn't covered. A missing x-default is the most common error of all.

Correct ISO codes: Language per ISO 639-1, optionally country per ISO 3166-1 alpha-2. So de-AT, de-DE, de-CH. A language-only value "de" applies to all German-speaking regions.

Avoid canonical conflicts: Every language version gets a self-referencing canonical. A canonical that points from the AT version to the DE version overrides the entire hreflang logic.

DACH specifics: de-DE vs de-AT vs de-CH

The DACH region is the practical case where one language meets three markets. This is where you decide whether to run a shared German-language version or separate by country.

One subfolder per country (/de/, /at/, /ch/): Makes sense if the content genuinely differs: prices in euros vs. francs, legal notices, local contacts, Austrian vs. German vocabulary (Jänner instead of Januar for January, terminology, forms of address). With clean hreflang de-AT, de-DE, and de-CH, you signal the respective target region to Google.

One shared de version: Justifiable if your offering, prices, and legal framework are identical across all three markets and there is no need for local differentiation. It saves maintenance effort but gives up the chance to precisely serve Austrian search queries with a local angle.

For the Austrian market, the .at extension is an argument of its own. It works as a local signal and a trust signal because it is widespread in the market and predominantly held domestically. If Austria is your core market, you can use a .at ccTLD as your main presence and add EU expansion through subfolders, provided your budget can carry the separate authority.

Content localization instead of mere translation

Structure is only the shell. Conversion comes from real localization. According to an international CSA Research study, 76% of online shoppers prefer product information in their own language, and 40% never buy from websites in another language. The study is B2C and global (29 countries), but the basic pattern holds in B2B too: content in the buyer's own language lowers the barrier to purchase.

Localization means more than translation. It covers local examples, currency, legal framework, tone, and market-specific keywords. This is exactly where domain architecture pays off: a subfolder or ccTLD structure with clean hreflang ensures that the localized version is served to the right market instead of competing with other language versions for the same ranking.

Programmatic SEO and scalable country content

If you create country-specific content at scale, such as location, industry, or use-case pages per market, you need an architecture that scales with minimal friction. Subfolders are made for this: new markets mean new directories on the same domain, which immediately benefit from the existing domain authority. A ccTLD strategy requires a new domain with its own authority building for every new market, which slows programmatic SEO down considerably.

Important for content at scale: every generated country page has to offer real local content (prices, contacts, legal information, examples) and be cleanly annotated with hreflang. Masses of thin, near-identical translations without localization are a quality risk, not a scaling advantage.

Common mistakes

Choosing a subdomain on the assumption that it behaves like a subfolder: Google tends to treat it as a separate site, and authority fragments.

ccTLDs without a budget for separate link building: Every domain starts at zero. Without dedicated authority building per country, visibility stays weak.

hreflang without return tags or without x-default: According to the research, both errors are among the most common. Without return tags, Google ignores the annotation. Without x-default, users whose language or country has no version of its own get no fallback page.

Canonical points to another language version: This overrides hreflang and causes the wrong version to rank.

Underestimating migration: Changing your domain strategy takes a lot of work. Without clean 301 redirects, you risk traffic drops and long re-indexing phases.

Migration and internationalization risks

Making the right choice at the start saves you the most expensive operation: migration. If you later consolidate from ccTLDs to subfolders or the other way around, you have to redirect every URL with a 301 redirect, set up hreflang again, and expect temporary ranking and traffic losses until Google has re-indexed the new structure. Depending on site size, this phase lasts weeks to months.

A practical decision tree for Austrian B2B companies expanding into DACH or the EU:

Few strategic markets, strong local focus, budget for link building per country: One ccTLD per market, at least .at as your Austrian home presence.

Many markets or planned scaling, consolidated authority wanted, limited resources: Subfolders with clean hreflang. This is the default for most cases.

Significantly different technical requirements per market: A subdomain only if the technical separation justifies the loss of authority.

Metrics and measurement

You measure the success of a domain strategy per market, not in aggregate. Relevant metrics:

Organic traffic and rankings by country: Analyze them separately in Search Console per property or per subfolder. Are Austrian rankings rising for locally relevant keywords?

hreflang errors: Check them regularly with an SEO crawler. Tools like Screaming Frog report missing return tags, missing x-default, and references to redirected pages. Search Console has not shown hreflang errors since Google retired the International Targeting report.

Indexing per language version: Is the right version served in the right market, or do versions compete for the same search query?

Domain authority and backlink distribution: Is link equity consolidating as planned, or is it splintering across several domains?

Conversion per localized version: Shows whether localization actually drives conversion and doesn't just generate traffic.

Further reading

Domain strategy is the foundation on which hreflang, content localization, international keyword research, and programmatic SEO build. If you are planning for the DACH region, decide on the structure first (in most cases subfolders, with .at as an addition if Austria is your core market), then set up hreflang cleanly and invest the money you save in real localization instead of mere translation. Topics worth exploring further are hreflang implementation in detail, international link building strategies, and CDN and server location decisions for gTLD structures.