What Is International SEO? URL Structure and Strategy

The first decision in any international SEO project is where the different versions of the site will live, because a large share of the later maintenance depends on it. There are three models, and each one distributes geographic signal, operating cost, and accumulated domain authority differently.

The first model is the country-code domain, or ccTLD, for example example.de for Germany and example.fr for France. It's the strongest geographic signal available: Google reads the ccTLD as an explicit market declaration, with no extra configuration needed. The cost is high on two fronts. Each domain has to be bought, renewed, and in some countries hosted locally, and each version starts from zero authority, because backlinks pointing at example.de do nothing for example.fr. Keeping content current across six or seven ccTLDs means, in practice, running six or seven separate websites.

The second model is the subdomain, for example de.example.com for the German market. It's set up with a simple DNS record, no new domain purchase required. The geographic signal sits in the middle: it can be reinforced through the country setting in Search Console, but it lacks the automatic weight of a ccTLD. On authority, search engines treat each subdomain as a semi-independent entity, so there's still no full transfer between versions, even though the SSL certificate, server, and often the design template are shared.

The third model is the subfolder, for example example.com/de/ for the German market. It's by far the easiest to maintain: one installation, one certificate, one analytics dashboard for the whole site. All the authority from backlinks, mentions, and domain age accumulates in a single place and benefits every language version equally. Its geographic signal is the weakest of the three and depends almost entirely on hreflang and content signals such as the language of the text, the currency, or a local phone number. It's the model zds.es itself uses: /que-es-seo-internacional for Spanish and /en/what-is-international-seo/ for English, under the same domain and sharing all its accumulated authority.

No model is universally better, and picking one without weighing your own resources is the most expensive mistake in the whole process. A multinational with local teams in every country, an independent SEO budget per market, and a need for maximum brand differentiation often justifies the operating cost of several ccTLDs. A business expanding its three or four main languages from one central site, without a dedicated team in each country, is almost always better off with subfolders: less upkeep and shared authority from day one. The subdomain sits in the middle, useful when there's a technical reason to keep infrastructure separate, for instance a different CMS per region, but no budget for standalone domains.

A common mistake when planning international SEO is treating "language" and "country" as the same variable. They aren't, and confusing them produces either poorly segmented sites or, at the other extreme, a flood of versions nobody maintains. German is spoken in Germany, Austria, and Switzerland, but those are three markets with different prices, different tax rules, and sometimes different product availability: what sells in Germany at 19 percent VAT gets billed in Swiss francs in Switzerland and doesn't fall under the same EU data protection rules. The same holds for Spanish across Spain, Mexico, and Argentina, or for English across the UK, the US, and Australia: same language, different commercial and legal conditions.

Hreflang lets you combine both dimensions when needed, precisely because they're designed as independent axes. The plain language tag, for example "de", covers a German version aimed at any German-speaking user, with no country distinction. The language-country combination, for example "de-CH", covers German speakers in Switzerland specifically, with its own price in francs and its own legal requirements. How many combinations make sense isn't a technical call, it's a business one: a new country-language version is worth creating only when something genuinely changes for that market, price, legal requirements, product availability, or support, not out of sheer completeness or because a dedicated URL per country "looks more thorough."

This distinction also feeds back into the URL structure covered above. A single /de/ subfolder works fine when the German-speaking market is treated as one homogeneous block. If the company sells under different terms in Germany, Austria, and Switzerland, it needs separate subfolders, say /de-de/, /de-at/, and /de-ch/, or the equivalent in whichever domain model was chosen, and each one needs its own price, its own legal text, and its own hreflang tag to distinguish it from the others.

The opposite case is just as common: companies that spin up a separate country version for every Spanish-speaking market, Mexico, Argentina, Colombia, Chile, with no real difference in offer between them beyond minor wording. In that scenario, maintaining four nearly identical versions dilutes the content and link budget with no real advantage over a single general Spanish version tagged hreflang "es" with no country attached.

International SEO is the full strategy: which markets to target, which URL structure to use, which content to translate or adapt, and which technical signals to send for each version. Hreflang is one of those technical signals, specifically the one that tells Google which language or country version to show a given user in the search result. It's a piece of the overall plan, not the plan itself, and a site can have technically flawless hreflang and still fail at international SEO if the URL structure doesn't match available resources, or if each market's content is an unadapted translation with no local pricing or legal terms behind it.

The implementation details of hreflang, the rel="alternate" tags, the special x-default value, and the difference between placing it in the head, an XML sitemap, or an HTTP header, have their own article with full code examples and the six most common mistakes documented with real cases: what is hreflang. For this article, it's enough to know that this piece exists, what it does within the wider strategy, and that it only works properly when each version's canonical tag points to itself.

Before launching or expanding a site into several markets, it's worth checking:

• Choose the URL structure, ccTLD, subdomain, or subfolder, based on available budget and team, not just each model's theoretical geographic signal.
• Separate language and country only when a real difference in price, offer, or regulation justifies it, rather than multiplying versions without need.
• Keep hreflang consistent with each version's canonical tag, which must always point to itself and never to a redirect.
• Adapt price, currency, date format, and local contact details for each version, not just the visible text's language.
• Have a native speaker review each market's legal and product copy; an unreviewed machine translation is obvious to both users and Google.
• Pair each market with its own local SEO signals whenever the business has a physical or service presence in that country.
• Track each market's performance separately in Search Console, filtered by country and language, instead of only looking at the global aggregate.
• Plan 301 redirects ahead of time in case the chosen URL structure ever changes, to avoid losing the ranking each version has built up.

The most frequent failures in international SEO projects:

• Publishing a single English version for every English-speaking country, without adjusting prices in pounds, dollars, or euros or each market's tax rules.
• Translating the visible text but leaving the price, support phone number, or payment methods from the original market untouched, giving away that the version isn't really adapted.
• Creating country subfolders or subdomains with no content of their own, used only as a redirect, which Google can read as near-duplicate content between versions.
• Switching URL structure, say from subfolders to ccTLDs, without planning 301 redirects or updating hreflang, with the resulting loss of accumulated ranking.
• Multiplying country-language versions that add no real difference in offer, which splits the content and link budget without need.
• Assuming hreflang fixes weak content: the tag flags which version to show, it doesn't make up for a poor translation or a market with no real offer behind it.