SEO for International Sites: Choose Between Hreflang, Folders, and Separate Domains
Expanding into new markets means more than translating pages. Learn how to choose a site structure, target the right language and country audiences, and avoid common international SEO signals that confuse search engines.
For most site owners, the first decision is where international pages will live; the second is how to connect equivalent versions. Country domains, subfolders, and subdomains determine URL structure. Hreflang identifies language and regional alternatives. They are not competing solutions: you can use hreflang with any of these structures.
A practical starting point is a single domain with language or market subfolders when one team manages a shared business. Separate country domains become more attractive when local identity, operating independence, or market requirements justify their additional overhead. Before choosing either, establish whether you actually need separate country pages or simply translations.
Start with Your Markets, Languages, and Business Goals
A language is not a market. Spanish content might serve readers across several countries, while a Canadian store might need both English and French content. Country-specific pages are useful when the offer changes by location: availability, currency, delivery, taxes, support, or contractual terms. If those differences do not exist, one well-maintained language version may be more useful than multiple near-identical country sites.
Define the audience: which countries and languages can you support now, rather than eventually?
Define the transaction: can people in each market buy, subscribe, request a quote, or receive service?
Identify meaningful differences: note changes to products, pricing, delivery, terminology, regulations, and support.
Assign ownership: name the people responsible for translation, technical releases, local accuracy, and ongoing updates.
Set market-specific goals: choose relevant measures such as qualified inquiries, completed purchases, or useful organic visits.
Create a market-and-language matrix before designing URLs. For each intended version, record its audience, language, offer, URL location, owner, and launch priority. This exposes unnecessary duplication and operational gaps. A market without delivery coverage or local support is a business-readiness problem that URL architecture cannot solve.
Hypothetical example: a software company sells the same English-language subscription globally but offers a translated interface and documentation in German. English and German sections may be enough. Separate English pages for every country would add maintenance without necessarily improving the experience.
Compare Country Domains, Subfolders, and Subdomains
Choose a structure based on operating needs and the ability to maintain it, not on a promise of automatic ranking advantages. Each approach can support international search visibility. The important differences are geographic signaling, brand presentation, technical control, and the work required to maintain multiple destinations.
Country domains: strong local identity, more separate infrastructure
Country-code top-level domains, such as example.de or example.fr, provide a clear country association in many cases. They suit businesses with substantial local operations, distinct brands or catalogs, or a strong reason to present a local web address. Some country-code domains have registration restrictions, and search engines treat some as generic rather than country-specific, so verify the treatment of your chosen extension.
The tradeoff is separate domain management: registrations, certificates, monitoring, releases, redirects, and reporting all need attention. Earning recognition and links for one domain does not automatically establish the others. Country domains also do not solve multilingual targeting within a country; a Canadian domain may still need English and French sections.
Subfolders: a practical default for a shared operation
Subfolders such as example.com/de/ or example.com/en-gb/ keep international content on one domain. They often simplify shared navigation, analytics, technical maintenance, and internal linking. They are a strong starting point when the brand, platform, and content workflow are centrally managed.
Decide what each folder means before launch. Use /de/ for German-language content without a country-specific scope, or /de-de/ when the section specifically serves German speakers in Germany. Folder names are organizational choices, not a substitute for visible localization or hreflang. On a country-specific domain, folders for unrelated countries can also create conflicting geographic signals; a generic domain is usually a clearer home for a broad international site.
Subdomains: useful when technical separation matters
Subdomains such as de.example.com allow different hosting environments, application stacks, or publishing teams under the same parent brand. They can make sense when the main platform cannot support localized sections cleanly. However, they can complicate navigation, measurement, consent implementation, and release coordination. They are not inherently an SEO shortcut or penalty; choose them when the technical separation has a clear operational benefit.
Choose subfolders when one team runs a shared platform and needs a manageable expansion path.
Consider country domains when local positioning and independent operations justify separate domain investment.
Consider subdomains when platform constraints or deployment ownership require technical separation.
Keep an established, functional structure unless a migration solves a concrete problem. Changing URLs solely for a theoretical SEO advantage introduces avoidable risk.
Use Hreflang to Connect Equivalent Language and Country Pages
Hreflang helps supporting search engines understand which URLs are alternatives for different language or regional audiences. It can help them show a suitable version in search results, but it does not guarantee that a particular URL will appear. It does not translate content, replace localization, or prevent users in other countries from accessing a page.
Connect equivalent pages at page level. A French product page should reference its English counterpart, not the English homepage. If a product or article has no genuine equivalent in another market, leave that alternative out rather than connecting an unrelated destination.
Select language and region values deliberately
Use a supported language code, such as en for English or de for German.
Add a supported country code when a version targets a particular country, such as en-GB or de-CH. A country code alone is not valid.
Use en-GB rather than en-UK. Do not invent regional groupings such as en-EU to represent multiple countries.
Consider a language-only version when you have content intended for speakers outside your specifically targeted countries.
Use x-default for an appropriate fallback, such as a neutral market selector or a default page for audiences not otherwise matched.
Choose one maintainable implementation method
For Google, hreflang can be supplied through HTML link elements in the page head, HTTP Link headers, or XML sitemaps. HTML is often convenient for regular web pages; HTTP headers are useful for non-HTML files such as PDFs; sitemaps can suit large catalogs with a reliable central URL map. Using multiple methods is unnecessary and increases the chance that annotations disagree.
Each alternative should reference itself and the other relevant versions, with reciprocal references between them. Use complete absolute URLs, including the protocol and hostname. For a hypothetical product available in English for the United States, English for the United Kingdom, and French for France, each page should identify the same set of en-US, en-GB, and fr-FR alternatives, plus an appropriate x-default if used.
Keep canonicals and hreflang aligned
Canonical tags and hreflang answer different questions. A canonical identifies a preferred URL among duplicate or similar URLs; hreflang identifies localized alternatives. Distinct localized pages that should remain eligible for search will generally have self-referencing canonicals. Do not routinely canonicalize all translations to the original language page, because that asks search engines to consolidate pages you want treated as alternatives.
Hreflang is not a reliable fix for country pages that have no meaningful distinction. If regional versions are essentially identical, search engines may still consolidate them. Decide whether separate pages are necessary, then make the intended market differences useful and visible.
Hreflang destinations should be crawlable, indexable, canonical URLs that return successful responses. Avoid references to redirected URLs, error pages, blocked pages, or pages marked noindex. Search-engine support varies, so treat hreflang as one part of a broader localization system rather than a universal targeting mechanism.
Localize More Than the Words on the Page
Translation preserves meaning; localization makes the page usable for its intended audience. Begin with local search intent. People in different markets may use different product names, comparison criteria, units, or questions. Review local search language and results rather than assuming a literal translation of the original keyword will serve the same need.
Adapt titles, descriptions, headings, navigation, image text alternatives, and internal link labels—not just the main paragraph copy.
Show applicable currencies, payment options, product availability, delivery areas, and return conditions.
Use appropriate units, date formats, address fields, telephone formats, and writing direction.
Translate forms, validation messages, checkout steps, confirmation emails, and support information so the journey does not unexpectedly switch languages.
Review relevant legal notices, privacy information, and commercial terms with qualified local advisers where needed.
Keep structured data consistent with visible local content, especially price, currency, availability, and business details.
Use reviewers who understand the language and market, especially for technical, medical, financial, or legal content. Machine-assisted translation can be part of a workflow, but publishing without checks risks misleading terminology, broken formatting, and incorrect commercial information. Decide how changes to the source content will trigger updates across localized versions.
Make switching markets easy. Provide crawlable links with clear language or country labels, and preserve the equivalent page when a visitor switches versions. Avoid forcing users onto a different site solely because of their IP address or browser language. A dismissible suggestion lets travelers, multilingual users, and crawlers reach other versions without being trapped in a redirect loop.
Build an International SEO Launch and QA Checklist
Test a representative set of pages before rolling out the entire site: the homepage, a category, a product or service, an article, an unavailable item, and a page without a translated equivalent. Include every template and platform involved. A correct homepage implementation does not prove that product templates or sitemap generators work.
Before launch: confirm structure and content readiness
Approve the market-and-language matrix, URL conventions, and owners for every version.
Map equivalent pages using stable content or product identifiers rather than matching translated URL slugs.
Check localized copy, navigation, metadata, forms, currencies, availability, and support paths.
Confirm production domains, HTTPS, hosting, and access controls are ready; remove staging restrictions only where intended.
If replacing existing URLs, prepare direct permanent redirects from each old page to its closest relevant replacement and update internal links.
At launch: validate crawling, indexing, and annotations
Crawl every localized section and check response codes, redirect chains, broken links, robots directives, and canonical tags.
Confirm alternate URLs resolve directly to indexable pages and that any x-default destination is appropriate.
Ensure XML sitemaps contain intended canonical URLs and submit relevant sitemaps through available search-engine webmaster tools.
Test language and country switching on mobile and desktop, including users arriving directly on deep pages.
Check that location detection does not block crawlers or prevent visitors from accessing another version.
Verify analytics and conversion tracking across domains or subdomains where applicable, while respecting the site's consent setup.
After launch: diagnose market-specific problems
Monitor indexing, search impressions, clicks, landing pages, and business outcomes by market and language where the tools permit. Separate country from language: traffic from France does not prove a visitor wants French, and French content can attract readers elsewhere. New sections may take time to be crawled and understood; a lack of immediate traffic alone does not identify a technical fault.
If pages are not indexed, inspect accessibility, noindex directives, canonical selection, internal links, and content usefulness before blaming hreflang.
If the wrong regional page appears, review reciprocal annotations, canonical conflicts, page similarity, redirects, and visible market signals.
If visits arrive but users do not complete the task, check local availability, trust information, payment methods, and untranslated steps.
When adding, removing, or moving a page, update its alternate references and remove obsolete URLs from sitemaps and internal links.
Your next step is to build the market-and-language matrix and test one complete cluster of equivalent pages. Confirm that visitors can find, understand, and use each version before expanding the rollout. That small test will expose structural and workflow problems while they are still manageable.