ccTLD vs Subdirectory vs Subdomain for International SEO

In the ccTLD vs subdirectory vs subdomain decision, most small businesses should choose a subdirectory (example.com/de/). It costs nothing extra, runs on the same site and CMS, and builds on the authority your main domain already has.

A country-code domain (example.de) gives the clearest country signal but means building a new site's reputation from zero, so it suits established brands with local teams. A subdomain (de.example.com) sits in between and makes sense mainly when a market needs separate hosting or a different platform. All three work for Google, as long as each version has its own URL and is connected with hreflang.

Below: a side-by-side comparison, when each option is worth it, and the mistakes that make the choice expensive to undo.

ccTLD vs subdirectory vs subdomain at a glance

Each structure trades a stronger country signal against higher cost and more maintenance.

Google sets out these options, with pros and cons, in its guide to managing multi-regional and multilingual sites. The table below combines that guidance with the practical costs for a small team.

There is a fourth option, URL parameters such as example.com?lang=de, which Google does not recommend because the versions are hard to segment and users cannot see the targeting. Skip it.

When is a ccTLD worth it?

A ccTLD is worth the cost only when local trust, legal requirements or a local team justify running what is effectively a separate website.

Country-code domains are the strongest signal Google has that a site is meant for one country. They also signal it to people: a German shopper may trust a .de shop more than a .com, especially for payments and returns. If you have a local entity, local support, a local marketing budget and a reason to look domestic, a ccTLD can pay off.

The costs are real, though. Each ccTLD starts with no links, no history and its own analytics and Search Console property. Some countries restrict who can register their domains, so check the registry rules first. And each domain can only target one country, so a German-language site for Germany, Austria and Switzerland needs either three domains or a different structure.

Be careful with domains that look like country codes but are not treated as such. Google treats a list of ccTLDs as generic because people use them generically, including .ai, .io, .co, .me, .tv and .fm. A .io SaaS company gets no German targeting from a .io domain; it needs subdirectories or subdomains plus hreflang, like any .com.

Why subdirectories win for most small businesses

A subdirectory gives each market its own crawlable URLs on the domain you already grow, which is the best trade of cost against results for a small team.

The main argument is concentration. Every link, mention and piece of content you earn builds one domain. A new /de/ folder starts life on a site that Google already crawls and trusts, rather than on an unknown domain. Shopify's own documentation for international SEO with Markets recommends subfolders for most stores, describing them as the easiest to set up and manage, with hreflang connecting the versions automatically.

The operational argument is just as strong. One CMS, one deployment, one analytics property, one sitemap. Adding a market is a folder and a translation workflow, not a new website. That matters when one or two people do all the publishing.

The weaknesses are manageable.

Google notes that users may not recognise the target country from the URL alone, and that everything sits on a single server location. hreflang fixes the first point for search engines. For the second, a CDN serves pages quickly everywhere, and Google itself describes server location as a signal that is not definitive. Set up the folder structure and hreflang together, following the international SEO strategy for the market choice and the hreflang tags guide for the annotations.

When does a subdomain make sense?

Choose a subdomain when a market genuinely needs separate infrastructure, not as a default.

Good reasons include running the second market on a different platform (for example, a regional store on its own ecommerce stack), needing a different server location for legal or performance reasons, or having a separate team that deploys independently. Google lists easy setup, different server locations and easy separation of sites as the advantages.

The trade-off is that a subdomain behaves more like a separate property to manage: its own DNS record, often its own hosting, and its own Search Console verification unless you use a domain property. If none of the reasons above apply, a subdirectory gives you the same targeting with less to maintain. If you do go this way on a no-code platform, the steps in connecting a custom domain cover the DNS side.

Common mistakes when choosing a structure

The costliest mistakes are the ones you only discover after launch, when changing structure means a migration.

• Choosing a ccTLD for prestige, then not staffing it. A .de site with no German link building and few German pages usually performs worse than a well-built /de/ folder.
• Assuming .io or .ai targets a country. Google treats them as generic. Without hreflang and local content they carry no country signal.
• Mixing structures without a reason. A .de domain for Germany, a subdomain for France and a folder for Spain triples the maintenance and complicates hreflang. Pick one pattern.
• Skipping hreflang because the URL "says" the language. Google's documentation states that language labels in subdomains such as en or de are not used to determine the audience. You still need hreflang.
• Redirecting by IP or browser language. Googlebot mostly crawls from the US, so automatic redirects can hide your other versions. Use a switcher.
• Switching structure casually. Moving from subdomains to subdirectories, or from a ccTLD to a folder, is a site migration. Plan it with a migration checklist that protects rankings and one-to-one 301 redirects.

The one-line rule: pick the structure you can maintain for years, because the second-best structure kept consistent beats the best structure changed twice.

Frequently Asked Questions

Is a subdirectory or subdomain better for SEO?

For most sites a subdirectory is the better choice. It lives on your main domain, so new language or country pages benefit from the reputation that domain has already built, and it is easier to manage. A subdomain is worth it mainly when a market needs separate hosting, a different platform or independent deployment.

Does a ccTLD rank better than a .com?

A ccTLD does not automatically rank better, but it sends Google its clearest signal that a site targets one country, and local users may trust it more. A new ccTLD starts without links or history, so a well-built subdirectory on an established .com can outperform it. The ccTLD advantage pays off mainly for brands investing locally.

Does Google treat .io and .ai as country domains?

No. Google treats several country-code domains as generic because people use them generically, including .io, .ai, .co, .me and .tv. A site on one of these domains gets no country targeting from the domain itself. Use subdirectories or subdomains with hreflang to target specific countries or languages.

Can I change from subdomains to subdirectories later?

Yes, but it is a site migration. Every old URL needs a one-to-one 301 redirect to its new equivalent, hreflang and canonical tags must be updated to the new URLs, and sitemaps resubmitted. Expect some temporary ranking movement while Google processes the change. Plan it carefully and avoid changing structure more than once.

Do I still need hreflang with a ccTLD?

Usually yes, if the same content exists in other versions. A ccTLD tells Google which country a site targets, but hreflang tells it which pages are equivalents across your domains. Google's documentation confirms alternates can sit on different domains. Without hreflang, Google may show the wrong country version to searchers in shared-language markets.

Choosing between ccTLD vs subdirectory vs subdomain

The ccTLD vs subdirectory vs subdomain choice is mostly a resource decision. Choose a subdirectory unless you have a clear reason not to; choose a subdomain when a market needs separate infrastructure; choose a ccTLD when you have a local team, a local budget and a reason to look domestic. Whatever you choose, give each version its own URL, connect versions with hreflang, and keep the pattern consistent.

The structure is a one-time decision. Filling each market folder with well-researched, localised content every month is the ongoing work. Agent Solo's Growth plan publishes in two languages with hreflang, canonicals and per-market keywords, and the Scale plan handles up to five languages. If your second market folder is still empty, request early access.