SEO
How to Decide: ccTLDs vs Subdirectories for International SaaS
The short answer for SaaS teams under 300 employees
ccTLDs (yoursite.de, yoursite.fr) and subdirectories (yoursite.com/de/) both signal geographic targeting to Google, but they distribute authority in opposite ways. ccTLDs give an explicit country signal and start every domain at zero authority. Subdirectories keep all link equity on one root domain and inherit whatever crawl signals you already have. For B2B SaaS targeting two or more markets with a single SEO team, the ccTLD vs subdirectory SEO decision defaults to subdirectories. The exceptions are narrow, and this post lays out where they apply.
Most published advice on this topic assumes enterprise resources: dedicated country-level SEO teams, separate link-building budgets per market, local PR agencies on retainer. That is not the reality for 50 to 300 person SaaS companies. This post is calibrated for that band, with a decision matrix in section four if you want to skip to a specific scenario.
Key Takeaways
Subdirectories win for SaaS teams entering 3+ markets with one central SEO function because link equity compounds on a single root domain.
ccTLDs start at zero domain authority per country and typically take 12 to 18 months to reach ranking parity in competitive verticals.
A .de domain costs roughly €15 per year, but the real cost is a parallel SEO program (GSC, sitemaps, backlinks) for every ccTLD you launch.
Subdomains carry ccTLD-level overhead without the geographic trust signal, plus they introduce subdomain-takeover risk that harms root-domain SEO.
Hreflang is required either way. Choosing subdirectories does not remove it, only slightly reduces the error surface.
What do ccTLDs and subdirectories actually signal to Google?
ccTLDs tell Google a domain belongs to one country, explicitly, at the TLD level. Subdirectories tell Google a section of an existing site targets a specific locale, mostly through hreflang tags and localized content. Both are valid international targeting methods under Google's own guidance on managing multi-regional and multilingual sites.
The mechanical differences matter more than the theoretical ones. A ccTLD is a separate property in Search Console, has its own crawl queue, and starts authority accumulation at zero. A subdirectory is processed as part of the root domain, inheriting crawl budget, existing indexing signals, and whatever domain authority you have already built.
One nuance that trips up teams: the GSC International Targeting tool only offers geographic targeting for subdirectories and subdomains. You cannot set a country target for a ccTLD in Search Console because the TLD already defines it. That is not a limitation, it is by design, and it explains why hreflang errors on a ccTLD tend to be harder to diagnose from GSC alone.
What does a ccTLD really cost beyond the €15 registration fee?
A .de domain renewal is a rounding error. The actual cost is the SEO infrastructure required to make it rank. Every ccTLD needs its own link-building program, its own Search Console property, its own sitemap management, its own performance reporting stack. For a SaaS team targeting Germany, France, and the Netherlands at the same time, that triples the operational load before a single localized page ships.
The failure pattern we see in audits is thin localization. A team spins up yoursite.de, translates the homepage and pricing page, and calls it launched. Six months later the .de domain has fewer than ten referring domains, no organic traffic, and Google is quietly treating the pages as near-duplicates of the .com. According to the Impression Digital analysis of international SEO structures, a ccTLD makes it "almost impossible to rank in any country other than the one targeted", which cuts both ways: excellent geographic focus if you feed it, dead weight if you do not.
Practical threshold from our engagements: ccTLD investment starts producing positive ROI when you have a dedicated content and link operation per country. That usually appears around 200-plus employees, or when per-country ARR justifies a local agency retainer. Before that, you are paying enterprise overhead on a mid-market budget. If backlinks are a bottleneck, the honest fix is a real off-page program, not a domain-structure change. Our digital PR playbook for B2B SaaS covers where those links actually come from.
How does domain authority accumulate across each structure?
Every backlink pointing to yoursite.com/de/ strengthens yoursite.com. Every backlink pointing to yoursite.de strengthens yoursite.de only. That structural difference is the entire game for SaaS companies that have already built root-domain authority and do not want to fragment it across five country-level properties.
Amazon runs amazon.co.uk, amazon.de, and amazon.fr as separate ccTLDs because each has accumulated independent authority over two decades of link acquisition and brand queries. Apple, Samsung, and HP use subdirectory structures specifically to keep authority consolidated on one root domain. The difference is not preference. It is operational scale and per-market investment capacity.
For a five-year-old SaaS with a DR 55 root domain, launching a new .de in a competitive vertical typically means 12 to 18 months of ramp before ranking parity with established local domains. That timeline conflicts with almost every SaaS international launch plan we see. Subdirectories inherit the DR 55 immediately, which is the whole point. Root-domain authority is a lever you only get to pull once. Our technical SEO checklist covers the on-site cleanup that makes that authority actually convert into rankings.
Decision matrix: matching URL structure to your SaaS stage
The right structure follows from four variables: root domain authority, number of markets entered simultaneously, team capacity for parallel SEO programs, and whether a local TLD materially affects buyer trust in that country (notably .de in DACH procurement).
Factor | ccTLD | Subdirectory |
|---|---|---|
Domain authority required | High (competitive DA per ccTLD) | Any (inherits root) |
Markets targeted simultaneously | 1 to 2 | 3 or more |
Team capacity | Dedicated local program per country | Single central SEO team |
Setup and ongoing cost | High | Low |
Geographic signal strength | Explicit, strongest | Moderate, hreflang-dependent |
Conversion trust in target market | High (notably .de in DACH) | Moderate |
Time to rank in new market | 12 to 18 months from zero | Faster, inherits root |
ccTLD makes sense when you are entering one high-value market with a dedicated local SEO resource and a root domain already competitive there. A DACH-first SaaS going all-in on Germany before expanding elsewhere is the textbook fit.
Subdirectory makes sense when you are expanding to three or more EU markets with one team, root DR is above 40, and the product UX is already localized.
A hybrid also exists: ccTLD for the primary revenue country plus subdirectories for secondary markets. It is operationally messy but defensible when one country drives 60 percent or more of international ARR.
Why do subdomains rarely make sense for international SaaS?
Subdomains (de.yoursite.com) split domain authority like ccTLDs but without the geographic conversion trust that makes ccTLDs worth the investment. Google can associate subdomains with root domains, but link equity and crawl budget do not consolidate as cleanly as with subdirectories. You get the overhead of a separate property with none of the ".de looks German at checkout" benefit.
There is a second problem that never appears in the marketing-heavy comparison posts: subdomain takeover. A deprecated Heroku, Fastly, or S3 endpoint still pointed to by a stale DNS record can be claimed by an attacker, who then serves malicious or spammy content under your domain. Google penalizes the root, not just the subdomain. This is exactly the SEO-security overlap we've broken down before, and it is one reason Gravidy reviews subdomain architecture as part of both SEO audits and security assessments.
The cases where subdomains do make sense (docs.yoursite.com, app.yoursite.com, status.yoursite.com) are product architecture decisions, not international SEO decisions. If someone recommends de.yoursite.com for a new EU market, ask them what problem it solves that /de/ does not.
Does hreflang change based on which structure you pick?
No. Both structures need correctly implemented hreflang, and both fail the same way when it is broken: wrong-locale rankings, duplicate-content signals, or German users landing on English pricing pages. Choosing subdirectories does not remove the hreflang requirement, it only slightly reduces the error surface because the tags point to path variants on one domain instead of across separate roots.
The most common hreflang errors we find in audits are missing self-referential tags, incomplete reciprocal annotations between alternates, and incorrect ISO codes (de vs de-DE). The x-default tag also matters more than teams realize when the SaaS has a global-English signup flow that does not map cleanly to any one country. Google's own hreflang guidance is the reference to check against, not whatever your CMS plugin auto-generates.
One implementation trap specific to modern SaaS stacks: if you inject hreflang tags via client-side JavaScript, Googlebot may not process them reliably during indexing. Tags must appear in the server-rendered HTML response. We covered this pattern in more depth in the hydration trap post, which applies directly to Next.js and Nuxt teams shipping localized routes.
Frequently Asked Questions
Is a subdirectory better than a subdomain for international SEO?
For most SaaS teams, yes. Subdirectories consolidate authority on the root domain and avoid the security exposure that comes with unclaimed or deprecated subdomains. Subdomains carry the same operational overhead as ccTLDs without the explicit geographic trust signal that makes ccTLDs worth the cost. The cases where subdomains do make sense (a docs site, a product app, a status page) are product architecture decisions, not international SEO ones.
What is the best URL structure for international SEO?
For B2B SaaS under 300 employees targeting multiple EU markets with one SEO team: subdirectories with hreflang. For a company committing deeply to one country with a dedicated local marketing resource and sufficient root-domain authority: ccTLD. There is no third option that outperforms both. The "best" structure is the one your team can execute correctly and maintain for 18 months without fragmenting link acquisition efforts.
Does a ccTLD actually improve local rankings?
Yes, in that specific country, and only there. A .de domain carries an explicit German geographic signal that a subdirectory approximates but does not match. That signal only materializes if the ccTLD has enough domain authority to compete. A brand-new .de with three referring domains will not outrank a well-linked /de/ subdirectory on a DR 55 root domain, regardless of how German the TLD looks.
Where to go from here
The ccTLD vs subdirectory call is one of the few SEO decisions that is difficult to reverse once link equity accumulates in the chosen structure. Most B2B SaaS sites we audit have three to five international-SEO issues (broken hreflang, wrong-locale canonicals, or subdomain architecture that leaks authority) sitting in plain sight and quietly costing organic pipeline in the target market. If you want a second opinion on which fixes are draining your traffic before you commit to a domain strategy, book a Free SEO Audit Call. Thirty minutes, specific findings, no slide decks.
