How to Choose a URL Structure for International Websites

When a website serves people in more than one country or language, its URLs should help visitors find the right version and help site owners manage each one. A subdirectory places a version under the main domain, such as example.com/fr/. A subdomain places it before the main domain, such as fr.example.com.

For Google Search, neither structure has an inherent ranking advantage: Google says it has no preference between subdirectories and subdomains for indexing and ranking. Choose a structure your organization can maintain reliably. Give each important language or market a stable URL, and connect pages that have equivalent content with the right signals. The URL choice supports international SEO; it does not translate content or guarantee that Google will show the intended version.

Decide what each version represents

First decide whether each page serves speakers of a language, people in a country, or both. A French page for readers in France and a French page for readers in Canada share a language but serve different markets. They may need different prices, shipping details, contact information, or legal terms. A US English page and a UK English page share a language but may also need separate market details.

Use that distinction to choose the URL pattern. A language-based structure might use /fr/ and /en/. A market-based structure might use /fr-fr/, /fr-ca/, and /en-us/. These examples illustrate URL conventions; they do not set ranking rules. Choose a pattern that tells editors and visitors which audience each URL serves, then use it consistently.

Google describes a site that serves several languages as multilingual, one that targets different countries as multi-regional, and a site can be both. Its international site guidance explains the signals Google uses to understand those audiences.

Compare subdirectories, subdomains, and country domains

Google documents practical trade-offs among URL structures. Its guidance does not show that one structure ranks better than another.

Google says subdirectories are relatively easy to set up and maintain, but harder to separate from the rest of the site. Subdomains allow more separation and different server locations, but a label such as de might mean German or Germany. Country-code domains, such as .de, provide a strong country signal and clear separation, but require managing separate domains and target one country. These are documented operational trade-offs, not comparative performance results. See Google’s crawling and indexing FAQ and multi-regional site guidance.

For many organizations, a subdirectory is a sensible default when one publishing platform and one shared host meet their needs. Use a subdomain when the separation solves a real technical or operational need. Choose country domains when the country-specific identity and targeting justify the additional maintenance. Do not select a format on the promise that it will pass more ranking value.

Avoid using a query parameter, such as example.com?loc=de, as the main way to identify a language or market version. Google does not recommend this structure for targeting, and the URL gives visitors little context about the page they are opening.

Make every locale page accessible and clear

Give every language or market version its own stable URL. Google recommends separate URLs rather than changing page language based on a cookie or browser setting. Googlebot may not discover every variation of a page that depends on those settings. Automatic redirects based on a visitor’s location or guessed language can also hide versions from users and crawlers. Provide visible links to other locales, and let visitors choose where to go.

The URL itself does not establish a page’s language. Google uses the visible content to determine language; it does not use the URL or the HTML lang attribute for that purpose. A /fr/ path is useful for organizing pages, but the page’s main text should actually be in French. Localized prices and product availability should also match the market when they differ. The same applies to shipping terms and contact details.

For equivalent pages, use hreflang, an annotation that tells Google which language or regional versions correspond to one another. Google supports adding these references in page HTML. You can also add them in HTTP headers or XML sitemaps. Each page should reference itself and its relevant alternatives, and the references should work in both directions. Google’s localized-page documentation explains the supported formats and requirements.

Use hreflang to connect genuine alternatives, not to label every page on a site. Check that each referenced URL opens the intended page and that every alternate page returns the reference. If a page has no direct language or regional equivalent, do not invent one just to complete a set.

Check the implementation before launch

Test each URL as both a search crawler and a visitor would encounter it. Open each important URL for a language or market version without cookies or a location-specific connection. Confirm that it returns the intended content, that visitors can navigate to other versions, and that ordinary links lead to the pages. Google can crawl links when they use standard links with an href; its link guidance explains what to check.

Then review the signals that tell search engines which URL to use. Each page should have a canonical URL, the address search engines should treat as its preferred version. Keep the canonical consistent with the intended locale page. Do not point a genuinely distinct regional page to another market’s URL just because the text is similar. If near-identical pages serve the same audience, choose which URL search engines should prefer. Make the canonical and alternate-language signals point to that choice consistently.

Inspect the page’s server response and redirects as well. A URL for a language or market version cannot serve its purpose if it redirects to the wrong market, returns an error, or blocks crawlers. A sitemap can help search engines discover URLs, but it does not guarantee that they will crawl or index them. After launch, use your reporting tools to review crawling, indexing, and search traffic for each group of language or market URLs, or for each host.

Avoid failures that obscure the intended market

A common mistake is treating the locale code as the whole SEO strategy. A /de/ path does not tell Google whether a page targets German speakers generally or a particular country. Make the audience clear through the content and relevant local details, and connect alternate pages appropriately.

Another failure is publishing many nearly identical market URLs without a clear reason. Separate pages make sense when the markets need different information or service terms. When they do not, extra URLs create more pages to maintain and can make it harder to identify the version that should appear. Google’s URL structure guidance recommends logical, descriptive URLs and warns that unnecessarily complex URL spaces can make crawling and indexing harder.

Changing an established domain, hostname, or directory pattern also requires migration work. Map each old URL to the relevant new address. Update internal links and sitemaps, and check the redirects and canonical URLs. Google’s site-move guidance describes the steps for URL changes and notes that search visibility can fluctuate during a move. Avoid restructuring solely to pursue an unproven ranking advantage.

What the evidence means for SEO and AI search

Google’s published guidance points to a practical choice: use the structure that fits your operating needs. Google does not state that subdirectories or subdomains rank better. The guidance describes signals and implementation practices, not guaranteed ranking gains. It also does not establish that every search engine treats these structures identically.

The same restraint applies to AI search. Google says its AI search features use existing Search systems, and a page must be indexed and eligible to appear with a Search snippet to be considered for those features. Its guidance for generative AI features does not identify subdomains, subdirectories, or country domains as special advantages. Keep locale pages accessible, useful, and technically clear; a URL structure alone does not guarantee an AI citation or appearance.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com