Should you really give up national domains for a generic .com in international SEO?

Why does Google distinguish between generic domains and national domains?

The fundamental difference lies in the rigidity of the geographical signal. A national domain like .de or .fr sends a fixed signal to Google: this site targets Germany or France, end of story. It is impossible to change this setting in Search Console.

Generic domains (.com, .net, .org, .info) send no geographical signal by default. Google considers them neutral until a country is assigned via the international targeting setting in Search Console. This neutrality becomes an asset when aiming for multiple markets.

How does geographical targeting work in Search Console?

For a generic domain, Search Console allows you to set a primary target country at the root domain level or for each subdomain. For example: example.com can target France, de.example.com targets Germany, uk.example.com targets the United Kingdom.

This flexibility completely disappears with a .de or .fr. The domain is locked to its country of origin, regardless of content, language, or structure changes. Even a .de hosted in the United States with English content will remain geographically anchored in Germany.

What is the reasoning behind this recommendation for multilingual setups?

Google advocates for a centralized architecture: a single generic domain with subdirectories or subdomains by language. The main argument is the pooling of domain authority — all backlinks and quality signals converge to a single root.

With separate national domains (.fr, .de, .es), each site rebuilds its authority from scratch. Backlinks to the .fr do not benefit the .de. It's like managing five small sites instead of one large one — more costly in SEO efforts, content production, and link building.

• Fixed geographical signal for ccTLDs (.fr, .de) vs configurable for gTLDs (.com, .net)
• Centralization of authority on a generic domain with subdirectories or subdomains
• Flexibility in targeting via Search Console to adjust country by country without redesigning the architecture
• Reduced SEO costs: one domain to optimize rather than multiple independent national sites

Is this statement consistent with what we observe in practice?

Partially. On paper, the logic holds: a .com with subdirectories pools authority and simplifies management. In practice, national domains often perform better in their local market than .com/fr or .com/de subdirectories — especially when local competition is strong.

Several case studies show that users and Google place greater trust in ccTLDs in their country. A .fr inspires more credibility in France than a .com/fr, even though Google claims to treat both equivalently. [To be verified]: the real impact of the TLD on click-through rates and conversions remains debated; public data is scarce.

In what cases is a national domain still preferable?

If your brand targets a single market in the long term, .fr or .de remains a solid choice. The geographical signal is stronger, user trust is better, and you avoid the complexity of a poorly calibrated multilingual infrastructure.

Local e-commerce sites, regional B2B services, and national media have no interest in diluting their signal with a .com. Trying to keep the door open to international opportunities “just in case” often leads to a clumsy strategy: neither truly local nor genuinely global.

Is Search Console targeting really enough to compensate for a ccTLD?

Google claims it is, but no official data quantifies the performance gap. In theory, defining “France” in Search Console for a .com should be equivalent to a .fr. In practice, many practitioners observe that the ccTLD remains a stronger signal.

The real issue is that Search Console targeting is binary and exclusive: you can only target one country per domain or subdomain. If your .com targets France, it loses its universality — you might as well choose a .fr from the start. The flexibility touted by Google only exists if you structure with subdomains or subdirectories, which brings us back to architectural constraints.

What should you do concretely based on your situation?

If you are starting a project that is clearly multilingual or multi-country, opt for a generic domain with a subdirectory architecture (example.com/fr/, example.com/de/) or subdomains (fr.example.com, de.example.com). Set up geographical targeting in Search Console for each section.

If your business remains anchored in a single national market, the ccTLD remains relevant. Don’t complicate your life with a .com “just in case” if you have no concrete international projects in the next 18 months. A well-optimized .fr will always outperform a poorly structured .com/fr.

How to migrate from a ccTLD to a generic domain without breaking everything?

Prepare a flawless technical migration: complete 301 redirects, perfectly configured hreflang, verified Search Console targeting. Anticipate a temporary drop in visibility — Google needs time to reassess your geographical signals.

Monitor Search Console daily for the first 8 weeks. Ensure that the local versions index correctly and that organic traffic by country does not collapse. If the migration is poorly executed, you could lose 30 to 50% of your local visibility for several months.

What mistakes to avoid in geographical targeting?

Never mix signals. If you use a generic domain with subdirectories, do not set country targeting at the root level — leave it neutral and only target the subdirectories. A .com targeting “France” with a /de/ targeting “Germany” creates algorithmic confusion.

Avoid hybrid architectures: a mix of ccTLD and .com subdirectories dilutes your authority without providing any benefits. Choose a logic and stick to it. And, above all, do not launch a language version without substantial content — a /es/ with three hastily translated pages does more harm than good.

• Audit your international strategy: one single market or multiple countries in the medium term?
• Choice of architecture: subdirectories (.com/fr/) or subdomains (fr.example.com) depending on your technical resources
• Search Console setup: geographical targeting by section, never at the root level if multilingual
• Mandatory hreflang: rigorous implementation to avoid cannibalization between language versions
• Detailed migration plan if moving from ccTLD to gTLD, with intensive monitoring post-launch
• Localized content production: each language version must have substantial volume, not just a symbolic translation