International SEO: design multilingual websites for real markets

A multilingual site does not become international when it adds a language selector. International SEO requires market choices, local research, technical architecture and an editorial process capable of maintaining consistent pages, products and geographical signals over time.

Translate all pages can be expensive and produce sections without question. The starting point is to decide where the company can really serve users and customers, what offers are relevant and how the research intention changes in each country.

Multilanguage and multiregional: two different problems

A multilingual site offers content in multiple languages. A multiregional site distinguishes markets that can share the same language but have different memberships, currencies, regulations or messages. A project can be both.

The distinction guides hreflang codes, URL structure and content. en indicates English without a specific country; en-GB and en-US describe regional variants. Using country codes alone or inventing combinations makes annotations invalid.

Choose markets before languages

Priority should combine demand potential and operational capacity. Before opening a new section you must check:

1. products or services actually available;
2. shipment, assistance, payments and commercial conditions;
3. terminology and local competition;
4. legal, tax or sector constraints;
5. resources for translation, revision and updating;
6. possibility to manage leads and customers in the promised language.

An incomplete or unmaintained section can create more friction than opportunity. It is often preferable to start from a market and a group of priority pages, measure them and expand gradually.

Keyword research by country: translating is not equivalent to seeking

The same requirement can be expressed in different terms, and a correct translation on the linguistic level may not coincide with the query used. They also change dominant brands, perceived categories, units of measurement and market maturity.

The search should be carried out in the local language by observing SERP, suggestions, competing sites, Search Console and commercial data. A native speaker with knowledge of the sector helps to distinguish natural terms from formally correct but unused formulations.

Not all Italian keywords must have an equivalent page. The map must be reconstructed by market, maintaining a clear editorial relationship between really corresponding versions.

Architecture URL: ccTLD, subdomains or subfolders

The main options are national domains, subdomains and subfolders. No one is universally better.

National domains

They offer a clear geographical signal and can support a local identity, but require more technical, legal and editorial management. Authorities and maintenance are distributed among several properties.

Subdomain

They allow separate infrastructure and responsibilities, useful in complex organizations. They require consistent control of linking, analytics and technical configuration.

Subfolders

They concentrate the project on a domain and simplify management and measurement often. They must have distinct and navigable URLs for each language, such as /it/ or /en/.

The choice depends on market, governance, platform, brand and resources. Changing architecture later involves migrations and redirects: it should be decided with a medium-term perspective.

Hreflang: mutual relationship between equivalent pages

Hreflang tells Google the language or regional versions of the same page. Each version must list itself and other variants; references must be reciprocated and use valid absolute URLs. x-default can indicate the fallback page when no language matches.

The implementation can take place in HTML, HTTP headers or sitemaps. Using all methods together does not offer an automatic advantage and increases control work. The best choice is that the team manages to maintain without inconsistencies.

Hreflang does not translate the page, does not guarantee indexing and does not replace a correct canonical. It is a record between URLs that need to be accessible, indexable and really localized.

Canonical and hreflang are not interchangeable

The canonical identifies the preferred version between duplicated or very similar URLs; hreflang associates language or regional variants. Typically an indexable localized page uses an authoritative canonical and participates in the hreflang cluster.

Canonicalizing all languages to the Italian version can make the local pages lose. Similarly, hreflang towards redirected URLs, in noindex or canonical elsewhere produces inconsistent signals.

Sitemap, crawling and navigation

Each language must be reached through HTML links, not only after automatic location or browser detection. Googlebot often requests from the United States and without specific language headings; IP-based rigid redirects can hide variants.

Sitemaps must include canonical and published URLs. When hreflang is run in sitemap, each URL lists all cluster variants. The control must look for missing pages, wrong codes, unreciprocal returns, redirects and different answers from 200.

Localization of content

Localization means adapting examples, terminology, currency, measures, tests, conditions and CTA. A service page can maintain the same strategic structure but change topics according to the market. For an ecommerce often change assortment, availability and delivery expectations.

The SEO for ecommerce requires special attention to categories, filters and product data; in international markets these elements must remain consistent with local currency, availability and feed.

For technical catalogues, the guide on Industrial SEO deepens terminology, PDF and specification, elements that cannot be translated without revision of sector.

Recurring technical problems

1. a single URL that changes language through cookies or JavaScript;
2. automatic redirects that prevent market change;
3. hreflang does not reciprocate or with invalid codes;
4. canonical towards a different language;
5. translated pages but in noindex or absent from the sitemap;
6. menu and internal links pointing to the wrong language;
7. partial translations of templates, metadata or structured data;
8. Local URLs that return Italian content by mistake.

Search Console and measurement by market

You need to separate country, language, directory and page type. Impressions and clicks indicate if Google exposes the expected version; analytics and CRM show if users and leads belong to target markets.

Useful questions are: what queries only emerge locally? What versions receive traffic from the wrong country? Where is the CTR weak for unlocalized titles? What landings generate requests that the company can serve?

AI search adds another level: responses can vary by language, location and available sources. Monitoring should then use local and repeated prompts, without extending the results of a market to all others.

International Expansion Roadmap

1. Select sustainable markets and priority offers.
2. Rebuild queries, intent and competition by country.
3. Choose URL architecture and editorial governance.
4. Locate key pages before expanding the volume.
5. Implement canonical, hreflang, sitemap and links.
6. Verify 200 response, indexability and consistency of templates.
7. Measure visibility, lead and commercial quality by market.
8. Update pages and annotations along with catalog and offer.

One SEO advice can help transform these decisions into a verifiable technical and editorial plan, avoiding that internationalization becomes a simple duplication of the site.